IBM Connect 2016 - I'm going
I will be there. Will you?
Just to be clear and so there is NO CONFUSION, MWLUG 2015 at the Ritz-Carlton in Downtown Atlanta, GA next month (August 19-21) is all about content and value and crap we YellowBleeders care about.
IBM is a huge sponsor, but so is redpill development, and so are BCC, DOCOVA, HADSL, Panagenda, PSC Group, Riva, teamstudio, Ytria, along with all the other MWLUG 2015 Sponsors.
Without these sponsors, awesome geek-focused conferences such as MWLUG simply could not exist. The costs putting together a decent conference at a good venue are phenomenonally high, and if the sponsors were not there with their money then the conference fee would be prohibitively expensive (take the cost of the last Lotusphere you attended and triple it).
MWLUG is a technical content focused conference, CREATED BY YellowBleeders FOR YellowBleeders. Quit your bitching, fork over your measly $50, and join me in Atlanta this August. I'll see you there.
I have posted a utility SSJS funcion at Learning XPages wherein I extend Tommy Valand's clearMap function.
I have publised a new blogpost on Learning XPages. It is A little bit of scope will never. Never, ever, ever erase, and is my attempt to explain some scope and serialization issues.
The new blog is up, and accessible. DNS should have propagated by now, and most importantly I have the network cables plugged into the correct devices. DOH!
My first post is:
Episode IV - A New Hope
The Blog itself is called:
Well yesterday's announcement has turned out to be a bit of a flop. It seems that my new blog site is not yet accessible.
"We are aware of the issue and hope to have it resolved promptly."
Sigh. I'll post again once it is online. Thanks for your patience.-Devin
I'm starting a new blog specifically aimed at learning XPages. If you are interested, my first post is
Episode IV - A New Hope
The Blog itself is called
Read this before you go any further. I'll wait.....
Now allow me to make one thing perfectly clear:
There has been a whole lot of fuss over the last 18 months about "social", "cloud" and "web based" solutions. XPages technology (which is extremely powerful and cool) seems to have been caught up with a lot of this hyperbole, which is a shame because it generates an unhelpful association with these other things.
Getting back to my point about thick clients, they are going to be around for a long time. The primary reason for this is the same reason they evolved in the first place -local data access. The pro thin client, pro cloud marketing crowd just don't seem to grasp that "always connected" is a myth. There are a bunch of other ancillary reasons for the thick client to stay around (security, encryption, processing speed, etc), but the most important one is local data access.
Which brings us to XPINC. A critically important business need for running XPages in the Notes Client seems to have been forgotten: getting work done -even when disconnected. Accessing an XPages application on a Domino server somewhere from your Notes Client is fine and dandy, but what about when you don't have access to the server? The Notes Client has it's own internal XPages server (a GREAT start BTW); but until the Notes Client / Local XPages server combination is fully capable it is really nothing more than a fun playground.
In Sean's blog post (you did read it, right?) he talks about the troubles with opening an XPage from another database. The real crux of the problem isn't so much how you get the data as it is accessing the database itself. There is the rub. We need to be able to define RULES for accessing other databases -how to find it, where to find it, and under what conditions should we even look for it.
Until we we can programmatically determine at run-time what data sources to use, and where to find them XPINC will languish in the realm of "could-have-been" computer stuff -a world occupied by the likes of the NeXT computer, OS/2, and Second Life.
I'm not trying to belittle the work done so far. XPINC really has come a long way and is getting better with each release -but it is not good enough yet. I want to encourage IBM to keep pushing, keep making this better; because I really want to use XPINC. My backlog of potential projects waiting for a fully functional, fully featured XPINC implementation is huge. It is large enough to keep me billable for many, many years. But until such an implementation is delivered this backlog will remain nothing more than "potential".