Definitely use a pool. The creation of new widgets is very cost-y.
The general recommendation, If you can, is always reuse widgets.
On Wed, Mar 9, 2011 at 5:54 PM, John de la Garza wrote:
> I have a tabView with a page that has several progress bars
>
> I have a timer that runs every two seconds
I have a tabView with a page that has several progress bars
I have a timer that runs every two seconds and gets data via rpc to
update the prg bars
sometimes I'll have new prog bars, some will be removed, and others only updated
I'm wondering if I should destroy the qx.ui.indicator.ProgressBa
Thanks, i put it there deliberatly to test your bug hunting skills
honest!
The icon and title don't tend to be dynamic which is why this wasn't
picked up until now. I'm looking forward to having this as a contrib so
other people can pick up on my delibrate mistakes (still waiting for an
e-
Hi Matthew,
only one think :)
In your code you should add 'icon' property and your title property
sets property to wrong widget (this._description).
Only needed to modify this:
_applyIcon : function(value)
{
this._icon.setSource(value);
},
_applyTitle : function(value)
Jean-Baptiste BRIAUD - Novlog schrieb:
> It worked and is very usefull.
> Thanks a lot !
>
> As a future optimisation, I was wondering if we could improve the way
> to add data :
>
>> for (var i = 0; i < 10; i++) {
>> ...
>> list.add(item);
>> }
>>
> I'm guessing (I'm new to qooXdoo) but
Andreas Ecker wrote:
> Matt, what exactly is the "scrolling bug"?
The list is a scrolling widget with a composite container containing all
of the children. With a VBox layout (for example) it can add up all of
the height of the children to find out the what the height of the
container should be
Hi Chris,
Thanks!
Yes, AFAIK getWidthForHeight is not called in 0.8 but will be in 0.8.1
which is the cause of the bug.
Chris Banford wrote:
> Hi Matt,
>
> Your TileView looks rather nice! :-)
>
> I'm wondering if the scrolling bug you mention would be that the Flow
> Layout doesn't support h
It worked and is very usefull.
Thanks a lot !
As a future optimisation, I was wondering if we could improve the way
to add data :
> for (var i = 0; i < 10; i++) {
> ...
> list.add(item);
> }
I'm guessing (I'm new to qooXdoo) but adding an element inside the
loop will probably launch the rende
Thanks for sharing this !
This is really useful code and I'm looking forward to use it
Cheers
- Petr
2008/10/2 Jean-Baptiste BRIAUD - Novlog <[EMAIL PROTECTED]>:
> TileView works fine in 0.8.
> TileView would certainly be a cool contrib !
>
> +1 for TileView as a contrib.
>
> I'm not using ListV
TileView works fine in 0.8.
TileView would certainly be a cool contrib !
+1 for TileView as a contrib.
I'm not using ListView and apparently, Table is better, so ... I don't
see any interest in ListView right now.
On 2 Oct 2008, at 11:42, Matthew Gregory wrote:
> Thanks,
> I'll send you an e-
Thanks,
I'll send you an e-mail shortly.
To all: Is there anybody else who might be interested in this?
Andreas Ecker wrote:
> Hi Matt!
>
>> Andreas Ecker: I think your the maintainer of the listview in contrib.
>> The listview control in windows has the tile view built in. Would it be
>> wort
Chris Banford schrieb:
> Hi Matt,
>
> Your TileView looks rather nice! :-)
>
> I'm wondering if the scrolling bug you mention would be that the Flow
> Layout doesn't support height to width yet?
>
> Andreas (hope vacation was a good one!), any idea when support for
> this in Layouts will see the
Howdy!
> I'm wondering if the scrolling bug you mention would be that the Flow
> Layout doesn't support height to width yet?
Matt, what exactly is the "scrolling bug"?
> Andreas (hope vacation was a good one!)
Yeah, but too short, you all know...
> any idea when support for this in Layouts will
Suppose I should also give an example of how to use it ;)
var list = new custom.ui.comps.TileView();
this.add(list); // assuming your layout will size this
for (var i = 0; i < 10; i++)
{
var item = new custom.ui.comps.TileViewItem("File " + i + ".png",
"custom/icon/48/file.png", "png file", "
Hi,
(assumung you're using 0.8)
I've written something similar to this. My basic idea is to use
qx.ui.form.list with a few modifications, mainly using a flowlayout
(you'll have to get this from qooxdoo-contrib).
Here are a couple of classes for this which are still work in progress.
This is cu
Hi,
I'm coding a window that will show files (like Finder of Windows file
system explorer).
The current version use a table, each line is a file and column show
file attributes (could be size, ...).
This is like the details view on Windows OS.
I would like to have another view with icon inst
"Christian Boulanger" <[EMAIL PROTECTED]> writes:
> Hi Derrell,
>
> I was curious before to know what the fsm is for and what it does. Can you
> describe it in a few words (or even write a little tutorial?).
Christian, yes, I'll try to write some sort of tutorial or write-up
about the finite stat
Hi Derrell,
I was curious before to know what the fsm is for and what it does. Can you
describe it in a few words (or even write a little tutorial?).
Thanks,
Christian
> "Steve Ramage" <[EMAIL PROTECTED]> writes:
>
>> Okay my next question would be a generic design question. Lets say I was
>> d
"Steve Ramage" <[EMAIL PROTECTED]> writes:
> Okay my next question would be a generic design question. Lets say I was
> developing an IM application with Qooxdoo. So I would have a chat window but
> it would be possible to have more than one chat window open at time. How
> using Qooxdoo would I ke
Okay my next question would be a generic design question. Lets say I was
developing an IM application with Qooxdoo. So I would have a chat window but
it would be possible to have more than one chat window open at time. How
using Qooxdoo would I keep track of them?
So lets say I have on each window
Ok. I solved this by making a singleton class of mainpackage.
I don't really get it. My code has the "namespaces" structure like:
mainpackage
-dialog1(mainpackage.dialog1 class)
-dialog2(mainpackage.dialog1 class)
and all dialogs are attached to one container in the mainpac
I don't really get it. My code has the "namespaces" structure like:
mainpackage
-dialog1(mainpackage.dialog1 class)
-dialog2(mainpackage.dialog1 class)
and all dialogs are attached to one container in the mainpackage. So
all instances of the classes are known only in the mainpac
All my dialog code is at the top most level and the parent of the dialog is the outter most container. It works quite well.JimOn 11/13/06, Alex D.
<[EMAIL PROTECTED]> wrote:
Hi list,
i have a design problem here: my app. has look&feel of the typical
Windows MDI-Application. You have menub
Hi list,
i have a design problem here: my app. has look&feel of the typical
Windows MDI-Application. You have menubar and toolbar at the top, and
some kind of "container"-box in the middle where all dialog-windows
appear. So the container-class has all the pointer(variables) at the
dialog-wind
24 matches
Mail list logo