I'd be very interested in seeing your sharedcombobox, though I'm not sure if
it would help in my situation.

Our app is essentially a giant dynamic form.  All the data is posted to a
servlet that processes the data and returns results in XML.

The problem is that I have a class "FOO" which contains 8 comboboxes, and
the user can add 1 to 6 instances of this class to the form.

On another page, I have a class "BAR" which contains 8 comboboxes, and the
user can add 1 to 4 instances of this class to the form.

For performance reasons, we "pre-create" all instances of the classes, then
hide them until the user clicks the "Add" button.  We tried creating
instances on demand and it was just too slow.

Many of the comboboxes are simply YES/NO choices so maybe they might be a
candidate for your sharedcombobox.

Because of the design of our app all "FOO" and "BAR" instances have to be
visible at all times so I don't think your second suggestion can be
implemented in our app.




-----Original Message-----
From: Garth Smedley [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 23, 2006 5:27 PM
To: Laszlo-User
Subject: Re: [Laszlo-user] combo box bloat == 100 meg laszlo app



Hi William,

We ran into a similar problem with dynamically updated comboboxes and
ended up doing two things:

- We made a sharedcombobox which allowed all comboboxes with the same
content to share a common underlying combobox. This is an incomplete
class but I'd be willing to share it.

- We changed our UI so that instead of showing all the comboboxes at the
same time we show only those for the selected row. Even with the
sharedcombobox, putting more than 10-20 comboboxes on a page was too slow.


Regards,

Garth

William Krick wrote:
> I'm working on an OpenLaszlo application that has a lot of controls for
data
> input.
>
> When I load our app up in a browser and check the memory use for that
> browser instance in task manager, it's around 100 megs.
>
> Obviously this is WAY too large and something has to be done to bring the
> size down.
>
> After some digging, it appears that the majority of our apps memory use is
> due to combo boxes.  LOTS of comboboxes.
>
> The combobox is critical to our application so we need a solution that
> brings the memory use for comboboxes way down.
>
> Also, a side effect of this bloat is that anything that dynamically
> manipulates the contents of a combobox like adding or removing items, or
> refreshing the list when connected to a dataset, is unusably slow in our
> application.
>
> I know there was some work done on a "newcombobox" but it appears that
that
> might have been abandoned in favor of the "datacombobox" which doesn't
> really address the bloat problem.
>
> Can anyone tell me what, if anything, can be done to remedy our situation?
>
> My co-worker is putting together and will post an example that
specifically
> addresses the performance problems when manipulating comboboxes but I just
> wanted to query the list about a solution to the larger problem of
> application bloat due to comboboxes.
>
> Is it possible to strip down the combobox and/or textlistitem to make them
> less memory hungry?
>
> ...
> Krick
>
> _______________________________________________
> Laszlo-user mailing list
> [email protected]
> http://www.openlaszlo.org/mailman/listinfo/laszlo-user
>
>
>
_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user


_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to