25 Mar
2010
25 Mar
'10
11:53 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
Dne Tue, 23 Mar 2010 14:44:47 +0100
Dieter Adriaenssens <dieter.adriaenssens(a)gmail.com> napsal(a):
Writing good code is always about discipline, if you
don't have the
discipline to apply the same coding style, think about the best
solution in the long run and don't go for the quick and dirty, use
comments where necessary, write documentation, ... then using a
templating system or any other tool is not going to solve that. ;)
It's not going to solve that, but it's going to help. It is hard to
force discipline from external contributors (you usually end up
rewriting patch yourself or not applying it at all) and when there is
force from the tools into right direction, it always helps. At least
this is my experience from other projects.
I can even provide example from phpMyAdmin - the current versions use
php files for translations. One of translations used things not
expected by our tools to update and sort translations, but valid in
PHP. Over time, the translation got horribly broken without anybody
noticing. This is exactly problem which can appear if you provide too
much flexibility where it is actually not needed.
I haven't used a templating system before, but
I'm interested in it.
But I think the MVC concept is more important, than using just any
templating system. As choosing a system for PMA will affect a big part
of the current code, I think it's a good idea to look for the best
fitting solution (but that's a discussion that's going on in a
different thread, I think), before rushing into just any system.
Well I'm not really sure if right now is good time for such move.
Starting this in parallel with GSoC will make things really hard to
merge and synchronize.
- --
Michal Čihař | http://cihar.com | http://blog.cihar.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkurJKUACgkQ3DVS6DbnVgSl2ACfdJ7AoSN6b0hKTqjmxotEXtKY
GVYAn2scDoaP8XlMQeibEWV1IzCz4Ji1
=AVqQ
-----END PGP SIGNATURE-----