Carsten Ziegeler wrote:
Glen Ezkovich wrote:
The fix appears easy, but is something broken? Has someone expressed
the desire to use two languages in a single sitemap or is this just
an instance of feature creep?
I tend to agree, so I think we should for now just forbid to write
different map:flow sections in a single sitemap (by different I mean
that they use a different interpreter). If someone wants to use more
than one language we can add that easily.
agree
My fear is that this may lead to
conflicts in function naming that we will need to resolve in the
future.
On the other hand your proposal for a SitemapEnvironment
object seems like a smart refactoring.
Ok :)
in spite of being a specialist in this area of Cocoon, I think it makes sense.
--
Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
