Unfortunately, the MVC "à la Notes" is a myth, Notes already offers heavy component,
A way is to create "layered application" to reuse code.
In this case the agents are a technical layer in the middle. It gives us Notes or web context, business logic selector, late bindings mecanism (a controller/Factory )ect. The class & forms are on both ends with business logic and presentation/input validation. A domino's framework would be rather a whole(?) of best pratices/systematics ( centralize validation & hide-when rules for both Notes & web(server side validation), deport code to LSS) and Domino's funky geek's technics (doClick, formula return code). This with the goal of embrasse change, keep simple (at least be systematics !:-))
LS OO implementation is poor. But encapsulation give us great tools to simplify the code (less parameters between calls...)... please avoid globals variable (aaargh!!).
I commonly use a "singleton" object (ok ok it's a global...) to cache instance of heavy object (view, ext db) -> only 1 new NotesView(), DB ect.
It's also cool for collection processing : Create a bean class for your document, walk on each document one time to instanciate beans & finally do what you need on those instance.
In this context, the list are real powerfull tools to hold instance in a "hashmap" structure... There are a lot of techical or functionnal wrapper class to write (mails,RT, queryString parser, (notes)date/time helper).
With tools like lsdoc, TSscript browser or NotesHound you have alternative to poor Designer IDE integration.. garggl
Yes Bjornm, you are right.
Unfortunately, the MVC "à la Notes" is a myth, Notes already offers heavy component,
A way is to create "layered application" to reuse code.
In this case the agents are a technical layer in the middle. It gives us Notes or web context, business logic selector, late bindings mecanism (a controller/Factory )ect. The class & forms are on both ends with business logic and presentation/input validation. A domino's framework would be rather a whole(?) of best pratices/systematics ( centralize validation & hide-when rules for both Notes & web(server side validation), deport code to LSS) and Domino's funky geek's technics (doClick, formula return code). This with the goal of embrasse change, keep simple (at least be systematics !:-))
LS OO implementation is poor. But encapsulation give us great tools to simplify the code (less parameters between calls...)... please avoid globals variable (aaargh!!).
I commonly use a "singleton" object (ok ok it's a global...) to cache instance of heavy object (view, ext db) -> only 1 new NotesView(), DB ect.
It's also cool for collection processing : Create a bean class for your document, walk on each document one time to instanciate beans & finally do what you need on those instance.
In this context, the list are real powerfull tools to hold instance in a "hashmap" structure... There are a lot of techical or functionnal wrapper class to write (mails,RT, queryString parser, (notes)date/time helper).
With tools like lsdoc, TSscript browser or NotesHound you have alternative to poor Designer IDE integration.. garggl
Class will really help you :-)