[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cgmo-webcgm] The highlight() method
Benoit, Thanks for pointing this out, and for your additional "typos" mail message. At 10:54 AM 11/25/2005 -0500, Benoit Bezaire wrote: >[...] > Itedo noticed that the highlight() method on the Picture interface > may be problematic. [...] > Here are some options that we have: All -- Perhaps we should clarify our TC status and modus operandi now. Altho' days and weeks continue to pass, OASIS governance and TC admin. seem to be creeping towards a WebCGM 2.0 Submission to W3C. Accordingly, with the formal approval of the Committee Spec. last week, all formal technical work on the specification will halt within the WebCGM TC, while W3C takes the spec through its Last Call process. I.e., we cannot unilaterally modify the spec. (This all assumes that: OASIS does indeed eventually make the Submission; and, W3C accepts the project and starts a WG). That does not mean that we must be idle on questions such as Benoit raises. Indeed, we should deal with them. But problems such as this one now will have to be *formally* addressed during the W3C cycle(s): 1.) several TC members will also be WG members; 2.) the WG will operate in "public" mode -- all of its mail archives etc are publicly readable, and there will be a public comment list. Dave -- I think you need to keep track of post-CS issues that come up in the TC, such as this one. That clarified, we should indeed discuss the problem and the options that Benoit has enumerated (thanks Benoit). Have at it... > i) leave it like this, fix in a later version (2.1) but that means > WebCGM 2.0 users will not be able to highlight a single Application > Structures. > > ii) change getAppStructureById to return a WebCGMNodeList. This > however will force script writers to write: > var id = pic.getAppStructureById("myID"); > if( id.count > 0 ) > { > id.item(0). etc... > } > every time they want to access and APS by Id. > > iii) have two highlight methods. One that is called highlight( > takes a WebCGMNode ) and one called highlightMany( takes a > WebCGMNodeList). It wouldn't look very good in the spec, but hey, it > would work. > > iv) introduce some sort of WebCGMNode.makeList() method that > would return a WebCGMNodeList from a WebCGMNode. This approach would > need more thoughts, as it could complicate the 'live' node > implementation of our DOM. > > Thoughts, -Lofton.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]