Hi Andreas,
Thank you very much for the explanation. That --package-id parameter
seems to be what I was looking for. But I got a couple of other
questions:
Could current 0.7 generator produce something like list of used classes
including all dependencies (qx.* in particular)?
Could it use an alternate source loader (not filesystem, but say python
package resources or so)?
Thanks,
Oleksiy
On Mon, 2008-05-05 at 19:18 +0200, Andreas Ecker wrote:
> Hi Oleksiy,
>
> the concept of modularizing a qooxdoo app into packages is already quite
> powerful in 0.7. But it is neither well documented nor has it profen all
> to practical. We ourselves started to develop generator2, because the
> previous system was of limited use for practical large-scale
> applications (e.g. gmx.com).
>
> Therefore, the possibilities of generator2 (and the upcoming qooxdoo
> 0.8) will be much more usable. Of course, you have to decide yourself if
> you wanna dive into these features of 0.7 now or if you could wait for
> the future 0.8, which brings a lot of changes for the build process (but
> also for the GUI part, so there will be some manual migration work
> involved as well)
>
> The current documentation (incomplete in terms of packages):
> http://qooxdoo.org/documentation/0.7/split_up_application
> http://qooxdoo.org/documentation/0.7/custom_builds
>
> You may also want to have a look at the presets/ folder of
> framework/tool. As I said, the docs are not very good (worse than I
> thought they were - sorry about that).
>
> Bye,
>
> Andreas
>
>
> On Mon, 2008-05-05 at 19:23 +0300, Oleksiy Golovko wrote:
> > Andreas, thanks for the reply
> >
> > Could you please point me to the documentation page with 'packages'
> > concept described? Probably that is what I'm thinking about :)
> >
> > Thanks,
> > Oleksiy
> > On Mon, 2008-05-05 at 18:02 +0200, Andreas Ecker wrote:
> > > Hi Oleksiy!
> > >
> > > > I wonder if there any non-hackish way to define my own name for the "$"
> > > > variable in build? (using some command-line arg or Makefile parameter)
> > >
> > > For so-called "packages" in 0.7 this is automatically taken care of.
> > > When not using the more advanced packaging mechanism, you can still use
> > > an additional option for build process and define a package id that will
> > > be appended to the global $ variable, e.g. put the following into your
> > > Makefile
> > >
> > > APPLICATION_ADDITIONAL_BUILD_OPTIONS = --package-id=foo
> > >
> > > in order to generate a global $foo for the string optimization instead.
> > >
> > > Bye,
> > >
> > > Andreas
> > >
> > > PS: The build process will be changed significantly for qooxdoo 0.8.
> > > Please see the development docs and preliminary documentation about
> > > "generator2":
> > > http://qooxdoo.org/documentation/general/generator2
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
