Seeing it – developer pages
It's often important to have a complete and unobstructed view of the data within your application. This statement sounds simple and obvious, but sometimes, it isn't quite that easy. Many times, the core pages and data grids you will be asked to add to your application will constrain your data over certain criteria. Perhaps an XPath over a certain attribute or combination of attributes, for example. And, depending on that data and application, it could become difficult to get a complete picture of your entire dataset. The concept of a "developer page" is just that complete, unobstructed view of a particular dataset. Think of a data grid without any XPath applied to it where all (or almost all) attributes are visible.
Sounds like a great idea, right? In many scenarios it is, yes. But, like all things, it's important to always keep the context in mind. For example, what data are you making available to be viewed? Is it personal...
