I'm building a quite complex application that have a lot of custom UI requirement, especially when displaying one item. The item show parts of it only when specific rules are met (mostly related to the user's group membership), related items (some lookups), etC.
What are the options for such customization? What are pro and cons of each methods ?
By now, I can see this options :
- create a custom application page with an ID in the query string, and build the UI using traditional ASP.Net techniques
- Pros: easy to create and deploy
- cons: quite static, not customizable by the users
- create a bunch of web parts, and add them to the OOB dispform.Aspx
- Pros: not so hard to deploy
- Cons: same as an application page, but within the webpart (still have to build the UI manually)
- create control templates for the list form
- Pros: looks like the blessed way to do such things
- cons: hard to construct, as it require a lot of nested controls
- use xsl (I'm a newbie in this way)
- pros: can be build with SPD before importing into VS
- cons: xsl can be a bit of pain
I'd appreciate your feedback about your own experience.
To be more precise about my requirement, here is a list of things my page must show :
- the details of my item (main fields)
- one tab for each kind of action possible on the item. each tab have its own set of controls, and buttons (jQueryUI is my friend)
- several "related" information, that are stored in other lists, with lookups. This views have custom formatting when some rules applied.