Le Jeudi, 2 oct 2003, � 14:28 Europe/Zurich, Berin Loritsch a �crit
...For instance, if you changed BLOCK-INF to COCOON-INF, then it is very clear
that the Cocoon solution is proprietary to Cocoon, and noone should expect
a Cocoon block to function the same way in a Merlin/Phoenix environment.
Sorry, I overlooked this when saying that I basically agree with Stefano on going our own way for blocks at this time.
I'm +1 on changing the BLOCK-INF name to COCOON-INF or whatever makes sense and does not cause conflicts.
+1 here too.
Ciao,
-- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Now blogging at: http://blogs.cocoondev.org/gianugo/)
