Actually only the packaging of zeta matters as we want to provide everything or a part of it. The jQuery UI package download system seems to be a good start, I guess. Another question comes if we do like this : will it be possible to make heterogeneous packages with this system. I mean can I ask Graph 1.0 with Config 3.2 ? or do I have a minimum rules to follow ?
Max (Thomas is my last name, guys) 2010/11/18, Tobias Schlitt <[email protected]>: > Hi guys, > > On 11/17/2010 03:58 PM, Jerome Renard wrote: > >> On Tue, Nov 16, 2010 at 5:43 PM, Gaetano Giunta <[email protected]> >> wrote: > >> [...] > >>> But think about this: why is eZ Publish bundling the whole of the ZetaC >>> when >>> it only uses a couple of components? > >> Simply because that was the easiest (and quickest) solution when I >> wrote the build system ;) >> I agree with you only required components should be included though >> but this discussion must >> go to another list ;) > > without talking too much of eZ Publish here, I think it makes sense in > that case. eZ Publish is a framework for which people want to write > extensions easily. So delivering the whole Zeta stack provides them with > more comfort actually. > > However, for a custom app, it does not make sense to bundle all Zeta > Components if you only want to use e.g. Graph or Mail (which are 2 of > the most used components). > > Regards, > Toby > > -- > Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 > Want to hire me? Need quality assurance? http://qafoo.com > eZ Components are Zeta Components now! http://bit.ly/9S7zbn >
