@Jake - "...Didn't see anything that I couldn't do without XPages though or anything that made me stop in my tracks and vow to learn XPages."
There's nothing there you *couldn't* do in classic Domino web dev (with or without Flex), it would just take you forever and be far less maintainable.
For example, take a repeat control + a pager... you can page through groups of data. A standard Web 2.0 concept. Trivial on an XPage, but utterly horrible to recreate with classic Domino web dev. At least 20x-30x longer than doing it via an XPage.
Now imagine that inside that repeat control is a 4-column table. One of those columns programatically hides. In classic dev, that would be.... UGH.
In XPages, it's one line of code on the "visibile" attribute of the column.
Now, you could do all this in Flex fairly easily too, but you get left behind as soon as you want to start deriving things *programatically*.
Going back to my example, the effort involved to programatically hide that column via Flex would be a lot more effort than a simple "@DbLookup(....)" as you would write on an XPage.
The programmatic stuff really starts to snowball after awhile -- the pseudo-JOINs, @GetProfileField, etc. etc. That's where XPages shows off its tight integration with Domino.
@Jake - "...Didn't see anything that I couldn't do without XPages though or anything that made me stop in my tracks and vow to learn XPages."
There's nothing there you *couldn't* do in classic Domino web dev (with or without Flex), it would just take you forever and be far less maintainable.
For example, take a repeat control + a pager... you can page through groups of data. A standard Web 2.0 concept. Trivial on an XPage, but utterly horrible to recreate with classic Domino web dev. At least 20x-30x longer than doing it via an XPage.
Now imagine that inside that repeat control is a 4-column table. One of those columns programatically hides. In classic dev, that would be.... UGH.
In XPages, it's one line of code on the "visibile" attribute of the column.
Now, you could do all this in Flex fairly easily too, but you get left behind as soon as you want to start deriving things *programatically*.
Going back to my example, the effort involved to programatically hide that column via Flex would be a lot more effort than a simple "@DbLookup(....)" as you would write on an XPage.
The programmatic stuff really starts to snowball after awhile -- the pseudo-JOINs, @GetProfileField, etc. etc. That's where XPages shows off its tight integration with Domino.