Works for me, thank you!
Derrell Lipman schrieb:
> On 8/4/07, Derrell Lipman <[EMAIL PROTECTED]> wrote:
>
>> On 8/4/07, bibliograph <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Could I convince you?
>>>
>> Good enough. :-) Your request and explanation look completely rational.
>>
>> Woul
Hello,
Im looking through the 0.7-API and believe you currently need to set each
column individually and loop over each column? Perhaps a good addition would
be a setRowData(row, data) for tables. Pass it an array and it will
overwrite the entire row.
Eg: Currently:
for (var i = 1; i < tableMo
Uggh. I hate it when I do that. Here's the previously missing patch...
Derrell
On 8/4/07, Derrell Lipman <[EMAIL PROTECTED]> wrote:
> On 8/4/07, bibliograph <[EMAIL PROTECTED]> wrote:
>
> > Could I convince you?
>
> Good enough. :-) Your request and explanation look completely rational.
>
> W
On 8/4/07, bibliograph <[EMAIL PROTECTED]> wrote:
> Could I convince you?
Good enough. :-) Your request and explanation look completely rational.
Would you please try this attached patch before I check it in. You'll
note that I made a few additional changes:
1. Instead of assuming that the e
Brendon Eich of Mozilla, claimed many times at TAE that FireFox 3 will have
the Tamarin engine in it (it's possible that the current alpha does not have
it in yet) and it will have about a 10X increase in speed. It is a JIT
compiler for JavaScript developed by Adobe. I have also read other articles
I haven't yet found an easy guide to building firefox in visualstudio, else i
might profile it to see what would need work to speedup qooxdoo.
-Original Message-
From: Sebastian Werner [mailto:[EMAIL PROTECTED]
Sent: Sun 5-8-2007 0:06
To: qooxdoo Development
Subject: Re: [qooxdoo-devel]
Derrell wrote:
> Yes, there are disadvantages as well as advantages to the virtual
> table. The time must be spent rendering at some point. That means it
> must be done either before the whole page is displayed (traditional
> table) or as you scroll (virtual table). The rendering speed is
> *gr
-Original Message-
Sent: Sat 4-8-2007 20:38
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] qx.ui.table.Table with (too) many columns
> Good luck. I have found it hard to fight others that think web applications
> should have the exact same speed as native desktop apps. They current
Hi Jim.
Do you mean that Firefox3 is 10% or 10X faster? Just curious. For me
Firefox 3 is comparable in speed to Firefox 2. Nothing to beat Webkit
for now.
Sebastian
Am 04.08.2007 um 20:38 schrieb Jim Hunter:
Good luck. I have found it hard to fight others that think web
applications
On 8/2/07, Bart van der Werf <[EMAIL PROTECTED]> wrote:
>
>
> only short strings all data is formatted on the serverside
>
> the base data has about 120 columns, but we're bringing it down to 10-20
> ish, but this still makes qx sluggish
>
> about 2 rows, but we're using blocks so only about 20
Good luck. I have found it hard to fight others that think web applications
should have the exact same speed as native desktop apps. They currently are
slower, and there is nothing you can do about that. There are limitations in
what JavaScript in a browser can do and how fast it can be done. FireF
wrong link in my last message
bibliograph schrieb:
> I need to include a few helper functions BEFORE the classes are
> included. See the files here:
>
http://qxtransformer.svn.sourceforge.net/svnroot/qxtransformer/trunk/apps/applications/staffscheduler/backend/php/lib/tools/
> - one file dea
Hi Derrel,
I am just working on extending the PHP backend. You can see the current
(unstable) code here:
http://qxtransformer.svn.sourceforge.net/svnroot/qxtransformer/trunk/apps/applications/staffscheduler/backend/php/
I need to include a few helper functions BEFORE the classes are
included.
On 8/4/07, bibliograph <[EMAIL PROTECTED]> wrote:
> can I ask you to include the following snippet in your backend?
>
> /*
> * This is a simple JSON-RPC server. We receive a service name in
> * dot-separated path format and expect to find the class containing the
> * service in a file of the se
Hi everybody,
I've got a table placed in a qx.ui.layout.CanvasLayout. The CanvasLayout is
inside a page of a ButtonView. What I get is that the table is drawn without
borders. Just columns and rows, no borders except the bottom one that
separates table data from status bar. Do you have any idea wh
Hi Derrell,
can I ask you to include the following snippet in your backend?
/*
* This is a simple JSON-RPC server. We receive a service name in
* dot-separated path format and expect to find the class containing the
* service in a file of the service name (with dots converted to slashes and
Hi,
I am maintaining the qx.event.message package and am thinking about
making it compatible to the newly announced Tibco Page Bus syntax (while
keeping backwards compatibility).
http://www.tibco.com/devnet/pagebus/default.jsp
One could also think about passing the qooxdoo-internal messages to
It is 300ms per scroll action, regardless if it is 1 row or a pagedown, so if
you are using a cursor to step down thorugh a table it is near unworkable.
I agree that the bottleneck seems to be in te browser not javascript.
well it should be near instantaneous, 600 cells isn't really that much da
300 ms to do a page down (20 columns x 30 rows = 600 cells, is a full page
not a row scroll) is not that slow. Are you thinking that displaying that
much data should be instantaneous? That's not going to happen with any of
the toolkits. I have evaluated them all and this is one of the fastest grids
19 matches
Mail list logo
