Hi Christian,
if you take the newest download version, you will have the
qx = require('./qx-oo')
syntax. Thats what I prefer. :)
Regards,
Martin
Am 09.08.2010 um 20:46 schrieb panyasan:
>
> Hi Martin,
>
>
> MartinWittemann wrote:
>>
>>> be solved differently. How did you import qx-oo a
Thanks a lot, that was it.
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
Hi Martin,
MartinWittemann wrote:
>
>> be solved differently. How did you import qx-oo as a module in node.js?
>
> I just used the require statement and did not assign the return value of
> it to qx. As the qx-oo script defines a global qx variable, it is not
> necessary to assign it. But the
> Look at the recent thread about performance decrease from one version to
another.! In that case he has developed new so called light-weight
widgets, but > for compatibility he might want to use the same namespace =
no changing, and then hook in the new ones instead of the old ones
Ov
I appreciate your answers, but to get a flexible framework there must be a
flexible way of handling this.
1. I could not find this documented (which means I didn't find it and that
means it was not clear enough or whatever!):
a. that it is not possible to add new classes in existing namespace
The flaw is...
> "jobs" :
> {
> ...
here:
> "cache" :
> {
> "compile" : "${CACHE}",
> "downloads" : "${CACHE}/downloads"
> },
What you meant to say was:
"cache" :
{
"cache" :
{
"compile" : "${CACHE}",
"do
Hello Christina,
> I am currently porting Martin's json-rpc/node code [1] to qxoo to run on the
> server (as a contribution named "RpcNode").
Thats really good to hear that my code is worth something at last. :)
> In contrast to Derrell's RPC implementation [2], the current 1.0 [3] and
> 2.0 [
Hello,
I am currently porting Martin's json-rpc/node code [1] to qxoo to run on the
server (as a contribution named "RpcNode"). I plan various modifications,
but want to announce the following beforehand to hear your thoughts:
In contrast to Derrell's RPC implementation [2], the current 1.0 [3]
Hey,
Thank you sooo much !
I'll migrate from JS.Class to qxoo after a few tries AFAIC.
I'll let you know any issue.
Thank you again !
Before Printing, Think about Your Environmental Responsibility!
Avant d'Imprimer, Pensez à Votre Responsabilitée Environnementale!
On Mon, Aug 9, 2010 at 4:00
On 08/09/2010 08:29 AM, Stéphane wrote:
> Hi Martin,
>
> Yes I would definitily love the sending of the js files !
>
> I want the source to see how it works only, not to change the things.
> But if it is something hard to have, well the build will be enough (hope
> there is no obfuscation or su
On 08/09/2010 11:32 AM, Stefan Andersson wrote:
> I make the following changes: qx -> qxe
>
> root
> I---tools
> I I---source
> II---class
> II---qxe
> I I---ui
> I I---A
Yes, I did a migration job with the result:
UPGRADE TO 1.2
* Processing script files:
- File: /home/alex/alinex/src/core/start/class/core/start/Application.js
- /home/alex/alinex/src/core/start/class/core/start/Ap
I try this, but it doesn't work :/
But if I upload the script to a web-server, everything works fine. I changed
nothing, I only replace "127.0.0.1" with the url of my homepage. Very
strange.
Here is the important part of the php script:
header('Content-type: image/jpeg');
$max_thumbwidthheig
Hello Julian,
the framework needs to know what kind of image you are loading which it is
trying to read from the URL. If you are not supplying a file extension in your
url, the framework does not know what to do. Bug you can cheat and just supply
an argument not read by the server:
"http://127.
I make the following changes: qx -> qxe
root
I---tools
I I---source
II---class
II---qxe
I I---ui
I I---A
I I---B
I---App
in A and
- did you run the migration job when switching to 1.2?
- did you run a 'distclean' before compiling under 1.2?
- can you post your entire config?
t.
On 08/09/2010 06:49 AM, Alexander Schilling wrote:
> The output of generate.py build -s is:
>
> ===
On 08/09/2010 01:17 AM, Ralf Nieuwenhuijsen wrote:
> Hi all,
>
> I'm fighting with the generator. I don't think I'll even understand how
> to deal with the 'internal' resource.
> There is so much path aliasing by default, at so many different places.
The central thing to understand is the idea
Hi Guys,
I wrote similar object oriented model some time ago, accessible as BLite.
The library contains also some dom manipulation methods, but they can be
ripped out.
BLite: http://code.google.com/p/blite
Source http://code.google.com/p/blite/source/browse/trunk/BLite/Lib.Core.js
Using BLite is
Hello,
i want to add Icons to my ListItems. But the browser doesn't display them :(
These is my Code:
[...]
var tmp = new qx.ui.form.ListItem(name,
"http://127.0.0.1/api.php?size=64&name="; + name);
[...]
If I insert e.g. the adress http://127.0.0.1/api.php?size=64&name=sdf.jpg in
my browser, ev
Am 09.08.2010 08:26, schrieb Martin Wittemann:
> I've created a test implementation of a "lightweight" version of
>> qx.ui.form.CheckBox and qx.ui.form.RadioButton. I've started this as a
>> contribution project with some still missing features and alignment
>> features. The appearance is missing
See also
http://qooxdoo.678.n2.nabble.com/about-the-upload-widget-td5200577.html
Cheers,
Fritz
On Mon, 9 Aug 2010, Martin Wittemann wrote:
> Hello Julian,
> have you checked the trunk version of the UploadWidget [1] in the qooxdoo
> contrib. As far as I know, we are using this in some 1&1 proj
21 matches
Mail list logo
