Today Ing. Josue Mojena Marin wrote:
> Hello community , I need to set my qooxdoo application for the
> generate.py , I copy files to compile the same place as the
> generate.py build , in this case I want in a folder outside the
> project itself , that is, a level before . Any idea how could
> p
Hello community , I need to set my qooxdoo application for the generate.py , I
copy files to compile the same place as the generate.py build , in this case I
want in a folder outside the project itself , that is, a level before . Any
idea how could personalisarlo ?
___
Ing. Jo
I have to choose between Qooxdoo and ExtJS and I don't regret my choice
especially when I learned it become very expensive
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Hello-new-to-qooxdoo-tp7586501p7586505.html
Sent from the qooxdoo mailing list archive at Nabble.com.
---
Your German is better than my Dutch ... ;-)
Fritz Zaucker
Oetiker+Partner AG
Aarweg 15
CH-4600 Olten
+41 62 775 9903
> Am 20.12.2014 um 22:29 schrieb halcwb :
>
> zaucker wrote
>> Qooxdoo is kind of an English phonetic translation of the German phrase
>> "(da )kuckst du", meaning something along
zaucker wrote
> Qooxdoo is kind of an English phonetic translation of the German phrase
> "(da )kuckst du", meaning something along the line "aren't you impressed?"
> ... of course that is nit as easily appreciated by none-German speakers
> ..,
Hatte ich das gewusst dan hatte ich das vielleicht ge
Hi nameless new Qooxdoo user ... :-)
great to hear your praise and appreciation of the Qooxdoo tram's effort.
The name actually reflects your expression perfectly.
Qooxdoo is kind of an English phonetic translation of the German phrase "(da
)kuckst du", meaning something along the line "aren't
Coming from ExtJs, my first impression of qooxdoo feels like a fresh bath.
Getting up and running was soo much easier than with ExtjJs. Even got me
started with using Coffee script (don't forget to add compiler option --bare
to disable function wrapping).
The only thing that bothers me is the name
Thanks. I will check what changes and we will see what the solution will be.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Hello-from-a-newbie-tp5227706p5263952.html
Sent from the qooxdoo mailing list archive at Nabble.com.
---
Sorry for the late reply. Good to know that my problem was not local. Yes, I
will be more then happy to raise a bug report.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Hello-from-a-newbie-tp5227706p5262456.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
Hey,
thanks for giving it a try. I just tried it myself and seems that either YQL
or twitter doesn't work together currently. Would you mind open a bug report
in out bugzilla [1] describing the problem? I can remember someone talking
about a change in the twitter API regarding OAuth ... maybe that
Hey Martin thanks for your continued help. I tried the YQL console:
use 'http://www.yqlblog.net/samples/twitter.status.xml'; insert into
twitter.status (status,username,password) values ("Playing with INSERT
UPDATE and DELETE in YQL", ","")
Of course - with my real twitter username and passwor
Hi,
I really think that problem is not in the qooxdoo code (Your application and
framework). Have you tried to post a message using YQL console? You can
switch on the diagnostic feature there to see whats happening with your
call. So maybe something has changed at yahoo or at twitter so that the c
Hello,
Thanks for that. I picked up the latest code from :-
http://github.com/wittemann/qooxdoo-tutorial/tree/master/source/class/twitter/
I still can't post to twitter. So in my TwitterService post() function, I
have the following debug stmts:-
post : function(message, username, password)
Hi,
The line you mentioned is in the load handler so the post should already be
made. But it's interesting that you get another result of your call. Maybe
you should check out what the result really is using qx.dev.Debug.
debugProperties [1]. I'm quite sure YQL is giving some error message back.
Thanks guys for the pointers. Lots of stuff to consider.
I have one more problem on the Twitter demo in that I can't post. I am using
the source code from github, but I think that in TwitterService.js, post()
function, the line :-
var returnedText = model.getQuery().getResults().getStatus().getT
Hi.
> 1. How do I do async updates back to the qx client? Or do I have to
> implement up a client driven polling mechanism?
Maybe you'd get some ideas by looking at the package qx.data.controller. I'd
make a model throwing events to which the UI subscribes, and isolate all the
server polling/
Hi,
the Feed Reader uses it. You find the sources for e.g. in the SDK in the
"application/feedreader/source" folder.
Cheers,
Chris
Am 28.06.2010 23:03, schrieb nrg-b:
> Oh well - polling it is.
>
> Thx for the pointer to qx.io.PartLoader.require - are there any
> tutorials/examples which make u
Oh well - polling it is.
Thx for the pointer to qx.io.PartLoader.require - are there any
tutorials/examples which make use of partitioning?
As for the footie, there is a strong case that goal-line technology (or an
extra official at either end) can only help provide more info to the
Referree. H
> 1. How do I do async updates back to the qx client? Or do I have to
> implement up a client driven polling mechanism?
Yes. As there is no reversing of client - server roles in HTTP, if you
want to implement server-driven changes, the client either has to send a
request for updates periodiacally
Hello All,
I work on real-time financial trading systems written in Java/Swing/Sybase
(and some other technologies). However, I am quite inexperienced with web
technologies such as JavaScript, Ajax, json, servlets etc. Please go easy on
me ;-)
I'd like to create a web front-end on one of these
Hi again,
On Mon, Jan 11, 2010 at 11:19 AM, Nick Glencross
wrote:
> Hi Miguiel,
>
> On Sat, Jan 9, 2010 at 3:46 PM, Miguiel Manso wrote:
>> I've created the "Hello World" application to start testing it and
>> understanding some of the concepts around it and I've noticed that everytime
>> I "rel
Hi Miguiel,
On Sat, Jan 9, 2010 at 3:46 PM, Miguiel Manso wrote:
> I've created the "Hello World" application to start testing it and
> understanding some of the concepts around it and I've noticed that everytime
> I "reload" the page to do some testing Firefox loads DOZENS of "js" files
> taking
Hi Miguiel,
On Saturday 09 January 2010 16:46:36 Miguiel Manso wrote:
> I've just started playing around with qooxdoo and I think it's a wonderful
> project.
Thanks for the kudos and welcome to qooxdoo!
> I've created the "Hello World" application to start testing it and
> understanding some of t
Hi there,
I've just started playing around with qooxdoo and I think it's a wonderful
project.
I've created the "Hello World" application to start testing it and
understanding some of the concepts around it and I've noticed that everytime
I "reload" the page to do some testing Firefox loads DOZEN
> I've also had good luck using the source versions with Google's Chrome
> browser, but my requests are backed by yaws so YMMV.
>
You're using Yaws, cool...
T.
--
Let Crystal Reports handle the reporting - Free Cryst
I've also had good luck using the source versions with Google's Chrome browser,
but my requests are backed by yaws so YMMV.
Rob
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simpl
On Mon, 10 Aug 2009 13:53 +0200, "thron7"
wrote:
> A 'source' version of a demo app as around 180 class files to load, the
> 'source-all' version around 560. This, together with the fact that most
> of these files have to be loaded sequentially from a web server (limit
> of socket connections),
> Thanks Fritz and Skar, using source (instead of source-all) brings it
> for me down to around 15 seconds.
>
> However, I realized my webserver (Lighttpd) is causing another serious
> delay. When I use file:// instead of http:// it takes less than 2
> seconds to load. Quite an improvement from 50
Hello Reimer,
the difference between the source and the source-all job is, that the
soure-all job includes all classes which, as you have seen, can take
much more time. So its always a good idea if you have some problems
with latency to use the source version. But keep in mind that if you
On Fri, 07 Aug 2009 17:39 +0200, "Fritz Zaucker"
wrote:
> ./generate.py source (not source-all)
Thanks Fritz and Skar, using source (instead of source-all) brings it
for me down to around 15 seconds.
However, I realized my webserver (Lighttpd) is causing another serious
delay. When I use file:
On Fri, Aug 7, 2009 at 8:58 PM, reimer wrote:
> On Fri, 07 Aug 2009 17:09 +0200, "Fritz Zaucker"
> wrote:
> > I just tried the
> >
> > createapplication-application demo (from svn trunk). It took about 8
> > Seconds
>
> Hi Fritz,
>
> Just to clarify: this is the "Hello World" application?
>
> I
Hi "reimer",
yes, the application with just a "Hello world" button. I did:
tool/bin/create-application.py --name=test
cd test
./generate.py source (not source-all)
Doing it with source-all took 17 Seconds and gave two errors on the firebug
console ...
source-all includes all classes, probably
On Fri, 07 Aug 2009 17:09 +0200, "Fritz Zaucker"
wrote:
> I just tried the
>
> createapplication-application demo (from svn trunk). It took about 8
> Seconds
Hi Fritz,
Just to clarify: this is the "Hello World" application?
I am running:
$ tool/bin/create-application.py --name=custom --out=.
$
I just tried the
createapplication-application demo (from svn trunk). It took about 8 Seconds
to load the application (Firefox 3.5.1 on Ubuntu-Jaunty). The browser is
running on one (shared) machine (not very busy) and the file is stored on
another machine and accessed through NFS.
Cheers,
Fritz
The source version is not supposed to load fast. It is there for debugging
purposes only. Once you have your application working, you do a build
version and deploy it to your server. And yes, the source version does take
a long time to load. And it you are using an older browser, especially IE6
or
On Fri, 07 Aug 2009 18:46 +0530, "skar"
wrote:
> If you "build" the app, then it should have 2 files, the js, the html
> and of course, the resources like images used for buttons etc. My build
> dir is around 2.9M and it loads pretty fast, say 2-3 secs.
Hi skar, just to clarify: I'm talking about
Hello Reimer,
wellcome to qooxdoo. :)
More than 50sec for a page load is way too long an not as it supposed
to be. But as skar said, the source version loads every single
javascript class as a single file so there may be some hundred files
to load, which can take some time you have a latency
reimer wrote:
> Hi all,
>
> I am trying out qooxdoo since yesterday. The Getting Started
> documentation is very clear, so I had no problem getting the "Hello
> World" example up and running. However, opening source/index.html takes
> very long (>50s). I am using a seperate server, so there will be
Hi all,
I am trying out qooxdoo since yesterday. The Getting Started
documentation is very clear, so I had no problem getting the "Hello
World" example up and running. However, opening source/index.html takes
very long (>50s). I am using a seperate server, so there will be some
download time, but
> Chris,
>
> Thanks for making the effort. We appreciate all input which is at least
> "50% in the right direction" (to quote R. Gabriel). I thought you would
> be more platform savvy, but that's fair enough, others can always take a
> second look and build upon what you've written. So no side
>> Two days ago that mini-fix described here, didn't help, there was
another
>> failure later on which I couldn't resolve because I never worked with
>> python before.
>>
>So you are saying you applied that patch 2 days ago, but then ran into
>another problem?! Is this other problem gone now?
[EMAIL PROTECTED] wrote:
> To reproduce (using windows):
>
> - check out trunk to 'C:\temp\qooxdoo trunk' (<- one space in path)
> - go to dir 'C:\temp\qooxdoo trunk\tool\bin'
> - call 'create-application.py --name TEST' (<- works)
> - switch to dir 'C:\TEMP\qooxdoo trunk\tool\bin\TEST'
> - call
> Hi Thomas,
>
> Yes, I'm sure that this is the issue -- but as I'm not a command line
> type of guy and I'm just trying to follow the Hello World example
> (which in all sincerity should be *idiot proof*, and yes, I count
> myself in this category at the moment with qooxdoo!).
>
> Ideally thes
To reproduce (using windows):
- check out trunk to 'C:\temp\qooxdoo trunk' (<- one space in path)
- go to dir 'C:\temp\qooxdoo trunk\tool\bin'
- call 'create-application.py --name TEST' (<- works)
- switch to dir 'C:\TEMP\qooxdoo trunk\tool\bin\TEST'
- call 'generate.py source' (<- nothing I c
thron7 wrote:
Chris Banford wrote:
thron7 wrote:
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom
--out=C:
command was failing due to there being spaces and other crud in the
path to my qooxdoo-0.8-sdk folder.
If this hints at a general p
[EMAIL PROTECTED] wrote:
>>> If this hints at a general problem we'd like to hear about it.
>>>
>
> When trying out the trunk (yesterday) I had the same problem.
> I can't remember whether this involved 'create-application.py', but
> 'generate.py' definitely had problems (on windows) when
Chris Banford wrote:
> thron7 wrote:
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom
--out=C:
>>> command was failing due to there being spaces and other crud in the
>>> path to my qooxdoo-0.8-sdk folder.
>>>
>>
>> If this hints at a general problem we'd
>> If this hints at a general problem we'd like to hear about it.
When trying out the trunk (yesterday) I had the same problem.
I can't remember whether this involved 'create-application.py', but
'generate.py' definitely had problems (on windows) when the current
working folder has spaces in it
thron7 wrote:
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom --out=C:
command was failing due to there being spaces and other crud in the
path to my qooxdoo-0.8-sdk folder.
If this hints at a general problem we'd like to hear about it.
I originally tried to us
Chris Banford wrote:
> Thanks for the hand-holding!
> I've managed to get SVN access and create-application.py building a
> custom starting point :-) . It took me a few minutes to realize that
> running the
>> C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom --out=C:
>>
> comman
Tobias Oetiker wrote:
> I just tested the create-application.py with my sn checkout and it
> wors fine, except for two nitpicks.
>
> a) the generate.py that gets created is missing the execute bits
>
> b) the cakes icon on the "First Button" seems to be truncated on
>the right edge. It is the i
Yes, was trying to run it directly.
After reading the docs I thought one didn't need cygwin anymore...
Yes, it was Windows not finding python. Thanks for the help with these
Windows differences -- it all brings me ever closer to making the jump
to Linux (Wine for Photoshop...).
Cheers,
-Chris
Hi Thomas,
Yes -- right after I'd sent this, I realized that there was an issue
with generate.py source and that neither the compiled or the uncompiled
versions where working properly.
No, the "compiled" version wasn't working due to the generate.py issue,
and I just didn't realize that I
> Hi Thomas,
>
> Yes -- right after I'd sent this, I realized that there was an issue
> with generate.py source and that neither the compiled or the uncompiled
> versions where working properly.
Right, but why wouldn't the compiled version work? That bothers me...
>
> Sorry for the noise! Just my
Hi Thomas,
Yes -- right after I'd sent this, I realized that there was an issue
with generate.py source and that neither the compiled or the uncompiled
versions where working properly.
Sorry for the noise! Just my total inexperience with your tools (I learn
quickly, so am hoping I won't send
I gather from your first mail that you are invoking the generate.py script
directly, right?! Are you running on Windows cmd or cygwin bash? There is
an issue with windows being able to associate .py with the python
interpreter, but not finding the 'python' command (since it is not in the
PATH). Try
Chris,
>
> In my efforts to clean up the Hello World wiki docs a bit, I'm wondering
> about the following heading on the page:
> http://qooxdoo.org/documentation/0.8/helloworld
>
> After I run:
> C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom --out=C:
> I'm already presented with
Here you go :-)
#!/usr/bin/env python
#
# qooxdoo - the new era of web development
#
# http://qooxdoo.org
#
# Copyright:
#2008 1&1 Internet AG, Germany, http://www.1und1.de
#
# License:
#LGPL: http://ww
Chris,
could you post the contents of the generate.py script.
Thomas
> Hi devs,
>
> I'm getting the following when trying to generate the simple Hello World
> app:
>> C:\custom>generate.py source
>> Traceback (most recent call last):
>> File "C:\custom\generate.py", line 40, in
>> os.exe
Hi devs,
I'm getting the following when trying to generate the simple Hello World
app:
> C:\custom>generate.py source
> Traceback (most recent call last):
> File "C:\custom\generate.py", line 40, in
> os.execvp(CMD_PYTHON, argList)
> File "C:\Python25\lib\os.py", line 353, in execvp
>
In my efforts to clean up the Hello World wiki docs a bit, I'm wondering
about the following heading on the page:
http://qooxdoo.org/documentation/0.8/helloworld
After I run:
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom --out=C:
I'm already presented with a runnable applica
Thanks for the hand-holding!
I've managed to get SVN access and create-application.py building a
custom starting point :-) . It took me a few minutes to realize that
running the
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py --name=custom --out=C:
command was failing due to there being sp
I just tested the create-application.py with my sn checkout and it
wors fine, except for two nitpicks.
a) the generate.py that gets created is missing the execute bits
b) the cakes icon on the "First Button" seems to be truncated on
the right edge. It is the icon test.png which looks to me as
thron7 wrote:
I downloaded it last night when I saw that there was a bunch of new
documentation related to the 0.8 release. Installing and getting
TortoiseSVN is simple, but I quickly lost my way at the following in
the *Checking out from SVN* page:
Subversion details
The following
> https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo/trunk/qooxdoo - and
>
For read-only access you can even use the same URL with 'http' scheme -
might be faster ;).
T.
-
This SF.Net email is sponsored by the Moblin
>
> I downloaded it last night when I saw that there was a bunch of new
> documentation related to the 0.8 release. Installing and getting
> TortoiseSVN is simple, but I quickly lost my way at the following in
> the *Checking out from SVN* page:
>
>>
>> Subversion details
>>
>> The followin
Hi devs,
One step further with the Hello World documentation, and stuck again! :-) .
The docs say:
To create your application |custom| to |C:|, while the qooxdoo SDK is
available at |C:\qooxdoo-0.8-sdk|, call the script as follows:
and run:
C:\
Chris Banford schrieb:
> Sebastian Werner wrote:
>> Chris Banford schrieb:
>>
>>> Hi devs,
>>>
>>> One step further with the Hello World documentation, and stuck again! :-) .
>>>
>>> The docs say:
>>>
To create your application |custom| to |C:|, while the qooxdoo SDK is
available
Sebastian Werner wrote:
Chris Banford schrieb:
Hi devs,
One step further with the Hello World documentation, and stuck again! :-) .
The docs say:
To create your application |custom| to |C:|, while the qooxdoo SDK is
available at |C:\qooxdoo-0.8-sdk|, call the script as follows:
Chris Banford schrieb:
> Hi devs,
>
> One step further with the Hello World documentation, and stuck again! :-) .
>
> The docs say:
>> To create your application |custom| to |C:|, while the qooxdoo SDK is
>> available at |C:\qooxdoo-0.8-sdk|, call the script as follows:
> and run:
>> C:\qooxdoo
Hi devs,
One step further with the Hello World documentation, and stuck again! :-) .
The docs say:
To create your application |custom| to |C:|, while the qooxdoo SDK is
available at |C:\qooxdoo-0.8-sdk|, call the script as follows:
and run:
C:\qooxdoo-0.8-sdk\tool\bin\create-application.py -
[EMAIL PROTECTED] wrote:
> Sorry. I read:
>
> http://qooxdoo.org/documentation/0.7/skeleton
>
> and looks like my problem is that I tried to use a
> different drive and the document is correct: cygwin
> doesn't work right under Windows like that. Once I
> place the skeleton on the same drive as q
path, things work.
Regards,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
On
> Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, April 08, 2008 5:15 PM
> To: qooxdoo-devel@lists.sourceforge.net
> Subject: [qooxdoo-devel] Hello World tutorial is
PROTECTED]
On
> Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, April 08, 2008 4:10 PM
> To: qooxdoo-devel@lists.sourceforge.net
> Subject: [qooxdoo-devel] Hello World tutorial is out
of date?
>
>
> Hi list:
>
> Now that I have qooxdoo-0.7.3 working, my first task
&
Hi list:
Now that I have qooxdoo-0.7.3 working, my first task
is to try to follow the tutorial at:
http://qooxdoo.org/documentation/0.7/hello_world_tutorial
Unfortunately, it's obvious that tutorial is out of
date.There is no QOOXDOO_URI in
QOOXDOO/helloworld/Makefile, and when I tried to do
Dietrich Streifert schrieb:
Hi,
I'm using FCKeditor from http://www.fckeditor.net in two of our projects
and I'm very pleased about the functionality. The editor is licensed
under the LGPL. I think it would be a great mariage to have the
functionality of FCKeditor in qooxdoo.
FCKeditor is b
Hi,
I'm using FCKeditor from http://www.fckeditor.net in two of our projects
and I'm very pleased about the functionality. The editor is licensed
under the LGPL. I think it would be a great mariage to have the
functionality of FCKeditor in qooxdoo.
Sorry for not having the time to do the wor
Andrey Prigogin schrieb:
Hi list,
Hi Andrey,
Just stumbled across the Qooxdoo project couple of days ago in the
search of widget library for a rich client app. We are (the company I
work for) seriously considering using qooxdoo and provide colloboration
with the project. Hats off to Sebas
Hi list,Just stumbled across the Qooxdoo project couple of days ago in the search of widget library for a rich client app. We are (the company I work for) seriously considering using qooxdoo and provide colloboration with the project. Hats off to Sebastian and Andreas for getting the project this f
79 matches
Mail list logo
