Re: CVS modules proposed reorg

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

2006/8/28, Philippe Ombredanne <[email protected]>:
>
> Hi:
> Here is the proposed reorg of the module I am planning to ask to sf.net.
> This would be about moving files/dirs and prune empty dirs so history
> will be kept.
> The main goal is to keep as top level modules core plugins and features,
> and move
> Please comment...
> No comment means acceptance. I will ask that in a couple days.
>
> Modules that stay the way they are:
> net.sourceforge.phpeclipse/
> net.sourceforge.phpeclipse.core/
> net.sourceforge.phpeclipse.debug.core/
> net.sourceforge.phpeclipse.debug.launching/
> net.sourceforge.phpeclipse.debug.phphelp/
> net.sourceforge.phpeclipse.debug.ui/
> net.sourceforge.phpeclipse.externaltools/
> net.sourceforge.phpeclipse.feature/
> net.sourceforge.phpeclipse.feature.core/
> net.sourceforge.phpeclipse.launching/
> net.sourceforge.phpeclipse.nl1/
> net.sourceforge.phpeclipse.phphelp/
> net.sourceforge.phpeclipse.phphelp.nl1/
> net.sourceforge.phpeclipse.phpunit/
> net.sourceforge.phpeclipse.smarty.ui/
> net.sourceforge.phpeclipse.tests/
> net.sourceforge.phpeclipse.ui/
> net.sourceforge.phpeclipse.updatesite/
> net.sourceforge.phpeclipse.webbrowser/
> net.sourceforge.phpeclipse.wizards/
> net.sourceforge.phpeclipse.xdebug.core/
> net.sourceforge.phpeclipse.xdebug.ui/
> net.sourceforge.phpeclipse.xml.core/
> net.sourceforge.phpeclipse.xml.ui/
>
>
> Those modules would be moved from top level under wiki/
> org.plog4u.wiki/
> org.plog4u.wiki.test/
> net.sourceforge.phpeclipse.wiki/
>
> Those (empty dirs) would be deleted:
> org.eclipse.jdt.debug/
> pluginphpeclipsetest/
> testplugin/
> phpeclipse/
>
> Those two files would be moved from top level under build/
> phpeclipse-extssh.psf
> phpeclipse-pserver.psf
>
> Those modules would be moved from top level under archives/
> net.sourceforge.phpeclipse.css.core/
> net.sourceforge.phpeclipse.css.ui/
> net.sourceforge.phpeclipse.html.ui/
> net.sourceforge.phpeclipse.js.core/
> net.sourceforge.phpeclipse.js.ui/
> net.sourceforge.phpeclipse.quantum.sql/
> net.sourceforge.phpeclipse.sql/
> net.sourceforge.phpeclipse.monitor.core/
> net.sourceforge.phpeclipse.monitor.ui/
> net.sourceforge.phpeclipse.news/
> net.sourceforge.phpeclipse.jtidy/
>
>
> Cheers
> Philippe
>
> philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
> nexB - Open by Design (tm) - http://www.nexb.com
> http://easyeclipse.org  -  irc://irc.freenode.net/easyeclipse
>
>
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Phpeclipse-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/phpeclipse-devel
>

-------------------------------------------------------------------------
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

_______________________________________________
Phpeclipse-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/phpeclipse-devel