Composer

[perftools]

Composer

[markstory]

Twig is already in the code though. I could see a use for composer if we had more dependencies. As it stands with only one, I don't think it makes much sense. Also including composer means there are more steps to getting things setup and working.

[onigoetz]

I know that twig is already included. But with composer that would mean
that it'es easier to upgrade. Also you could provide a zip package
containing the dependencies.

wouldn't it also be nicer to use a microframework to handle the routing/url
stuff ? that could be handled in dependencies.

Le jeudi 7 mars 2013, Mark Story a écrit :

Twig is already in the code though. I could see a use for composer if we
had more dependencies. As it stands with only one, I don't think it makes
much sense. Also including composer means there are more steps to getting
things setup and working.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-14572535
.

[markstory]

Providing zip files that aren't git repo dumps means we'd need to setup alternate hosting as github doesn't support that anymore. Github also doesn't include submodules in zip files so that's not really a viable option either.

A micro framework might be nicer, but at this point xhgui is pretty small, and a micro framework wouldn't really add much in terms of benefit. I'm a big proponent of frameworks, but in this case I'm not sure there would be much value added by adopting one. The big drawback would be that xhgui would be considerably larger, as most frameworks easily dwarf the current xhgui codebase.

If in the future xhgui becomes a larger thing adopting a framework would make sense.

[onigoetz]

Yeah you're right. it doesn't make sense for the moment.