@Patrick: gzip is actually available in 8.5, but only within the xpage context (take a look at the db properties/xpages tab from domino designer). @Erik: glad to hear that gzip will be a db-wide feature in 8.5.1 - hope the rumor is true ;)
The more I play/develop with xpages, I find myself more and more happy with the technology. I use xpages both the regular way but also as pure data sources (delivering JSON with ease to different front-end components (with the json package from json.org), and XML to external systems). Access to the native servlet context is very convenient (it also allows you to output binary data directly, not just textual stuff)
I really like that I can join data from several locations and display it in a view control (thank you Nathan for the tutorial). Access to the back-end at runtime from almost everywhere inside the xpage is very, very powerful
Another thing I like is that we now can put several view-components on one xpage and control them individually from the URL to the xpage (via the RequestParamPrefix property on the view-component). This means for example that you can perform a search in one view and a single-category restriction in another and expand a category in a third, directly from the URL (or compute it at runtime)
The property definition mechanism on custom-controls and how it allows us to build reusable and very advanced components that can be configured to plug in nicely to different contexts is another thing I find very useful.
The possibility to store stuff in different scopes is something that’s been on my wish-list for a long long time. This makes overall development way more effective.
The “large” number of JavaScript includes, and CSS includes (http requests) is something I hope eventually will go away - I hope a solution similar to Yahoos service that allows you to merge all js files into one file (automatically on-the-fly) will be developed for Dojo/domino (or for all js files in domino). Today’s solution can be implemented more elegantly imho.
I can live with the “hi-jacking” of id’s, and the extra effort to calculate id’s if I want to access them from a client side JavaScript or similar (I understand why). I can live with the bugs currently in Domino Designer (for now) and other strange stuff happening from time to time because I can see progress and (true) commitment, stuff is *finally* happening in the domino development area.
@Patrick: gzip is actually available in 8.5, but only within the xpage context (take a look at the db properties/xpages tab from domino designer). @Erik: glad to hear that gzip will be a db-wide feature in 8.5.1 - hope the rumor is true ;)
The more I play/develop with xpages, I find myself more and more happy with the technology. I use xpages both the regular way but also as pure data sources (delivering JSON with ease to different front-end components (with the json package from json.org), and XML to external systems). Access to the native servlet context is very convenient (it also allows you to output binary data directly, not just textual stuff)
I really like that I can join data from several locations and display it in a view control (thank you Nathan for the tutorial). Access to the back-end at runtime from almost everywhere inside the xpage is very, very powerful
Another thing I like is that we now can put several view-components on one xpage and control them individually from the URL to the xpage (via the RequestParamPrefix property on the view-component). This means for example that you can perform a search in one view and a single-category restriction in another and expand a category in a third, directly from the URL (or compute it at runtime)
The property definition mechanism on custom-controls and how it allows us to build reusable and very advanced components that can be configured to plug in nicely to different contexts is another thing I find very useful.
The possibility to store stuff in different scopes is something that’s been on my wish-list for a long long time. This makes overall development way more effective.
The “large” number of JavaScript includes, and CSS includes (http requests) is something I hope eventually will go away - I hope a solution similar to Yahoos service that allows you to merge all js files into one file (automatically on-the-fly) will be developed for Dojo/domino (or for all js files in domino). Today’s solution can be implemented more elegantly imho.
I can live with the “hi-jacking” of id’s, and the extra effort to calculate id’s if I want to access them from a client side JavaScript or similar (I understand why). I can live with the bugs currently in Domino Designer (for now) and other strange stuff happening from time to time because I can see progress and (true) commitment, stuff is *finally* happening in the domino development area.