Hi Sascha,
I am happy that qooxdoo mets your requirements.
Object.prototype destroys the typical usage of hash maps (objects).
There is no way around. qooxdoo use maps all over te place. It should
be by far easier to change your stuff to not extend Object.prototype.
See also:
http://dean.
Found the answer myself by digging deeper in the docu:
http://qooxdoo.org/documentation/user_manual/drag_drop
explains everything. I first thought the dragend and dragmove events are
always fired when the window is moved. But they belong to the
DragAndDropHandler as clearly visible in the api v
Thanks for the reply, Fabian.
No need for an alternate solution. The application I developed is already
in place. It's a GUI that displays a bunch of data stored in a mySQL
database. Currently, I am pulling the data out, creating a nice JSON
representation of it, passing it to the GUI, which i
Hi,
I'm new to qooxdoo and quite impressed about the framework. Great work!
Could someone tell me why the following code snipplet is not working
regarding the "dragend" or "dragmove" event. The events like "dragstart"
and "beforedisappear" work well.
Thanks!
Gudio
--
qx.co
Hello,
I am developing for the open source project XML11 and we are currently
working on implementing a JavaScript library that offers Desktop-GUI like
features. From what I've seen, Qooxdoo seems to be perfectly suited for this
task.
Unfortunately I fail when trying to implement qooxdoo in our
I think I found it:
APPLICATION_OPTIMIZE_STRINGS = false
APPLICATION_OPTIMIZE_VARIABLES = false
also, for anyone else looking for MAKE info, check out the Wiki at:
http://qooxdoo.org/documentation/user_manual/application_mk
Jim
www.D4PHP.org
www.D4PHP-Hosting.com
On 5/8/07, Jim Hunter <[EMAI
Hi.
After some help from Alex, i got my second listview working fine :D
My problem now is: listview is not updating :(
I have an aux function to add items to listview wich is working for my
second listview (same application) but not for the first.
application: http://200.178.186.14/squidmin/s
dperez wrote:
> With the "Web developer" extension, I disable the cache for Firefox.
I'm still getting that error with the cache disabled (and it gives me
"slow script" warnings to boot).
> James A. Pyrich wrote:
>> Greetings all,
>>
>>I am doing development using qx 0.6.6, and, as I am usin
jd102684 schrieb:
> Hello,
>
> I need to be able to convert some complex custom qooxdoo objects to JSON.
> After searching for newsgroup, I found out about
> qx.io.Json.stringify(myObject); But for some reason I can't get it to
> work, even with simple objects. For example,
>
>
> var test = new
These changes worked for that piece of code. But I am running into many
other places where optimization is causing issues. Is there a setting I can
provide that will NOT optimize the code? I am just making a beta version so
I don't care if it's not as small or 'tight' as I can get it, I just want
Excellent catch! I'll give that a try.
Thanks!!!
Jim
On 5/8/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
Peter Schneider schrieb:
> Hi Jim,
>
> it's the call to eval() that's causing the trouble.
> (sorry can't find the documentation to this issue...)
> The issue is the line (as you stated):
Dear table gurus,
Why changing the visibility of a column in a table produces strange visual
effects?
Is this a bug?
Here is the code:
myTable.getTableColumnModel().setColumnVisible(0, false)
This happens for example when hiding the ID column of a ComboBoxEx.
See sample ComboBoxEx_1.html
Shoul
An atom isn't a simple object!.
Have you looked at the JSON spec?
Only dictionaries, arrays, numbers, booleans, strings and few more are
supported.
jd102684 wrote:
>
> Hello,
>
> I need to be able to convert some complex custom qooxdoo objects to JSON.
> After searching for newsgroup, I found
Hi,
But I need the thickness of the new border to be applied, not the old one.
Sebastian Werner wrote:
>
> Each Widget has protected members for this e.g. _cachedBorderRight
>
--
View this message in context:
http://www.nabble.com/Equivalent-to-BorderPresets-in-0.7--tf3709495.html#a103
Each Widget has protected members for this e.g. _cachedBorderRight
Sebastian
dperez schrieb:
> Hi Sebastian,
>
> I need to know the thickness of the border. I could assume it is 1 or 2,
> but it is best to assume nothing.
>
> Old code:
>
> var border = qx.renderer.border.BorderPresets.getI
Thanks Derrell, :-)
It would be nice if documented here:
http://qooxdoo.org/documentation/developer_manual/properties
Derrell.Lipman wrote:
>
> dperez <[EMAIL PROTECTED]> writes:
>
>> What's the best practice in 0.7 for changing the value of a property in
>> its
>> apply method.
>>
>> qx.Cla
Hello,
I need to be able to convert some complex custom qooxdoo objects to JSON.
After searching for newsgroup, I found out about
qx.io.Json.stringify(myObject); But for some reason I can't get it to
work, even with simple objects. For example,
var test = new qx.ui.basic.Atom("hi");
alert(q
Hi Sebastian,
I need to know the thickness of the border. I could assume it is 1 or 2,
but it is best to assume nothing.
Old code:
var border = qx.renderer.border.BorderPresets.getInstance().inset;
var newListSettings = {
height:
border.getTopWidth()+this._list.getHeight()+border.getBo
Documented here:
http://qooxdoo.org/documentation/developer_manual/properties
Sebastian Werner wrote:
>
> The old "return true;" is not needed anymore in 0.7.
>
--
View this message in context:
http://www.nabble.com/Return-value-of-apply-tf3708792.html#a10376725
Sent from the qooxdoo-devel
dperez <[EMAIL PROTECTED]> writes:
> What's the best practice in 0.7 for changing the value of a property in its
> apply method.
>
> qx.Class.define('myClass', {
> properties: {
> value: {
> apply: '_applyValue'
> }
> },
> methods: {
>_applyValue: function(propValue
Dear community,
What's the best practice in 0.7 for changing the value of a property in its
apply method.
qx.Class.define('myClass', {
properties: {
value: {
apply: '_applyValue'
}
},
methods: {
_applyValue: function(propValue) {
//Here a need to cha
dperez schrieb:
> Hi,
>
> I'm fixing some converted code in ComboBoxEx.js to 0.7 version.
>
> Old code:
> var border = qx.renderer.border.BorderPresets.getInstance().inset;
> Converted code:
> var border = "inset"
>
> I need a real Border object, not a string.
Ok, why do you need a border
Sebastian Werner schrieb:
> Rüdiger Herrmann schrieb:
>> Hi,
>>
>> sorry, but this is again something font-related :(
>>
>> I saw that there is now a font property on class Widget. Looks great on
>> the first sight, but after some investigation - frankly I don't like it.
>>
>> With inheritance as
The only place where _compileClipString is used is from the setClip
properties. Maybe you use some of them. Otherwise this methods should
not get executed.
Sebastian
Rüdiger Herrmann schrieb:
> Hi Sebastian,
>
> thanks for the quick solution. As I said, there is *no* call to
> getClipLeft()
Hi Sebastian,
thanks for the quick solution. As I said, there is *no* call to
getClipLeft() in my code. The only reference I found is in Widget.js in
_compileClipString.
I just want to avoid that the real source of the problem gets hidden by
this.
Cheers,
Rüdiger
Sebastian Werner wrote:
> The
Rüdiger Herrmann schrieb:
> Hi,
>
> sorry, but this is again something font-related :(
>
> I saw that there is now a font property on class Widget. Looks great on
> the first sight, but after some investigation - frankly I don't like it.
>
> With inheritance as a generalization to specializatio
that's good news:)
Thanks
Rüdiger
dperez wrote:
> Hi Rüdiger,
>
> This event already exists:
> myCombo.getField().addEventListener('changeValue', function() {})
>
>
> Rüdiger Herrmann wrote:
>> Hi,
>>
>> what I would appreciate is an event that is fired whenever the edit
>> field is changed
Hi,
sorry, but this is again something font-related :(
I saw that there is now a font property on class Widget. Looks great on
the first sight, but after some investigation - frankly I don't like it.
With inheritance as a generalization to specialization hierarchy, the
font property is misplac
Peter Schneider schrieb:
> Hi Jim,
>
> it's the call to eval() that's causing the trouble.
> (sorry can't find the documentation to this issue...)
> The issue is the line (as you stated):
> eval('var f_' + x + '_' + y + ' = new
> qx.ui.tree.TreeFile(newValues[x][y])');
>
> Due to the fact that t
Hi,
I'm fixing some converted code in ComboBoxEx.js to 0.7 version.
Old code:
var border = qx.renderer.border.BorderPresets.getInstance().inset;
Converted code:
var border = "inset"
I need a real Border object, not a string.
How do I get it?
I suspect this is handled now by the theme.
Re
Thank you very much for the help, Sebastian. I'll try that.
Joe
Sebastian Werner wrote:
"auto" means to use the dimensions required to show all the content
(without scrolling). So this seems to be the wrong value in your
application. If you need a scrollbar you can set overflow to "scroll" or
I like more the new behaviour.
Nearly always return true was used.
Sebastian Werner wrote:
>
> The better alternative is to throw an exception. However, please
> remember, that the values should be checked before the apply method is
> executed e.g. in complex cases with a better "check" attri
OK, we go with solution number #2.
* "align" is now supported as "textAlign" in both, Label and TextField.
* There was created a new bug about creating a new RichLabel widget to
cover the removed properties:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=398
Hope you like it.
Sebastian
Sebastia
Sebastian,
> > Can't you use mixin classes to make it easier?
>
> I talk about the API not the code.
I meant to make it easier to implement the correct API.
> That was a bit unfriendly.
My apologies. You are working very hard, as I can see from all the code
checkins.
> I even think it is
>
That helped, thanks for clarifying this.
Rüdiger
Alex Back wrote:
> Hi Rüdiger,
>
> Rüdiger Herrmann wrote:
>> while migrating to 0.7 I read that the naming conventions for
>> property-change-events have changed [1]. Instead of "changeWidth"
>> (0.6.x) it would be "widthChanged" now.
> This is a
The better alternative is to throw an exception. However, please
remember, that the values should be checked before the apply method is
executed e.g. in complex cases with a better "check" attribute.
Sebastian
Dietrich Streifert schrieb:
>
>
> Sebastian Werner schrieb:
>> The old "return tru
Sebastian Werner schrieb:
The old "return true;" is not needed anymore in 0.7.
In 0.6 returning a value of "false" made the setter fail. How is this
done now in 0.7?
Sebastian
dperez schrieb:
Hi,
Does the apply method associated with a property to return success in 0.7?
In 0.6.x
The old "return true;" is not needed anymore in 0.7.
Sebastian
dperez schrieb:
> Hi,
>
> Does the apply method associated with a property to return success in 0.7?
>
> In 0.6.x _modifyPropertyName had to return true if successful.
>
> Thanks for any answer.
>
> Regards
> David
Hi,
Does the apply method associated with a property to return success in 0.7?
In 0.6.x _modifyPropertyName had to return true if successful.
Thanks for any answer.
Regards
David
--
View this message in context:
http://www.nabble.com/Return-value-of-apply-tf3708792.html#a10373284
Sent from t
With the "Web developer" extension, I disable the cache for Firefox.
James A. Pyrich wrote:
>
> Greetings all,
>
>I am doing development using qx 0.6.6, and, as I am using sources and
> FireFox appears to neglect checking if all files are the most recent, I
> have been clearing the cache
Hi Rüdiger,
Rüdiger Herrmann wrote:
> while migrating to 0.7 I read that the naming conventions for
> property-change-events have changed [1]. Instead of "changeWidth"
> (0.6.x) it would be "widthChanged" now.
This is a misunderstanding. The events of property-changes will remain in the
pattern "
Thanks Fabian, always so helpful.
Updated the wiki
http://qooxdoo.org/documentation/articles/comparison_of_class_declarations_between_0.6.x_and_0.7
with your valuable info!.
Fabian Jakobs-2 wrote:
>
> there is now direct equivalent to this syntax. You can still use the old
> version or if you
Hi Jim,
it's the call to eval() that's causing the trouble.
(sorry can't find the documentation to this issue...)
The issue is the line (as you stated):
eval('var f_' + x + '_' + y + ' = new qx.ui.tree.TreeFile(newValues[x][y])');
Due to the fact that the "variable optimization" replaced the 'x
Hi all,
while migrating to 0.7 I read that the naming conventions for
property-change-events have changed [1]. Instead of "changeWidth"
(0.6.x) it would be "widthChanged" now.
Since the current source code still shows lots of "changeXXX" event
names, I was wondering if this is just work to be d
Hi Rüdiger,
This event already exists:
myCombo.getField().addEventListener('changeValue', function() {})
Rüdiger Herrmann wrote:
>
> Hi,
>
> what I would appreciate is an event that is fired whenever the edit
> field is changed.
> I am not sure whether this is possible with the current imp
Done. The column visibility button is back again in rev. 7713 of trunk ;-)
Sebastian Werner schrieb:
Dietrich Streifert schrieb:
I had a look at the invisible menu button problem:
That's great. Thank you.
The menu button (created in Table.js, line 172:
this._columnVisibilityBt) i
Hi,
what I would appreciate is an event that is fired whenever the edit
field is changed.
I am not sure whether this is possible with the current implementation
but if there are plans to enhance the ComboBoxEx maybe that could fit in
as well;)
Cheers,
Rüdiger
dperez wrote:
> Planned enhanceme
[EMAIL PROTECTED] schrieb:
> Sebastian Werner <[EMAIL PROTECTED]> writes:
>
>> * the editing feature seems not to work, after editing a cell, the cell
>> is empty or shows NaN.
>
> I had a few minutes, so I looked into this. The problem is here:
Fine.
>
> getCellEditorValue : function(ce
Dietrich Streifert schrieb:
> I had a look at the invisible menu button problem:
That's great. Thank you.
>
> The menu button (created in Table.js, line 172:
> this._columnVisibilityBt) is an instance of qx.ui.toolbar.Button:
>
> this._columnVisibilityBt = new qx.ui.toolbar.Button(null,
>
"auto" means to use the dimensions required to show all the content
(without scrolling). So this seems to be the wrong value in your
application. If you need a scrollbar you can set overflow to "scroll" or
"scrollY". The height is often limited by the outer dimensions so I
would think you need
You can use qx.ui.embed.Iframe to embed other pages. What is not
possible is the focus handling you describe. There is no possibility for
qooxdoo to catch events which are adressed to another document. This is
only possible if the loaded content sends back the events to the outer
qooxdoo applic
I had a look at the invisible menu button problem:
The menu button (created in Table.js, line 172:
this._columnVisibilityBt) is an instance of qx.ui.toolbar.Button:
this._columnVisibilityBt = new qx.ui.toolbar.Button(null,
"widget/table/selectColumnOrder.png");
If instead qx.ui.form.Button
Hugh Gibson schrieb:
> Sebastian,
Hugh,
>
>>> When looking into Font.js, I think the properties align, transform,
>>> letterSpacing, wordSpacing and lineHeight and do not belong to a Font
>>> class for the same reasons that apply to wrap.
>
>> I think that "wrap" could alternatively in the La
I have an application that works fine while in individual files, but when I
did a MAKE BUILD I am getting very strange results. I fixed one problem but
a new one has popped up. I am getting an error stating 'Y' is undefined. The
problem is that Y is the VAR of a FOR loop and the line the error is
54 matches
Mail list logo
