These new controllers are closer to your vision than the current JLegacy implementation, but I'm not 100% confident they are platform independent.
I definitely did not use JToolbarHelper in them, but I did use JSession, JText, and JFactory. Using the factory directly was probably a bad idea. Now that I think about it, it is probably best to wrap it in a utility function.
I don't see anything keeping them from being used in other applications except perhaps the assumptions that were made about the meaning of option and view.
Since the real work is kept in the business layer, if model implements the required interface, it should work.
On Tuesday, April 22, 2014 6:14:58 AM UTC+9, Andrew Eddie wrote:
Who said anything about writing CMS specific classes? The pattern
should be similar regardless of whether you are doing a Joomla
extension, RESTful application, CLI task/command, Drupal module,
WordPress plugin, etc and so on. The only things in the CMS I would
use are its application and things like the Toolbar helper maybe (but
I'd try to avoid even that).