[wp-hackers] Improving Plugin (and Theme) metadata

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jacob Santos wrote:
| I say, I think after Matt's announcement, we are going about it slightly
| off.
|
| I think we should fix the current localization issues with the current
| base, since both issues have patches which with a few slight
| modifications can fix the issues for 2.5. The current discussion can
| make it into 2.6, and by the time that happens, probably will have an
| awesome solution.
|
| The patch for #3089, only needs to have all __() functions switched to
| translate(), so that it doesn't pollute the WordPress catalog. The
| current patch by Hodgdon works, except for that one issue. Once that fix
| is committed, it will remove that ticket from our minds for 2.5 and we
| can move on implementing a better way in 2.6.

I am not comfortable with introducing one solution for localisation now
when we are already talking about replacing it with something better.

I think we would do better to push the localisation of metadata for
plugins (and themes) out to 2.6 so that we can develop a good all-round
solution.

Introducing localisation for this metadata is going to cause work for
plugin and theme authors to make use of it.  We do not want to give them
more work by changing how it works in the next version - we do better to
do it once in a way that works best and we are going to support forever.

| The patch for #5651, only needs to be completed and should reduce the
| memory load on big single file plugins. Add in the fix for #3141, and
| you have the recipe for something that fixes three central issues, two
| with memory usage and one with localization of plugins. I think it would
| make 2.5 even better than it already is and will mean a lot to those
| that use the features.

Optimising the current code for less memory usage and better performance
is good for 2.5.

westi
- --
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
~ C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHmirWVPRdzag0AcURAhkgAJoC0e+g5GEUsBdTPMqOEMVBgCDpXgCcDLts
dDJSbSMB0ZVoTjOOZJL8v3g=
=G4xV
-----END PGP SIGNATURE-----