[EMAIL PROTECTED] wrote:
In addition we have implemented part of a debugger (consisting of another plugin and the Cocoon side) that some of you saw in Ghent. Sylvain posted the link to a screenshot earlier.
Yes, and it looks cool indeed.
Hmmm... not really. How about working together on a underlying common debugging architecture? I'm talking about communication protocols between a debugger and the server, as well as needed server-side components. This way one might be free to implement the client at will, so that you might have the Eclipse plugin as part of a broader set of Cocoon tools, Cocoon might include a Swing plugin, some other might write a command line debugger... how about it? It might be a good way to:At the moment I am trying to convince "the powers" that we should donate sunBow and the debugger to Cocoon. There are various reasons for this that I won't get into now. The outcome of my push to do this is also uncertain at the moment. > Now, Nicola mentioned that the concept for the debugger he discussed with Gianugo should not be based on eclipse. So that would of course rule out what we currently have.
1. not reinvent the wheel: S&N might consider donating the "generic" components, while preserving the investment in the commercial eclipse stuff (your boss might like that better ;-)).
2. have a flexible architecture wich might allow for future extension. Think JPDA for Cocoon.
How does that sound?
Ciao,
--
Gianugo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
