I know I said on Twitter yesterday that the chances are I'll never ever use an XPage. But I did once. It's called test.xsp and lives in a test.nsf somewhere.
The xpage doesn't do much. Anything for that matter. My main impression was just a massive WTF. Completely non-intuitive. I just didn't get it. Nor did I feel like it would be something I'd like to try and get.
One of the things I love about ASP.NET is how you have an .aspx file and a aspx.cs file to contain "code behind" code. You know where everything is. I never liked in Domino how everything was "hidden" away in property boxes. All too easy to lose complete track of what's going on. Xpages seems like it hung on to this way of doing it somewhat.
I know I said on Twitter yesterday that the chances are I'll never ever use an XPage. But I did once. It's called test.xsp and lives in a test.nsf somewhere.
The xpage doesn't do much. Anything for that matter. My main impression was just a massive WTF. Completely non-intuitive. I just didn't get it. Nor did I feel like it would be something I'd like to try and get.
One of the things I love about ASP.NET is how you have an .aspx file and a aspx.cs file to contain "code behind" code. You know where everything is. I never liked in Domino how everything was "hidden" away in property boxes. All too easy to lose complete track of what's going on. Xpages seems like it hung on to this way of doing it somewhat.