On Tue, 2008-11-18 at 20:53 +0100, Frank Schönheit - Sun Microsystems Germany wrote: > I'm asking because I still am interested in getting this useful feature > into "upstream OOo", but because of the ... colorful past of this > proposal, I cannot simply commit your patch, when there are chances > (though pretty small, IMO) that the file format changes will not become > part of an upcoming ODF standard.
There is a very large chance that the file format change won't become part of the upcoming ODF standard because, as far as Michael Brauer is concerned, it's completely wrong. Given the alternative he's suggested, I'm inclined to agree. So, what Michael wants is for us to use xml:id (introduced as part of the metadata spec, iirc) for control names/Ids, and thus the form:name attribute can be used ~solely for radio button group names. The downside is that I have no idea how much work that will involve, and I suspect it will be a significant chunk of work, involving changes to the Properties dialog (to expose the xml:id property), serialization (saving the control name as xml:id), uniqueness (can't have duplicate xml:id values, can we?), and integration with the Script engine so that it looks for xml:id in addition to form:name. In short, it's equivalent to dumping all the current group-name work and starting from scratch, but it's apparently what Michael wants. - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
