XPages - The Good, The Bad and the UGLY - I
Now that I am back playing around in Xpages kindergarten I am going to try to chronicle some of my "experiences" in learning (and hopefully mastering) Xpages. In an attempt to be balanced I will try each day to find something good, something bad (and perhaps sometimes) something UGLY.
The Good: View Reuse. Previously it was always necessary to design a view to meet the needs of its ultimate purpose. Views used in the background could be consolidated but views displayed to the user always had to be designed the exactlyas they are to be displayed. This leads to the need to create multiple views containing the same collection of documents. With Xpages I can now use a single view and present it in multiple ways by selecting each time those columns I wish to display. I can even change the column headings assigned to each column and add new columns. This means I can protentially build an application with fewer views than before, a decided performance advantage for databases with large numbers of documents. And less views for a developer to manage has to be a good thing.
The Bad: Legacy Code. When constructing an Xpage it appears almost impossible to use much of the existing (non-Xpage) design componennts contained in this or other applications. About the only thing I seem to be able to copy and paste form other design elements to an XPage is text. I can't seem to copy fields (forms) , tables(pages/forms), columns (views), actions (views,forms,pages), computed text, outlines, layers, or even images (forms/pages) into an Xpage. So in terms up taking an existing application and redeveloping it to use Xpages I basically have to build the application from scratch. Unless later versions of Designer address this I suspect we will have a lot more legacy (non-XPage) applications than we would like.
|
Ratings
0
|
Comments (4)
Also given that all but the most simple of traditional Domino applications makes heavy use of sub-forms, I would also like to have a tool available that mimicks this design element functionally in XPages and imports existing sub-form data into the XPages equivalent.
Failing that, a tool that can read the design synopsis of a Domino
database and scopes and document those design elements that that
can be kept as is, and those design elements will most benefit from
redevelopment.
There are currently tools available that help developers to migrate
from Domino to other platforms (including .Net, SharePoint &
WebSphere), so why can't Lotus provide similar migration tools to
assist Domino developers to migrate existing Domino applications to
more fully exploit XPages and replace the many hacks and
workarounds developed over the years with XPages code?
Failing that, perhaps there is a niche for the .Domino Framework to
perform some or all of that function. I get the impression that
XPages is primarily used for greenfield Web development.
Ian Randall
" I would also like to have a tool available that mimicks this design element functionally in XPages"
It's called a Custom Control, and it's listed immediately below
Xpages in the design navigator.
Peter, have you tried dragging/dropping a view or form from the Data source tab on to your Xpage? It should auto-generate a lot of design content for you. Not actions, unfortunately. But view columns and field forms should all show up automatically.
@Nathan, Yes the drag/drop of a view control onto an Xpage is pretty intuitive and even a novice like me could use this pretty easily. With Notes 6 I didn't even have shared columns and so I would often copy a column from one view into other views as a way of making an update to multiple views. If I now have an application and the user says could you add a new column to all the views I can create it once and paste it to all my existing views but I cannot paste this column into the views on my Xpages. I would have to find another way to do this.