IBM is hosting an Open Mic conference call with Lotus Development and Support Engineering to discuss “XPages and Domino Designer”.
The Open Mic call will be held on Wednesday, August 18. The call will take place at 10:00 AM US Eastern Time (2:00 PM GMT) and will last for 1 hour. This call is designed to be an open question & answer format, so bring your questions.
Refer to the following technote for phone and web conference details:
Technote: 1433035
Title: Open Mic Q&A: XPages & Domino Designer - August 18th, 2010
Are there any new optons for pre or post- save processing from Xpages? I’ve seen a few suggested solutions that seem a little odd. What is the recommended way to handle this?
Subject: Requesting servlets in a XPage in Notes Client
Hello,
we have a question about Servlet Support in a Notes Client XPage (XPiNC:
We are implementing XPages in Web Client. In the XPage we are requesting business critical servlets which are running in the Domino Servlet engine.
The user is authenticated via Domino Web Login against the Domino Directory, so the servlet request is in a authenticated way.
Domino provides in this case a browser cookie, which contains the session data. This works well.
A fundamental new feature of an XPage is that it runs in Web Browser Client as well in the Notes Client.
In our application we provide historically two user interfaces. So our plan is to renew and consolidate the user interface of our application on the base of XPages,
so the customer can decide themselves if he wants to use the application in web or in the Notes Client.
Here is the problem:
There is no way / we find no way to request the servlet in the XPage in the Notes Client in a authenticated way with session of the Notes Client User.
For e.g. we want to use the standard Notes Client Login, but there is no session cookie available.
We think this conceptional gap of providing XPages in the Notes Client.
I have never been able to get ‘drop down’ buttons to work in XPages. I’d like some buttons whereby when you click them, they expand into a subset of options.
I’ve tried using the documented style classes but without success. Could you demonstrate?
Hi Ian, I’m sorry I missed your request yesterday for information on how to get on a distribution list for future Open Mic calls. Please send an email to ndinfo@us.ibm.com. As the subject of the email, type “subscribe”. We will get you added.
Subject: OMG. I could write volumes on this one. How long do we have?..
My primary questions would be, however:
How did XPages make it out the door with essentially non-existent legacy code support? Sure, R8.5.2 is supposed to “fix all that”, but even if it does, it should have been in place from the get-go, not over a year later and still so broken. Even if it was intentional, it should have been plainly stated, everywhere, including by Lotus support, that legacy code does not work in this version, and it will be included later. This was never done.
How did DDE make it out the door with so much incompatibility with legacy code? LotusScript that builds fine in all versions before DDE fails routinely in DDE. Java does the same. XPages are incompatible even between R8 minor versions, and DDE gets errors from one to the next. It’s vastly superior now to what it was a year ago, but that’s not the point. The point is every single version of Designer before DDE would recompile existing legacy code without issue, and DDE will not, even now.
But perhaps that’s water under the bridge. I mean, what are they going to say on the Open Mic? “Sorry!” That does no one any good.
So let’s scrap those questions. I have only one:
Is Lotus going to ensure R8.5.2 works USABLY before releasing it?
Usably means complete and total legacy support in XPages and DDE, at least to the level the prior Designer versions have included legacy support. It means the near constant flakiness in DDE is gone; sure it’ll freak out from time to time, what doesn’t, but sheesh it’s wonky thing. It means none of the rampant focus issues Erik is always on about. It means Pagers will show the correct last page and rowCount() will have the right value, ALL the time (bogus rowCount() makes XPage JS pretty much useless). It means ViewPanel will be usable like an actual View, or some other control will be introduced that provides data presentation flexibility without man-months of effort. It means the DDE interface placing a higher priority on what the developer is doing and typing than on than on its own background processes, like content assist, so characters appear more than one every other second. It means consistency of operation across the board instead of each panel appearing to be implemented by a different committee. It means “help” will be context-sensitive like it’s been for the last thirteen years, and it doesn’t always appear in an uselessly squished panel on the right of the editor window when F1 is pressed … it appears where and how the developer left it last.
The list is literally nearly endless. Will R8.5.2 be usable? I don’t mean “perfect”, I mean properly usable. I’d happily wait for two more years to get properly usable, rather than have more of the same in two months.
Subject: Oh, 8.5.2 isn’t going to “fix all that” with legacy LS code.
The “bridge” still isn’t completely there. Running an agent on an in-memory doc works only if the session and agent are “run as web user”. I.E. there’s still no replacement for running a WQO/WQS that was running as the signer.
Could you explain how we can use tabbed panels and still validate the entire XPage? Currently, server-side validation is only conducted on the tab you are viewing
Is there any way to speedup the designer client on win xp?
Is there any way to save rich text contents in xpages as notes rich text without converting them as MIME? or is there any way to use inotes richtext editor in other apps?