I got back from the US yesterday and hung my Lotusphere 2009 badge in my office with the rest of them and again got surprised by the number of stickers I managed to attain. Blogger, exhibitor/sponsor, speaker, press/analyst, bdday and of cause the Danish flag… 🙂 Wow! The press/analyst I got because it was the only one I didn’t have (besides the IBM ones).
Thanks to Andrew Pollack for this one:
This session, delivered by Mikkel Heisterberg — was tailor made for me. I’ve done no plug in development because despite knowing Java and knowing Notes, when it came to plug-in development I didn’t know where to start or what was really feasible. I know the information is out there, but it takes time to go find it and figure it all out. Mikkel put together a session that was absolutely everything I needed to know to start building plug-ins immediately — and not a single thing I didn’t need. This was all signal, no noise and perfectly leveled for someone in my position. Another developer I talked to on the way out called it “three months of head banging frustration skipped over as a result of reading a dozen slides.”
OK last post about the session demos – really! Don’t know what I did to create a 7 mb archive and even worse an archive you couldn’t unpack but I just created new RAR and ZIP versions both around 600 KB so download away.
I might have been out sick all day yesterday but I’ve seen enough during the week to be confirmed in the fact that IBM Lotus is changing the game when it relates to collaboration. XPages is great and will change the way applications are developed for the platform. This has been discussed online in the Yellow Bubble earlier but to see the XPage excitement by “the general public” is new and very nice to see.
XPages is a game changer. No doubt about it!
Seeing the stuff that Stephan Wissel showed in his Practical DXL Magic session only confirmed this. Remember that XPages is just XML underneath and one of his demos Stephan demoed how to create XPages from Notes view and Notes forms using DXL and XSLT. Now try to do equivalent stuff on any other platform!
I just added a (Win)RAR-version of the archive with the demos from my session to the blog so head over to the session page to download it.
Just sat through Stephan Wissels session on DXL and it was great. Good slides, not too many of them, excellent demos and altogether a great session. Way to go!
Below are the cliff notes.
- IResource in DDE returns DXL
- DXL Studio by Stephan Wissel
- DXL Explorer
- Setting setForceNoteFormat=”true” makes export round trip safe but not usable for anything else than round tripping (== binary)
- stream out has to be UTF-8
- Switch of “Compile LotusScript” to avoid script related import options; you can always recompile later
- Watch out for line break issues; improvements needed; work from DOM tree in memory
- If export fails try exporting design elements one by one; issue is probably a race condition as an 88 millisecond wait between design elements makes it work
- Get a decent XSLT/XPath editor – NO Notepad/vi
- Approx. 156k lines of LotusScript in all IBM templates – thought it would be more (based on 69 templates
- Cocomo tool for estimating how much time it takes to redo code
- Cool demo showing how to transform a view to a XPage, some copy/pasting required but it works like a charm
- Even cooler demo transforming a view to a XPage, again copy/pasting required but worked perfectly
Those who do not speak at Lotusphere might not know this but as a speaker you are required to go to the presentation venue the night before your presentation and do a mandatory TEK CHECK. This is basically to make your computer can connect to the presentation projector etc. Seeing my share of sessions this week it has again become clear that a couple of checks should be added to the TEK CHECK or added to the presentation check that also occurs before the presentation.
Some would say that it’s basic presentation guidelines but I think the following should be enforced:
- If using bullets keep it to 5 or 6 per slide
- Don’t use a font smaller than 20 points
- If showing code use a proportional font such as Courier
- If demoing in an IDE remember to increase the font size
- Make sure the resolution you’re using still allows for people to read the slides and demos clearly from the back rows