Ok, the confusion came from application and library but it is the same, technically. Thanks for that important clarification, I'll use create- application.py now.
On Sep 16, 2009, at 12:20 , thron7 wrote: > > > Jean-Baptiste BRIAUD -- Novlog wrote: >> Hi, >> >> I'm trying to build a library, a "place" where I could put code to >> share across applications. >> I'll deploy that lib with all applications. >> >> I feel lost in all that Manifest.json, config.json, various >> options ... >> >> 1. The lib part >> First, in a qxfwk folder (the lib) , I put the following : >> source/class folder >> source/resource folder >> source/translation folder >> Manifest.json >> config.json ? Do I have to put that file here ? > > Look, J-B, don't do that by hand. Use the "create-application.py" > wizzard to create the basic structure for you. Just follow the initial > how-to-get-started document > (http://qooxdoo.org/documentation/0.8/helloworld#create_your_application > ). > >> Inside that Manifest.json, the last element from that doc >> : http://qooxdoo.org/documentation/0.8/application_structure/manifest >> is a type, but witch other values are allowed ? Only application is >> documented. That qxfwk doesn't "execute", it doesn't look like an >> application. There is no main in it. >> "type" : "application" > > To qooxdoo, the basic structure is always the same, no matter if you > have an application, a library, or what have you. So the "type" > entry is > informational. You can just set it to "library". > >> >> Now about the name space, how can I ensure novlog.fwk ? >> I want all the class in that qxfwk lib to be inside novlog.fwk >> namespace. I feel I could only put novlog, or fwk, but not >> novlog.fwk. Any confirmation, infirmation ? > > You could invoke create-application like this: > create-application.py -n qxfwk -s novolog.fwk > > This will create a subdirectory qxfwk with a qooxdoo skeleton in it, > with the name space novolog.fwk, and all directories adapted to that. > You might come across issues when you then develop and use your > code, as > complex name spaces are little used so far, but I know others are > using > them too. If you come across issues, let us know. > >> config.json : I also have no idea about what to put, if I have to, >> in the config.json file. > > Again, just read through the Hello World example. After running > create-application, the skeleton should compile out of the box; try > that. If you are only developing a library, you might never need to > tweak the config.json (You can even develop a little test > application in > this library without changing config.json, to module-test the library > itself). > >> 2. The application that will use the lib >> In the config.json for the application, I'll add the following : >> libraries" : { >> "library" : [ >> { "manifest" : "<build-time path to the previous qxfwk >> folder>/Manifest.json", >> "uri" : "<run-time path to the qxfwk folder or to the >> qxfwk/source or to the qxfwk/source/class folder ?????>" >> } >> ] >> } >> >> Am I correct ? > > Yep, that looks good. As you already know from my mail from last > night, > the path given in "uri" should end in the directory holding the > Manifest.json of the lib. > > T. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
