tag:old.nabble.com,2006:forum-3821Nabble - qooxdoo2009-12-01T07:58:46Zqooxdoo is an advanced javascript based web application framework. qooxdoo allows the user to build application-like graphical user interfaces with just a few lines of javascript. qooxdoo home is <a href="http://sourceforge.net/projects/qooxdoo/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26594163Re: Rpc* backend "harmonization"2009-12-01T07:58:46Z2009-12-01T07:58:46ZFritz Zaucker-3Hmm,
<br><br>neither the Internet nor the Epoch notation were invented my Microsoft ...
<br><br>Not a first hand source, but <a href="http://en.wikipedia.org/wiki/Unix_time" target="_top" rel="nofollow">http://en.wikipedia.org/wiki/Unix_time</a> gives
<br>some more information.
<br><br><a href="http://en.wikipedia.org/wiki/ISO_8601" target="_top" rel="nofollow">http://en.wikipedia.org/wiki/ISO_8601</a> has a discussion of this standard
<br>which has the advantage compared to Epoch notation, that leap seconds are
<br>handled correctly (they cannot be represented in Epoch it seems).
<br><br>On the other hand, Epoch makes it a lot easier to do date/time calculations.
<br><br>Cheers,
<br>Fritz
<br><br>On Tue, 1 Dec 2009, Gene Amtower wrote:
<br><div class='shrinkable-quote'><br>> Team,
<br>>
<br>> I've been researching the JSON Date problem a bit, and I wanted to share
<br>> some information from my web research. Since I'm working on an Oracle
<br>> RPC backend, I'd like to design and develop it once, so I'd prefer to
<br>> sort this out before doing the heavy lifting in my development.
<br>>
<br>> It is clear to all that the JSON standard does not offer a standard
<br>> method for dealing with dates, beyond the fact that they are to be
<br>> represented as a string in whatever form the developer chooses. This
<br>> leaves developers with a myriad of choices for handling JSON dates.
<br>> IMHO, Qooxdoo developers have chosen a string format that is uniquely
<br>> different than anyone else's chosen format, likely chosen before any
<br>> established practices began to surface in the industry. So, no fault is
<br>> intended towards the Qooxdoo development team. However, I wonder if
<br>> it's time to consider using a more common approach to JSON dates in
<br>> order to align with other development environments, although I recognize
<br>> that it may have downsides to Qooxdoo developers, especially WRT
<br>> backwards compatibility.
<br>>
<br>> I've come up with the following resources that you may want to review,
<br>> with related links provided at the end...
<br>>
<br>> On the json.org website, I found a lengthy PowerPoint presentation [1]
<br>> on the JSON standard that includes mention of new proposed extensions
<br>> for generating JSON data structures near the end (slide 40 of 55
<br>> slides). It references a js file containing proposed javascript code
<br>> [2] to extend various javascript prototypes in order to generate
<br>> standard JSON structures. Of course, one of these is the Date
<br>> prototype, and it might offer the Qooxdoo team a suitable pseudo-
<br>> standard since it comes directly from the JSON.org team.
<br>>
<br>> In addition, I found a really great discussion [3] while googling the
<br>> topic, which talks about two of the most common methods for encoding
<br>> dates in JSON structures. While one method is based on epoch time in
<br>> milliseconds since January 1st, 1970 UTC, I think many dislike it
<br>> because it's not human-readable. (Most of us would be hard-pressed to
<br>> be able to read milliseconds and readily relate them to a specific
<br>> date/time value!) This appears to be the method preferred by
<br>> VisualStudio and .Net tools. The other method mentioned is based on the
<br>> W3C ISO-8601 standard [4], which calls for date/time values in a
<br>> standard string representation of varying granularity such as
<br>> "1997-07-16", "1997-07-16T19:20+01:00", and "1997-07-16T19:20:30.45
<br>> +01:00", depending on the precision requirements of the usage. This is
<br>> much more human-readable and comes directly from the W3C standards body,
<br>> offering a more solid foundation for a choice in Qooxdoo direction.
<br>>
<br>> The prototype extension code contained in the json.org js file [2] is
<br>> based on this ISO-8601 standard, suggesting to me that this would be the
<br>> preferred approach despite its convergence away from the Microsoft
<br>> approach. (Is that so bad?)
<br>>
<br>> It's my opinion that any changes implemented in the Qooxdoo RPC methods
<br>> as a result of ongoing discussions should attempt to align Qooxdoo's
<br>> date-handling with a pseudo-standard in the industry. Keeping the
<br>> current implementation as a non-standard alternative (selected through a
<br>> class-level or project-level flag) would be OK for those who need it.
<br>> Additional comments and discussions would likely be beneficial to
<br>> Qooxdoo's future.
<br>>
<br>> Hope this is more helpful than disruptive! I welcome your thoughts on
<br>> the topic.
<br>>
<br>> Thanks,
<br>>
<br>> Gene
<br>>
<br>> [1] <a href="http://www.json.org/xml2006.ppt" target="_top" rel="nofollow">http://www.json.org/xml2006.ppt</a><br>> [2] <a href="http://json.org/json.js" target="_top" rel="nofollow">http://json.org/json.js</a><br>> [3] <a href="http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx" target="_top" rel="nofollow">http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx</a><br>> [4] <a href="http://www.w3.org/TR/NOTE-datetime" target="_top" rel="nofollow">http://www.w3.org/TR/NOTE-datetime</a><br>>
<br>> On Tue, 2009-12-01 at 02:01 -0800, panyasan wrote:
<br>>
<br>>> Hi Derrell,
<br>>>
<br>>>
<br>>> Derrell Lipman wrote:
<br>>>>
<br>>>> I just added the following to the jsonrpc_extensions wiki pgae:
<br>>>>
<br>>>> qooxdoo JSON dates
<br>>>>
<br>>>> Traditionally, qooxdoo JSON-RPC backends have been required to support a
<br>>>> non-standard feature of JSON, passing Date object instances as
<br>>>> instantiations of a Date object using syntax like new
<br>>>> Date(Date.UTC(2009,11,29,3,10,23,973)) since dates are not a part of the
<br>>>> JSON specification. This proposal moves qooxdoo Dates into the realm of
<br>>>> ?extension? rather than required functionality.
<br>>>>
<br>>>>
<br>>>
<br>>> I think this is a good idea, because supporting JSON Dates makes generating
<br>>> the json more complicated and not every application needs this functionality
<br>>> (I don't, for example). So servers might not implement this at all or offer
<br>>> a way of turning JSON dates "on" and "off". Maybe you might want to add a
<br>>> "system.useJsonDates(boolean v)" system method to your proposal?
<br>>>
<br>>> Cheers,
<br>>>
<br>>> Christian
<br>>
</div><br>--
<br>Oetiker+Partner AG tel: +41 62 775 9903 (direct)
<br>Fritz Zaucker +41 62 775 9900 (switch board)
<br>Aarweg 15 +41 79 675 0630 (mobile)
<br>CH-4600 Olten fax: +41 62 775 9905
<br>Schweiz web: www.oetiker.ch
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26594163&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26594118Question about delegate: delegate.bindItem() and controller.bindProperty() functions2009-12-01T07:55:59Z2009-12-01T07:55:59Zbenco<br>Hi again!
<br><br>I was wondering if the bindItem() function was called dynamically or if it
<br>was called only once after the model is attached to a controller...
<br><br>I have a very specific model to handle for trees where childs and labels
<br>contain sometimes arrays of values... Here is a little example:
<br><br>var model =
<br>{
<br> title:'root'
<br> childs:
<br> {
<br> {
<br> title:'title1',
<br> language:'fr',
<br> childs: ...
<br> },
<br> {
<br> [
<br> {
<br> title:'titre2-fr',
<br> language:'fr'
<br> },
<br> {
<br> title:'titre2-en',
<br> language:'en'
<br> }
<br> ],
<br> childs: ...
<br> }
<br> }
<br>};
<br><br><br>In my bindItem function, I included a test on the id model:
<br><br>if (typeof(id['getTitle'])!='undefined')
<br>{
<br> controller.bindProperty("title", "label", null, item, id);
<br>}
<br>else
<br>{
<br> var props = id.basename.split('"');
<br> for (var i=0, l=props.length; i<l; i++)
<br> {
<br> if (props[i]!='childs')
<br> {
<br> if (id.get(props[i]).getLanguage()==currentLanguage) break; //
<br>currentLanguage is defined outside of the function
<br> }
<br> }
<br>
<br> if (i>l) i=0;
<br>
<br> controller.bindProperty(i+".title", "label", null, item, id);
<br>}
<br><br>But it seems that the bindProperty isn't reaffected. I added some
<br>console.log() in order to check if first condition was retested but it seems
<br>to be done only once.
<br><br>So... Maybe I've done some mistakes elsewhere in my code but my question is
<br>simply:
<br><br>should this kind of bindItem() declaration work ?
<br><br>Regards,
<br><br>Benoît
<br>--
<br>View this message in context: <a href="http://n2.nabble.com/Question-about-delegate-delegate-bindItem-and-controller-bindProperty-functions-tp4094402p4094402.html" target="_top" rel="nofollow">http://n2.nabble.com/Question-about-delegate-delegate-bindItem-and-controller-bindProperty-functions-tp4094402p4094402.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26594118&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26593796Re: Rpc* backend "harmonization"2009-12-01T07:35:33Z2009-12-01T07:35:33ZGene Amtower<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
Team,<BR>
<BR>
I've been researching the JSON Date problem a bit, and I wanted to share some information from my web research. Since I'm working on an Oracle RPC backend, I'd like to design and develop it once, so I'd prefer to sort this out before doing the heavy lifting in my development.<BR>
<BR>
It is clear to all that the JSON standard does not offer a standard method for dealing with dates, beyond the fact that they are to be represented as a string in whatever form the developer chooses. This leaves developers with a myriad of choices for handling JSON dates. IMHO, Qooxdoo developers have chosen a string format that is uniquely different than anyone else's chosen format, likely chosen before any established practices began to surface in the industry. So, no fault is intended towards the Qooxdoo development team. However, I wonder if it's time to consider using a more common approach to JSON dates in order to align with other development environments, although I recognize that it may have downsides to Qooxdoo developers, especially WRT backwards compatibility.<BR>
<BR>
I've come up with the following resources that you may want to review, with related links provided at the end...<BR>
<BR>
On the json.org website, I found a lengthy PowerPoint presentation [1] on the JSON standard that includes mention of new proposed extensions for generating JSON data structures near the end (slide 40 of 55 slides). It references a js file containing proposed javascript code [2] to extend various javascript prototypes in order to generate standard JSON structures. Of course, one of these is the Date prototype, and it might offer the Qooxdoo team a suitable pseudo-standard since it comes directly from the JSON.org team.<BR>
<BR>
In addition, I found a really great discussion [3] while googling the topic, which talks about two of the most common methods for encoding dates in JSON structures. While one method is based on epoch time in milliseconds since January 1st, 1970 UTC, I think many dislike it because it's not human-readable. (Most of us would be hard-pressed to be able to read milliseconds and readily relate them to a specific date/time value!) This appears to be the method preferred by VisualStudio and .Net tools. The other method mentioned is based on the W3C ISO-8601 standard [4], which calls for date/time values in a standard string representation of varying granularity such as "1997-07-16", "1997-07-16T19:20+01:00", and "1997-07-16T19:20:30.45+01:00", depending on the precision requirements of the usage. This is much more human-readable and comes directly from the W3C standards body, offering a more solid foundation for a choice in Qooxdoo direction.<BR>
<BR>
The prototype extension code contained in the json.org js file [2] is based on this ISO-8601 standard, suggesting to me that this would be the preferred approach despite its convergence away from the Microsoft approach. (Is that so bad?)<BR>
<BR>
It's my opinion that any changes implemented in the Qooxdoo RPC methods as a result of ongoing discussions should attempt to align Qooxdoo's date-handling with a pseudo-standard in the industry. Keeping the current implementation as a non-standard alternative (selected through a class-level or project-level flag) would be OK for those who need it. Additional comments and discussions would likely be beneficial to Qooxdoo's future.<BR>
<BR>
Hope this is more helpful than disruptive! I welcome your thoughts on the topic.<BR>
<BR>
Thanks,<BR>
<BR>
Gene<BR>
<BR>
[1] <A HREF="http://www.json.org/xml2006.ppt" target="_top" rel="nofollow">http://www.json.org/xml2006.ppt</A><BR>
[2] <A HREF="http://json.org/json.js" target="_top" rel="nofollow">http://json.org/json.js</A><BR>
[3] <A HREF="http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx" target="_top" rel="nofollow">http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx</A><BR>
[4] <A HREF="http://www.w3.org/TR/NOTE-datetime" target="_top" rel="nofollow">http://www.w3.org/TR/NOTE-datetime</A><BR>
<BR>
On Tue, 2009-12-01 at 02:01 -0800, panyasan wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hi Derrell,</FONT>
<FONT COLOR="#000000">Derrell Lipman wrote:</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> I just added the following to the jsonrpc_extensions wiki pgae:</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> qooxdoo JSON dates</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> Traditionally, qooxdoo JSON-RPC backends have been required to support a</FONT>
<FONT COLOR="#000000">> non-standard feature of JSON, passing Date object instances as</FONT>
<FONT COLOR="#000000">> instantiations of a Date object using syntax like new</FONT>
<FONT COLOR="#000000">> Date(Date.UTC(2009,11,29,3,10,23,973)) since dates are not a part of the</FONT>
<FONT COLOR="#000000">> JSON specification. This proposal moves qooxdoo Dates into the realm of</FONT>
<FONT COLOR="#000000">> “extension” rather than required functionality.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">I think this is a good idea, because supporting JSON Dates makes generating</FONT>
<FONT COLOR="#000000">the json more complicated and not every application needs this functionality</FONT>
<FONT COLOR="#000000">(I don't, for example). So servers might not implement this at all or offer</FONT>
<FONT COLOR="#000000">a way of turning JSON dates "on" and "off". Maybe you might want to add a</FONT>
<FONT COLOR="#000000">"system.useJsonDates(boolean v)" system method to your proposal?</FONT>
<FONT COLOR="#000000">Cheers,</FONT>
<FONT COLOR="#000000">Christian </FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>
<br />------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br />_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26593796&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26593527Re: bug in qx.data.controller.Tree ?2009-12-01T07:18:54Z2009-12-01T07:18:54ZMartin Wittemann<br>Hi Benoît,
<br>thanks for the report. This really looks like a bug:
<br><a href="http://bugzilla.qooxdoo.org/show_bug.cgi?id=3151" target="_top" rel="nofollow">http://bugzilla.qooxdoo.org/show_bug.cgi?id=3151</a><br>I'll take care of it tomorrow.
<br>Best,
<br>Martin
<br><br><br><br>benco wrote:
<div class='shrinkable-quote'><br>>
<br>> Hello,
<br>>
<br>> I'm using the binding features on trees with delegate options in order to
<br>> manage specific models (PS: thanks Martin for your comment about the bug
<br>> 2632 - I didn't catch directly how to use the delegate options (great
<br>> feature by the way :-) ).
<br>>
<br>> I'm not sure if it is a bug - maybe I'm completely mistaken - but the
<br>> following code seems not work :
<br>>
<br>> var tree = new qx.ui.tree.Tree();
<br>> tree.controller = new qx.data.controller.Tree(null,tree);
<br>>
<br>> var model = qx.data.marshal.Json.createModel(datas); // datas = js object
<br>>
<br>> var delegate =
<br>> {
<br>> createItem: function()
<br>> {
<br>> var treeItem = new qx.ui.tree.TreeFolder();
<br>> treeItem.setUserData('homepage',new qx.ui.basic.Image());
<br>> treeItem.addWidget(treeItem.getUserData('homepage'));
<br>> treeItem.addLabel("");
<br>> treeItem.addWidget(new qx.ui.core.Spacer(), {flex: 1});
<br>> treeItem.setUserData('public',new qx.ui.basic.Image());
<br>> treeItem.addWidget(treeItem.getUserData('public'));
<br>> treeItem.setUserData('in_menu',new qx.ui.basic.Image());
<br>> treeItem.addWidget(treeItem.getUserData('in_menu'));
<br>> treeItem.setUserData('translated',new qx.ui.basic.Image());
<br>> treeItem.addWidget(treeItem.getUserData('translated'));
<br>> treeItem.setOpen(true);
<br>>
<br>> return treeItem;
<br>> },
<br>> configureItem: function(item)
<br>> {
<br>> item.getUserData('public').setWidth(80);
<br>> item.getUserData('in_menu').setWidth(70);
<br>> item.getUserData('translated').setWidth(40);
<br>> }
<br>> };
<br>>
<br>> tree.controller.setDelegate(delegate);
<br>> tree.controller.setModel(model);
<br>>
<br>> ...
<br>>
<br>>
<br>> It throws an error at runtime because when _setConfigureItem() is called,
<br>> it is looking for the root of the tree but it of course doesn't exists yet
<br>> at the first step: the error is "this.getTarget().getRoot() is null".
<br>>
<br>> I can manage it by adding a dummy root to my tree at init stage using the
<br>> createItem function but maybe it would be more intuitive to modify the
<br>> _setConfigureItem() function by setting the targeted treeItem as root of
<br>> the tree if it doesn't yet exists ?
<br>>
<br>> Regards,
<br>>
<br>> Benoît.
<br>>
</div><br>--
<br>View this message in context: <a href="http://n2.nabble.com/bug-in-qx-data-controller-Tree-tp4093385p4094202.html" target="_top" rel="nofollow">http://n2.nabble.com/bug-in-qx-data-controller-Tree-tp4093385p4094202.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26593527&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26592922Get the height of a widgets shadow?2009-12-01T06:41:14Z2009-12-01T06:41:14Zjoakim_Hi.
<br><br>Is there a way to get the height of a widgets shadow? Thanks a lot.<p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26592813Re: change background and knob background slider?2009-12-01T06:34:46Z2009-12-01T06:34:46ZFabian JakobsHi skar,
<br><br>there are two ways to style a widget, which apply to the Slider as well:
<br><br>1. Set the properties directly
<br><br>You can style the background by setting properties on the slider. You
<br>can access the knob using
<br>slider.getChildcontrol("knob"). The background of a widget is usually
<br>defined using the "decorator" property.
<br><br>2. Use themes
<br><br>You can define the look of a slider using the appearance theme. This is
<br>how the slider is styled in the framework:
<br><br> "slider" :
<br> {
<br> style : function(states)
<br> {
<br> var decorator;
<br><br> var focused = !!states.focused;
<br> var invalid = !!states.invalid;
<br> var disabled = !!states.disabled;
<br><br> if (focused && invalid && !disabled) {
<br> decorator = "input-focused-invalid";
<br> } else if (focused && !invalid && !disabled) {
<br> decorator = "input-focused";
<br> } else if (disabled) {
<br> decorator = "input-disabled";
<br> } else if (!focused && invalid && !disabled) {
<br> decorator = "border-invalid";
<br> } else {
<br> decorator = "input";
<br> }
<br><br> return {
<br> decorator : decorator
<br> }
<br> }
<br> },
<br><br> "slider/knob" :
<br> {
<br> include : "button-frame",
<br><br> style : function(states)
<br> {
<br> return {
<br> decorator : states.disabled ?
<br>"scrollbar-slider-horizontal-disabled" :
<br> "scrollbar-slider-horizontal",
<br> shadow: undefined,
<br> height : 14,
<br> width : 14
<br> };
<br> }
<br> },
<div class='shrinkable-quote'><br>> Hi,
<br>>
<br>> How do I set a background image/color to the slider and also color/image
<br>> to the slider's knob?
<br>>
<br>> see <a href="http://vps.net/" target="_top" rel="nofollow">http://vps.net/</a> for an example slider I like to emulate. It has the
<br>> custom knox, thinner slider bg and also markings for the possible step
<br>> values.
<br>>
<br>> For me, the step values aren't important. But I'd like to customize the
<br>> knob and the rest of the slider to have different bg color and also an
<br>> image for the knob and another image repeated inside the slider bg.
<br>>
<br>> cheers,
<br>> skar.
<br>>
<br>>
</div><br><br>--
<br>Fabian Jakobs
<br>JavaScript Framework Developer
<br><br>1&1 Internet AG - Web Technologies
<br>Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
<br>Telefon: +49 721 91374-6784
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26592813&i=0" target="_top" rel="nofollow">fabian.jakobs@...</a>
<br><br>Amtsgericht Montabaur / HRB 6484
<br>Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
<br>Aufsichtsratsvorsitzender: Michael Scheeren
<br><br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26592813&i=1" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26590994bug in qx.data.controller.Tree ?2009-12-01T04:29:50Z2009-12-01T04:29:50Zbenco<br>Hello,
<br><br>I'm using the binding features on trees with delegate options in order to
<br>manage specific models (PS: thanks Martin for your comment about the bug
<br>2632 - I didn't catch directly how to use the delegate options (great
<br>feature by the way :-) ).
<br><br>I'm not sure if it is a bug - maybe I'm completely mistaken - but the
<br>following code seems not work :
<br><br>var tree = new qx.ui.tree.Tree();
<br>tree.controller = new qx.data.controller.Tree(null,tree);
<br><br>var model = qx.data.marshal.Json.createModel(datas); // datas = js object
<br><br>var delegate =
<br>{
<br> createItem: function()
<br> {
<br> var treeItem = new qx.ui.tree.TreeFolder();
<br> treeItem.setUserData('homepage',new qx.ui.basic.Image());
<br> treeItem.addWidget(treeItem.getUserData('homepage'));
<br> treeItem.addLabel("");
<br> treeItem.addWidget(new qx.ui.core.Spacer(), {flex: 1});
<br> treeItem.setUserData('public',new qx.ui.basic.Image());
<br> treeItem.addWidget(treeItem.getUserData('public'));
<br> treeItem.setUserData('in_menu',new qx.ui.basic.Image());
<br> treeItem.addWidget(treeItem.getUserData('in_menu'));
<br> treeItem.setUserData('translated',new qx.ui.basic.Image());
<br> treeItem.addWidget(treeItem.getUserData('translated'));
<br> treeItem.setOpen(true);
<br>
<br> return treeItem;
<br> },
<br> configureItem: function(item)
<br> {
<br> item.getUserData('public').setWidth(80);
<br> item.getUserData('in_menu').setWidth(70);
<br> item.getUserData('translated').setWidth(40);
<br> }
<br>};
<br>
<br>tree.controller.setDelegate(delegate);
<br>tree.controller.setModel(model);
<br><br>...
<br><br><br>It throws an error at runtime because when _setConfigureItem() is called, it
<br>is looking for the root of the tree but it of course doesn't exists yet at
<br>the first step: the error is "this.getTarget().getRoot() is null".
<br><br>I can manage it by adding a dummy root to my tree at init stage using the
<br>createItem function but maybe it would be more intuitive to modify the
<br>_setConfigureItem() function by setting the targeted treeItem as root of the
<br>tree if it doesn't yet exists ?
<br><br>Regards,
<br><br>Benoît.
<br>--
<br>View this message in context: <a href="http://n2.nabble.com/bug-in-qx-data-controller-Tree-tp4093385p4093385.html" target="_top" rel="nofollow">http://n2.nabble.com/bug-in-qx-data-controller-Tree-tp4093385p4093385.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26590994&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26591339change background and knob background slider?2009-12-01T04:18:52Z2009-12-01T04:18:52Zskar karthikeyanHi,
<br><br>How do I set a background image/color to the slider and also color/image
<br>to the slider's knob?
<br><br>see <a href="http://vps.net/" target="_top" rel="nofollow">http://vps.net/</a> for an example slider I like to emulate. It has the
<br>custom knox, thinner slider bg and also markings for the possible step
<br>values.
<br><br>For me, the step values aren't important. But I'd like to customize the
<br>knob and the rest of the slider to have different bg color and also an
<br>image for the knob and another image repeated inside the slider bg.
<br><br>cheers,
<br>skar.
<br><br>--
<br>--
<br>The life so short, the craft so long to learn.
<br><br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26591339&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26590787Re: Python docstring format: how to extract API information?2009-12-01T04:09:57Z2009-12-01T04:09:57Zthron7-2<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The patched pythondoc.py is in tool/admin/bin,<br>
tool/data/py contains doc templates for modules, classes and
functions/methods,<br>
and, yes, there is probably no single Python module in the tool section
that I could offer as a well-documented sample :-/<br>
<br>
T.<br>
</tt><br>
panyasan wrote:
<blockquote cite="mid:1259664331581-4092963.post@n2.nabble.com" type="cite">
<pre wrap="">Ups. Sorry, didn't event think to consult the manual after looking through
some python scripts in the tool/ folder, which did not contain any API
documentation. Probably I missed the ones which did. Thanks!
thron7-2 wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Fortunately, dear Christian, has this issue been addressed in the
qooxdoo before :). As usual, it's "somewhere" in the Wiki:
<a class="moz-txt-link-freetext" href="http://qooxdoo.org/documentation/0.7/python_module_documentation" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.7/python_module_documentation</a>
The base line is: We're using a patched version of Fredi Lundh's
"pythondoc" doc generator. There is tooling to extract XML from
JDoc-like comments and then convert this XML into Apiviewer data files,
so they can be viewed in the Apiviewer. Probably all a bit rusty, but
the basics are there. Bugs are welcome :).
Thomas
panyasan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi everybody,
this is a point touching both the toolchain and the json-rpc python
backend:
coming from PHP to python, I was struck by the fact that there doesn't
seem
to be any standard way to add parseable signature documentation to
methods.
As I write in the introspection extension proposal:
"methodSignature is currently not implemented, because we don’t know how
to
infer types from Python code’s API documentation. Like PHP and unlike
Java,
Python is a dynamic language and doesn’t have fixed return and parameter
types. In PHP, one can analyze the docstring for @return and @param tags,
but that doesn’t seem to be the case in the Python world."
PHP simply copies the JavaDoc standard with more or less satifsfying
results, but it is good enough to extract information that can be used
for
introspection (the array type being a headache). However, for python,
there
seem to be zillion proposals, but no standard. Correct me if I am wrong.
Thanks,
Christian
</pre>
</blockquote>
<pre wrap="">------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a>
_______________________________________________
qooxdoo-devel mailing list
<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26590787&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
<br />------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br />_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26590787&i=1" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26590230Re: Rpc* backend "harmonization"2009-12-01T03:19:03Z2009-12-01T03:19:03ZStefan VolbersHey hey,
<br><br>+1 me too.
<br>Performance is king.
<br><br>Greetings,
<br>Stefan
<br><br>Helder Magalhães wrote:
<div class='shrinkable-quote'><br>> Hi everone,
<br>>
<br>>
<br>>
<br>> Derrell Lipman wrote:
<br>>> I just added the following to the jsonrpc_extensions wiki pgae:
<br>>>
<br>>> qooxdoo JSON dates [...]
<br>>>
<br>>
<br>> +1 for completely moving the date object [1] to an extension [2]. It's also
<br>> not natively supported by JSON and it would help fixing bug 1400 [3]:
<br>> whenever this extension was not being used, the browser native JSON support
<br>> could then be used, which would mean a significant performance boost. :-)
<br>>
<br>>
<br>> Cheers,
<br>> Helder
<br>>
<br>>
<br>> [1] <a href="http://qooxdoo.org/documentation/jsonrpc_server_specs#date_objects" target="_top" rel="nofollow">http://qooxdoo.org/documentation/jsonrpc_server_specs#date_objects</a><br>> [2] <a href="http://qooxdoo.org/documentation/jsonrpc_extensions#qooxdoo_json_dates" target="_top" rel="nofollow">http://qooxdoo.org/documentation/jsonrpc_extensions#qooxdoo_json_dates</a><br>> [3] <a href="http://bugzilla.qooxdoo.org/show_bug.cgi?id=1400" target="_top" rel="nofollow">http://bugzilla.qooxdoo.org/show_bug.cgi?id=1400</a></div><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26590230&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26590087Re: Rpc* backend "harmonization"2009-12-01T03:06:05Z2009-12-01T03:06:05ZHelder MagalhãesHi everone,
<br><br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Derrell Lipman wrote:</div>
<div class="quote-message">I just added the following to the jsonrpc_extensions wiki pgae:
<br><br>qooxdoo JSON dates [...]
</div>
</div></blockquote>
+1 for completely moving the date object [1] to an extension [2]. It's also not natively supported by JSON and it would help fixing bug 1400 [3]: whenever this extension was not being used, the browser native JSON support could then be used, which would mean a significant performance boost. :-)
<br><br><br>Cheers,
<br> Helder
<br><br><br>[1] <a href="http://qooxdoo.org/documentation/jsonrpc_server_specs#date_objects" target="_top" rel="nofollow">http://qooxdoo.org/documentation/jsonrpc_server_specs#date_objects</a><br>[2] <a href="http://qooxdoo.org/documentation/jsonrpc_extensions#qooxdoo_json_dates" target="_top" rel="nofollow">http://qooxdoo.org/documentation/jsonrpc_extensions#qooxdoo_json_dates</a><br>[3] <a href="http://bugzilla.qooxdoo.org/show_bug.cgi?id=1400" target="_top" rel="nofollow">http://bugzilla.qooxdoo.org/show_bug.cgi?id=1400</a><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26589850Re: Python docstring format: how to extract API information?2009-12-01T02:45:31Z2009-12-01T02:45:31Zpanyasan<br>Ups. Sorry, didn't event think to consult the manual after looking through
<br>some python scripts in the tool/ folder, which did not contain any API
<br>documentation. Probably I missed the ones which did. Thanks!
<br><br><br><br>thron7-2 wrote:
<div class='shrinkable-quote'><br>>
<br>> Fortunately, dear Christian, has this issue been addressed in the
<br>> qooxdoo before :). As usual, it's "somewhere" in the Wiki:
<br>> <a href="http://qooxdoo.org/documentation/0.7/python_module_documentation" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.7/python_module_documentation</a><br>>
<br>> The base line is: We're using a patched version of Fredi Lundh's
<br>> "pythondoc" doc generator. There is tooling to extract XML from
<br>> JDoc-like comments and then convert this XML into Apiviewer data files,
<br>> so they can be viewed in the Apiviewer. Probably all a bit rusty, but
<br>> the basics are there. Bugs are welcome :).
<br>>
<br>> Thomas
<br>>
<br>> panyasan wrote:
<br>>> Hi everybody,
<br>>>
<br>>> this is a point touching both the toolchain and the json-rpc python
<br>>> backend:
<br>>> coming from PHP to python, I was struck by the fact that there doesn't
<br>>> seem
<br>>> to be any standard way to add parseable signature documentation to
<br>>> methods.
<br>>> As I write in the introspection extension proposal:
<br>>>
<br>>> "methodSignature is currently not implemented, because we don’t know how
<br>>> to
<br>>> infer types from Python code’s API documentation. Like PHP and unlike
<br>>> Java,
<br>>> Python is a dynamic language and doesn’t have fixed return and parameter
<br>>> types. In PHP, one can analyze the docstring for @return and @param tags,
<br>>> but that doesn’t seem to be the case in the Python world."
<br>>>
<br>>> PHP simply copies the JavaDoc standard with more or less satifsfying
<br>>> results, but it is good enough to extract information that can be used
<br>>> for
<br>>> introspection (the array type being a headache). However, for python,
<br>>> there
<br>>> seem to be zillion proposals, but no standard. Correct me if I am wrong.
<br>>>
<br>>> Thanks,
<br>>>
<br>>> Christian
<br>>>
<br>>
<br>> ------------------------------------------------------------------------------
<br>> Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>> a free event focused on virtualization and cloud computing.
<br>> Attend in-depth sessions from your desk. Your couch. Anywhere.
<br>> <a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>> _______________________________________________
<br>> qooxdoo-devel mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26589850&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br>> <a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br>>
<br>>
</div><br>--
<br>View this message in context: <a href="http://n2.nabble.com/Python-docstring-format-how-to-extract-API-information-tp4092900p4092963.html" target="_top" rel="nofollow">http://n2.nabble.com/Python-docstring-format-how-to-extract-API-information-tp4092900p4092963.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26589850&i=1" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26589737Re: Python docstring format: how to extract API information?2009-12-01T02:35:29Z2009-12-01T02:35:29Zthron7-2Fortunately, dear Christian, has this issue been addressed in the
<br>qooxdoo before :). As usual, it's "somewhere" in the Wiki:
<br><a href="http://qooxdoo.org/documentation/0.7/python_module_documentation" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.7/python_module_documentation</a><br><br>The base line is: We're using a patched version of Fredi Lundh's
<br>"pythondoc" doc generator. There is tooling to extract XML from
<br>JDoc-like comments and then convert this XML into Apiviewer data files,
<br>so they can be viewed in the Apiviewer. Probably all a bit rusty, but
<br>the basics are there. Bugs are welcome :).
<br><br>Thomas
<br><br>panyasan wrote:
<div class='shrinkable-quote'><br>> Hi everybody,
<br>>
<br>> this is a point touching both the toolchain and the json-rpc python backend:
<br>> coming from PHP to python, I was struck by the fact that there doesn't seem
<br>> to be any standard way to add parseable signature documentation to methods.
<br>> As I write in the introspection extension proposal:
<br>>
<br>> "methodSignature is currently not implemented, because we don’t know how to
<br>> infer types from Python code’s API documentation. Like PHP and unlike Java,
<br>> Python is a dynamic language and doesn’t have fixed return and parameter
<br>> types. In PHP, one can analyze the docstring for @return and @param tags,
<br>> but that doesn’t seem to be the case in the Python world."
<br>>
<br>> PHP simply copies the JavaDoc standard with more or less satifsfying
<br>> results, but it is good enough to extract information that can be used for
<br>> introspection (the array type being a headache). However, for python, there
<br>> seem to be zillion proposals, but no standard. Correct me if I am wrong.
<br>>
<br>> Thanks,
<br>>
<br>> Christian
<br>>
</div><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26589737&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26589602Python docstring format: how to extract API information?2009-12-01T02:23:40Z2009-12-01T02:23:40Zpanyasan<br>Hi everybody,
<br><br>this is a point touching both the toolchain and the json-rpc python backend:
<br>coming from PHP to python, I was struck by the fact that there doesn't seem
<br>to be any standard way to add parseable signature documentation to methods.
<br>As I write in the introspection extension proposal:
<br><br>"methodSignature is currently not implemented, because we don’t know how to
<br>infer types from Python code’s API documentation. Like PHP and unlike Java,
<br>Python is a dynamic language and doesn’t have fixed return and parameter
<br>types. In PHP, one can analyze the docstring for @return and @param tags,
<br>but that doesn’t seem to be the case in the Python world."
<br><br>PHP simply copies the JavaDoc standard with more or less satifsfying
<br>results, but it is good enough to extract information that can be used for
<br>introspection (the array type being a headache). However, for python, there
<br>seem to be zillion proposals, but no standard. Correct me if I am wrong.
<br><br>Thanks,
<br><br>Christian
<br>--
<br>View this message in context: <a href="http://n2.nabble.com/Python-docstring-format-how-to-extract-API-information-tp4092900p4092900.html" target="_top" rel="nofollow">http://n2.nabble.com/Python-docstring-format-how-to-extract-API-information-tp4092900p4092900.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26589602&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26589360Re: Rpc* backend "harmonization"2009-12-01T02:01:33Z2009-12-01T02:01:33Zpanyasan<br>Hi Derrell,
<br><br><br>Derrell Lipman wrote:
<div class='shrinkable-quote'><br>>
<br>> I just added the following to the jsonrpc_extensions wiki pgae:
<br>>
<br>> qooxdoo JSON dates
<br>>
<br>> Traditionally, qooxdoo JSON-RPC backends have been required to support a
<br>> non-standard feature of JSON, passing Date object instances as
<br>> instantiations of a Date object using syntax like new
<br>> Date(Date.UTC(2009,11,29,3,10,23,973)) since dates are not a part of the
<br>> JSON specification. This proposal moves qooxdoo Dates into the realm of
<br>> “extension” rather than required functionality.
<br>>
<br>>
</div><br>I think this is a good idea, because supporting JSON Dates makes generating
<br>the json more complicated and not every application needs this functionality
<br>(I don't, for example). So servers might not implement this at all or offer
<br>a way of turning JSON dates "on" and "off". Maybe you might want to add a
<br>"system.useJsonDates(boolean v)" system method to your proposal?
<br><br>Cheers,
<br><br>Christian
<br>--
<br>View this message in context: <a href="http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4092820.html" target="_top" rel="nofollow">http://n2.nabble.com/Rpc-backend-harmonization-tp4075821p4092820.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26589360&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26588842[SOLVED] generator and generic accesses to qx.ui.*2009-12-01T01:20:54Z2009-12-01T01:20:54Zbenco<br>Hi thron7-2,
<br><br>Sorry for the lack of detailed explanations... There wasn't any compilation
<br>errors but the specified widget classes weren't found at runtime. The
<br>compilation errors occured only when I add i the "include" key in my config
<br>file... but it's now OK. Thanks!
<br><br>Regards,
<br><br>Benoît.
<br><br>PS: @Matt: Thank you too !
<br><br><br><br>thron7-2 wrote:
<div class='shrinkable-quote'><br>>
<br>> Hi Benoit,
<br>>
<br>>> if (level>0)
<br>>> {
<br>>> new qx.ui[packageNames[0]].{widgetName}(...)
<br>>> }
<br>>> else new qx.ui[packageNames[1]].{widgetName}(...)
<br>>>
<br>>>
<br>>> But as I expected, the generator can't recognise the kind of
<br>>> declaration...
<br>>
<br>> Meaning what? Do you get errors at compile time, or later at run time in
<br>> the browser? You should be more specific about the error case.
<br>>
<br>>>
<br>>> How can I force it the inclusion the targeted classes ? I tried to use
<br>>> the
<br>>> "include" config key like it:
<br>>>
<br>>> "include" : ["qx.ui.toolbar.*","qx.ui.menu.*"]
<br>>>
<br>>> but it throws an error "No such file or directory" [Errno 2] as if I
<br>>> sould
<br>>> specify path-like strings...
<br>>
<br>> No, the syntax is ok. It's also the right intuition, with this setting you
<br>> can draw the set of classes into your application. - In which job did you
<br>> specify this key? It should be "source-script" and "build-script", to have
<br>> them in both source and build versions. Did you mix it up with the
<br>> top-level "include" key?! (s. [1] vs. [2])
<br>>
<br>>> Also notice that this factory class is called
<br>>> as a library in my main application, so maybe the "include" directive
<br>>> isn't
<br>>> located at the good place ?
<br>>
<br>> You're right. Using the "include" key needs to be done in the config file
<br>> of main application. The alternative is what Matt suggested, using #use()
<br>> compiler hints in one of the library classes.
<br>>
<br>> T.
<br>>
<br>> [1]
<br>> <a href="http://qooxdoo.org/documentation/0.8/generator_config_ref#include_top-level" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.8/generator_config_ref#include_top-level</a><br>> [2] <a href="http://qooxdoo.org/documentation/0.8/generator_config_ref#include" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.8/generator_config_ref#include</a><br>>
<br>>
<br>> ------------------------------------------------------------------------------
<br>> Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>> a free event focused on virtualization and cloud computing.
<br>> Attend in-depth sessions from your desk. Your couch. Anywhere.
<br>> <a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>> _______________________________________________
<br>> qooxdoo-devel mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26588842&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br>> <a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br>>
<br>>
</div><br>--
<br>View this message in context: <a href="http://n2.nabble.com/generator-and-generic-accesses-to-qx-ui-tp4088148p4092664.html" target="_top" rel="nofollow">http://n2.nabble.com/generator-and-generic-accesses-to-qx-ui-tp4088148p4092664.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26588842&i=1" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26588560Re: how to set font for a tabview page's title label and a table's header labels?2009-12-01T00:59:25Z2009-12-01T00:59:25Zskar karthikeyanskar wrote:
<br>> It works :) However, the text doesn't have the indented look, with a
<br>> top, left and right border to make a box.
<br>I was doing this:
<br><br>> "tabview-page/button" : {
<br>> style : function(states) {
<br>> return {
<br>> font : "boldnormal"
<br>> };
<br>> }
<br>> }
<br>Now I styled just the label for the button alone and it works fine like
<br>this:
<br>> "tabview-page/button/label" : {
<br>> style : function(states) {
<br>> return {
<br>> font : "boldnormal"
<br>> };
<br>> }
<br>> }
<br><br>cheers,
<br>skar.
<br><br>--
<br>--
<br>The life so short, the craft so long to learn.
<br><br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26588560&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26588077Re: A few questions regarding development of custom widgets2009-12-01T00:25:37Z2009-12-01T00:25:37Zjoakim_Thank you, that solved it! :)
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Fritz Zaucker-3 wrote:</div>
<div class="quote-message shrinkable-quote">On Mon, 30 Nov 2009, joakim_ wrote:
<br><br>> I see. I try to get "this" or the widget inside an event, like this:
<br>>
<br>> fade.addListener("finish", function(e) {
<br>> this.hide();
<br>> overlay.hide();
<br>> });
<br><br> fade.addListener("finish", function(e) {
<br> this.hide();
<br> overlay.hide();
<br> }, this);
<br> ^^^^
<br><br>Cheers,
<br>Fritz
<br><br>--
<br>Oetiker+Partner AG tel: +41 62 775 9903 (direct)
<br>Fritz Zaucker +41 62 775 9900 (switch board)
<br>Aarweg 15 +41 79 675 0630 (mobile)
<br>CH-4600 Olten fax: +41 62 775 9905
<br>Schweiz web: www.oetiker.ch
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br>qooxdoo-devel@lists.sourceforge.net
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a></div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26581670Re: generator and generic accesses to qx.ui.*2009-11-30T12:52:40Z2009-11-30T12:52:40Zthron7-2Hi Benoit,
<br><br>> if (level>0)
<br>> {
<br>> new qx.ui[packageNames[0]].{widgetName}(...)
<br>> }
<br>> else new qx.ui[packageNames[1]].{widgetName}(...)
<br>>
<br>>
<br>> But as I expected, the generator can't recognise the kind of
<br>> declaration...
<br><br>Meaning what? Do you get errors at compile time, or later at run time in
<br>the browser? You should be more specific about the error case.
<br><br>>
<br>> How can I force it the inclusion the targeted classes ? I tried to use the
<br>> "include" config key like it:
<br>>
<br>> "include" : ["qx.ui.toolbar.*","qx.ui.menu.*"]
<br>>
<br>> but it throws an error "No such file or directory" [Errno 2] as if I sould
<br>> specify path-like strings...
<br><br>No, the syntax is ok. It's also the right intuition, with this setting you
<br>can draw the set of classes into your application. - In which job did you
<br>specify this key? It should be "source-script" and "build-script", to have
<br>them in both source and build versions. Did you mix it up with the
<br>top-level "include" key?! (s. [1] vs. [2])
<br><br>> Also notice that this factory class is called
<br>> as a library in my main application, so maybe the "include" directive
<br>> isn't
<br>> located at the good place ?
<br><br>You're right. Using the "include" key needs to be done in the config file
<br>of main application. The alternative is what Matt suggested, using #use()
<br>compiler hints in one of the library classes.
<br><br>T.
<br><br>[1]
<br><a href="http://qooxdoo.org/documentation/0.8/generator_config_ref#include_top-level" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.8/generator_config_ref#include_top-level</a><br>[2] <a href="http://qooxdoo.org/documentation/0.8/generator_config_ref#include" target="_top" rel="nofollow">http://qooxdoo.org/documentation/0.8/generator_config_ref#include</a><br><br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26581670&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26579516Trunk users: Enabled automatic Cache Deletion2009-11-30T10:25:09Z2009-11-30T10:25:09Zthron7-2Hi all!
<br><br>This is just to inform people using the trunk version of qooxdoo: With
<br>resolving bug#2149 (with r20846), the (compile) cache (but not the
<br>downloads!) will be cleared whenever the 'tool' section has changes. So
<br>don't be surprised if you now see a message saying "Cleaning compile
<br>cache, as tool chain is newer".
<br><br>This will get you rid of all misbehaviours that stem from changes in the
<br>tool chain which require a cache clean-up (although not all changes
<br>would need that). I hope this finds everybody's consent. Speak up if you
<br>disagree. The behaviour is controlled by a new config key,
<br>"cache/invalidate-on-tool-change", which is set to true in base.json,
<br>but you can set it to false in your jobs, if you're absolutely positive
<br>about controlling your cache yourself.
<br><br>Thomas
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26579516&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26578411Re: generator and generic accesses to qx.ui.*2009-11-30T09:20:35Z2009-11-30T09:20:35ZMatthew GregoryYou need to add the following to the top of your file
<br><br>/*
<br>#use(qx.ui.toolbar.*)
<br>#use(qx.ui.menu.*)
<br>*/
<br><br>I am not sure it if will pick up the classes correctly based on the
<br>wildchar, worth a shot. If it doesn't work you can use the same syntax
<br>but just list each class.
<br><br>HTH,
<br>Matt
<br><br>benco wrote:
<div class='shrinkable-quote'><br>> Hello,
<br>>
<br>> I'm currently working on a toolbar factory class by passing (using a
<br>> definition map and some static functions).
<br>>
<br>> I noticed that the qx.ui.toolbar and qx.ui.menu packages shares some common
<br>> widget names and I tried to simplify my code by adding some genericity like
<br>> it:
<br>>
<br>> var packageNames = ['menu','toolbar'];
<br>>
<br>> ...
<br>>
<br>> if (level>0)
<br>> {
<br>> new qx.ui[packageNames[0]].{widgetName}(...)
<br>> }
<br>> else new qx.ui[packageNames[1]].{widgetName}(...)
<br>>
<br>>
<br>> But as I expected, the generator can't recognise the kind of declaration...
<br>>
<br>> How can I force it the inclusion the targeted classes ? I tried to use the
<br>> "include" config key like it:
<br>>
<br>> "include" : ["qx.ui.toolbar.*","qx.ui.menu.*"]
<br>>
<br>> but it throws an error "No such file or directory" [Errno 2] as if I sould
<br>> specify path-like strings...
<br>>
<br>>
<br>> What is the correct syntax ? Also notice that this factory class is called
<br>> as a library in my main application, so maybe the "include" directive isn't
<br>> located at the good place ?
<br>>
<br>>
<br>> Thanks in advance for your help,
<br>>
<br>> Best,
<br>>
<br>> Benoît.
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
</div><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26578411&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26576377Re: rpc in qooxdoo2009-11-30T07:20:35Z2009-11-30T07:20:35ZBurak Arslan-4panyasan wrote:
<br>> What I would propose, however, concerning your SOAP contribution, is to
<br>> reorganize the contribution structure according to the new contribution
<br>> skeleton, i.e., separationg library code from demo application,. Also, I
<br>> would propose to put the backend in a dedicated directory (I use "services"
<br>> for the PHP and Python jsonrpc servers on the same level as the "source"
<br>> directory). I think this would make including and using your contrib much
<br>> easier.
<br>>
<br>>
<br><br>hi,
<br><br>fyi, i just did that. it's in the trunk. i.e.
<br><a href="https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/Soap/trunk" target="_top" rel="nofollow">https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/Soap/trunk</a><br><br>let me know how compliant it is :)
<br><br>best,
<br>burak
<br><br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576377&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26576315generator and generic accesses to qx.ui.*2009-11-30T07:17:01Z2009-11-30T07:17:01Zbenco<br>Hello,
<br><br>I'm currently working on a toolbar factory class by passing (using a
<br>definition map and some static functions).
<br><br>I noticed that the qx.ui.toolbar and qx.ui.menu packages shares some common
<br>widget names and I tried to simplify my code by adding some genericity like
<br>it:
<br><br>var packageNames = ['menu','toolbar'];
<br><br>...
<br><br>if (level>0)
<br>{
<br> new qx.ui[packageNames[0]].{widgetName}(...)
<br>}
<br>else new qx.ui[packageNames[1]].{widgetName}(...)
<br><br><br>But as I expected, the generator can't recognise the kind of declaration...
<br><br>How can I force it the inclusion the targeted classes ? I tried to use the
<br>"include" config key like it:
<br><br>"include" : ["qx.ui.toolbar.*","qx.ui.menu.*"]
<br><br>but it throws an error "No such file or directory" [Errno 2] as if I sould
<br>specify path-like strings...
<br><br><br>What is the correct syntax ? Also notice that this factory class is called
<br>as a library in my main application, so maybe the "include" directive isn't
<br>located at the good place ?
<br><br><br>Thanks in advance for your help,
<br><br>Best,
<br><br>Benoît.
<br><br><br><br><br><br><br><br>--
<br>View this message in context: <a href="http://n2.nabble.com/generator-and-generic-accesses-to-qx-ui-tp4088148p4088148.html" target="_top" rel="nofollow">http://n2.nabble.com/generator-and-generic-accesses-to-qx-ui-tp4088148p4088148.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26576315&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575833Re: A few questions regarding development of custom widgets2009-11-30T06:42:38Z2009-11-30T06:42:38ZFritz Zaucker-3On Mon, 30 Nov 2009, joakim_ wrote:
<br><br>> I see. I try to get "this" or the widget inside an event, like this:
<br>>
<br>> fade.addListener("finish", function(e) {
<br>> this.hide();
<br>> overlay.hide();
<br>> });
<br><br> fade.addListener("finish", function(e) {
<br> this.hide();
<br> overlay.hide();
<br> }, this);
<br> ^^^^
<br><br>Cheers,
<br>Fritz
<br><br>--
<br>Oetiker+Partner AG tel: +41 62 775 9903 (direct)
<br>Fritz Zaucker +41 62 775 9900 (switch board)
<br>Aarweg 15 +41 79 675 0630 (mobile)
<br>CH-4600 Olten fax: +41 62 775 9905
<br>Schweiz web: www.oetiker.ch
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575833&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575739Re: A few questions regarding development of custom widgets2009-11-30T06:38:25Z2009-11-30T06:38:25Zjoakim_Hi Daniel,
<br><br>Thank you for your answers.
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">d_wagner wrote:</div>
<div class="quote-message">Generally, you want to reuse widgets if you can because creating and
<br>disposing them is fairly expensive in terms of processing time and
<br>memory usage. I'd create the widgets in the constructor and just set
<br>their content/visibility/whatever properties in the slideUp and
<br>slideDown methods.
</div>
</div></blockquote>
Okey, I'll do it that way.
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">d_wagner wrote:</div>
<div class="quote-message">Hmm, global variables are almost never a good idea. What are you trying
<br>to achieve with this?
</div>
</div></blockquote>
I see. I try to get "this" or the widget inside an event, like this:
<br><br>fade.addListener("finish", function(e) {
<br> this.hide();
<br> overlay.hide();
<br>});
<br><br>Thanks! :)<p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575626Re: New contrib releases: RpcConsole, RpcPhp, RpcPython2009-11-30T06:29:21Z2009-11-30T06:29:21Zthron7-2<br><br>panyasan wrote:
<br>> Hi Thomas,
<br>>
<br>> these are great ideas and could be implemented in my - admittedly hacky -
<br>> approach! I agree that the request should be part of the data and that one
<br>> file should contain more than one request. I don't think I'll be able to do
<br>> this this week, but it will be coming!
<br><br>No worries!
<br><br>> Probably we need a "Record", "Pause",
<br>> "Discard" and "Save" Button for the recording of the requests, then.
<br>>
<br><br>That sounds very good. I could see using the interactive console to e.g.
<br>send a couple of requests to the server, covering the equivalence
<br>classes of all potential requests, save to file, and then use file
<br>tooling to insert additional generate requests that vary over some
<br>parameter, to get a real range coverage of the test cases.
<br><br>> As to a more comprehensive solution - I fully agree with you that something
<br>> more stable is needed. My solution was simply to be a quick-and-dirty way to
<br>> create interactive demos without a server backend. So I think that both
<br>> appraoches target different use cases.
<br>>
<br><br>I totally agree.
<br><br>By way of saying this I want to add a bit of the scenarios I have in
<br>mind. What I like to see possible (and is already partly supported with
<br>the current implementation) is the possibility to utilize it in unit
<br>tests. Given a - however fabricated - mockup data file of Rpc requests I
<br>want to do the following from my test code:
<br><br>a) switch to mockup mode (currently "on"), invoke my client applications
<br>classes so they end up doing Rpc requests that match the pre-fabricated
<br>ones, and are answered from the mock data; this is to offline unit-test
<br>the *client* classes
<br><br>b) in an entirely different test, switch to no mockup mode ("off"), read
<br>the *request* data from the mockup file, create corresponding Rpc
<br>requests and directly fire them against the server backend (ie.
<br>re-running the request), then *compare* the returned result against the
<br>*response* section of the mockup data; this is to mass unit-test the
<br>*server* backend
<br><br>T.
<br><br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575626&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575546Re: Can't theme Table Cells?2009-11-30T06:26:17Z2009-11-30T06:26:17Zjoakim_Ah I see, thanks! :)
<br><br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">d_wagner wrote:</div>
<div class="quote-message shrinkable-quote">Hi joakim,
<br><br>Correct, the table cells aren't widgets so they can't be themed using
<br>appearances. You could use the HTML cell renderer and use CSS to style
<br>the cells, or you could look into writing your own cell renderer.
<br><br><br>Regards,
<br>Daniel
<br><br>joakim_ schrieb:
<br>> Hi there.
<br>>
<br>> I trying to theme the table widget but can't find the appearance ID for the
<br>> cells. It's it not possible to theme the cells via the Appearance.js file?
<br>>
<br>> Thanks. :)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br>qooxdoo-devel@lists.sourceforge.net
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a></div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575176Re: Rpc* backend "harmonization"2009-11-30T05:57:41Z2009-11-30T05:57:41ZDerrell LipmanI just added the following to the jsonrpc_extensions wiki pgae:<br><br><h2 id="qooxdoo_json_dates">qooxdoo JSON dates</h2>
<div class="level2">
<p>
Traditionally, qooxdoo JSON-<acronym title="Remote Procedure Call">RPC</acronym>
backends have been required to support a non-standard feature of JSON,
passing Date object instances as instantiations of a Date object using
syntax like <code>new Date(Date.UTC(2009,11,29,3,10,23,973))</code>
since dates are not a part of the JSON specification. This proposal
moves qooxdoo Dates into the realm of “extension” rather than required
functionality.</p><p><br></p><p>Derrell</p><p><br></p></div>
<br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575176&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575249Re: New contrib releases: RpcConsole, RpcPhp, RpcPython2009-11-30T05:56:26Z2009-11-30T05:56:26Zpanyasan<br>Hi Thomas,
<br><br>these are great ideas and could be implemented in my - admittedly hacky -
<br>approach! I agree that the request should be part of the data and that one
<br>file should contain more than one request. I don't think I'll be able to do
<br>this this week, but it will be coming! Probably we need a "Record", "Pause",
<br>"Discard" and "Save" Button for the recording of the requests, then.
<br><br>As to a more comprehensive solution - I fully agree with you that something
<br>more stable is needed. My solution was simply to be a quick-and-dirty way to
<br>create interactive demos without a server backend. So I think that both
<br>appraoches target different use cases.
<br><br>So let's keep thinking and developing this further!
<br><br>Christian
<br><br>I see the need
<br><br>thron7-2 wrote:
<div class='shrinkable-quote'><br>>
<br>>
<br>>> MRpcMockup:
<br>>> - comfortable
<br>>> - tight coupling
<br>>> - relies on Rpc internals (unreliable interface)
<br>>> - only for ad-hoc, interactive usage
<br>>>
<br>>>
<br>> So, saving rpc traffic data to file is there, but I see you only capture
<br>> the response data. I'm not sure this is sufficient. You pick up
<br>> responses in the mockup mode by going through the hash of the rpc
<br>> signature (prob. over something like service-name/params), right?! But
<br>> the request signature is only captured as comments. I think it would be
<br>> better a part of the generated Json. Capture data should be
<br>> self-contained, to the extend that a single Json key (the request hash,
<br>> if you will) contains subkeys "request" and "response" that represent
<br>> both sides of the request in a standardized why. I think this would be
<br>> way more useful.
<br>>
<br>> The Json file format should also allow for more than one request per
<br>> file. This is probably nothing you could support on the capturing side,
<br>> but would be done by hand. But the replay facility should be able to
<br>> handle this, so you can pass, say, 1,000 requests within a single file.
<br>> Something like this:
<br>>
<br>> {
<br>>
<br>> "deb693849aab654cde5261a77ae8c0f41943dc60":
<br>> {
<br>> "request" :
<br>> {
<br>> "serverUrl" : "<a href="http://.../RpcPhp/1.0.1/services/index.php" target="_top" rel="nofollow">http://.../RpcPhp/1.0.1/services/index.php</a>",
<br>> "serviceName" : "qooxdoo.test",
<br>> "serviceMethod" : "echo",
<br>> "params" : ["Hello World"],
<br>> "serverData" : null
<br>> },
<br>> "response" :
<br>> {
<br>> "id" : 4711,
<br>> "error" : null,
<br>> "response" : "Client said: [Hello World]"
<br>> }
<br>> },
<br>>
<br>> "x5z693849aab654cde5261a77ae8c0f41943dc60":
<br>> {
<br>> "request" : ...,
<br>>
<br>> "response" : ...
<br>> },
<br>>
<br>> ...
<br>> }
<br>>
<br>> T.
<br>>
<br>> ------------------------------------------------------------------------------
<br>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
<br>> 30-Day
<br>> trial. Simplify your report design, integration and deployment - and focus
<br>> on
<br>> what you do best, core application coding. Discover what's new with
<br>> Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>> _______________________________________________
<br>> qooxdoo-devel mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575249&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br>> <a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br>>
<br>>
</div><br>--
<br>View this message in context: <a href="http://n2.nabble.com/New-contrib-releases-RpcConsole-RpcPhp-RpcPython-tp4084412p4087710.html" target="_top" rel="nofollow">http://n2.nabble.com/New-contrib-releases-RpcConsole-RpcPhp-RpcPython-tp4084412p4087710.html</a><br>Sent from the qooxdoo mailing list archive at Nabble.com.
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575249&i=1" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26575057Re: A few questions regarding development of custom widgets2009-11-30T05:48:01Z2009-11-30T05:48:01Zd_wagnerHi joakim,
<br><br>joakim_ schrieb:
<div class='shrinkable-quote'><br>> Hi there.
<br>>
<br>> I've some questions regarding development of custom widgets which I hope
<br>> someone can help me with.
<br>>
<br>> I developing a simple dialog widget which extends Composite. The dialog have
<br>> a slideDown and slideUp method as well as a overlay which fades in. The
<br>> dialog's content is set via the setLayout() property. The content should be
<br>> reset every time the dialog closes. So I'm wondering if it's a good practice
<br>> to create the dialog and overlay on-the-fly every time when using the
<br>> slideDown method and then remove it all when using the slideUp method, or
<br>> does this stuff belong to the Constructor?
</div><br>Generally, you want to reuse widgets if you can because creating and
<br>disposing them is fairly expensive in terms of processing time and
<br>memory usage. I'd create the widgets in the constructor and just set
<br>their content/visibility/whatever properties in the slideUp and
<br>slideDown methods.
<br><br>>
<br>> I also wondering what's the best way to define "this" throughout the widget
<br>> class? Should I put it in a global variable in the constructor like:
<br>>
<br>> dialog = this;
<br>>
<br>> or is there a better way?
<br><br>Hmm, global variables are almost never a good idea. What are you trying
<br>to achieve with this?
<br><br>>
<br>> Any help is very appreciated. Thanks! :)
<br>>
<br><br>Regards,
<br>Daniel
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26575057&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26574631Re: Can't theme Table Cells?2009-11-30T05:22:42Z2009-11-30T05:22:42Zd_wagnerHi joakim,
<br><br>Correct, the table cells aren't widgets so they can't be themed using
<br>appearances. You could use the HTML cell renderer and use CSS to style
<br>the cells, or you could look into writing your own cell renderer.
<br><br><br>Regards,
<br>Daniel
<br><br>joakim_ schrieb:
<br>> Hi there.
<br>>
<br>> I trying to theme the table widget but can't find the appearance ID for the
<br>> cells. It's it not possible to theme the cells via the Appearance.js file?
<br>>
<br>> Thanks. :)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26574631&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26574498Re: New contrib releases: RpcConsole, RpcPhp, RpcPython2009-11-30T05:12:12Z2009-11-30T05:12:12Zthron7-2<br>> MRpcMockup:
<br>> - comfortable
<br>> - tight coupling
<br>> - relies on Rpc internals (unreliable interface)
<br>> - only for ad-hoc, interactive usage
<br>>
<br>>
<br>So, saving rpc traffic data to file is there, but I see you only capture
<br>the response data. I'm not sure this is sufficient. You pick up
<br>responses in the mockup mode by going through the hash of the rpc
<br>signature (prob. over something like service-name/params), right?! But
<br>the request signature is only captured as comments. I think it would be
<br>better a part of the generated Json. Capture data should be
<br>self-contained, to the extend that a single Json key (the request hash,
<br>if you will) contains subkeys "request" and "response" that represent
<br>both sides of the request in a standardized why. I think this would be
<br>way more useful.
<br><br>The Json file format should also allow for more than one request per
<br>file. This is probably nothing you could support on the capturing side,
<br>but would be done by hand. But the replay facility should be able to
<br>handle this, so you can pass, say, 1,000 requests within a single file.
<br>Something like this:
<br><br>{
<br><br>"deb693849aab654cde5261a77ae8c0f41943dc60":
<br>{
<br>"request" :
<br>{
<br>"serverUrl" : "<a href="http://.../RpcPhp/1.0.1/services/index.php" target="_top" rel="nofollow">http://.../RpcPhp/1.0.1/services/index.php</a>",
<br>"serviceName" : "qooxdoo.test",
<br>"serviceMethod" : "echo",
<br>"params" : ["Hello World"],
<br>"serverData" : null
<br>},
<br>"response" :
<br>{
<br>"id" : 4711,
<br>"error" : null,
<br>"response" : "Client said: [Hello World]"
<br>}
<br>},
<br><br>"x5z693849aab654cde5261a77ae8c0f41943dc60":
<br>{
<br>"request" : ...,
<br><br>"response" : ...
<br>},
<br><br>...
<br>}
<br><br>T.
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26574498&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26574114Can't theme Table Cells?2009-11-30T04:44:20Z2009-11-30T04:44:20Zjoakim_Hi there.
<br><br>I trying to theme the table widget but can't find the appearance ID for the cells. It's it not possible to theme the cells via the Appearance.js file?
<br><br>Thanks. :)<p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26573679Re: New contrib releases: RpcConsole, RpcPhp, RpcPython2009-11-30T04:08:23Z2009-11-30T04:08:23Zthron7-2<br><br><br>> MRpcMockup:
<br>> - comfortable
<br>> - tight coupling
<br>> - relies on Rpc internals (unreliable interface)
<br>> - only for ad-hoc, interactive usage
<br>>
<br><br>Ah, wait, you *do* provide for saving request data to file, so that's
<br>good. I have to dig further...
<br><br>T.
<br><br>>
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26573679&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>tag:old.nabble.com,2006:post-26573418Re: New contrib releases: RpcConsole, RpcPhp, RpcPython2009-11-30T03:48:13Z2009-11-30T03:48:13Zthron7-2Hi Christian,
<br><br>I'm joining in to Derrell's hails, you're doing a really good job :). As
<br>I've promised to look at the RpcMockup issue, this post is mainly about it.
<br><br><br>> <a href="http://qooxdoo.org/contrib/project#rpcconsole" target="_top" rel="nofollow">http://qooxdoo.org/contrib/project#rpcconsole</a><br>> <a href="http://qooxdoo.org/contrib/project/rpcconsole" target="_top" rel="nofollow">http://qooxdoo.org/contrib/project/rpcconsole</a><br>>
<br>> This debugging tool should be pretty stable by now and could very well be
<br>> 1.0 soon. I am still waiting because I am still interested in feedback on
<br>> the mockup data generation feature
<br>> (<a href="http://qooxdoo.org/contrib/project/rpcconsole#creating_mockup_data" target="_top" rel="nofollow">http://qooxdoo.org/contrib/project/rpcconsole#creating_mockup_data</a>) through
<br>> the rpcconsole.MRpcMockup mixin.
<br><br>For one thing, I see you have taken a different approach than I had in
<br>mind with an additional transport. You chose to patch qx.io.remote.Rpc
<br>directly, which looks interesting but I would be curious about your
<br>rational. Your approach is more tightly integrated and hence offers a
<br>certain comfort ("monitor"ing a request exchange, then replaying it with
<br>the "on" mode). That's kind of cute, but relies on the qx.io.remote.Rpc
<br>implementation. I thought of a looser coupling using the Transport API,
<br>which will be probably much more stable than internals of the Rpc class.
<br>In my scenario the monitoring would be done by the rpcconsole itself,
<br>not the Rpc class, and the replaying would be achieved by switching to
<br>the Mockup transport class in the code, supplying the captured data.
<br>This requires code change, yes, but wouldn't you change your code, too,
<br>removing the use of the MRpcMockup mixin, or at least "on" and "monitor"
<br>modes, etc., before going into production?!
<br><br>Your approach is really charming for ad-hoc, interactive sessions, my
<br>requires more fiddling, saving trace data to a file, loading this file
<br>again, etc. But I'm really concerned about open and stable interfaces.
<br>What if you want to re-use captured data in regression tests, over and
<br>over again? What if, for large applications, you don't want to
<br>interactively capture the rpc traffic at all, but want to generate it
<br>from scratch?! These are the things I don't see possible with your approach.
<br><br>So my current summary would be:
<br><br>MRpcMockup:
<br> - comfortable
<br> - tight coupling
<br> - relies on Rpc internals (unreliable interface)
<br> - only for ad-hoc, interactive usage
<br><br>Mockup Transport class:
<br> - less comforable
<br> - loose coupling
<br> - relies on transport API and the Json data format for the rpc call
<br>trace (more stable interfaces)
<br> - good for automated tests, also with generated request data
<br><br>T.
<br><br><br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>qooxdoo-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26573418&i=0" target="_top" rel="nofollow">qooxdoo-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel</a><br><p>From forum: <a href="http://old.nabble.com/qooxdoo-devel-f3822.html" embed="fixTarget[3822]" target="_top" >qooxdoo-devel</a></p>