I'm still looking at PHP features: If you're a PHP expert, you can add your own library, but you usually have a system running...
This is the same idea. A project called PHP Groupware has also block notions and you can activate/deactivate/install/uninstall through a web interface. Basically, I completely agree on what you're saying When do we start? -----Message d'origine----- De : Tim Holloway [mailto:[EMAIL PROTECTED] Envoy� : vendredi 7 novembre 2003 16:13 � : '[EMAIL PROTECTED]' Objet : RE: Compilation of Cocoon / Binary Distribution / Different Configurations, Cocoon out-of-the-box is a wonderful showcase for all the great things it can do. However, once you're done admiring all the neat features it has, you really want to build your /own/ Cocoon. Preferably, you'll do this as an additive process, rather than a subtractive one. Firstly, because it's more likely to produce a smaller production system and secondly because Microsoft has given us all numerous object lessons in what can happen when everyhing's turned on by default. Not to suggest that the cocoon samples are inherently unsafe, but few complex systems are completely safe, especially in subsystems that no one's watching because they aren't part of the "important" part. I think that the blocks showcase page was a great idea. It does a decent job of summarizing what the presupplied features of Cocoon are. I'd even go so far as to say that one way of making customization easier would be to put checkboxes on that page so that people could preview facilities, then uncheck the boxes for blocks their production system isn't going to need. Then that list could be gathered up to make the new build profile. Adding, of course, external block definitions for third-party and in-house supplied extensions. Tim Holloway > -----Original Message----- > From: Nicolas Toper [mailto:[EMAIL PROTECTED] > Sent: Friday, November 07, 2003 9:54 AM > To: [EMAIL PROTECTED] > Subject: RE: Compilation of Cocoon / Binary Distribution / Different > Configurations, > > > Yes you're right, I meant something more easier to use but on > the Website > and adding new processes (but automatic). > > On the broadening base, let's look at PHP vs EJB (I know this > is stupid :=)) > > EJB doesn't have so many users as PHP but it doesn't matters > b/c EJB are > used in specific context... > > Some core Cocoon's concept could be used not only for XML > publishing but for > all kind of websites. > > -----Message d'origine----- > De : Alexander Schatten [mailto:[EMAIL PROTECTED] > Envoye : vendredi 7 novembre 2003 15:34 > A : [EMAIL PROTECTED] > Objet : Re: Compilation of Cocoon / Binary Distribution / Different > Configurations, > > > Nicolas Toper wrote: > > >Yes, but we would need to rethink the Cocoon build/releases cycles to > >simplify the installation... > > > > > no, I do not see why; As an expert one could rather easily > provide such > an binary installation package. no problem at all I see. > > >But we first need to know if we want to broaden the user base or the > >situation is fine (cocoon is seen as a powerful but > difficult product) > > > > > yes, *this* is an important consideration; I have no clear > answer yet. I > would suggest, that we should try to broaden the perspective. > > you might not forget, that Cocoon is for many purposes not much more > complex then e.g. PHP. If you want to do XML publishing and you would > have the simple installation as described it is not so complex: > > with things like Automounting of subsitemaps (great feature) > and the like. > > you only should remove the complexity from the installation and mark > *much, much clearer* what is ready for prime-time and what is > experimental. > > I often hear complaints like: Cocoon is nice, but I do not > know where to > start when I want to solve problem X; there is solution A, B > and C, ... > > like: a dozen of form frameworks; database actions, SQL transformer, > XSP, logicsheets, ... > > and no "best practice" document that is problem oriented... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender and delete it from your computer. Although our company attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
