RE: [cgmo-webcgm] default/explicit -- _replace clarification

[Lofton Henderson <lofton@rockynet.com>]

At 12:04 AM 6/16/2005 +0200, =?us-ascii?Q?Dieter__Weidenbruck?=
wrote:
[...]

Old text

-----

The viewer shall replace the current picture by the designated picture in the same rectangular area in the same frame or window as the picture which refers to this target. This is the default behavior for CGM-to-CGM links.

New text

-----

The viewer shall replace the current CGM picture by the designated CGM picture in the same rectangular area in the same frame as the picture which refers to this target. If the ending resource (CGM) is the same as the linking resource, the viewer does not reload the resource.

[DW] I suggest to add: "This is the default behavior for CGM-to-CGM links."

Yes, it's already there -- copy/paste error.

[...]

1.) do we want to distinguish between *explicit* _replace and *defaulted* _replace ?  (Dieter's mail seems to imply that.)  It seems odd that these should behave differently (if we are viewing myCGM.cgm currently):

#name(myObj, move)

#picseqno(1,_replace).name(myObj, move)

myCGM.cgm#picseqno(1,_replace).name(myObj, move)

myCGM.cgm#name(myObj, move)

[DW] no, we should not distinguish between these cases.

Good.

There is even a third variant, where the full fragment needs to be written only because the name contains certain characters, e.g. a period. Kind of an unwanted explicit _replace then.

So let's treat them all the same way.

-Lofton.