Hi Christian,
strange Problem. I have just tried the same with the skeleton of 0.7 and
everything just worked. Could you provide some details?
Best Fabian
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express
Hello,
after 0.7 is out what's the plan for 0.8 and what strategy do you advise
for keeping in sync with the repository? I assume you'll use the trunk
for 0.8 development and not a branch. So for a project based on 0.7, it
is probably best to stick with the 0.7 tag instead of the *trunk* isn't
Hello,
after 0.7 is out what's the plan for 0.8 and what strategy do you advise
for keeping in sync with the repository? I assume you'll use the trunk
for 0.8 development and not a branch. So for a project based on 0.7, it
is probably best to stick with the 0.7 tag instead of the branch, isn't
Don't wait to long for it, the demos were the Nr. 1 learning base for
me, and I think for others, too :)
(Ok, it's still possible, but in the past it was more easy to see the
sourcecode).
The the browser itself is very nice.
Sebastian Werner wrote:
> This was planned but has not been stable sinc
FrozenDice <[EMAIL PROTECTED]> writes:
> I found the radiomanager and tried to implement it, but for some
> reason all I get is a blank page. When I remove the radiomanager the
> page displays correctly. I am totally stumped, my manager is at the
> end of the code, scroll down to the end to see
Fabian Jakobs wrote:
> James A. Pyrich schrieb:
>> Greetings all,
>>
>> Are there major differences in the build engine (generator.py)
>> between 0.6.x and 0.7? I'd like to get into separating the build files
>> into distinct modules but don't want to spend a lot of time looking into
>> the
This was planned but has not been stable since our release date.
There will be further improvements over time :)
Sebastian
Am 05.06.2007 um 23:10 schrieb FrozenDice:
> Here here! I had the same problem this morning. An additional tab
> with the source would be nice, if anyone wanted they c
I found the radiomanager and tried to implement it, but for some
reason all I get is a blank page. When I remove the radiomanager the
page displays correctly. I am totally stumped, my manager is at the
end of the code, scroll down to the end to see it(starts with var
rg1). I know it sucks readin
Here here! I had the same problem this morning. An additional tab
with the source would be nice, if anyone wanted they could also make
it do markup in color, bold, italics, you know.
On 6/5/07, Christian Boulanger <[EMAIL PROTECTED]> wrote:
> Hello,
>
> the demo browser looks very nice! However,
Hello,
the demo browser looks very nice! However, one thing is missing: you
cannot view the source code easily, like you can in demo browsers of
other frameworks. You can of course right-click on the iframe (if you
know that there is an iframe) and then view the source in the context menu.
But
Hello,
thank you for the 0.7 release, so far everything is working fine over
here since I migrated some time ago. But I have a problem with
translation. In my auto-generated code, for example, I have the following:
var qx_id2273032 = new qx.ui.form.ListItem(this.tr('CD'),null,null);
qx_id227300
Hi,
just realised that qx.core.Object.get() doesn't exist in 0.7.
I'm using this at various places in my application to access properties
which are e.g. defined later in derived classes.
As I don't know the requested property names at design-time, is there an
easy way to read property values with
FrozenDice <[EMAIL PROTECTED]> writes:
> So I have my tree and it had checkboxes, now it has radiobuttons.
> What I'm trying to do here is make a menu where you go through the
> tree, and the last level(the leaves/"files") have radiobuttons.
>
> Ex. Data->
> Display ->
>
So I have my tree and it had checkboxes, now it has radiobuttons.
What I'm trying to do here is make a menu where you go through the
tree, and the last level(the leaves/"files") have radiobuttons.
Ex. Data->
Display ->
{} html
Good news, everyone!
After some challenging development and intense testing, supported by
excellent feedback from the community, qooxdoo has finally been released
in version 0.7.
For more info, please see the corresponding news at
http://news.qooxdoo.org/qooxdoo-07-released
Thanks again for your
This seems to be a more general problem where the refine of the init
attribute is ignored if the original property definition does not
contain the init attribute.
I've created a bugzilla issue for this:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=467
Dietrich Streifert schrieb:
> Hello List,
Hello List,
I've derived a class from qx.ui.tree.TreeFolder which refines the icon
property this way:
icon :
{
refine : true,
icon : "icon/16/myIcon.png"
}
If I check the property through its getter in the overriden constructor
the value of the property is null:
James A. Pyrich schrieb:
> Greetings all,
>
> Are there major differences in the build engine (generator.py)
> between 0.6.x and 0.7? I'd like to get into separating the build files
> into distinct modules but don't want to spend a lot of time looking into
> the 0.6.6 build engine if that's
Greetings all,
Are there major differences in the build engine (generator.py)
between 0.6.x and 0.7? I'd like to get into separating the build files
into distinct modules but don't want to spend a lot of time looking into
the 0.6.6 build engine if that's all going to change when we migrate
[EMAIL PROTECTED],
I have a big problem.
I connect from a hardware-thin-client to a TerminalServer.
After starting the IE with my qooxdoo-app the Browser crashes.
The following error occurs:
Die Anwendung "C:\Programme\Internet Explorer\iexplore.exe" hat einen
Programmfehler verursacht.
Hi again,
I just noticed that the line
decoration: "underline"
in our font theme stopped working. The decoration is not rendered
anymore. Are their any changes to the syntax?
Thanks, Ralf
-
This SF.net email is sponso
For editing of my table cells I use the click event. For an boolean column I
can click and set the value of the opposite value.
if(this.getTableColumnModel ().getDataCellRenderer(column) instanceof
qx.ui.table.BooleanDataCellRenderer){
var value = table.getTableModel ().getValue(column,ro
Hi Fabian,
thanks for your fast response.
Fabian Jakobs schrieb:
> setting explicitly to null means "don't use any color". This is treated
> as an user value and takes precedence over init and themed values.
> Calling reset means "clear user value". Once the user value is resetted
> either th
Ralf Sternberg schrieb:
> Hi,
>
> when I set a user-defined text/background color to a widget, and reset
> the color using e.g. setBackgroundColor( null ), the themed color value
> is not reinstalled. Using resetBackgroundColor() works as expected.
>
> Is this method of resetting by setting to nu
Hi,
when I set a user-defined text/background color to a widget, and reset
the color using e.g. setBackgroundColor( null ), the themed color value
is not reinstalled. Using resetBackgroundColor() works as expected.
Is this method of resetting by setting to null generally discouraged?
From my
OK, thanks for your answer. I will split the files, migrate and merge back.
Sebastian Werner wrote:
>
> Not using one class per file I problematic. It will break a lot of stuff
> e.g. things like the API viewer, the include sort system, the file
> tracer (to find out the name of a class and
26 matches
Mail list logo
