Christian Boulanger <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] schrieb:
>> Christian Boulanger <[EMAIL PROTECTED]> writes:
>>
You can define a mixin with the desired property and include the mixin at
runtime into any class you want.
>>> but I forgot to ask: how is this done exactly?
[EMAIL PROTECTED] schrieb:
> Christian Boulanger <[EMAIL PROTECTED]> writes:
>
>>> You can define a mixin with the desired property and include the mixin
>>> at runtime into any class you want.
>>>
>> but I forgot to ask: how is this done exactly? I haven't found any
>> example or doc
Christian Boulanger <[EMAIL PROTECTED]> writes:
>> Not in the way it was done in 0.5 and 0.6 but in a much cleaner way ;-)
>>
>> You can define a mixin with the desired property and include the mixin
>> at runtime into any class you want.
>>
> but I forgot to ask: how is this done exactly? I h
Fabian answered long ago:
>> I suppose that dynamic properties are only possible at declaration
>> time, not at run time anymore, like it was possible in 0.5. Or can I
>> still retrofit existing classes with additional properties without
>> having to extend them?
>>
> Not in the way it wa
That was it, thank you very much! Now I have finally a working SVN build
environment... and I feel the thrill of living dangerously. C.
[EMAIL PROTECTED] schrieb:
> [EMAIL PROTECTED] writes:
>
>
>> The compiler is not detecting, for some reason, that the Classic appearance
>> used by the skele
[EMAIL PROTECTED] schrieb:
>> * in qx.ui.treefullcontrol.Tree is a direct access to a property value, i
>> adapted it to the qx 0.7 property value
>> that's no good manner, but i had no other idea
>>
> Erich, I forgot to credit you in the check-ins for these two problems, but
> thanks for tr
[EMAIL PROTECTED] writes:
> The compiler is not detecting, for some reason, that the Classic appearance
> used by the skeleton requires qx.renderer.border.BorderPresets. One of the
> compiler gurus will have to find the problem that is causing this, but in the
> interim, I've temporarily solved t
Christian Boulanger <[EMAIL PROTECTED]> writes:
> Win32/Cygwin/SVN-rev.7241:
>
> after svn update / make distclean / make build and clearing the
> browser-cache, I am getting the following error in my unmodified skeleton
> linked to the svn version
>
> 031297 ERROR: qx.ui.form.Button[60]: Could n
Win32/Cygwin/SVN-rev.7241:
after svn update / make distclean / make build and clearing the
browser-cache, I am getting the following error in my unmodified
skeleton linked to the svn version
031297 ERROR: qx.ui.form.Button[60]: Could not apply state appearance:
TypeError - qx.renderer.border.
Erich Konicek <[EMAIL PROTECTED]> writes:
> I tryed a little with the trunc-version and i found two little errors:
> * in a few classes there are calls to Widget.isEnabled()
> (witch earlier was the getAlias of the enabled property in qx.core.Object and
> is not a property in qx.ui.core.Widget -
A really very, very good work!
The extended OO functions (Mixins, Interfaces) and the enhanced property
features are great.
Also the new appearance theme "Ext" is much more beautifuly as Classic.
I was surprised about the migration. Such a complex migration without an
error - amazing!
I tryed
Hello David,
> Good job and very well documented for being an alpha. :-)
> It looks like the new 0.7 version is quite advanced.
> I like how the new appearance looks, with gradients in the buttons.
>
> Question:
> With qooxdoo 0.6.x you can have an event for any property change.
> Now we only can
Hello Christian,
> Hello,
>
> it is a truly impressive improvement that shows how much thought you put
> into a well-designed framework.
>
> But I suppose that dynamic properties are only possible at declaration
> time, not at run time anymore, like it was possible in 0.5. Or can I
> still retro
Good job and very well documented for being an alpha. :-)
It looks like the new 0.7 version is quite advanced.
I like how the new appearance looks, with gradients in the buttons.
Question:
With qooxdoo 0.6.x you can have an event for any property change.
Now we only can have events if the design
Hello,
it is a truly impressive improvement that shows how much thought you put
into a well-designed framework.
But I suppose that dynamic properties are only possible at declaration
time, not at run time anymore, like it was possible in 0.5. Or can I
still retrofit existing classes with addit
Hi all,
just wanted to let you know about a tiny surprise before the Easter
break: another pre-release is available, 0.7-alpha2 !
Please see the following news entry for more information:
http://news.qooxdoo.org/another-exciting-technical-preview
Any feedback on the new features, particularly th
16 matches
Mail list logo
