For me, comprehensive examples that show off how all available parameters are used are probably more important to rapid comprehension of a new component or library of components than a color coded table. The table is useful as a reference, once I already have a baseline familiarity with how things work, but as someone who first used Tacos less than 12 hours ago, I can say that some of the examples in the documentation could have been clearer and more up to date. But, if you are going to generate a table of parameters, color coding them according to client-side or server side would certainly aid comprehension and readability. But since I assume they'll be grouped together, the colors are probably superfluous.
--sam On 4/1/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > Jesse Kuhnert wrote: > > I wanted to know how people feel about what should be done with all of the > > additional parameters that will soon be available on a lot of our > > components. The tacos component documentation has been said to be confusing > > because of this, but I don't really know what to do about it. > > > > Adding in all of these client side features do open up a whole world of new > > parameters to people, so they exist whether documented or not. If I can find > > a way, maybe color coding the parameter table would be a better option? Ie > > normal table for typical parameters, and then a "blue" background table or > > something for the client side parameters. We could use this color scheming > > theme throughout the documentation to make it easier for people to > > understand what sort of information we are documenting. > > > > -- > > Jesse Kuhnert > > Tacos/Tapestry, team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. http://opennotion.com > > > > > Great idea ;). > > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
