Hi Pete, hi all, On Wed, Jul 28, 2010 at 3:35 AM, Peter Lavender <pla...@internode.on.net> wrote: > ... 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.
I will try to add the information to the wiki within the next days, to http://padre.perlide.org/trac/wiki/TranslationIntro which is not really clearly arranged, so I may even split it up into different pages, like "i18n for programmers", "creating a new translation", "updating an existing translation", "translating plugins", etc. Plugin i18n seems to be broken right now anyway, but I still lack the knowledge to fix and document. I hope to get there soon, though ;-) Clutter is a problem of many pages in the wiki, the download docs are a good example: http://padre.perlide.org/trac/wiki/Download I tried to tackle this a few months ago, by creating each a download instructions and a packaging status page for each operating system/distribution, but I did not finalize this because there were links from the static website and Hyppolit that would have been broken. The (preliminary) result can be seen here: http://padre.perlide.org/trac/wiki/DownloadOverview I'd suggest we try to use those pages from now on, and fix all links on the static website and on Hyppolit. I have the strong opinion that the smaller pages are both easier to read and easier to maintain. I am rather used to wikis, but large and (rather) unstructured pages are not really an invitation to add/modify content. > 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. Agreed. It would be great to have an intro to Padre's architecture/code structure (even if this may change over time), and a plug-in writing howto. I am willing to contribute to those as I learn more about Padre. > 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. See above ;-). I volunteer to something here (if time allows), but any additional help is appreciated. For example: 1. http://padre.perlide.org/trac/wiki/Plugins - the plugins page has a nice structure (a table), but the information is incomplete. Everyone could check out their favourite plugin and see whether the info there is still up to date. Or you could try a new plugin. 2. http://padre.perlide.org/trac/wiki/FAQ - if you hang out in IRC a lot, you may see questions coming up again and again - put the answers there ;-) 3. http://padre.perlide.org/trac/wiki/TitleIndex - have a look at the index and make orphaned pages reachable again. > > 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. Okay. > 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. Great! One more thing: Concerning the wiki and the website, I suggest people be bold in their actions. There are many things there right now that require improvements or even fixes, so don't be too afraid to break something. Use of course common sense ;-) Best regards, Zeno _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
