>From Python to Qooxdoo
1) the local object is called this. So you do "this.x" instead of @x
2) there is no layout sensitive syntax, you need to use braces
3) the syntax for creating classes is slightly different, see:
http://qooxdoo.org/documentation/0.7/class_declaration
4) you main iterators:
// ordinary for-loop
for(var i=0; i<10; i++)
alert(i);
// reflexive for-loop
foreach (key in someObj)
alert (k + " is " + someObj[k])
5) All objects are dictionaries in javascript. So myObj['x'] is the same as
myObj.x
6) put "var" before any initialisation of a _local_ variable
7) functions are just values like anything else, so you can do:
x = function (name) { alert ('Hi, ' + name); }
8) you want to use the firebug firefox extension. This gives you a live
'eval', 'inspect' etc. of your application.
9) see http://qooxdoo.org/documentation/0.7/hello_world_tutorial
You need to use a terminal somehow. (what is your development platform?)
Anyways, when using skeletons, you need to know these commands:
make ==> makes the development version work
make build ==> makes the production (optimized) version work in /build
make api ==> creates an api viewer for all qooxdoo classes -AND- your own
;-)
Most programmer's editors allow you to bind such commands and/or shell
scripts to certain keys.
For me, for example f5-f6-f7 do the above commands and then open my browser
there.
If you easily want to stay current, you always want subversioin to just get
the latest.
THis is all easier on a mac or on linux, since windows has crappy terminal
support.
You can also try a special version of eclipse that 'knows' qooxdoo.
I haven't tried it myself, but I assume it has setup these commands and
such.
Short-version: when using a new framework/ language/etc. the issue is not
the language.
You'll be spending more time learning the tools. Javascript is actually
quite simerlar to python, since both are dynamically typed languages with
easy reflection. It would be much harder if you were used to statically
typed languages such as Java or C. (although Java is a weird beast in
trying to combine the disadvantages of dynamically typed language with the
disadvantage of statically typed languages with a topping of all the
disadvantages of low-level programming language)
2008/4/3, Dan <[EMAIL PROTECTED]>:
>
>
>
> On 4/3/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> >
> > Dear all,
> >
> > I have a dilemma. I only know Python. I don't know
> > Java, and I don't even know Java Script - but I really
> > like what I see from the qooxdoo web page. Someone
> > suggested that I look at pyjamas (a Python wrapper
> > over the Google SDK) which might not look as good as
> > qooxdoo but it's Python. That's an attractive
> > argument.
>
>
> Pyjamas isn't a wrapper around the Google SDK, it's a Python clone.
> There's only an early beta and the project seems quite stagnant. It's a
> shame, when they released 0.1, I was really waiting forward to the
> less-buggy, more cross-browser versions that were going to come.
>
> As much as I love Python, I wouldn't suggest you do any serious work with
> Pyjamas.
>
> So, the question is:
> >
> > 1) How does qooxdoo compares to the Google SDK? Is
> > there a comparison of the two on the Internet that can
> > help me decide which way I should go?
>
>
> The Google SDK is much faster to learn but it does much less. Its main
> strength is that it lets you use all the Java tools you were used to. It's
> mostly useful if you were already a Java programmer.
>
> I did a blackjack game with it and didn't run in any special difficulties.
> Just be aware that you have to style your app by yourself with CSS and to do
> that, you have to understand what kind of HTML GWT creates. I didn't care at
> all about a plain black on white look for my app so I can't comment on the
> difficulty of doing so.
>
> It also streamlines the communication between your app and a Java server
> but why would you want your server backend written in Java when you have
> Python?
>
> 2) How much Java script do I really need to know
> > before I can use qooxdoo?
>
>
> Very little. You will learn *much* more Qooxdoo than Javascript. A few
> tutorial from the W3 School should get you started. You won't have to do any
> fancy javascript tricks to get your app working, qooxdoo will do that. But
> qooxdoo itself does have a learning curve.
>
> 3) Apparently somebody is working on a Java wrapper of
> > qooxdoo (qwt), but is there somebody working on a
> > Python wrapper of qooxdoo?
>
>
> Not that I know of. Doesn't mean you can't use Python to write some of
> your code, I'm currently thinking about writting Python code to generate
> javascript to enter data in my Django models.
>
> I suggest you go to the documentation, check if things make sense to you,
> if they are compatible with your brain. If so, go learn some javascript and
> come back learning the details.
>
> Unless you need to finish your project ASAP, then go with GWT.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
