The ultimate Domino Designer performance improvement for XPages developers
If you're an experienced XPages developer,
chances are you live in the Source tab of the XPages editor. But even if
you live in that editor, you'll notice that various
things seem to slow down Designer
with mysterious causes.
If you're willing to give up some of the bells & whistles, like drag/drop from the Controls Palette, custom editors for Properties, or icon cues on the Outline, you can switch from the XSP editor to the native XML editor using the following preference setting. Just go to the File Associations list and select the XML Editor, and click "Default.."
Read on for more...
If you're willing to give up some of the bells & whistles, like drag/drop from the Controls Palette, custom editors for Properties, or icon cues on the Outline, you can switch from the XSP editor to the native XML editor using the following preference setting. Just go to the File Associations list and select the XML Editor, and click "Default.."
Read on for more...
Then whenever you open an .xsp file from
the Package Explorer, you get an editing experience like this...
Obviously you need to know what you're doing if you're working strictly in the XML editor, but the build process will still provide you with the same validation messages through the Problems pane that the regular editor does.
My experience with this mode of work, especially with large XPages (and the GBS Transformer generates quite large XPages controls,) has been overwhelmingly positive. And I can still right-click on the file or switch back to the Application Navigator to work with the visual XSP editor when needed.
I'm bound by NDA on the details, but it should come as no surprise that IBM is hard at work on improving the visual editor experience. There are considerable improvements in 8.5.3, and the Designer team is not resting on its laurels. But in the meantime, hopefully this will help the XPages community continue <doing>.
Obviously you need to know what you're doing if you're working strictly in the XML editor, but the build process will still provide you with the same validation messages through the Problems pane that the regular editor does.
My experience with this mode of work, especially with large XPages (and the GBS Transformer generates quite large XPages controls,) has been overwhelmingly positive. And I can still right-click on the file or switch back to the Application Navigator to work with the visual XSP editor when needed.
I'm bound by NDA on the details, but it should come as no surprise that IBM is hard at work on improving the visual editor experience. There are considerable improvements in 8.5.3, and the Designer team is not resting on its laurels. But in the meantime, hopefully this will help the XPages community continue <doing>.
Comments
Posted by Bruce Elgort At 06:01:43 PM On 09/19/2011 |
Posted by Ben Langhinrichs At 09:08:44 PM On 09/19/2011 |
Posted by Paul Withers At 05:13:09 AM On 09/20/2011 |