Re: [cgmo-webcgm] ISSUE: visibility & interactivity at picture level

[Benoit Bezaire <benoit@itedo.com>]

Hi Lofton,

I tend to agree with you...

For visibility, I don't really see why someone would want to make the
entire picture invisible. So this one doesn't concern me very much.

For interactivity, if someone wanted to make the entire picture
non-interactive, a script writer could do:

var meta = objectId.getWebCGMMetafile();
var pic = meta.pic;
var nodes = pic.firstChild;

while( nodes )
{
  nodes.setAppStructureAttr("interactivity","off");
  nodes = nodes.nextSibling;
}

I think (personally) that this is an acceptable workaround for the
WebCGM 2.0 timeframe.

-- 
 Benoit   mailto:benoit@itedo.com

 
Monday, June 13, 2005, 12:39:17 PM, Lofton wrote:

LH>  From Dieter's comments:
LH> http://lists.oasis-open.org/archives/cgmo-webcgm/200506/msg00021.html

LH> ISSUE:  visibility   interactivity at picturelevel

LH> 3.2.2.9
LH> how do we state that visibility can be set at picture level?

LH> 3.2.2.10
LH> how do we state that interactivity can be set at picturelevel?


LH> DISCUSSION.  We have three things to consider: 
LH> WebCGM(metafile instances), DOM, XCF.

LH> In WebCGM...  Since these are APS Attributes, it can't be
LH> done in a straight forward manner.  You can achieve the effect (at
LH> least for visibility, maybe for interactivity) by wrapping the
LH> whole picture body in an APS.   Or apply the attributes to the
LH> layers in a layered picture.  In DOM or XCF, not currently
LH> possible.  Various solutions that come to mind -- for WebCGMs
LH> and/or DOM and/or XCF --either violate CGM:1999, or create
LH> incompatibility between the three functional areas, or are hacks.

LH> This is not going to be a simple problem to solve cleanly. 
LH> If it is not an *important* use case, it might be a good strategy
LH> that we postpone the solution.

LH> RECOMMENDATION:  don't try to solve it in 2.0.

LH> Regards,
LH> -Lofton.