[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re[4]: [cgmo-webcgm] Question about NVDC and APS attributes
Hi Dieter, Ok so according to you, there's only one; either viewContext or virtualViewContext. That's fine with me. I think it should be called 'viewContext' even if it is expressed in NVDC. virtualViewContext is confusing. Besides, we have that section in the spec which explains that NVDC coords are used in the WebCGM DOM. I can wait a bit, but if nobody can justify having both of them, I suggest that we drop one (virtualViewContext). Regards, -- Benoit mailto:benoit@itedo.com Thursday, December 2, 2004, 8:17:15 AM, Dieter wrote: DW> well.... DW> I think that we decided to allow for setting a view context using a DW> setAttribute DW> call. The view context should be specified in NVDC to match all other DW> coordinates DW> used in the DOM context. So the view context became a virtual view context. DW> I am not 100% sure, but that's my only recollection. DW> Dieter DW> -----Original Message----- DW> From: Benoit Bezaire [mailto:benoit@itedo.com] DW> Sent: Thursday, December 02, 2004 1:20 PM DW> To: CGM Open WebCGM TC DW> Subject: Re[2]: [cgmo-webcgm] Question about NVDC and APS attributes DW> Wednesday, December 1, 2004, 8:12:56 PM, Lofton wrote: LH>> At 04:04 PM 12/1/2004 -0500, Benoit Bezaire wrote: >>>[...] >>>Second, could someone explain to me what virtualViewContext means? LH>> Huh? Where did this come from? Is this something we invented in the LH>> post-Houston, 11/16 telecon? DW> I don't know where it came from; the only thing I remember is that you DW> and Dieter understood its meaning. LH>> I wonder if this is the "target rectangle" concept from section 3.2 of LH>> Dieter's object behaviors proposal, which we discussed in the telecon DW> right LH>> after Houston? DW> maybe? DW> -- DW> Benoit mailto:benoit@itedo.com LH>> DW> http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/email/archives/2004 DW> 11/doc00001.doc LH>> If so, then I'm pretty sure it should *not* be an ApsAttr. Therefore, DW> it LH>> shouldn't be in the DOM. Is this what you would call a "shadow DOM" LH>> entity? I can see someone wanting to inquire it, possibly (but let's DW> make LH>> sure there is a strong use case, rather than adding more functions LH>> gratuitously). It should not, however, be settable. LH>> -Lofton.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]