Idea Summary
Support an option to directly export a page PL/SQL process to a compiled program/procedure/package. Better yet if a best practice would be enforced for naming or such packaged/programs

Use Case
If page X has a number of PL/SQL “code-fragments” scattered across, before header / on processing / Ajax call back processes, It would be really helpful if there is a consistent pattern of generated code that happens behind the scene to support the page/application. e.g. APP_X_PAGE_Y_BEFORE_HEADERS stub procedure can be created at request to better organize the code and benefit from single compilation and caching

Preferred Solution (Optional)
Add an option to the code editor to “export code into backing package” which would use an established convention to alter the said package by adding a new procedure that handles this particular processing point.