Zhiwu Xie wrote:
However the question remains that if an editor does not support certain things shall we just leave it and lose certain functionality,
one thing we can do is introduce various levels of compliance, e.g. re editing Level 1) New, Open, Save, Save As, Exit Level 2) Save All, Close, Close All
e.g., from tightly integration with Lenya to loosely integration, or simply an external editor that does editing job only but cannot access assets and links managed by Apache Lenya?
for instance specific "lookups" can be part of higher compliance level
This may sound absurd in the first sight but if the tightly coupled editor cannot do certain things an external editor can do, isn't it better to be able to do it awkwardly rather than cannot do it at all?
I am not sure if I fully understand. What exactly do you mean by tightly coupled editor and external editor?
At this stage I have almost no idea how Lenya works so the above question is only speculation.
I think that's actually a plus ;-), because it hopefully means you tend to a more generic approach. Michi -- Michael Wechner Wyona - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
