Here is a quick comparison. Please correct me if I am wrong. Goals: NetBeans/Eclipse are intended as rich-client platforms http://en.wikipedia.org/wiki/Rich_Client_Platform. Padre is not at the moment :)
Maturity: I remember using Eclipse for the first time in 2002 and crashes were the normal thing to expect while developing/building projects. Nowadays, I do not encounter any stability problems like before but that's after 6-8 years :) The same goes for NetBeans. Both need 1GB+ memory to operate seamlessly. Padre is 2 years old and is not resource heavy. Philosophy: NetBeans follows the batteries-included philosophy such as the very nice subversion support and green/red margin-UI for diff changes). Eclipse can be a bare-bone platform which means you'll need to install plugins to make it more useful to your particular task. Both are written in Java. Padre is written in Perl to actually write Perl and you have the ability to install plugins to extend its usefulness. Eclipse+EPIC for Perl (tested on win32): First you need to install Eclipse+Java (~440 MB) and then install EPIC via Eclipse using its update manager. The installation is easy once you have eclipse installed and then you need to restart Eclipse to apply the changes. And then you'll need to search in the new stuff wizard to find "Perl Project" to actually create a project which does not have Module::Starter enabled by default. You will need to go and write the path of Module::Starter (the default one is /usr/bin/module-starter). To enable Perl::Critic you will need to do the same thing but the interface is really nice. You can set the Perl::Critic level severity from there. You can also enable Perl::Critic to run automatically after Perl Syntax checking is finished. Since Eclipse build/task system is way mature, you will find that project Perl Syntax checking is really feasible for the whole project when applied only to modified files. Another plus for EPIC is the syntax checking color customization and Smart Typing (completing brackets, quotes, double quotes, ...etc). PerlDoc tool has no auto completion like Padre but it docks nicely near "Problems" tabs in the bottom. And you get to see PerlDoc and its source. Perl Debugger did not work for me at all on win32 with the error message "perl5db.pl did not return a true value". So basically EPIC at its current version is usable after installing it over Eclipse and on Linux (since the default configuration is *nix-based for the Perl::Critic and Module::Starter tools). Notepad++ for Perl (win32): The biggest plus of Notepad++ is that it is fast, stable when opening multiple files and integrates nicely with the shell. You have "Edit with Notepad++" action when you right-click files. All the other features are really seldom used as Peter said :) Bottom Line: Stabilize Task system Add a task manager view to list running tasks with the ability kill tasks safely Add file logging by default? A wizard for "Perl Project" that is based on a plugin for Module::Starter that reduces the nuisances of re-editing stuff. Please see Module::Starter reviews/bugs. I started doing the wizard stuff but I stopped to fix more important ones. Revamp preferences to enable plugin preferences with search ability Merge PerlDoc tools on Padre. I know I am the one to blame on this one :) Integrate Perl::Critic with a reasonable amount of starting options for development. Integrate Dist::Zilla support? :) Start the Alien::Scintilla or Wx::Scintilla project... and depend on it instead of the ancient Wx STC. so far I found that compiling stc needs g++ which Alien::wxWidgets needs anyways. Build up-to-date Padre binaries on *inux and win32 or at least make it easier for anyone to do it. Keep an open channel with Padre package maintainers on different platforms and try to help them as much as we can. And we need to focus on what's really useful and should be included in core by default based on community feedback or at least make it way easy to install Padre plugins and upgrade Padre in Padre :) Regards, Ahmad M. Zawawi azawawi On Tue, Nov 30, 2010 at 11:00 AM, Peter Lavender <pla...@internode.on.net>wrote: > On Tue, 2010-11-30 at 14:43 +1100, Adam Kennedy wrote: > > That's a good point. The SVN implementation is rather primitive, and IDE's > like eclipse and netbeans do do it rather nicely, well at least netbeans did > the last time I used it. > > I certainly think that a debugger that works like the debugger in Visual > Studio, the ability to move around the code base by right clicking on > methods and the like, along with decent support of various version control > systems would see Padre well out front. > > It's just the effort to do that and the time people can commit to the > effort, keeping in mind IDE's like Eclipse and Netbeans get commercial > support through various companies employing people to work on it, is what > will determine how long it takes for Padre to get everything we want in an > IDE. > > But for me today, Padre does a pretty darn good job and it's what I use > when I can. IT sure beats Notepad++, which to be fair does a decent job > itself if all you want is syntax highlighting and a zillion options to do > with text that I never ever use. > > > > > I would suggest that any feature which is not Perl specific, like the > svn and ftp stuff, will be more advanced than in Padre as we are > having to implement from scratch something which is provided for free > by the core Eclipse platform. > > Things that are more Perl specific, like the intuition and refactoring > and such, can be better. > > Adam K > > On 30 November 2010 14:40, Gabor Szabo <szab...@gmail.com> wrote: > > Shlomi, > > > > > > On Mon, Nov 29, 2010 at 7:11 PM, Shlomi Fish <shlo...@iglu.org.il> wrote: > >> On Monday 29 November 2010 17:09:37 Ahmad Zawawi wrote: > >>> Hi Shlomi, > >>> > >>> Could you please provide any links of such a discussion? :) > >> > >> This is the closest I found by grepping my mailing lists' archives: > >> > >> http://mail.perl.org.il/pipermail/perl/2009-December/010704.html > > > > First of all you could have said in your original mail that you are quoting > > me > > and not "a core Padre developer". Or did you write that message *before* > > finding the quote? > > > > Second, I don't think I wrote there that "EPIC is recommended". > > I wrote Eclipse+EPIC is more advanced. > > > > As I have not been using Eclipse for a while I don't know in which > > feature have Padre supassed it and in which features Padre is still > > lacking. Azawawi, it would be nice if you could give use a comparison. > > > > The issues I can see are > > 1) syntax highlighting for 5.10 > > 2) the debgugger in Padre is still not being very usable. > > 3) VCS integration > > 4) Editing via FTP? - I have never used it but as I understand many > > people do. Does it work well in Padre? > > > > > > Gabor > > _______________________________________________ > > Padre-dev mailing list > > Padre-dev@perlide.org > > http://mail.perlide.org/mailman/listinfo/padre-dev > > > _______________________________________________ > Padre-dev mailing > listpadre-...@perlide.orghttp://mail.perlide.org/mailman/listinfo/padre-dev > > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > >
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
