Hi Leandro,

> I think center all qooxdoo funcionalities into only a program is a
> better approach. Something liks this:
> 
> $ /path/to/qooxdoo create-applicaton --name myApplication
> 
> And to build:
> 
> $ /path/to/qooxdoo build # or maybe job=transform,build,etc

Yeah, there are somewhat mixed opinions on that. There is something to a
single command as the user interface (compare svn, git, ...), with lots
of sub-commands. Others like distinct commands better...

> 
> This eliminated the file ./generate.py and keep in the project
> directory only the project code.

'generate.py' is only a very small proxy to the real generator script,
which is QX/tool/bin/generator.py, and exists only so people don't have
to remember the path to the qooxdoo tools. I wouldn't be sad at all if
it goes away... You can call QX/tool/bin/generator.py directly, if you want.

> 
> If the user put qooxdoo into the PATH env var, it can just call...
> 
> $ qooxdoo build

You can already do that. Just put QX/tool/bin in your PATH, and
create-application.py, generator.py, ecmalint.py, etc. are all directly
callable (That's what I do :)).


> 
> .. to build the application
> 
> Currenty if the user change the qooxdoo framework location, it needs
> to adapt the config.json file. In my opinion the most dificult part in
> qooxdoo is the setup :-) With this approach the user just needs change
> some env variables, or optionally change it in the let session in
> config.json.

That's also already true. To switch to another qooxdoo installation,
just edit the QOOXDOO_PATH in the global 'let' of your config.json.
That's all.

> 
> In adition news commands could be implemented in the qooxdoo
> application. For example:
> $ qooxdoo create-class myApplication.admin.BlackList [--extend
> qx.ui.form.Button] [--type singleton|static|etc]

That's what we basically do with generate.py, just that it doesn't cover
each and every use case.

T.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to