[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re[2]: [cgmo-webcgm] default/explicit -- _replace clarification
Looks good to me... Wednesday, June 15, 2005, 6:04:21 PM, Dieter wrote: DW> see inline DW> -----Original Message----- DW> From: Lofton Henderson [mailto:lofton@rockynet.com] DW> Sent: Wednesday, June 15, 2005 11:57 PM DW> To: cgmo-webcgm@lists.oasis-open.org DW> Subject: [cgmo-webcgm] default/explicit -- _replace clarification DW> Feedback welcome (esp. implementors)... DW> As a first cut at implementing the no-reload decision for DW> _replace, I took Benoit's suggested words and applied them to DW> _replace in the definition list of 3.1.2.2 and to the _replace DW> cell of the table. Which resulted in... DW> Old text DW> ----- DW> The viewer shall replace the current picture by the DW> designated picture in the same rectangular area in the same DW> frame or window as the picture which refers to this target. This DW> is the default behavior for CGM-to-CGM links. DW> New text DW> ----- DW> The viewer shall replace the current CGM picture by the DW> designated CGM picture in the same rectangular area in the DW> same frame as the picture which refers to this target. If the DW> ending resource (CGM) is the same as the linking resource, the DW> viewer does not reload the resource. DW> [DW] I suggest to add: "This is the default behavior for CGM-to-CGM links." DW> [_replace in the definition list of 3.1.2.2 has this DW> additional sentence at the end, "Applicable only to CGM-to-CGM DW> links (i.e., this is not defined in HTML 4.01), this is the DW> default behavior for such links."] DW> Then I looked again at Dieter's mail, which raised two questions (see after): DW> At 05:18 PM 6/14/2005 +0200, DW> =?us-ascii?Q?Dieter__Weidenbruck?= wrote: DW> 1. LinkURIs DW> CGM to CGM linkURIs like DW> #name(myObj,move) simple navigation to another object DW> #xcf(myXCF.xml) load and apply this companion file DW> DW> 2. DOM calls DW> (assume a cgm is loaded and displayed) DW> cgmDoc.src = "#name(myObj,move)" DW> cgmDoc.src = "#xcf(myXCF.xml)" DW> DW> This is especially important to be able to load XML companion DW> files in a sequence, e.g. DW> - myScreentips.xml DW> - myLinks.xml DW> - myConfiguration.xml DW> DW> Suggestion: DW> If a picture behavior is explicitely stated, it must be used DW> If no picture behavior is stated, and the nature of the DW> link doesn't require a reload of the file, don't use a DW> picture behavior. DW> Questions: DW> 1.) do we want to distinguish between *explicit* _replace DW> and *defaulted* _replace ? (Dieter's mail seems to imply DW> that.) It seems odd that these should behave differently (if we DW> are viewing myCGM.cgm currently): DW> #name(myObj, move) DW> #picseqno(1,_replace).name(myObj, move) DW> myCGM.cgm#picseqno(1,_replace).name(myObj, move) DW> myCGM.cgm#name(myObj, move) DW> [DW] no, we should not distinguish between these cases. DW> There is even a third variant, where the full fragment needs to DW> be written only because the name contains certain characters, e.g. DW> a period. Kind of an unwanted explicit _replace then. DW> So let's treat them all the same way. DW> [DW] Regards, DW> Dieter DW> (Btw, on an intra-cgm link, the preferred form is that the DW> picture behavior is put into the 3rd parameter of the linkuri, DW> but I have used the un-preferred form for concise illustration DW> purposes.) DW> 2.) [...next message, to split issues apart...] DW> Regards, DW> -Lofton. -- Benoit mailto:benoit@itedo.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]