[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[jfw] Re: Extracting J! CMS libraries
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?
El miércoles, 16 de noviembre de 2016, 21:16:34 (UTC-3), George Wilson escribió:
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
On Thursday, October 20, 2016 at 7:03:13 AM UTC+1, Matias Aguirre wrote:
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:
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.
Framework source code: https://github.com/joomla-framework
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+unsubscribe AT googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-framework.