document the parameter names and expected values to help subclassers
Simplify this so the developer of a new recurring item/event doesn't have to work so hard. There should be a way to (1) have the recurrence widget update the [tablename]_recurring_[tablename]_id column when saving the recurrence (this would save a couple of lines) and (2) there should be a way to simplify or eliminate the code in the DELETE triggers. Some of this stuff really belongs in an AFTER trigger instead of a before trigger.
expose QFile and QDir to scripting, including static methods, then deprecate the methods here that wrap them.
figure out how to link this class with the scriptapi group
| Generated on Thu Dec 9 09:13:18 2010 | xTuple ERP Programmer Reference, Version 3.6.0 |
1.6.1
|