Another way could simply be to pass a URL parameter that toggles the
ID-generation on, much in the same way the gwt.codesvr parameter toggles
dev mode instead of running the compiled version of the app.
On 09/01/2010 05:03 PM, Joseph Marques wrote:
Why not just create a boolean in the entry point class (CoreGUI)
and
have a method of toggling this (either a hidden config page or global
keypress listener). Then the selenium utility checks the state of this
variable, and creates ID-aware (or ID-less) components accordingly.
On 09/01/2010 04:33 PM, Jay Shaughnessy wrote:
> I've been working on adding Selenium integration into the SmartGWT-based
> CoreGUI. This involves adding a lot of explicit ID assignment to the
> widgets. The explicit ID's aren't necessary for general use but are
> critical for automation testing. Enabling the ID generation is also
> useful during GUI development as a means of identifying DOM "leaks" and
> errant rendering paths.
>
> So, I want to have the ID generation off by default but easily enabled
> with a startup property or option. Does anyone know a good way to do
> this with SmartGWT? Today it's a compile time boolean setting, and
> turned off in Master.
>
> Jay
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel