[qooxdoo-devel] Help ! What's wrong with my class Inheritance?
first sorry for my pool english, I wish you can understand me,thanks!
who can help me?what's with my class Inheritance? it cant work!thanks
qx.Class.define('template.TreeFile',
{
extend: qx.ui.tree.TreeFile,
construct : function(labelOrTreeRowStructure, icon, iconSelected)
{
this.base(arguments,this._getRowStructure(labelOrTreeRowStructure,
icon, iconSelected));
},
properties :
{
/**
* description
*/
id :
{
nullable : true,
check : "Integer"
},
order :
{
nullable : true,
check : "Integer"
},
url :
{
nullable : true,
check : "String",
}
},
members :
{
}
});
--
View this message in context:
http://www.nabble.com/Help-%21-What%27s-wrong-with-my-class-Inheritance--tp17583936p17583936.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Problem when I try read if a checkbox is checked in a tree...
Hi Edgardo, > > I'm starting work with QooxDoo, I have a tree with checkboxes object, > my problem is when I try read the checkboxes selected this not show > anything. > Good choice :-) > I checked each tree's node and use isChecked() function but this no > say anything. > > When mark the checkboxes with code using setChecked() function, this > show me each checkboxes checked. But if I change one checkbox on the > screen the isChecked function no detect this change. > > I need your help a lot. > > Thanks. > Could you post the relevant code snipplets? From You description it is hard to tell, what is going wrong. Best Fabian -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas Gauger, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
[qooxdoo-devel] Disable log window
Hi! I´m trying to disable the log pop up. But I don´t manage it.. I have searched other threads but I tried differents things like writing qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); or something similar and thats doesn´t work... please I need to close log pop up! thanks! -- View this message in context: http://www.nabble.com/Disable-log-window-tp17596301p17596301.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Can't turn-off qooxdoo logging in build version
kanugula wrote: > Hi, > > I am using Demo Browser terminology for simplicity. > > I put the following code in Makefile.demo and Makefile.demobrowser. > APPLICATION_BUILD_LOG_LEVEL = off > > I still see the INFO messages logged in Log tab. > Are you looking at the build version of your app (APPLICATION_BUILD_LOG_LEVEL only influences the build version)? Did you do a 'make build' after changing the Makefile? Which messages get through? Your own, or some system messages of the qooxdoo runtime (like boot message etc.)? There is a chance that those might leak through the filter in 0.7. Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Disable log window
Thanks for the answer. In the build version the windows appears too. It´s not important the log in the sourve version. But in the build version I´d like it.. Where is the variable of makefile? I didn´t find it thron7 wrote: > > Pirlo wrote: >> Hi! >> >> I´m trying to disable the log pop up. But I don´t manage it.. I have >> searched other threads but I tried differents things like writing >> qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); >> or >> something similar and thats doesn´t work... >> >> please I need to close log pop up! >> >> thanks! >> > Pirlo, > > the log window should be off by default in the build version of your > app. Get back if this is not the case. > > If you want to disable the log window for the source version, try > setting APPLICATION_SOURCE_LOG_LEVEL = off in the Makefile and re-run > make. If that doesn't work, try removing all appenders in your app using > removeAllAppenders(), or setting your log appender to > qx.log.appender.RingBuffer, which stores all messages internally (but > this consumes memory!). > > HTH, > Thomas > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://www.nabble.com/Disable-log-window-tp17596301p17597620.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Disable log window
Pirlo wrote: > Hi! > > I´m trying to disable the log pop up. But I don´t manage it.. I have > searched other threads but I tried differents things like writing > qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); or > something similar and thats doesn´t work... > > please I need to close log pop up! > > thanks! > Pirlo, the log window should be off by default in the build version of your app. Get back if this is not the case. If you want to disable the log window for the source version, try setting APPLICATION_SOURCE_LOG_LEVEL = off in the Makefile and re-run make. If that doesn't work, try removing all appenders in your app using removeAllAppenders(), or setting your log appender to qx.log.appender.RingBuffer, which stores all messages internally (but this consumes memory!). HTH, Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Disable log window
Finally I got...! thanks for all! Pirlo wrote: > > Thanks for the answer. In the build version the windows appears too. It´s > not important the log in the sourve version. But in the build version I´d > like it.. > > Where is the variable of makefile? I didn´t find it > > thron7 wrote: >> >> Pirlo wrote: >>> Hi! >>> >>> I´m trying to disable the log pop up. But I don´t manage it.. I have >>> searched other threads but I tried differents things like writing >>> qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); >>> or >>> something similar and thats doesn´t work... >>> >>> please I need to close log pop up! >>> >>> thanks! >>> >> Pirlo, >> >> the log window should be off by default in the build version of your >> app. Get back if this is not the case. >> >> If you want to disable the log window for the source version, try >> setting APPLICATION_SOURCE_LOG_LEVEL = off in the Makefile and re-run >> make. If that doesn't work, try removing all appenders in your app using >> removeAllAppenders(), or setting your log appender to >> qx.log.appender.RingBuffer, which stores all messages internally (but >> this consumes memory!). >> >> HTH, >> Thomas >> >> >> - >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ >> ___ >> qooxdoo-devel mailing list >> qooxdoo-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > > -- View this message in context: http://www.nabble.com/Disable-log-window-tp17596301p17598211.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Help ! What's wrong with my class Inheritance?
Hi hywhy!
Which qooxdoo version are you working with?
On first glance, I don't see any issue with your code. What problem
exactly do you get? (Error messages etc. would be helpful).
Thomas
hywhy wrote:
> first sorry for my pool english, I wish you can understand me,thanks!
>
> who can help me?what's with my class Inheritance? it cant work!thanks
>
> qx.Class.define('template.TreeFile',
> {
> extend: qx.ui.tree.TreeFile,
>
> construct : function(labelOrTreeRowStructure, icon, iconSelected)
> {
> this.base(arguments,this._getRowStructure(labelOrTreeRowStructure,
> icon, iconSelected));
> },
>
> properties :
> {
>/**
> * description
> */
> id :
> {
> nullable : true,
> check : "Integer"
> },
>
> order :
> {
> nullable : true,
> check : "Integer"
> },
>
> url :
> {
> nullable : true,
> check : "String",
> }
> },
>
> members :
> {
> }
> });
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
[qooxdoo-devel] using CSS style inside HorizontalSplitPane
Hi, I have the following situation: a HorizontalSplitPane where I flow into the RIGHT side a HTML content using a qx.ui.embed.HtmlEmbed object. My problem is if the HTML content has a CSS style defined for body that style is applied for the LEFT side of the HorizontalSplitPane too. Any idea how implement this design so the CSS style to be applied only to that HTML content (the right side of the splitpane) and not affect other areas. Regards, Dan -- Dan Trif Java Development 1&1 Internet AG - Romania 18 Mircea Eliade St. Tel :+40-21-319-3571 ext. 511 Sect 1, Bucharest Mobile: +40-749-770-517 012015, Romania Email : [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Can't turn-off qooxdoo logging in build version
I already rebuilt the build after the setting APPLICATION_BUILD_LOG_LEVEL = off Small correction. It stopped application logging. But its still logs system info like Demo Browser 273295" load demo: MyTest.html qx.core.Init[4] 277889: qooxdoo 0.7.3 277889: loaded 1 old classes .. After surfing the forum, most of the replies are setting APPLICATION_BUILD_LOG_LEVEL and qx.log.Logger.ROOT_LOGGER.setMinLevel(); It would be easy to set APPLICATION_BUILD_LOG_LEVEL and it should work. As per your guess, it could be the filter leak. Thanks. Kanugua. Thanks. Kanugula. The Log tab shows both system thron7 wrote: > > kanugula wrote: >> Hi, >> >> I am using Demo Browser terminology for simplicity. >> >> I put the following code in Makefile.demo and Makefile.demobrowser. >> APPLICATION_BUILD_LOG_LEVEL = off >> >> I still see the INFO messages logged in Log tab. >> > > Are you looking at the build version of your app > (APPLICATION_BUILD_LOG_LEVEL only influences the build version)? > > Did you do a 'make build' after changing the Makefile? > > Which messages get through? Your own, or some system messages of the > qooxdoo runtime (like boot message etc.)? There is a chance that those > might leak through the filter in 0.7. > > Thomas > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://www.nabble.com/Can%27t-turn-off-qooxdoo-logging-in-build-version-tp17565686p17602341.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
[qooxdoo-devel] KeepFirstVisibleRowComplete(true) breaks when browser window is resized
Hi, qooxdoo 0.7.3 IE6/FF KeepFirstVisibleRowComplete(true) on Table works great when the browser size is normal. Some crazy users resize the browser to their personal preference. At that time, the last row is partially visible. I see the same behaviour in Demo Browser/Table_1. Does KeepFirstVisibleRowComplete(true) work with specific screen size? IS it possible to avoid absolute positions in the entire application like Demo Browser? And is it a good practice to maximize the window on startup and block resize? Thanks. Kanugula. -- View this message in context: http://www.nabble.com/KeepFirstVisibleRowComplete%28true%29-breaks-when-browser-window-is-resized-tp17602597p17602597.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Problem when I try read if a checkbox is checked in a tree...
Fabian thanks for you answer.
function stuff(vLabel, vValue, vAddCheckBox, vCheckedBox, vIcon,
vIconSelected)
{
treeRowStructure = qx.ui.tree.TreeRowStructure.getInstance().newRow();
// Here's our indentation and tree-lines
treeRowStructure.addIndent();
// The standard tree icon follows
/*treeRowStructure.addIcon(
arguments.length >= 5 ? vIcon : "icon/16/places/user-desktop.png",
arguments.length >= 6 ? vIconSelected :
"icon/16/apps/accessories-dictionary.png");*/
// A checkbox comes right after the tree icon
if( vAddCheckBox )
{
obj = new qx.ui.form.CheckBox(null, vValue, null, vCheckedBox);
obj.setPadding(0, 0);
obj.id = "CheckBoxId_" + vValue;
treeRowStructure.addObject(obj, false);
}
// The label
treeRowStructure.addLabel(vLabel);
return treeRowStructure;
}
I found the problem, in the before code in the row:
treeRowStructure.addObject(obj, false);
If this parameter is true (parameter in red) that I make changes to the
checkboxes in the tree can not be seen to isChecked function.
In the examples the parameter's value is true, my problem was solved by
changing this parameter to false.
--
Saludos!!!...
Edgardo Hernández López
On 6/2/08, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
>
> Hi Edgardo,
> >
> > I'm starting work with QooxDoo, I have a tree with checkboxes object,
> > my problem is when I try read the checkboxes selected this not show
> > anything.
> >
> Good choice :-)
>
> > I checked each tree's node and use isChecked() function but this no
> > say anything.
> >
> > When mark the checkboxes with code using setChecked() function, this
> > show me each checkboxes checked. But if I change one checkbox on the
> > screen the isChecked function no detect this change.
> >
> > I need your help a lot.
> >
> > Thanks.
> >
> Could you post the relevant code snipplets? From You description it is
> hard to tell, what is going wrong.
>
> Best Fabian
>
>
> --
> Fabian Jakobs
> JavaScript Framework Developer
>
> 1&1 Internet AG
> Brauerstraße 48
> 76135 Karlsruhe
>
> Amtsgericht Montabaur HRB 6484
>
> Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas
> Gauger, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn,
> Achim Weiss
> Aufsichtsratsvorsitzender: Michael Scheeren
>
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] KeepFirstVisibleRowComplete(true) breaks when browser window is resized
On Mon, Jun 2, 2008 at 10:26 AM, kanugula <[EMAIL PROTECTED]> wrote: > > KeepFirstVisibleRowComplete(true) on Table works great when the browser > size > is normal. Some crazy users resize the browser to their personal > preference. Doesn't seem crazy to me. I believe users should be able to configure their environment however they like it. > At that time, the last row is partially visible. It sounds like you're describing exactly the intended behavior. The property keepFirstVisibleRowComplete does just that: it keeps the FIRST visible row complete as you scroll vertically. It implies nothing about the LAST visible row. > Does KeepFirstVisibleRowComplete(true) work with specific screen size? It works regardless of screen or window size. > And is it a good practice to maximize the window on startup and block > resize? Absolutely not, in most circumstances. Whenever possible, window sizes should be at the user's discretion. (You may define a minimum window size that's required to see everything on the screen without scrolling, but that's a separate issue.) Derrell - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] KeepFirstVisibleRowComplete(true) breaks when browser window is resized
I never sensed the name KeepFirstVisibleRowComplete properly. Looks to me that it only fixes the 1st row and in fact it does. Why don't we have KeepLastVisibleRowComplete also? Huh..this may also break underlying remote table to adjust the data model accordingly. Thanks. Kanugula. Thanks. Kanugula. Derrell Lipman wrote: > > On Mon, Jun 2, 2008 at 10:26 AM, kanugula <[EMAIL PROTECTED]> > wrote: > >> >> KeepFirstVisibleRowComplete(true) on Table works great when the browser >> size >> is normal. Some crazy users resize the browser to their personal >> preference. > > > Doesn't seem crazy to me. I believe users should be able to configure > their > environment however they like it. > > >> At that time, the last row is partially visible. > > > It sounds like you're describing exactly the intended behavior. The > property keepFirstVisibleRowComplete does just that: it keeps the FIRST > visible row complete as you scroll vertically. It implies nothing about > the > LAST visible row. > > >> Does KeepFirstVisibleRowComplete(true) work with specific screen size? > > > It works regardless of screen or window size. > > >> And is it a good practice to maximize the window on startup and block >> resize? > > > Absolutely not, in most circumstances. Whenever possible, window sizes > should be at the user's discretion. (You may define a minimum window size > that's required to see everything on the screen without scrolling, but > that's a separate issue.) > > Derrell > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://www.nabble.com/KeepFirstVisibleRowComplete%28true%29-breaks-when-browser-window-is-resized-tp17602597p17604957.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Disable log window
Pirlo wrote: > Finally I got...! thanks for all! > So how did you do it? Share your experience with us! Thomas > Pirlo wrote: > >> Thanks for the answer. In the build version the windows appears too. It´s >> not important the log in the sourve version. But in the build version I´d >> like it.. >> >> Where is the variable of makefile? I didn´t find it >> >> thron7 wrote: >> >>> Pirlo wrote: >>> Hi! I´m trying to disable the log pop up. But I don´t manage it.. I have searched other threads but I tried differents things like writing qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); or something similar and thats doesn´t work... please I need to close log pop up! thanks! >>> Pirlo, >>> >>> the log window should be off by default in the build version of your >>> app. Get back if this is not the case. >>> >>> If you want to disable the log window for the source version, try >>> setting APPLICATION_SOURCE_LOG_LEVEL = off in the Makefile and re-run >>> make. If that doesn't work, try removing all appenders in your app using >>> removeAllAppenders(), or setting your log appender to >>> qx.log.appender.RingBuffer, which stores all messages internally (but >>> this consumes memory!). >>> >>> HTH, >>> Thomas >>> >>> >>> - >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ >>> ___ >>> qooxdoo-devel mailing list >>> qooxdoo-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> >>> >> > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] using CSS style inside HorizontalSplitPane
Dan, mh, we have a similar scenario which works. Which widget is in your left hand side split? If you look at the Demobrowser, it uses style sheets (style.css and sourceview.css). They get included in the main app class with qx.html.StyleSheet.includeFile() and then the appropriate widgets get HTML 'id' attributes that reference the css locators (e.g. look for "qx_srcview"). So the link between widget and styles is through specific 'id' attributes. I think the trick is not to attach styles to the 'body' tag directly. HTH, Thomas Dan, Trif wrote: > Hi, > I have the following situation: a HorizontalSplitPane where I flow > into the RIGHT side a HTML content using a qx.ui.embed.HtmlEmbed object. > > My problem is if the HTML content has a CSS style defined for body that > style is applied for the LEFT side of the HorizontalSplitPane too. > > Any idea how implement this design so the CSS style to be applied only > to that HTML content (the right side of the splitpane) and not affect > other areas. > > > Regards, >Dan > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
[qooxdoo-devel] destruct() question
Hi,
Using Demo Browser terminology for simplicity.
If I have something like
var window = new qx.ui.window.Window();
var group = new qx.ui.groupbox.GroupBox();
var label = new qx.ui.basic.Label();
group.add(label);
window.add(group);
this.window=window;
this.group=group;
this.label=label;
1) Is it enough to just destruct "window" object only, instead of all the
underlying so many tiny objects like group, label,e.t.c.
destruct : function()
{
this._disposeObjects("window");
}
2) Wouldn't it be nice to have the above functionality in
disposeObjectDeep("window", 1) where the object will recursively look for
its elements, not only for Maps and Arrays as per the framework code.
3) Sometimes I have seen a long running dispose() in Demo Browser when you
jump from one page to another under examples. I believe it could be because
of the time taken for destruct() to complete
on last page. A dumb question. Can I put dispose() asynchronously without
the risk of same object collision?
Thanks.
Kanugula.
--
View this message in context:
http://www.nabble.com/destruct%28%29-question-tp17605645p17605645.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] destruct() question
kanugula wrote:
> Hi,
>
> Using Demo Browser terminology for simplicity.
>
> If I have something like
> var window = new qx.ui.window.Window();
> var group = new qx.ui.groupbox.GroupBox();
> var label = new qx.ui.basic.Label();
> group.add(label);
> window.add(group);
>
> this.window=window;
> this.group=group;
> this.label=label;
>
> 1) Is it enough to just destruct "window" object only, instead of all the
> underlying so many tiny objects like group, label,e.t.c.
> destruct : function()
> {
>this._disposeObjects("window");
> }
>
No. As a rule of thumb, you have to dispose everything you attached to
'this'. The '_disposeObjects("window")' call would really just dispose
the 'window' object.
> 2) Wouldn't it be nice to have the above functionality in
> disposeObjectDeep("window", 1) where the object will recursively look for
> its elements, not only for Maps and Arrays as per the framework code.
>
Actually, I would have expected it does just that, disposing referenced
objects recursively. Doesn't it?! You could check it with the
description given here:
http://qooxdoo.org/documentation/0.7/destructor_support#how_to_test_the_destructor
But the check might complain anyway since it would still find the
this.group and this.label members. Try it.
> 3) Sometimes I have seen a long running dispose() in Demo Browser when you
> jump from one page to another under examples. I believe it could be because
> of the time taken for destruct() to complete
> on last page. A dumb question. Can I put dispose() asynchronously without
> the risk of same object collision?
>
I'm not sure I'm getting you right here. If you switch between examples
in Demobrowser, you are switching between self-contained pages in the
demo iframe, which means there is a complete unload/load cycle, and I
don't think there is a way around it. And yes, the disposer runs on
unload which consumes time (but also prevents memory pollution in the
browser). But you cannot run the disposer earlier - well, in fact you
can, but then the whole demo application is reduced to a frozen image
where nothing continues to work, since all the objects that do the work
are gone :). And you cannot dispose after the new page has loaded - "in
the background" so to speak - since unfortunately different pages do not
run in different interpreter instances (I wish they would). And two apps
living side by side in the interpreter ... I'm not sure how this could
be handled.
HTH,
Thomas
> Thanks.
> Kanugula.
>
>
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Disable log window
Of course! I did you told me. I found the make variable for build log (APPLICATION_SOURCE_LOG_LEVEL) and I setted off. Then I made build and it worked! ;) thanks for all! thron7 wrote: > > Pirlo wrote: >> Finally I got...! thanks for all! >> > > So how did you do it? Share your experience with us! > > Thomas > >> Pirlo wrote: >> >>> Thanks for the answer. In the build version the windows appears too. >>> It´s >>> not important the log in the sourve version. But in the build version >>> I´d >>> like it.. >>> >>> Where is the variable of makefile? I didn´t find it >>> >>> thron7 wrote: >>> Pirlo wrote: > Hi! > > I´m trying to disable the log pop up. But I don´t manage it.. I have > searched other threads but I tried differents things like writing > qx.dev.log.Logger.ROOT_LOGGER.setMinLevel(qx.dev.log.Logger.LEVEL_OFF); > or > something similar and thats doesn´t work... > > please I need to close log pop up! > > thanks! > > Pirlo, the log window should be off by default in the build version of your app. Get back if this is not the case. If you want to disable the log window for the source version, try setting APPLICATION_SOURCE_LOG_LEVEL = off in the Makefile and re-run make. If that doesn't work, try removing all appenders in your app using removeAllAppenders(), or setting your log appender to qx.log.appender.RingBuffer, which stores all messages internally (but this consumes memory!). HTH, Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >> >> > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://www.nabble.com/Disable-log-window-tp17596301p17612716.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Help ! What's wrong with my class Inheritance?
thanks my friend,my problem has solved. I reMake the code ,and now it's work fine.The version that I use is the lasted release.thanks for your help! -- View this message in context: http://www.nabble.com/Help-%21-What%27s-wrong-with-my-class-Inheritance--tp17583936p17615180.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
[qooxdoo-devel] Is this a bug on IE7 with new tab creating,help!
what I use : IE7, QOOXDOO 0.7.3 now another problem, When I click the tree node , a new tab will be create,but the css style of the new tab has something wrong,the yellow bar on the top of the tab was lost, but it's work fine on firefox,anybody know why?thanks very much! -- View this message in context: http://www.nabble.com/Is-this-a-bug-on-IE7-with-new-tab-creating%2Chelp%21-tp17615223p17615223.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
