LDN - Luminis Developer Network

Can't make it to summit this year, so you all will have to fill us in on anything new. Last summit it sounded like Luminis 4 was going xhtml / css based, but when I went in the nested-tables file, and uncovered the sad truth, rather than brave through reworking their "new" skins (which are utterly useless) I decided to fall back on just keeping my mods in the nested tables file, which adds resources (CSS, JS, etc...) outside of the luminis patch folders.

Got sent for a whirl when I got back from Summit, finally got around to checking in... Nice to meet everyone and the Dev lounge was even better than last year. We need a much bigger room!

Anyways, I told a few people that I'd post my Notes Email / Calendar code so I still need to run it by my boss and clean it up a bit, I'll post it as soon as I can.

On a side note after I lost all the money I cared to lose in Vegas I had a free night Thursday and needed something free to do, so I snagged a couple of photos my last night there.

I mentioned this to Jon at Summit and finally got around to testing it out. I haven't tested this in production so I can't vouch for the performance hit if there is any. Shouldn’t be…

Here’s how it works, you would have a customization layer that would be named nested-tables.xsl that has an import statement to the renamed original, say nested-tables-orig.xsl. The only things in your customization layer would be the xsl <template> tags that you need to modify and the import statement (and some other minor stuff see example). Whatever is in the customization layer would over-ride the originals with the same name *and* attributes. Unfortunately you would need to copy over the entire <template> block, even if you're just changing a small part of it.