The legacy MVC structure leans heavily on JTable, and that's one package that wasn't carried forward into the Framework. This mainly impacts models and the way the web hooks are implemented right now. Figure out if this is code we want to use, or if not, write the suitable replacement code.
Looks good to me. I don't know if we'll need the assets support (depends on how we deal with ACL), but we can definitely work with a stripped down JTable and hack away as needed.
Seems like it's working ok.
I have committed a refactored JTable class: 160e996
The main differences are:
tableFields
stdClass var is used, which is accessed by magic__get()
and__set()
methods.There should be no differences in using this class.
false
, exceptions are thrown on failure.Maybe this could work for a while..