Is it possible to have the generator show deprecated warnings during the
source and/or build step.
I only see warnings when the app is running (in firebug). Since so much has
been deprecated (and removed from trunk) recently - this would be extremely
helpful.
Thanks
Mike
--
View this message
I am also using Qooxdoo 0.8.3-pre
I had lots of problems with Qooxdoo 0.8.x and Firebug 1.3.x. relating to
html Frames.
I have been using Firebug 1.4 (with Firefox 3.0 & 3.5) seems to work pretty
well.
You might want to update. You may have to create a new Firefox profile
before installing
Martin,
I did a quick test and your suggestion seems to work - thanks.
I am a little concerned about the Warning in the API docs for
Widget.getChildControl() .
"Warning: This method exposes widget internals and modifying the returned
sub widget may bring the widget into an inconsistent state. A
Gene Amtower wrote:
>
> Mike,
>
> I have to wonder if the problem is because the Qooxdoo "SelectBox" is
> like an HTML single-height select box, while the Qooxdoo "List" is like
> an HTML select box displaying multiple lines. In HTML, a LIst is a
> display text layout object, not a select bo
Martin,
I guess my problem arises because the I was originally using the ComboBox
which has (or did have) the behavior I want. But in 0.8.x I can no longer
set a ComboBox to "readOnly", so I had to switch to a SelectBox.
To tell the truth - it would be much easier for me if ComboBox still
su
Upload was missing - here it is
http://www.nabble.com/file/p24078320/Application.js Application.js
--
View this message in context:
http://www.nabble.com/SelectionAPI-woes-%28part-1%29-tp24077884p24078320.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
---
I am finding the new Selection API really hard to work with.
1. ChangeSelection events and Add.
It appears SelectBox is firing a ChangeSelection event when the first
ListItem is added. I am using the trunk (0.8.3-pre) version.
I would expect a ChangeSelection event to be triggered by a call to
Chris,
I took your example and modified it to more closely match one of the places
where I am having the problem.
Summary of changes:
1. created a new class (TableTest) which extends qx.ui.container.Composite
2. copied the logic from your Application.js into TableTest.js
2. replaced the SplitPa
I am using Qooxdoo 0.8.3-pre (updated as of last week)
as of revision 17204, the preferred height of a table is hard coded to 400
pixels (in Pane.js)
See: http://bugzilla.qooxdoo.org/show_bug.cgi?id=1476
Without defining a specific pixel height, how do I get a table (or
TreeVirtual) to scale co
The Radio Buttons in 0.8.3pre do not allow you set a user defined value.
getValue() returns either true/false. setValue(userVal) throws an error if
userVal is not a boolean.
Assertion error! Invalid incoming value for property 'value' of class
'qx.ui.form.RadioButton': Expected value to be a bo
thron7-2 wrote:
>
>>
>> The length of the qx.$$loader.uris line is causing problems in my
>> development
>> environment.
>>
>> This line can be extremely long.
>>
>> Sometimes it will cause Firefox/Firebug to hang
>
> I never heard of that. How many classes are included in the build?
>
700+
wrote:
>
> Mike,
>
> mshillin wrote:
>> The latest version of qx.ui.core.MMultiSelectionHandling.js contains
>> invalid
>> chararcters at the start of the file.
>>
>
> Well, not quite invalid ... it's the UTF-8 BOM (byte-order marker).
> Generall
The length of the qx.$$loader.uris line is causing problems in my development
environment.
This line can be extremely long.
Sometimes it will cause Firefox/Firebug to hang
I cannot check the file into source control (Clearcase thinks that something
with 47k characters on a line is a binary fil
The latest version of qx.ui.core.MMultiSelectionHandling.js contains invalid
chararcters at the start of the file.
Causes a runtime error when initializing qx.ui.form.List in this mornings
SVN update.
If you remove the characters and recompile - all is working
-
Mike
--
View this message in co
I added a comment to the bug describing how I implemented a hybrid build -
not a particularly elegant hack, but it gets the job done. I wanted to do
it in python, but am not to familiar with the language and changing the
generator itself lead to update/merge headaches.
If you have any other qu
The "build" job has been filtered in the framework/config.json in .0.8.3-pre
in a recent SVN update (on 5/6/09)
Why? Is this job deprecated?
I ask because Qooxdoo does not offer a hybrid build (my code in source mode
- qx code in compiled mode). I have been using the "build" target/job to
h
In Qooxdoo 7.x you could change the log level via the qxsettings array
qxsettings["qx.minLogLevel"]=700;
How do you do this in 0.8.2?
There seems to be no documentation about logging configuration - the API
docs for core.Setting point to a manual entry that no longer exists.
Thanks
Mike
--
V
Calling qx.ui.form.Textfield.setValue(null)
throws an exception
[Exception... "'Error: Invalid value type: null' when calling method:
[nsIDOMEventListener::handleEvent]" nsresult: "0x8057001c
(NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "" data: no]
This is different from 0.7.x where setting a
Actually found a solution - at least to my problem.
If I change the last line in my generate.py to the following
result = subprocess.call(cmd, shell=True)
sys.exit(result)
The sub process return code is used as the exit code.
BTW: I am using python 2.5.2
--
View this message in context:
h
I am calling ./generate.py from a script and it looks like when a build fails
- generate.py still returns 0.
I am using 0.8.2 on windows and linux - same behavior in both places.
This is causing a problem in my automated build environment - Don't remember
this being a problem in 0.7.x
Here is m
Translated text on legacy labels is NOT working in IE7 with Qooxdoo 0.8.1.
The following works fine in FF2 & FF3
qx.legacy.ui.basic.Label(this.tr("Login Name:"));
In IE I get a blank label.
IE will work if I do the following
qx.legacy.ui.basic.Label(this.tr("Login Name:").toString());
Other
A reply to myself.
I solved this issue by setting variants qx.debug="off" in
framework/config.json when building the qx.js and qx-0.js. It had nothing
to do with the way the qx.loader was operating for my application
The qx.debug="on" in the "build" version was causing problems in the
ui.lega
For my development environment, I would like my classes to be available in
"source" version , but have the qooxdoo library classes in "build" version.
I could not figure out how to do this with the build tool, so I tried
hacking the loader script for my app.
If I execute "generate.py build" in
All,
This ended up being a firebug issue with nested frames. Seems that
replacing nested framesets would break firebug debugging on scripts loaded
by nested framesets - supposed to be fixed in Firebug 1.4a13.
For those interested see :
Discussion :
http://groups.google.com/group/firebug/brow
Has anybody been able to get FF3 & FB 1.3.x or FB 1.4 to work with qooxdoo.
Seems I cannot debug. Breakpoints don't work. Sometimes the files don't
show up in the FB script tab. The qooxdoo logger always opens a second
window - doesn't log to the FB console.
When trying to debug Qooxdoo 0.8
Helder Magalhães wrote:
>
>
> This seems tightly related with bug 776 [1]...
>
> Hope this helps,
> Helder Magalhães
>
> [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=776
>
Thanks.
Does anyone know if patches to .0.7.x are being rolled forward into
qx.legacy in .8.x ?
Thanks again.
M
Looks like there is an old Treevirtual bug in 0.8.1.
Looks like some Table changes were merged from 0.7.x but TreeVirtual changes
were not. The TreeVirtual.js fix for this error was made in revision 11066
in the legacy_0_7_x branch.
Specifically, qx.legacy.ui.treevirtual.TreeVirtual is still ca
thron7-2 wrote:
>
>> My custom theme starts with the following
>>
>>
>> qx.legacy.Theme.define("my.ui.theme.MYTheme",
>>
>>
>> If I change this to
>>
>> qx.Theme.define("my.ui.theme.MYTheme",
>>
>> I get a clean build
>
> Mh, that's strange...
>
Strange that it will not compile or strange tha
I am migrating from 0.7.3 to 0.8.1. My app uses a custom theme
When I attempt to set the QXTHEME in the my config.json
"let" :
{
"QXTHEME" : "my.ui.theme.MYTheme",
"APPLICATION" : "my",
"QOOXDOO_PATH" : "../../qooxdoo-sdk",
Andreas Ecker-2 wrote:
>
> Hi Mike!
>
>
> A while ago we talked about the same idea: during regular application
> development to use a qooxdoo library file ("build") while keeping all
> individual custom classes ("source"). This would help keeping browser
> reloads fast. Need to see if we mis
Sebastian Werner wrote:
>
>
>
> This basically look like you do not have a configuration for the
> packages support. There seems to be a misunderstanding of the idea of
> what packages can do for you. These are not thought to build library
> like packages which may be used by different
mshillin wrote:
>
> Can someone post an example of how to use the "packages" feature in the
> 0.8 build framework. I have read the online docs but cannot seem to get
> it to work.
>
> My config.json contains a "packages" top level ke
Can someone post an example of how to use the "packages" feature in the 0.8
build framework. I have read the online docs but cannot seem to get it to
work.
My config.json contains a "packages" top level key
"packages" :
{
"parts":
{
"qooxdoo" : [ "qx.*
Petr Kobalíček wrote:
>
> Hi all,
>
> I have taken a note that keyboard handling in qooxdoo is slow. When I
> press a key, my 1.6Ghz processor runs at 100% speed even that
> application is doing nothing. This also happens to mouse moving in
> browser client area.
>
I have found the same. In
The ComboBox CellEditor has an event handling problem in FF2 and FF3. If the
combobox dropdown list overlays rows in the table and you select an item,
the focus indicator in the table (darkblue bar) will move to the row under
the item which was selected. A lightblue focus indicator remains on th
Turns out it is working for Python 2.5.
Sorry for the false alarm.
Because I am on RedHat, I cannot remove Python 2.3.x or up2date will fail,
so after I installed Python 2.5 to an alternate location, I created an alias
to the new python to test with
My build script was executing bash which th
Fabian Jakobs-2 wrote:
>
>
> The mouseover focus indicator has not (yet) been optimized because most
> application I know of don't use it. If you turn this off the table
> should be much faster. The same is of cause true for treevirtual.
> Currently no table work is scheduled but contributi
Hugh Gibson wrote:
>
>
> Can you run the Firebug profiler to see what is taking all the time?
>
> Hugh
>
I am having similar problems with TreeVitrual (see
http://www.nabble.com/TreeVirtual---Severe-performance-problems-%280.7.1-vs.-0.7.3---SVN%29-to14841428.html
)
Here is profile data us
Here is the profile data.
The TreeVirtual has about 70 individual nodes, there are about 15 top level
nodes.
I am using Firefox 2.0.0.11 on a Windows 2003 Server. Here is the profile
using Firebug (sorted by percent).
Once the tree is populated, I hover the mouse over each of the 1st 10 rows
(s
Is anyone else seeing severe performance problems with TreeVirtual. The
overall feel is slow. The hover indicator in the non tree column is slower
than the hover indicator in the tree column. The get out of sync for 1-2
seconds. The CPU utilization is high. This seems to be a new problem in
0.
I am seeing scrollbar flicker/excessive CPU usage and memory leaks with
TreeVirtual. Seems to do with resize events.
I updated to latest legacy_0.7.x SVN (as of 1/14/2008) and the problems
still exists. It is so bad that it will spike the CPU at 100% and
eventually consume all memory. This prob
I have an app that is part Qooxdoo (20%) and part plain javascript & html
(80%). Is it possible to expose the qooxdoo internationalization stuff to
the 80% of my app that does not use the full Qooxdoo library.
I am currently only using Qooxdoo for the really complex parts of the app,
so I don't
T.J.,
Thanks for the great explanation. Your option2 (below) works perfectly,
exactly what I was looking for. Good reading on the links too.
Thanks again,
Mike
T.J. Crowder wrote:
>
> =
> someSetupMethod : function()
> {
> vartextfield;
>
>
>
It is not a problem to code like this - I just wanted to make sure I am
coding the correct way and there was not some "trick" to accessing UI
components in a layout. It is a bit of a hassle when I am refactoring.
If I perform "simple actions" on UI components, the logic goes into event
listene
I am writing an app with data entry forms. To be able to access the various
UI components (TextField, Checkbox, etc) from different functions in the
class, it seems that I need to declare them as class member variables and
always refer to them with "this" (this.myTextField.getValue()).
While t
The attached patch implements optional icons for the treevirtual control.
The default behavior is to use Icons. You can enable/disable icons in the
same way as you enable/disable treeLines
http://www.nabble.com/file/p12673879/virtualTreeOptionalIcon.patch
virtualTreeOptionalIcon.patch
The patc
I can confirm, this patch fixes the problem.
Thanks for the quick response!
mshillin
Derrell Lipman wrote:
>
> On 7/31/07, mshillin <[EMAIL PROTECTED]> wrote:
>>
>> I cannot figure out how to remove all nodes in the tree. (7.1)
>>
>> Calling tree.get
I cannot figure out how to remove all nodes in the tree. (7.1)
Calling tree.getDataModel().prune(0, true) throws an exception
this._nodeArr[node.parentNodeId] has no properties - in
SimpleTreeDataMod... (line 537)
Stepping through the code, it looks like it is trying to delete children of
th
48 matches
Mail list logo
