Hi Jim,
I'm working on a cms. Like in the colorpicker tool we have to give the user
the possibility to enter a color or to select one. And we save it of course
in a hex string in the database.
I took a snippet of lines from the colorpicker tool, but I think it should
be general available.
Jim H
Hi List,
I am migrating some qx based classes from 0.6.5 to 0.7.1.
I found that if the source file contains a comment like this:
/*!
*/
The migration script will fail with this error message (below). Removing the !
from the comment enables the migration script to succeed. Perhaps the script
Starting today, I have been getting this error ("this._tablePane has no
properties") on and off. Sometimes it happens (and when it does it happens
many times a second and doesn't stop) and sometimes things run fine. It is
happening in this code:
_oninterval:function(){if(this._updateContentPlanned
The appear event is fired when all the visible items are done drawing. I use
it all the time. I just attach it to one of the items that I know are
getting rendered. I have never used any other global event, just appear
attached onto one of the main things on my form.
Jim
www.D4PHP.org
www.D4PHP-Ho
Hello,
I have just put a preview of the qooxdoo component library (qcl) sample
application online:
http://m41s09.vlinux.de/qooxdoo/qcl_sample_app/frontend/build/
the qcl is already available form qooxdoo-contrib:
https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo
I am confused, why would you need it in qooxdoo when you can use the RGB
value in all color properties?
Jim
www.D4PHP.org
www.D4PHP-Hosting.com
On 9/17/07, westor <[EMAIL PROTECTED]> wrote:
>
>
> I could not find a method in qx.util.ColorUtil to convert a rgb string or
> a
> rgb array to a hex s
Jim, I did not know that! Thanks! C.
Jim Hunter schrieb:
> The appear event is fired when all the visible items are done drawing.
> I use it all the time. I just attach it to one of the items that I
> know are getting rendered. I have never used any other global event,
> just appear attached on
Thanks Jim, but I was looking for an event that fires after ALL widgets
are done, not just a particular one... I remember faintly that there was
a page in the documentation about the some "meta" events fired, but I
cannot find it anymore.
Christian
Jim Hunter schrieb:
> It's the appear event.
It's the appear event. You can attach code to the appear event of almost any
of your visible objects.
Jim
www.D4PHP.org
www.D4PHP-Hosting.com
On 9/17/07, bibliograph <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I was searching the documentation and the API but was not sucessful: is
> there an event
Hi,
I have seen in the source code that qx.ui.table will automatically
support a cell editor which is a subclass of qx.ui.window.Window for
editing cell content that is bigger than the cell. I was just about
writing one but then though that someone might have already done that.
Has anyone writ
Hello,
I was searching the documentation and the API but was not sucessful: is
there an event that is fired after all visible widgets have been
rendered? and what object fires it?
Thanks,
Christian
-
This SF.net email is s
westor schrieb:
> Thank you Fabian, Derrell,
>
> this looks pretty good. Also the celleditor is in place, I'm impressed ;-)
> As I noticed, the wrap of long lines now is default behaviour, I can forget
> my wrapping renderer... :-)
>
> Torsten
>
Sorry, I have to disappoint you. We decided to s
On Mon, 2007-09-17 at 10:52 -0400, Raul Gutierrez S. wrote:
> Hi,
>
> I am not sure if I am doing something wrong, if this is a bug in
> qx.theme.manager.Appearance or something with the Ext theme.
>
> I get this error in my Javascript console:
>
> "entry has no properties"
>
> and the correspo
Hi,
I am not sure if I am doing something wrong, if this is a bug in
qx.theme.manager.Appearance or something with the Ext theme.
I get this error in my Javascript console:
"entry has no properties"
and the corresponding lines of code in qx/theme/manager/Appearance.js
are:
// Fast fallba
Thank you again, Fabian. For all the others:
... this looks pretty good. Also the celleditor (focus indicator) is in
place, I'm impressed ;-)
As I noticed, the wrap of long lines now is default behaviour, I can forget
my wrapping renderer... :-)
Torsten
Fabian Jakobs-2 wrote:
>
> Hi,
>
> I hav
Thank you Fabian, Derrell,
this looks pretty good. Also the celleditor is in place, I'm impressed ;-)
As I noticed, the wrap of long lines now is default behaviour, I can forget
my wrapping renderer... :-)
Torsten
Derrell Lipman wrote:
>
> Fabian just checked in changes to Table to use div ta
On 9/17/07, dperez <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a table with a height of 100%, with a lot of data inside. I place
> the table inside a window whose height is 80%.
>
> The resulting height of the window is over 100%. Is this a bug?
Layout with percentages has some strange quirks.
Hi,
I have a table with a height of 100%, with a lot of data inside. I place
the table inside a window whose height is 80%.
The resulting height of the window is over 100%. Is this a bug?
Here is the code:
var vnt = new qx.ui.window.Window("My window");
var mo
Fabian, I solved my row order problem, and also the row select in FF works
well, if I use the solution of Dietrich:
this.getSelectionModel().getSelectedRanges()[0].minIndex
But I have still a question regarding the celleditor. Please have a look at
my question "Table DataCellRenderer problem in le
I prefer also a click cell event rather than a row event, as the column
information is sometimes very useful.
Fabian Jakobs-2 wrote:
>
> Yes this would be a good idea and maybe we should fire a "cell double
> click event" instead of a "row double click event" and pass the selected
> row and c
I could not find a method in qx.util.ColorUtil to convert a rgb string or a
rgb array to a hex string. Shouldn't it be there?
--
View this message in context:
http://www.nabble.com/missing-color-coverting-rgbtohex-tf4466433.html#a12735041
Sent from the qooxdoo-devel mailing list archive at Nabbl
On 9/17/07, westor <[EMAIL PROTECTED]> wrote:
>
> Fabian, I solved my row order problem, and also the row select in FF works
> well, if I use the solution of Dietrich:
> this.getSelectionModel().getSelectedRanges()[0].minIndex
> But I have still a question regarding the celleditor. Please have a lo
Hi,
I have finally come to the conclusion that HTML tables are not reliable
enough to render the table widget. I have finally switched back to a DIV
based rendering model. All other enhancements remain in place. The table
row height could not reliably been set to a fixed height. This change
sh
This test works ok in IE7 and FF 2
The column selection menu for the table is positioned ok, even though when
the window is vertically scrolled.
But my test is different. I have a regular HTML table, and try to position a
popup menu when clicking a data in a cell. I'm preparing a sample...
Fab
D Floss schrieb:
> I've just found qooxdoo and have been wandering around the site. I
> like many of the features. However, I do not see a couple of features
> that I expected like Accordion Style (aka Outlook) menus (i.e.
> scriptaculous or rialto) and a File Upload or "Browse" widget? Did I
>
Hi Dietrich,
>> Second double click events attached to the table scroller will also be
>> fired if the table header is double clicked. Since the public table API
>> does not provide a clean way to detect double clicks on table rows, I
>> have added a "rowdblclick" event to the table scroller.
>
Richard Bondi schrieb:
> Greetings,
>
> I had a problem with number format. Specifically, with es_MX for
> Mexico. I fixed it by changing
>
> frontend/framework/source/class/qx/locale/data/es_MX.js to:
>
> qx.locale.Locale.define("qx.locale.data.es_MX", {
> cldr_number_decimal_separator: ".",
rb,
According to my (somehow preliminar) knowledge of qooxdoo translation
infrastructure, one should probably create/change "es_MX.xml", including only
the change you are suggesting. All other default fields will revert to general
spanish ("es.xml"). Check out "en_US.xml" and "en.xml" for a go
Suggestion for prune:
Shouldn't prune bring back an array of the removed node id's? That would be
helpful for anyone who wants to associate other data (e.g. an array of
additional data, not displayed in the tree) together with the nodes.
I, for my needs, have overwritten prune like this:
prun
29 matches
Mail list logo
