Category yellowbubble
It's been a couple of weeks since I have posted here on my blog as I have concentrated on the XPages Blog over at XPagesBlog.com. But that hasn't slowed the development of YellowBubble.org at all!  I've got the first phase all coded and designed out, and am just working through making sure the experience is A grade amongst all supported browsers.

With that, I thought I'd give you a few more detailed screen shots (found at the end of this post), and let you know that we are going to be entering "managed beta" here in the next week or so. I'll be sending out an email to those who have raised their hand that they are interested in testing, etc with the beta URL to get in and try it out. This first round is going to be product/solution "providers" only, not product/solution "consumers" ... they will be included as part of the overall beta release to follow soon after.  If you haven't let me know already if you want in on the testing, leave a comment below (be sure to leave your email address).

Posted by Jeremy G Hodge At 2:46 PM Location ZetaOne | Permalink | Comments (5) |      

Category xpages
Ok, here's the scenario ...  I have a document based on FormA ... FormA has the property "Use XPage instead" set to an xPage .... open the form via the following syntax:

http://www.yourdomain.com/database.nsf/view/DOCID?opendocument&tab=2

then the following code WILL NOT return a value for the 'tab' parameter



BECAUSE, if you do url = context.getUrl(); then look at the url's value for the QueryString, you get this:

?documentId=D35C5CF800662F5D852575E900560624&action=openDocument

Guess I just need to get used to using sessionScope more ...

Posted by Jeremy G Hodge At 8:47 PM Location ZetaOne | Permalink | Comments (1) |      

Category xpages
Sometimes, I think the biggest hurdle in learning xPages is the documentation. Its not the easiest thing to find (it doesn't appear to be in the the 8.5 designer help, but only in eclipse style help, or at least I can't find it in NSF form.)  Anyway, I figured as I searched through and found some answers to common questions, I'd post them here to hopefully help guide others and prevent them from having to search as long as I had to just to find an answer.

This post is about the server side javascript required to get the value of a parameter sent in the url.

Posted by Jeremy G Hodge At 5:16 PM Location ZetaOne | Permalink | Comments (5) |      

Category yellowbubble
Ok, I've been a bit secretive about this until now because I wanted to get a head start on the project before opening up too much about it to the world.  I'm still a few weeks away from being ready for the first beta release, but I thought I'd give you all your first sneak peek. These pages are a pre-release look so they aren't complete, aren't 100% fleshed out, etc, but the pages pretty much tells the story so read away.

Home Page



Alphabetical Providers Listing - One of many ways to find a provider....



One of the "Set up your profile pages" ....


So Business Partners, or anybody with a Lotus related product or service offering, get ready to post your profile and products into the catalog. You are also the first round of testers I would like to see in the system when it's ready. (I should note that right now the catalog will simply be a way to direct people seeking your solutions back to you to complete the transaction. There is no intent (at the moment) to have an "app store" like portion to the catalog (but I have thought about it as a future possibility)

I plan to release the site in phases, with the first being the provider and product catalog, then the engagement bidding system, then the technical resource aggregator, and then more ideas that I have for the future...

Its also built 100% in xPages, so I may (depending on the sensitivity of the final design in the online bidding system) release the entire site as an xPages tutorial. Either way, if anybody wants to help contribute to the site as it progresses, I'll be happy to welcome you onboard.

The idea is that this is, and will always continue to be, a 100% free, community based site, where providers and customers can come together to find solutions...

Posted by Jeremy G Hodge At 9:38 AM Location ZetaOne | Permalink | Comments (11) |      

Category security advisory
Microsoft has released Security Advisory 972890 today describing the second vulnerability in a DirectX ActiveX component (msvidctl.dll). This is the second vulnerability reported (original reported on May 28, 2009 in advisory 971778 against the DirectX activex control. Microsoft recommends setting the killbit for the compromised media type in Internet Explorer (also disabling the ability to utilize the control for other valid content.

"Mitigating Factors" from the Advisory

• Customers who are using Windows Vista or Windows Server 2008 are not affected because the ability to pass data to this control within Internet Explorer has been restricted.
• By default, Internet Explorer on Windows Server 2003 and 2008 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.
• By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.
• In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
• An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

Or, if you "un-spin" it ... You users click a link, on that page there is a video with the vulnerability compromised, the attacker can get control of the PC with the same user rights as the logged in user. It affects all version of windows except Vista and Server 2008 that have DirectX 9 installed. (It comes pre-installed).

View the Security Advisory for the steps needed for protection, or if you need help, contact ZetaOne.

Posted by Jeremy G Hodge At 5:22 PM Location ZetaOne | Permalink | Comments (0) |      

Category lotusscript xml
I've just uploaded a LotusScript file to my downloads that is a LotusScript class to easily create and export XML files from lotusscript. This library is perfect for creating tight xml code when size or custom "schemas" are required versus using the ?readviewentries command from a view.  I use it all the time in conjunction with an XSLT style sheet and the free Altova XML kit to apply a XSL Stylesheet to generate HTML reports.

The class is not completed yet, as I haven't implemented a way to read and then manipulate the XML yet, but you can completely create and export with it.  Enjoy...

Posted by Jeremy G Hodge At 11:46 AM Location ZetaOne | Permalink | Comments (2) |      

Category xpages yellowbubble

First, an update on me, and xPages (i am sure you are all excited!)

I think I've broken through the first glass floor on development with xpages.  I call it the glass floor and not a glass ceiling because I feel I am to the point where I can development competently with xPages, and can do just about anything I could do with development of web apps in notes/domino before xPages. And because I am sure to have lots more to learn and tackle, I know I'll be able to do more than before (easier than before) soon enough. But I don't view it as an equivalent uphill climb to what I just went through to get to the level of comfort that i am with them now. I am excited about where this can take the development process for Notes/Domino.

In the coming days, I'm going to do a more full "wrap up" post withe a few of the hints tips and tricks I've learned during this time, and my overall thoughts on xPages, Domino Designer and xPages, and more .... stay tuned....

Now let's discuss the recent discussions on the Notes Client & it's future

There has been a lot of talk lately about what all this 'xPages' stuff means for the client, and what the fate of the Notes client is. Along with the usual discussion of the health of the Lotus product line in general, etc etc.

First, Peter is right  that the notes client is not going away just because of the advent of xPages. First, xPages is coming to the notes client, and that's just as important as xPages for the web is. Getting the ability to use newer, open technologies such as HTML/CSS/Javascript/XML/etc efficiently  (yes i did just use bold, italics, AND underline to triple stress my point) in the client is a big deal. However, traditional Lotus Notes client development is going to be around for long time to come. I fear that is not only because of the absolute mountain of "legacy" code that exists, and the rate of adoption for the 8.5.1+ code streams (I'm guessing that 8.5/8.5.1 will continue to deploy faster than previous versions, just like 8.0/8.5 has) ... but its going to be mainly because the traditional Lotus Notes Developer hasn't ventured too far out of the domino comfort zone is going to push back. They are going to have a very very steep learning curve.

I really do see two camps developing, the xPagers, and the traditionalists to give them a name. Peter is absolutely right when he talks about the required skill sets for Lotus Domino Developers are changing. Just about everybody needs to get on board. Not because we're all yellow bleeders and we should tow the yellow line, but because your future as developers really depends on it. When xPages come to the client, and applications get updated/migrated/built/whatever, your inability to develop or maintain them is not going to be just a mark against you, its going to be THE mark against you.

If you don't have a firm grasp today on HTML/CSS/Javascript/DOM/XML - I say to you, start learning. Learn as much about those technologies as you can, in that order.  The good news is you haven't been left behind ... yet. Sure you should have been learning and developing web applications already with Domino, but should have a lot of other developers out there, you can surf the wave of xPages rather then be trampled by it.

Traditionalists have had job security in a market where the uniqueness of the development process for Notes/Domino has been protective of the developers that learn it. Its a "relatively" easy place to develop,, and until now, it's been insulated from really having to learn new technologies, trends, etc. Add to that the fact that the XPagers will have both skill sets, and the fact that xPages could well be a key part of the puzzle that really starts to attract new developers, already familiar with HTML/CSS/Javascript/DOM/XML into the Lotus fold all adds up to the erosion of that job security.

I remember the stir that the introduction of LotusScript into Notes caused. I remember hearing (stupid silly) phrases like "We don't develop with LotusScript because its not going to stick around" ... It was really fear of the new and unknown, and the introduction of a "true" language into the product. That same sentiment is creeping up now, and its 100 times sillier. The writing is on the wall, and its time to read it, then tweet it, post it on facebook, and everywhere else ...

Ok, the juicy stuff on YellowBubble

Well, ok i'm not ready to let the cat all the way out of the bag yet. But, what I can say is I am getting close to releasing the first of several planned phases to the site. I personally think this is something that we as a community seriously are in need of, and I'm pretty excited about it. In the next few weeks, I'll be looking for some volunteers to help me beta test this first phase to prep for launch. I'll be looking for a specific "type" of community members first, then needing volunteers from the rest of the community a little later.  While I don't expect troves of volunteers without me telling you what the site is all about yet, if you're interested in participating in the "beta" leave a comment here (make sure to fill in your email address in the appropriate field so I can get back to you later with the details). Keep an eye here at my blog as well as I will release all the details about YellowBubble.org before the first beta round.

Posted by Jeremy G Hodge At 2:59 PM Location ZetaOne | Permalink | Comments (10) |      

Category xpages
I really do think xpages are great. For the first time I believe I have a real web development platform with Lotus Domino, rather than feeling like everything is a hack. The only problem is, its making me feel like a hack trying to figure some things out. Add to that Odd Quirks that throw me for loops for hours and it gets to be so frustrating and I start to feel as sharp as a pound of wet leather.

Now, I'm trying to set up a simple XPages user registration page. You know, enter your user name, password, confirm your password, etc ... I've got validation working all the way around, except I need to validate that the password and the confirm password boxes have the same value, and for the life of me, I can't figure it out. I try to write validators in the same manner that worked for other fields, except I hit roadblocks every time I attempt to compare the two fields.

I thought I was good when the Domino Designer Wiki had an example of exactly this .... well, it didn't work either it uses a method getSubmittedValue() that doesn't actually exist,and when I try to access the values any other way, it just doesn't work.

XPages are really great, they are game changers, but they are also a pain to figure out ...

Posted by Jeremy G Hodge At 11:05 AM Location ZetaOne | Permalink | Comments (1) |      

Category xpages
Did you know ... an XPage's name in the URL is case sensitive ?

http://www.YourDomain.com/yourpath/yourdb.nsf/UserProfile.xsp

is not the same as

http://www.YourDomain.com/yourpath/yourdb.nsf/userprofile.xsp

if your XPage is named UserProfile, userprofile.xsp returns a 404 error

Update: Its not consistent. while userprofile.xsp and UserProfile.xsp might work, userprofile-userconfig.xsp and UserProfile-userconfig.xsp may not.

Posted by Jeremy G Hodge At 5:47 PM Location ZetaOne | Permalink | Comments (3) |      

Category lotus domino documentation
Oh, Lotus documentation writers, for future reference, when I need to know how to create a theme document in a database, don't start me out by having me creating a new database .... It's bad enough the help here is 17 steps,difficult to visually follow, and looks like it came straight from the middle of the dictionary.  Seriously, this entire help document can be condensed down to:

"To create a new theme resource, Open your database in domino designer, and expand the Resources category. Double click the "Themes" entry, and click the "New Theme" button. Give the theme a name, and click ok... then add a few links about what the #&*$* a theme is, how to apply it to the database, and, add a few links to other topics and we're good. Seriously.

Posted by Jeremy G Hodge At 9:46 AM Location ZetaOne | Permalink | Comments (1) |      

Category xpages
So I have an xpage, inside that xpage, there are two Custom Controls ... the visual header and footer of the page ... in the header custom control, I load all my common CSS files, in the proper order I want them called ..

Then, in the xpage itself, I want to load another CSS file, specific to that xpage. That CSS overrides CSS defined in the linked style sheets that are included in the Header Custom Control, so the <link> in the generated HTML needs to appear after the CSS <links> from the header. In the XML code, the header is defined before the stylesheet resource, as below...

        <xc:yb-header></xc:yb-header>
        <xp:this.resources>
                <xp:styleSheet href="/default.css"></xp:styleSheet>
        </xp:this.resources>

However, the server always outputs the style sheets defined in the XPage first, then any in the included custom controls. If I look at the Styles property box, the only style sheet shown is the one from the xPage, not anything defined in the custom control.  So I can't specify to load those before the custom control.

Does anybody know a way to tell xpages the order of to load the linked CSS files, including the ones in the custom control? I'd hate to have to define them each time in the xpage itself.

Posted by Jeremy G Hodge At 3:42 PM Location ZetaOne | Permalink | Comments (2) |