It might do a bit of a better job of it. I'm actually thinking of putting the preview parsing stuff (just the parserOutput) into the initialization rather than arbitrarily calling a function which mixes UI and other stuff.
Though, I may be doing a bit more work in the UI area than a simple UI backend split. I'm actually splitting up the different areas of the UI so that parts can actually be overrided rather than needing to override and duplicate an entire large function in a way which may cause issues when some of that code is changed in future revisions.
~Daniel Friesen(Dantman, Nadir-Seen-Fire) of: -The Nadir-Point Group (http://nadir-point.com) --It's Wiki-Tools subgroup (http://wiki-tools.com) --The ElectronicMe project (http://electronic-me.org) --Games-G.P.S. (http://ggps.org) -And Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) --Animepedia (http://anime.wikia.com) --Narutopedia (http://naruto.wikia.com)
Roan Kattouw wrote:
Daniel Friesen schreef:
I'm actually working on refactoring the EditPage class. My goals are a bit different, but they still do require some more organization in EditPage.
I'm trying to make EditPage expendable. Currently the EditPage has so much different stuff mixed in different areas of the class that it's impossible to override a small area of it inside of a subclass. ie: A different type of edit page, such as SF's formedit.
If that results in a clean separation of UI and backend code, it would probably solve my problem.
Roan Kattouw (Catrope)