to try and investigate further.. I have played OxInline a bit more..
moving the containing dom node works fine.. menu items will come up in
the right place.. unless the page has scrolled. So it looks like the
rendering does not take into account possible page scroll.. if that
were added than at lea
I have tried 2 things to try to provide a more "web page" like app:
1 - using QxInline, and overriding the body scroll style stuff with
This almost worked, but menus and comboboxes in inline components that
may move as a page is scrolled are problematic.. the drop down part on
both will occur at
Ok, now I seem to understand your position better.
Thanks.
Sebastian
J. Russell Smyth schrieb:
Sebastian,
Thank you for taking the time to reply, and clarify.
I do understand that Qooxdoo is not 100% feature complete, and if we
do adopt it we would be more than willing to assist in thi
Sebastian,
Thank you for taking the time to reply, and clarify.
I do understand that Qooxdoo is not 100% feature complete, and if we
do adopt it we would be more than willing to assist in this effort -
the point being we have consisdered writing a similar tool ourselves,
and feel if we can fi
Kent Olsson schrieb:
Hej Sebastian!
Hej (I like this, a bit IKEA style ;)) Kent,
I am dealing with a problem with the layout mechanism of the QxSplitPane
and maybe you could give some ideas or advices.
So far I have let the QxSplitPaneLayoutImpl inherit from QxLayoutImpl.
It seems to work s
Kent Olsson schrieb:
Dear Russel,
I do agree on what you say and I have got the same response a few times
the last few days, also from Sebastian. I am not happy with that either.
I interpreted it as a mis-attitude and I was very sorry about that.
So far I have looked at it mainly as a language-
Hej Sebastian!
I am dealing with a problem with the layout mechanism of the QxSplitPane
and maybe you could give some ideas or advices.
So far I have let the QxSplitPaneLayoutImpl inherit from QxLayoutImpl.
It seems to work so so right now. The problem is the bar in between the
two components div
Sometimes a language barrier (i'm not talking code) can cause these kinds
of misunderstandings. English can sound a bit blunt if it's not someone's
first language, but if you strip down Sebastian's response it was fairly
straight-forward.
Izaak
On Fri, 06 Jan 2006 10:36:45 -0500, J. Russe
Dear Russel,
I do agree on what you say and I have got the same response a few times
the last few days, also from Sebastian. I am not happy with that either.
I interpreted it as a mis-attitude and I was very sorry about that.
So far I have looked at it mainly as a language-barrier problem/mistake
J. Russell Smyth schrieb:
from the FAQ:
"Is it possible to mix widgets with plain html? i.e. using menus and
toolbars over an existing page?
Yes, it is. Please have a look at the Examples which uses the QxInline
object. qooxdoo has some dependecies on css and html doctype which
need to be satis
J. Russell Smyth schrieb:
Wow, I have to say that this is a suprisingly unfriendly respnonse.
You asked me if we were using release or renderer, and this was my
answer. I say suprisingly unfriendly because I have been following
this list for quite some time and have not seen such a response
befo
I am sorry.. apparently there was something wrong with my text
search.. I found the example.
Apologies!
Russell
On 1/6/06, J. Russell Smyth <[EMAIL PROTECTED]> wrote:
> from the FAQ:
>
> "Is it possible to mix widgets with plain html? i.e. using menus and
> toolbars over an existing page?
>
> Yes
from the FAQ:
"Is it possible to mix widgets with plain html? i.e. using menus and
toolbars over an existing page?
Yes, it is. Please have a look at the Examples which uses the QxInline
object. qooxdoo has some dependecies on css and html doctype which
need to be satisfied."
I find no such examp
Wow, I have to say that this is a suprisingly unfriendly respnonse.
You asked me if we were using release or renderer, and this was my
answer. I say suprisingly unfriendly because I have been following
this list for quite some time and have not seen such a response
before.
I fully understand it i
J. Russell Smyth schrieb:
Another basic question, that is not readily apparent from the demos..
Is it possible to use Qooxdoo to create "web page" like apps, using
web page layout symantics, etc? so that as you add more the page can
scroll vertically?
Do the layouts respect their contents mins,
J. Russell Smyth schrieb:
Is there any work being done to create a TreeTable like component for
Qooxdoo? This is a primary component of our interface and if it does
not exist or is not in progress already for Qooxdoo, I may have to
take a stab at implementing myself.
With TreeTable you means so
...that I am working currently on the new appearance handling. Not that
you wondering why the CVS stands so still the last days. (Ok I was at
holiday some days, too).
The general API looks good. So I started to update some widgets to use
the new stuff. Here a short overview of the progress:
How Can I attach additional data to QxTreeFolder/QxTreeFiles?
I want to have one string for the display label and have another string
"stored" with the tree node for later use.
--
Jason J. Kahler
Software Engineer
BAE Systems
428 Phoenix Drive
Griffiss Business and Technology Park
Rome, NY 13
Kent Olsson schrieb:
THe question is how much a GUI like Qooxdoo is going to do. I guess it
would be better to let the server do this, and provide an interface for
AJAX here instead. At least for me it would be the choice.
That was what I meant with "move the sort handling to the server". :)
S
THe question is how much a GUI like Qooxdoo is going to do. I guess it
would be better to let the server do this, and provide an interface for
AJAX here instead. At least for me it would be the choice.
Kent
On Fri, 2006-01-06 at 11:46 +0100, Sebastian Werner wrote:
> Kent Olsson schrieb:
> > What
Well, I thought this list was open for discussion when it comes to these
issues.
;)
Kent
On Fri, 2006-01-06 at 11:48 +0100, Sebastian Werner wrote:
> sorry Kent, this was mainly an answer to J. Russell Smyth mail not to yours.
>
> Sebastian
>
>
> Sebastian Werner schrieb:
> > Kent Olsson schri
J. Russell Smyth schrieb:
Renderer. this would have to be our target if we were to use Qooxdoo,
for performance and advanced features, and we do not have the
opportunity to do a major rewrite just after adopting a new tool.
I am sorry. But this is not our problem. qooxdoo is currently at versio
sorry Kent, this was mainly an answer to J. Russell Smyth mail not to yours.
Sebastian
Sebastian Werner schrieb:
Kent Olsson schrieb:
What sort algorithm are we using here? Can it be optimized?
The "sort" use the native javascript sort. If it is slow for 10k entries
it is always slow. Gene
Kent Olsson schrieb:
What sort algorithm are we using here? Can it be optimized?
The "sort" use the native javascript sort. If it is slow for 10k entries
it is always slow. Generally IE performs bad on these actions - this is
already well known and nothing need to be discussed again.
You ca
Izaak Branderhorst schrieb:
Yeah on second thought (sent that email a bit too quick :P) it does seem
like a bit of a quick sketch and they should probably be implemented as
TYPEOF_OBJECT to allow for more complexity. For example, a validator
should have pairs of regexp -> appropriate error mess
Izaak Branderhorst schrieb:
The below is exactly the same as QxTextField.isValid () except it passes
the 'computedValue' rather than the 'value' to the validator. I found
this method useful for validating a form on every input event, allowing
an action like the submit button being enabled only
Izaak Branderhorst schrieb:
This results in the default value being null, when it should be ''
(empty string).
I noticed this because a createRegExpValidator () validator was choking
on the null value.
Changed behaviour in CVS. Hope this helps.
Sebastian
Izaak
-
Fixed in CVS.
Izaak Branderhorst schrieb:
In QxTextField.js:
//
QxTextField.addProperty({ name : "validator", type :
QxConst.TYPEOF_OBJECT });
//
but QxTextField.createRegExpValidator () returns a function.
Maybe I'm misunderstanding how these are supposed to be used. They do
seem like a
Izaak Branderhorst schrieb:
In QxTextField.js:
//
QxTextField.addProperty({ name : "validator", type :
QxConst.TYPEOF_OBJECT });
//
but QxTextField.createRegExpValidator () returns a function.
Maybe I'm misunderstanding how these are supposed to be used. They do
seem like a bit of a quick s
Izaak Branderhorst schrieb:
say we have:
//
win1 = new QxWindow ('Centered window');
win1.set ( { width: 'auto', height: 'auto', centered: true } );
win1.add (new QxAtom ('blah blah'));
d.add (win1);
win1.open ();
//
The window will center itself but the dimensions will be something like
3x3,
What sort algorithm are we using here? Can it be optimized?
Kent
On Thu, 2006-01-05 at 18:52 -0500, J. Russell Smyth wrote:
> well, I would say a 50% performance hit is problematic as well.. and
> 11 sec to load 10k lines on a machine with the power you are
> discussing.. still pretty bad.
>
> B
I guess it would be hard to implement a QxTree inside the QxListView.
What I can see there would be some major issues. The reason is that
QxListView has not been developed the modularized way yet, i.e. where it
is possible to plug in a any class in any column. It is more static in
its design. Maybe
Hej!
As far as I know, no one is implementing it. The component would be a
very good addition.
Kent
On Thu, 2006-01-05 at 18:54 -0500, J. Russell Smyth wrote:
> Is there any work being done to create a TreeTable like component for
> Qooxdoo? This is a primary component of our interface and if it
33 matches
Mail list logo
