Bryan Stearns wrote:
The thing I hate most about parcel.xml is that there's no way for me to represent or encapsulate this repetiton; the new proposal suffers from the same problem.Fair enough. It sounds like you have a specialized use and this particular proposal may not suit the detail view. However, I wonder how much effort is going into parameterizing the creation of these detail-specific blocks, when the CPIA xml might be fairly simple. I hate redundancy as well, but maybe its enough better than parcel.xml that it might be worth looking at? Let's try. <CalendarAllDayBlock id="CalendarAllDayArea"> <StaticText id="CalDetailsAllDayLabel" border="4,0,0,0" title="all-day".../> <StaticText minimumSize="8,-1"/> <AEBlock id="EditAllDay" viewAttribute="allDay" border="2,2,2,2"/> </DetailRow> So the "Cal" or "Calendar" appears 3 times here.. plus I imagine the text/spacer/AEBlock is part of the repetition you're talking about. So I'd be curious what the parameterized python might be like. This is obviously a very simplistic version of what you're trying to do as well, so I'm sure it only gets more complicated, not less :) So you're probably right, this might not be appropriate for complex stuff in the detail view... worth the exercise, anyway! But as the UI gets more complex (dashboard, toolbar, menus, etc) I can still see value in being able to declare a large part of it in XML. |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
