There is a lot of code in this area, which is also the main initial class for admin functionality. There's a few sections that can be a completely separate class...but if modularized, it is important it is very easy to read and understand in the file structure & format, and the OOP concept is well defined.
Notes on modularization (if the concept is applied).
There are 2/3 distinct types parts. The execute/creation class (maybe factory pattern), and relation class(es).
File & Class Structure:
Executive Class
Various Classes [a. b. c. 1. 2. 3]
Relation Class(es) [alphabet, numeric]
AVOID using confusing methods. For example, Inheritance can easily become hard to grasp.
Inheritance can improve optimization with similar variable and methods, but HAS to have a solid relation among classes.
Post Data Processing
Class name ideas:
APL_Editor
APL_Process
This is hook into and handle processing data. This around 30-45% of the code.
Admin Notices
Class name ideas
_Helper
_Assist
This would handle most of the extra admin ui features and support. This could be Notices, Help Text, Walkthrough/Pointers, etc.
There is a lot of code in this area, which is also the main initial class for admin functionality. There's a few sections that can be a completely separate class...but if modularized, it is important it is very easy to read and understand in the file structure & format, and the OOP concept is well defined.
Notes on modularization (if the concept is applied).
Post Data Processing
Class name ideas:
This is hook into and handle processing data. This around 30-45% of the code.
Admin Notices
Class name ideas
This would handle most of the extra admin ui features and support. This could be Notices, Help Text, Walkthrough/Pointers, etc.