Hi Everyone, After the rather productive birthday weekend of hacking on Padre, I think there are a few things people got their heads around things that really should be captured and documented on the site.
Of note is the translation stuff in Padre. I know Zeno spent a fair bit of time on this and I think along the way got the hang of when to use _T() and when to use Wx::gettext() for translation. This is the sort of thing that needs to be captured and made into a document for plugin developers and new comers alike. I even recall seeing someone say in the channel that it can be difficult to get started on something when it's hard to find the major bits of padre. Things like how and when you want to get a reference to "main", or the ide, or the current project etc etc. If we can take some of the effort out of reading through the code before getting started with simple examples etc, I think it will lower the barrier somewhat for people to get started. This is the sort of documentation that would make life a little easier for people to get into Padre development. The howto page http://padre.perlide.org/howto.html seems to be mostly about using Padre itself. The getting involved page http://padre.perlide.org/getting_involved.html outlines how to get involved in the various tasks that need to be done on a project, which mentions keeping the wiki up to date. To be honest, the wiki drives me crazy... I can't find my way around it at all... possibly something that can be remedidated with someone spending time sorting it out. Reading through all the words you do find a link to a "developers howto" on the wiki. But still not much about how to do things with the internal bits of Padre. The Developers Page is good, but I often find myself clicking on it with the intent of finding information about developing for the Padre platform, or at the least a "why Padre will make your life better" missive, with links to development documentation. Maybe that page could be named "About the Developers" and the link on the page changed. Anyway, there's a lot to do to improve the website, but at the very least, I'd like it if those of you who have worked on a part of Padre that took you a while to figure out, spend about 20minutes replying with some info about it I'll highlight that I'm after Zeno to put something down about the translations, it doesn't have to be 100% correct, that's what peer review is for. Also, I'll spend a bit of time covering Padre::Current and try to massage some sort of documentation about that and when and why you use it. Hope this kicks off a flood of info... I'll be happy to collate it and put it up somewhere on the site... Pete.
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
