-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer #10
Comments
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. |
I know that twig is already included. But with composer that would mean wouldn't it also be nicer to use a microframework to handle the routing/url Le jeudi 7 mars 2013, Mark Story a écrit :
|
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. |
Yeah you're right. it doesn't make sense for the moment. |
Update README.md with current compatibility info
Hi,
is there any plan or idea to include composer inside XHGUI ?
it would help for autoloading and inclusion of outer projects like twig
if yes, I would be happy to provide a pull request.
The text was updated successfully, but these errors were encountered: