Re: CVS modules proposed reorg

Hi Mike and all others :-)

Cleaning up wouldn't be a bad idea.

I think my knowledge about Java and also about eclipse is very low,
so I don't know whether it's easy to separate the debugger
from the PHPeclipse core, and whether it makes sense.

Also I don't know whether it make more sense to put dbg and xdebug
together in one plugin, or keep it separate.
I would expect, that about 50 % of the debugger plugin code could be shared
by dbg and xdebug. I think the main (and maybe only?) difference is in communication
between the debugger plugin and the debugger.

BTW, when talking about cleaning up the CVS repository,
wouldn't it be an idea to switch to subversion?
Converting the CVS repository to a subversion repository.
I think this is possible on sourceforge!?
Subversion would be an improvement in version control,
files could be renamed, moved or deleted without breaking the history.

And also BTW :-), what's about a new snapshot release of PHPeclipse for
the eclipse 3.2 user? Debugging is working again :-).
And is someone taking the patch into account, which was posted by the 
email from 2006-08-11 of Ben Konrath?

Servus
  Robert


On 29 Aug 2006 at 10:53, Mike wrote:

> 
> Hi,
> 
> if I recall correctly, one of the things thought about some time ago was to simplify PHPEclipse in a 
> way that detaches anything non-core and have just the base plugin. Everything else, like Smarty 
> and Debug support would be packaged externally. There are many advantages here. A very 
> important one is that the structure of the main functional areas of PHPEclipse becomes much 
> clearer and faster to grasp by developers interested in helping out. It is also much easier to test 
> (optional plugin vs. stable base plugin etc.) and also to release.
> 
> I am not really a Java programmer and helped this project primarily by occasionally releasing stuff 
> on Sourceforge. This is not even my idea. Therefore I am probably the least qualified to suggest 
> anything on this matter, but do so anyway before nobody else does.
> 
> I would suggest to strip the Smarty editor and all debug-related plugins from the PHPeclipse core. 
> Not throw them away, but have them live as optional standalone plugins that depend on the 
> PHPeclipse base plugin.
> 
> Smarty support is very rudimentary at present. There is just some rudimentary syntax highlighting 
> that is also broken. Also, the current Smarty editor depends on the 
> net.sourceforge.phpeclipse.xml.* plugins. I believe these are copies of a WTP predecessor or 
> something of that sort. Therefore these should probably be dropped too at some point once the 
> PHPEclipse code inherits the needed functionality from either WTP or some other appropriate 
> Eclipse components. That would remove plenty of code bloat from the PHPEclipse source. 
> Besides, the Smarty editor is just an editor and could or even should be a standalone plugin by 
> itself.
> 
> DBG and XDebug support:
> Right now there are two people working on debugger support in PHPeclipse that I am aware of. 
> Robert on DBG and Christian on XDebug. DBG support is currently "built-in" into the base 
> component while Robert is working on a branch with XDebug support. This makes it quite hard to 
> package and release and confusing for people not involved in the development process too. For 
> the end-user it would be great if the support for the desired debugger could just be installed as an 
> optional plugin. PHPEclipse as such does already basically work with both, right? I would be 
> grateful for comments from Robert and Christian to shed some light on this matter.
> 
> I do not know in how far this would suggest or even require further changes to the CVS structure 
> as already proposed by Philippe. So please comment.
> 
> Thanks
> Mike
> 

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642