Hi Thomas,
Chris Banford wrote:
Hi list,
Before asking my little question, just wanted to say that the work
done on the 0.8 documentation over the last weeks has been great!
Updated from SVN and got all working with the updated gernerat.py and
Hello World both quickly and easily -- kudos.
(Starting to get some glimmers of comprehension on how 0.8 works... :-) )
That said, I still find the *Tooling* part of qx rather dense and
difficult to get started on (power has its price).
/My question is:/
I'd like to have my little test project use a different 'namespace'
than that of its folder and to slightly adjust the directory structure
of the output folders/files from running build and/or source.
It seems as though both these can be accomplished via changing some
settings in the project's config.json file, but for the life of me I
can't figure out where to start.
Any chance someone could point me in the right direction here?
Chris,
With qooxdoo 0.8 we favored a bit the RoR mantra of "convention over
configuration". So a few things in the project setup are clad into iron,
and others are, well, going against the qooxdoo tool chain's nature, so
to speak. For one thing, you *can't* have the folder under your
source/class path be different from the project's name space. It just
won't work, sorry.
Firstly, thanks for the time to answer these types of questions --
appreciate it :-)
Ok -- I was just assuming it was my 80% lack of understanding on what's
going on with the whole generator/config.json stuff (well, it still is
am sure!). I'll try taking a step or two back and rethinking how I have
my projects set up and how they map to various folders on the server.
For another thing, you can e.g. tailor the root output path of running
build, using the "root" subkey of "compile-dist", but make sure to keep
the "file" subkey in sync with this; just check the reference for this
key [1] (re-vamping the subkeys and their dependendies for e.g.
"compile-dist" is on our list of todos). But you won't be able to change
much of the structure beneath it.
I can *almost* follow you on this... The two things I've found the most
difficult to figure out with qx (0.8 -- no experience with previous
versions) are the whole Meta-Theme/Theme/Appearance bits and the
development Tool-chain. These two areas fall outside of my experience
from doing other work, so its a bit like jumping in the deep end of the
pool at times :-)
I am starting to figure out how things work with Themes, although the
various paths are still challenging for me! (splicing/combining images!?!)
The Tool-chain (config.json, jobs, etc) is still over my head. I'm
hoping that there are a few more wiki docs/how-to's in store, from those
who feel comfortable with this stuff.
So, apart from playing around with the existing subkeys for the
"compile-dist"/"compile-source" config keys (drawing on the reference
page) there is not much you can do. But I recommend not to spent too
much time on it. It is easier to go with the default structure,
especially when you are trying to catch up with 0.8.
I'll keep plugging away at this. Really looking forward to grasping the
missing basics, so I can start to actually create cool stuff!
Cheers,
-Chris
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
