It's no secret that the IDE you use will change the way you write code. Down the line a bit, I'm sure XPages will have the biggest impact. The first impact however is a bit of surprise. Right now, I frequently use "PAGE" elements as CSS, Javascript, or HTML content. Editing them is weak but it works out fairly well.
Along comes Domino Designer in Eclipse. I had hoped that the editors would work against regular "Page" elements just by defining them as one kind or another. Instead, the new editors for javascript, css, html, etc. work on "File Resource" elements. The integration is fairly good in so far as it goes. If you create a NEW file resource, and give it a name ending in .html, the editor it loads up in will be the html editor. The same is true for .js, and .css (if you're paying attention, try it with .lss <grin>)
Anyway, from a database design method, that means instead of creating a new "PAGE" and putting HTML on it and then setting its content type to HTML, now I'll create a new FILE resource and give it an HTML file name, then use the actual editors to edit my HTML. They're not bad, by the way. Can't wait to try out the .XML and .CSS editors along with the .JS and .LSS
Comment Entry |
Please wait while your document is saved.
Eclipse plug-in a try: http://update.aptana.com/update/3.2
Features I like in Aptana is that the CSS Editor has a type-ahead feature that
shows which CSS property is supported in which browser, or if you are writing a
pure HTML file with DOTYPE and all, Aptana will actually check if your HTML
adheres to the declared DOCTYPE .