Hi, thanks for your response! It is very valuable to us.
On Sat, Feb 12, 2011 at 9:30 PM, chm <devel.chm...@gmail.com> wrote: > On 2/12/2011 10:09 AM, Claudio Ramirez wrote: >> >> I spent some time reading the mailing list and irc logs. Because of the >> distributed nature of the communications channels, the discussion is >> difficult to follow if you are not at the right time in the right place. > > Yes, especially if one is not part of IRC discussions. I know it is not easy but you can actually follow the IRC channel via its public log: http://irclog.perlgeek.de/padre/today >> Several developers feel that Padre is at a point where some stability is >> expected. While this is extremely good news for a young project like >> ours, it also means that "fast moving target" releases from the >> beginning are --or should be-- behind us: users rely on our project to >> do their work. > > I am one of the users who could try Padre but hasn't > yet for several reasons including: > > (1) My main platform is cygwin and I have not > been able to install Padre for that platform. > I'm not motivated to learn a new IDE for only > a subset of my perl usage platforms I don't recall seeing your failure reports. AFAIK currently none of the Padre developers is using cygwin so it would be very useful if you could describe your attempts to install Padre and what went wrong. In general I think there are two main issues with Padre: 1) You need a threaded Perl, this needs to return some true value: perl -MConfig -e' print "$Config{usethreads}\n" ' 2) You need to install Alien::wxWidgets and Wx I don't know if wxWidgets can be installed on Cygwin. Someone on the list might be able to help you further. Please open a separate e-mail thread for this and use a title including Cygwin. > (2) If the basic architecture and structure of > Padre is in constant flux: working, not working, > changing user interface, unclear or out of date > documentation, that is a barrier to potential > new Padre users. The situation is not THAT bad. Maybe except of documentation where we really lack. In general there are not THAT many changes but they still create noise. > (3) The "quick start" options to get Padre up on > the web page seem to be out of date and/or > incomplete. > > The two things that would most help me try/use/develop > with/for Padre include: > > (1) up to date, simple installs of the latest Padre > (1-click or less :-) for all the Perl platforms > (win32, *ix, macosx, cygwin), I think we all agree on this and we have been struggling with a solution since the inception of the project with various levels of success. We'll see the recently released CitrusPerl will be a good solution for at least Win32/Mac/Linux. > (2) up to date, clear and directly accessible docs > from the Padre web page > > A side benefit of the very easy install availability > is that the fact that Padre is still growing and > evolving would not be as much of an obstacle for > folks to try it along the way. Once it was clear > that Padre evolution had slowed and that growth > and maturing was mostly happening, that would be > the time for introducing a "stable" branch. It seems development have slowed down in the past few month and is coming in waves. regards Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
