Composer packaging?

[cviebrock]

Looks great! Any chance of re-working your code slightly to make incorporating it into Composer-managed projects easier? (i.e. composer.json file, namespacing and PSR-0 class names)?

[martinsteel]

Hi Colin,

I hadn't heard of the PSR-0 namespacing and class names, or Composer for dependencies, both look like they'd be a pretty good idea to adopt. At the moment my concern is how we'd sort out the namespacing without breaking compatibility when existing users update.

I'll definitely stick this on our todo list, it just needs a little thought before we commit to making any changes.

[weemen]

it's really hard introduce composer without breaking the compatibility now . Maybe you can create a tag. In general it's a bad idea to use the master branch for non development purposes. When tags are used then people can choose to pick a specific version number, they can stick with it or update it when new tags are available.

[cviebrock]

Sorry for not being clearer … I understand that, of course, there would be backwards-comparability issues. I wasn't suggesting and immediate change, but maybe something to consider for your "2.0" release.

[weemen]

It's ok :) btw I just saw you already have tags so my comment about the tags was quite useless. Another reason for not coding after midnight :). Anyway: I did make a pull request to you guys. Maybe you can do something with it.

[martinsteel]

Haven't forgotten about this but it's still on hold as it breaks WordPress (a significant number of our users) - hopefully they'll drop PHP 5.2 support soon and we can move with the times.

[develerltd]

Any update on this? It would be very useful to be able to use composer and namespace this