You are right, custom UI object may not be the right way.

Could these elements be defined and used separately? I mean using
Tellurium
widgets so that each widget has its own UI definition and functions,
i.e., methods.
If you can use widget, it will significantly reduce your UI definition
and make your
UI more modularized. But the downside is that the widget must be a
relatively static
piece of UI, i.e., you can change some parameters, but not the whole
structure.
That is why we create special widgets for Javascript frameworks such
as DOJO,
because the widgets for a framework are pretty static.

If it is not the case, i.e., the UI elements have to be part of other
UI elements so as
to be treated as a meaningful piece, then, what we need is very much
like Macros in C/C++,
which require some pre-processing. If this is really valuable, sure,
we can pursue
in this direction.

Thanks,

Jian


On Feb 27, 7:09 am, dominicm <[email protected]> wrote:
> Hi,
>
> Throughout our site code there are repetitions of certain elements
>
> e.g.
> Div(uid:'div', clocator:[id:'%%_divId'])
> InputBox(uid:'input', clocator:[id:'%%inputId])
> RadioButton(.... and so on for about 12 elements
>
> This particular set of elements occurs in multiple tables with some
> minor differences, and is causing some of my UI definitions to become
> very long and repetetive.
>
> What I would like to do is:
> 1. Create a base class for this set of elements
> 2. Be able to extend it to include extra elements
>
> What would be the best way to go about this? I've looked at the custom
> UI object code but cannot see how I could use this functionality to do
> what I need to do.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tellurium-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/tellurium-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to