At some point down the road, we should look at the dependencies we've introduced and see which ones we can drop. For example, instead of importing the full Framework, only grab what we need (and their dependencies, hopefully that doesn't inherently drag in the whole thing...). Also, should the renderer interface be sent up to the Framework, I think we can drop Mustache from our composer.json file.
Not a priority by any means, but jotting it down on the to-do list as I think about it.
I'll give it some thought when I get back to Australia tomorrow.
Regards,
Andrew Eddie
http://learn.theartofjoomla.com - free tutorials and videos on Joomla
development
I think the dependencies should be split out, but we could wait until the Framework tags it's first version (the FW is a pain at the moment because it clones instead of downloads). I'll start a new thread about the folder structure to answer the question about the Renderer package.
Framework is just about at 1.0. With that said, this is what we're actually using right now from the Framework:
The Log uses should be refactored out as we're using Monolog. String has one use here. Everything else looks to be good as it is.
Thoughts?
Looks good at the moment.
A side note on dependencies and the String package: String currently uses jimport()
which we don't import since the JTracker project is good with the PSR loader ;)
So I guess the above mentioned code that uses String would blow once it's used...
In the current Framework, jimport()
is actually gone (along with all of Joomla's custom loaders) and String just does a require_once
to the phputf8 library files. So, that isn't an issue.
Oh I see - an old commit 13 days ago ... we should update more frequently
Let's not talk about how far behind the server is compared to the git repo
Good points. Talking about dependencies, we can revise them when we will be in the final stage. But Renderer could already be proposed IMO :) BTW I asked Andrew to look into it :)