requirement
avatar mbabker
mbabker
31 May 2013

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.

avatar mbabker mbabker - open - 31 May 2013
avatar mbabker mbabker - open - 31 May 2013
avatar b2z
b2z - comment - 1 Jun 2013

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 :)

avatar eddieajau
eddieajau - comment - 1 Jun 2013

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

avatar eddieajau
eddieajau - comment - 2 Jun 2013

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.

avatar mbabker
mbabker - comment - 2 Nov 2013

Framework is just about at 1.0. With that said, this is what we're actually using right now from the Framework:

  • App
  • MVC
  • Database
  • Date
  • DI
  • Event
  • Filter
  • GitHub
  • HTTP
  • Input
  • Language (until #124 is in)
  • Log
  • Profiler
  • Registry
  • Router
  • String
  • URI
  • Utilities

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?

avatar b2z
b2z - comment - 2 Nov 2013

Looks good at the moment.

avatar elkuku
elkuku - comment - 2 Nov 2013

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...

avatar mbabker
mbabker - comment - 2 Nov 2013

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.

avatar elkuku
elkuku - comment - 2 Nov 2013

Oh I see - an old commit 13 days ago ... we should update more frequently :toilet:

avatar mbabker
mbabker - comment - 2 Nov 2013

Let's not talk about how far behind the server is compared to the git repo :clock9:

avatar b2z b2z - close - 3 Nov 2013
avatar b2z b2z - reopen - 3 Nov 2013
avatar dbhurley
dbhurley - comment - 3 Nov 2013

If you update you'll need to address the problem stated in Issue #164

avatar elkuku elkuku - close - 12 Dec 2013

Add a Comment

Login with GitHub to post a comment