Extracting J! CMS libraries

[Matias Aguirre]

Hello!

In this last time I decided to move the code jUpgradePro to use DI because this change would help me in many things and I have found that many of the libraries I need to jUpgradePro, are based on CMS.

Exactly, these are the libraries I need: Table (and its variants), Access, Event, and User.

So I have been forced to remove these libraries so they can be used outside the CMS. I leave two links with these libraries:

https://github.com/matware-lab/access
https://github.com/matware-lab/table

Anyone know if these libraries will someday be extracted or will remain in the CMS? What will be the way of Joomla! on this topic? Any thoughts are welcome.

[George Wilson]

Me and Michael have considered both these packages in the past.

For JAccess there would need to be sizeable changes because we can't distribute a package that's completely static method based. Me and Michael had a WIP based on JAccess as it was about 2 years ago but it never really went anywhere

I'm still not convinced if by the time JTable has been framework'd whether it will be hugely different from Eloquent

Kind Regards,

George 

[Matias Aguirre]

Thanks George for the answer.

Do you think is a good idea to replace all JTable with Eloquent directly or just wait for a Joomla! solution for ORM/database?

[Walt Sorensen aka photodude]

On Thursday, November 17, 2016 at 7:27:40 AM UTC-7, Matias Aguirre wrote:

or just wait for a Joomla! solution for ORM/database?

I'm not sure where things are at, but there has been some talk about using Doctrine DBAL under a Joomla ORM to replace the database package.  https://github.com/joomla-framework/database/issues/18

There is a project from 2014 that's using Doctrine ORM with Joomla https://github.com/jooctrine/jooctrine