petsagouris

Another (huge) one is Transifex But the bad thing is that none actually support the format for the translations that Processwire uses: File formats on transifex File formats on getlocalization

Heh, I am doubting myself because I have not done this before.

I am looking to check some requirements with the PHP environment before the module is installed and maybe even have the module deny or alert the user trying to install it of any issues. How would that happen ? I did find out about the Module:: __install() hook but where should how should I use it in the module itself ? Just go ahead and implement the method inside the module's class?

Yes I too believe that the intentions behind the PSR-2 are good mainly because it is a good thing to have if there are PSR-0 and PSR-1 standards in-place that promote code segmentation and proper focusing on the parts of the libraries. I am sad about PSR-2 being basically turned down in Processwire because having to deal with more than one source base (I am an avid open source stalker and minor contributor) hinders the ability to contribute by having another layer of adjustment before I get to see what is going on, that being the visual aspect of the code. But my main question was about how you think that namespaces in Processwire will be structured? Are there going to be big changes? Anything the community can help with?

The transliteration character replacement array can be changed in the settings for the Page Title module. http://your.host.address/<processwire_admin_path>/module/edit?name=InputfieldPageName

Oh, no PSR-2 then... thats a little bit sad. Thanks for the link diogo.

Hello all, first post, nice to be here. Thanks for Processwire. @ryan How are you thinking of going about namespacing and autoloading in Processwire? Isn't having the Wire class being the mother of all classes making this tricky? While you are on the standards issue, why not go for PSR-2 too ? Common coding style would benefit everyone.