Consider that all of these implementations of XPages rely on RAD techniques, use the Dojo libraries, etc. which -- I will say -- is often overkill.
However, if you deep-dive and actually write XPages apps, you'll quickly realize that you can go "beyond RAD", disable the auto-inclusion of Dojo libraries, and -- and please pay attention here -- FINALLY have complete control over the content while keeping in-line with the vendor best practices for application development.
The last 3 XPage-based apps I've written don't load the Dojo libraries. One of them loads iWebkit.css as it's an iPhone port of a Lotus Notes Client NotesDatabase.
And before anyone says it, sure - I could have done the same with blank Navigators, Forms, and other hacks that we've relied on over the years...
But while that's comforting to developers who have relied on those techniques for the better part of a decade, it's not future-proofed and working with the direction of the platform.
Jake,
Consider that all of these implementations of XPages rely on RAD techniques, use the Dojo libraries, etc. which -- I will say -- is often overkill.
However, if you deep-dive and actually write XPages apps, you'll quickly realize that you can go "beyond RAD", disable the auto-inclusion of Dojo libraries, and -- and please pay attention here -- FINALLY have complete control over the content while keeping in-line with the vendor best practices for application development.
The last 3 XPage-based apps I've written don't load the Dojo libraries. One of them loads iWebkit.css as it's an iPhone port of a Lotus Notes Client NotesDatabase.
And before anyone says it, sure - I could have done the same with blank Navigators, Forms, and other hacks that we've relied on over the years...
But while that's comforting to developers who have relied on those techniques for the better part of a decade, it's not future-proofed and working with the direction of the platform.