Toufeeq,
I'm still uncertain of is how the user selects what widgets he/she wants
displayed in the main window. Also once the user makes the selection, where
are those stored? You could do the following if an lzx file is built with
the user's widget selections:
-----main.lzx-----
<canvas debug=\"true\">
<window width=\"400\" height=\"300\">
<include href="user-widgets.xml" />
</window>
</canvas>
-----user-widgets.xml-----
<class name="child_window" extends="window" height="30" width="40">
<text>BLAH</text>
</class>
<child_window />
This way you could just import code into the main window, as long as the
file "user-widgets.xml" was generated dynamically.
-Anthony Bargnesi
On Feb 12, 2008 11:35 PM, Toufeeq Hussain <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 2/12/08, Anthony Bargnesi <[EMAIL PROTECTED]> wrote:
> Toufeeq,
> >
> > I\\\\\\\'m not sure why you would want to dynamically read a library to
> display instances of a window. You said that
> > you will pull this information at runtime, then why not just use
> datasets.
>
> The reason why I\'m using datasets for window-data is because each
> window might have a different set of controls associated with each.
> That is defined in the imported library. What I\'m trying to do is
> something like widgets which are displayed in a main window. The
> number of widgets are unknown when I writing the main-window but are
> instantiated based on what the user has selected.
>
> If the user has selected widget 1,4,5 (for example) the information is
> pulled in to a dataset and based on the selected widgets the
> corresponding widgets are instantiated.
>
> I guess with the above requirement I can go with a \"hard-coded\"
> windowing approach as the controls which make up each child-window are
> unknown.
>
> Hope I\'m clear on the requirement.
>
> Regards,
> Toufeeq
>
