Archive for the ‘Padre’ Category

24/7 commercial quality support – for an open source project

Wednesday, February 17th, 2010

Yesterday a fellow developer had a problem with a well known very big open source project. He tried to get support from that project, but nobody answered. It was one of those tools installed on most Linux servers – but the community wasn’t able to answer simple questions.

The Padre IRC channel window was next to his IM window when he told me and I was thinking about Padre support.

The Padre support channel (called #Padre on irc.perl.org) is open 24/7, and there are about 45 people and one or two bots around, but at least some of them are always alive and ready to answer questions.

There are two facts that gave us this high reachability (I think):

1. Our developers are all around the world

Some Australians are really pushing Padre, including Alias who did 16% of the core code and waxhead, our current release manager. We got some few US guys and a strong European and Middle Eastern group. Most of them are online and usually happy to help users when they’re at their desks.

2. Padre is a working tool

This is true for many open source things, but Padre is something you use everyday and – compared to tools like “less” or “traceroute” – you recognize it. Many people use Padre for working, it’s always visible while it’s being used – compared to Apache or syslogd that are hidden if they’re working probably.

Some people using Padre also open their IRC client or the Mibbit web-based IRC client for joining the Padre support, asking  questions and answering others.

Give us a try

Padre is a complex IDE. If you try it out, you’ll likely have questions or maybe even problems. Feel free to come to our support channel and ask your question. It might take some minutes or even half an hour until someone replies – as many people are busy with work – but I guess you’ll get your answer. And you’re welcome to stay there and spend a minute on answering a question of someone else.

Padre requires a perl built using threads

Wednesday, December 16th, 2009

A Padre user entered the Padre IRC channel today because he was unable to run Padre from the Ubuntu repositories on his Ubuntu 9.10. He got the error “Padre requires a perl built using threads”.

szbalint was also there and also using Ubuntu 9.10. He finally noticed that the user wasn’t using the Ubuntu perl.

He installed some CPAN modules some time ago – and one of them required Perl 5.10.1 (Ubuntu comes with 5.10.0). CPAN installed a new Perl but he answered the threading-question with “n”.

Module authors should check their requirements. Few things really require 5.10.1, most modules also run find on 5.9 or older versions.

If you get a thread error while starting any Perl application, try out the “which perl” command. It should point to /usr/bin/perl if you don’t have any custom Perl installed.

Padre 0.52 fresh on CPAN

Tuesday, December 15th, 2009

A German Padre 0.52 announcement was just posted, here is a short English one:

Padre 0.52 is out – and already downloadable from CPAN!

Peter (waxhead) did a very good release post, don’t miss it.

Also don’t miss the new Padre version which has few, but important news. For a full list, please check out Peters blog or the Padre 0.52 ChangeLog.

The Padre 0.51 story

Monday, December 7th, 2009

Finally,

Padre 0.51 was released last weekend.

It took longer than planned to make this release for various reasons. Padre hat some kind of code silence during the last weeks since 0.50. It was the worst “code silence” I noticed since I first tried Padre – we even had some days without one commit this time!

While 0.51 was coming up, many people got time to work on Padre again and we got a good release with new features and bugfixes.

Special thanks to Peter

Lavender (waxhead) for becoming release manager for 0.51. He managed to publish the release while being busy with other work, a kids birthday and really strange Perl::Critic problems. He did the official 0.51 promotion blog post. Don’t miss  it.

Padre news

Here are some (few) lines from the changelog for 0.51:

  • Find all option showing all matches in bottom tab (CODE4PAY)
  • Improved “Find Method Declaration” based on perltags (SMUELLER)
  • XS (perlapi) calltips based on the perlapi of 5.10.1 by default. Can be configured to show the perlapi of any release of perl back to 5.6.0 if Padre::Plugin::XS is installed. (SMUELLER)
  • Fixed a number of search/replace related bugs (ADAMK)
  • Upgraded tracing to new Padre::Debug that compiles out when not being used. (ADAMK)

Many more are listed in Peter’s blog and the full list could be found in the 0.51 changelog.

I was really happy to see Adam Kennedy, Steffen Müller and Ahmad M. Zawawi back on the list of regular committers. Ahmad promised “it is gonna be something special before the end of the year…” on IRC lately.

Upcoming

It looks like Padre 0.52 will be a big bugfixing release. If you don’t want to wait, feel free to look at the current changelog.

Please help!

Padre has a strange problem filed as ticket #750: Ctrl-Tab and Ctrl-Shift-Tab don’t work anymore on Ubuntu and maybe other Linux versions. I suspect some Wx issue but I’m no Wx guy at all. If you got any idea about this, please come to the Padre IRC channel #Padre on irc.perl.org or add your ideas to the ticket. Please also add your experience to it if you’re using a OS not mentioned there.

Working with Padre::File

Wednesday, December 2nd, 2009

Far away from being done, Padre::File is still a help.

I got a new project shortly: Create a web-based app including design and templates.

Like any other project, this one has a dedicated Padre session. I’m no design guy, so I was reusing CSS from another project – but the static files (including the CSS) were not on SVN and I don’t like temporary files polluting my disk because I often forget to delete them :-)

I just used Padre’s “File” -> “Open URL” and inserted the URL of the CSS file. Padre::File detected that this was no local file and used the HTTP driver, Padre::File::HTTP to get it. It’s marked read-only in Padre, but I could use it for reference like any local file.

The open CSS is included in the Padre session and whenever I open this project, Padre also opens the remote CSS file without wasting any bit of my local disk.