#XOJO WEBLISTBOX PRO#

Usually I only want to load 10 or 20 thousand rows.

My thoughts… 45 seconds is not unreasonable. The general consensus is that it’s “unreasonable” to do so. I’d be amazed if you could load up 3.5 million rows with nine columns into a XOJO listbox in a reasonable amount of time (if at all). That said…I compare it to the local compiled XOJO app and find the regular listbox a bit on the pokey side also…though it does offer quite a few features and it takes a while to set all those individual cell properties I’m sure. Still I’ve been a little disappointed that the performance of loading up a web listbox does not seem to be constrained by the data transport…rather by the process the framework uses to load the data into and render the control seems abnormally sluggish. The web listbox control is constrained to the browser after all. I built a listbox and pagination control that allows me to move back and forth though a file a configurable number of rows at a time (100, 250, 500, 1000) …or jump to any position in the rows set. Oh yes…for the web (which is this thread after all) I don’t recommend sending back too many rows. This puppy could load up 10,000 rows in a blink. As soon as I open a different table it dropped all the memory and then grew based on the size of the new table. Sure…it went up by enough where I assume they sucked the whole table into memory (about 150 MB)…but that’s what I expected. I was watching the memory pressure when this large grid opened. Ok…so does anyone really need 3.5 meeeelion rows in a grid? Not generally…but our tech ought to be able to handle it. To implement in the MouseUp event, you must provide the X and Y parameters for where the menu should appear.

#XOJO WEBLISTBOX PRO#

Yowza! BIg Iron? Nope… Macbook Pro 1.53 GHz Intel Core 2 Duo with 4 GB Ram. The resulting scroll window worked incredibly smooth and scrolled like greased lightning. It did so without complaining…and only took 45 seconds (during which I got a nice progress meter).

Then I asked it to open a table with 3,627,006 rows (each row has nine fields…nothing too complex…but a reasonable amount of data per record. I opened up a 1.77GB database file in a flash (it displays all the table names and their record counts), which is probably easy enough because I’m sure all that info is simply part of the MDB file structure. What good are all these CPU cycles and gigabytes of Ram if I can’t do something so “simple” as open and view (scrub through) a large delimited file. My thought has always been…if I need to load up a small (in some cases 50MB) delimited file to just view a a delimited file in something besides “TextEdit” there ought to be a way to do it. One that could handle “lots of rows” without going ape.

Ok…this is far and away from “Web” - but I’ve been looking for a real high performance listbox for a while.

Xojo weblistbox