Re: New blocks on the block and fixes to the build
Torsten Curdt wrote: > Probably best to move it back to scratchpad. I have some time off and I > could look into the servlet, but the code in the PHP servlet itself might > be more work than I'm willing to put into it... perhaps we could just > file > a bug against the PHP servlet :) Ok, if nobody comes up in the next days, I'll move it away into scratchpad. ...what about marking the block "unstable"? so nobody needs to move things around... I saw that you have done so with precept, and at first it seemed ok, but there is a problem with it. On Avalon we did it with Excalibur, and it was a real mess, because developers and users were not really aware of what was unstable and what not. Now we have a sandbox module, to make it clearer than ever where the unstable code is. So I'm quite strongly in favor of moving unstable stuff to scratchpad. By moving them to blocks we found dead code. Now I don't want to see dead code in blocks too... BTW, what about "precept"? Is it really still scratchpad? Is there a possibility of merging it to a unified form handling system, or I'm way off target? -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
> Probably best to move it back to scratchpad. I have some time off and I > could look into the servlet, but the code in the PHP servlet itself might > be more work than I'm willing to put into it... perhaps we could just > file > a bug against the PHP servlet :) Ok, if nobody comes up in the next days, I'll move it away into scratchpad. ...what about marking the block "unstable"? so nobody needs to move things around... -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
Tony Collen wrote: On Thu, 19 Dec 2002, Nicola Ken Barozzi wrote: That's what I feared. All this block stuff is indeed clearing a lot of cruft. Someone wants to follow-up and fix it. If not, I'll have to declare it unmanaged and move it somewhere else, maybe in scratchpad. Probably best to move it back to scratchpad. I have some time off and I could look into the servlet, but the code in the PHP servlet itself might be more work than I'm willing to put into it... perhaps we could just file a bug against the PHP servlet :) Ok, if nobody comes up in the next days, I'll move it away into scratchpad. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
On Thu, 19 Dec 2002, Nicola Ken Barozzi wrote: > That's what I feared. All this block stuff is indeed clearing a lot of > cruft. Someone wants to follow-up and fix it. If not, I'll have to > declare it unmanaged and move it somewhere else, maybe in scratchpad. Probably best to move it back to scratchpad. I have some time off and I could look into the servlet, but the code in the PHP servlet itself might be more work than I'm willing to put into it... perhaps we could just file a bug against the PHP servlet :) Tony Tony Collen -- [EMAIL PROTECTED] College of Liberal Arts University of Minnesota, Minneapolis, West Bank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
Tony Collen wrote: On Thu, 19 Dec 2002, Nicola Ken Barozzi wrote: For me it's ok. In the future I will move the build system to download the jars from the net instead of CVS if we will all agree, but in the meantime it seems like the best solution. More down to earth... where is it? It's created when you configure PHP with --with-java and --with-servlet. I suppose this is also a good time to bring up the fact that the PHP Servlet doesn't actually work. That's what I feared. All this block stuff is indeed clearing a lot of cruft. Someone wants to follow-up and fix it. If not, I'll have to declare it unmanaged and move it somewhere else, maybe in scratchpad. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
On Thu, 19 Dec 2002, Nicola Ken Barozzi wrote: > For me it's ok. In the future I will move the build system to download > the jars from the net instead of CVS if we will all agree, but in the > meantime it seems like the best solution. > > More down to earth... where is it? It's created when you configure PHP with --with-java and --with-servlet. I suppose this is also a good time to bring up the fact that the PHP Servlet doesn't actually work. Tony Tony Collen -- [EMAIL PROTECTED] College of Liberal Arts University of Minnesota, Minneapolis, West Bank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
Vadim Gritsenko wrote: Nicola Ken Barozzi wrote: As some have noticed there was a glitch in the block build system that made samples and mocks needed if a block has requested it, for all the following ones. This was due to Ant immutable properties: once set, they remain set. It's not fixed. I've also renamed module.xml to project-info.xml as decided here, and made 4 new blocks: bsf, html, php and lucene. For Lucene I've included the Lucene transformer that was in scratchpad, please let me know if there are objections. The html block now relies on jTidy but we can base it later on nekohtml. Thet's why it's called html and not tidy. Finally, the php block. Mock objects are missing, so I've commented it out in properties.xml for the build. Anyone can help on this? Can we put phpsrvlt in the cocoon CVS? PHP being Apache project, this should be ok For me it's ok. In the future I will move the build system to download the jars from the net instead of CVS if we will all agree, but in the meantime it seems like the best solution. More down to earth... where is it? -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New blocks on the block and fixes to the build
Nicola Ken Barozzi wrote: As some have noticed there was a glitch in the block build system that made samples and mocks needed if a block has requested it, for all the following ones. This was due to Ant immutable properties: once set, they remain set. It's not fixed. I've also renamed module.xml to project-info.xml as decided here, and made 4 new blocks: bsf, html, php and lucene. For Lucene I've included the Lucene transformer that was in scratchpad, please let me know if there are objections. The html block now relies on jTidy but we can base it later on nekohtml. Thet's why it's called html and not tidy. Finally, the php block. Mock objects are missing, so I've commented it out in properties.xml for the build. Anyone can help on this? Can we put phpsrvlt in the cocoon CVS? PHP being Apache project, this should be ok Vadim (mail of initial checkin) http://archives.real-time.com/pipermail/cocoon-devel/2000-June/000120.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
