On Thu, Mar 06, 2008 at 01:51:56PM -0800, Liane Praza wrote: > Mike Shapiro wrote: > >I sent a long e-mail to this list with comments on the original thing. > >I don't see "MS" in the comment_responses.txt. Did you lose that stuff? > > The only mail I found so far was on the very original thing (not the > design document), so no, I hadn't included explicit responses in the > comments file. > > http://www.opensolaris.org/jive/thread.jspa?messageID=67874𐤢 > > Largely, I simply addressed your comments, which were largely requests > for additional information in the previous version of the design. They > should remain addressed here. It seems #4 might not have been, so... > > Essentially: > 1) Yes. API now described. > 2) Correct. scf_value_set_from_string is not doing additional > validation. > 3) The mapping is described. While I agree with you that > property groups with the same name but different types is a > reasonable feature, it doesn't solve this problem because template > to pg isn't a one-to-one mapping. > 4. Jive's eating the useful context, but I'm wondering if you're > suggesting that visibility should just be set on the property > group? > > If I'm looking at the wrong mail, please let me know. > > liane
That's the right one. Here is #4 again with escape sequences: 4. It isn't clear whether <grouping> and <hidden> are complementary or conflicting attributes. Assume I have property groups G1, G2, ... GN. If I have a set of <grouping> elements which name one or more properties from G1 .. GN, does this imply that other properties are <hidden>? In other words, it seems like there are two models: one says that every group of type 'application' is to shown except for <hidden> members. The other model says that the explicit layout is controlled by <grouping> My question is whether we want to support both and whether both can be present simultaneously. Personally I feel that the <grouping> model is much more sensible, and if someone is going to take the time to set up these templates they should just do that. And therefore I would get rid of <hidden> entirely -- i.e. everything is visible unless you group. But other choices are possible. In any case, this should be clarified. Meantime I'll go read the updated proposal. -Mike -- Mike Shapiro, Sun Microsystems Fishworks. blogs.sun.com/mws/
