[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [cgmo-webcgm] getAppStructureExtent() was getObjectExtent()
Actually, I think the units of the values returned should be in NVDC units: From WebCGM 5.6: To simplify working with coordinates, the WebCGM DOM defines and uses a canonical, normalized coordinate system, Normalized VDC (NVDC). NVDC units are millimeters, in a coordinate system whose origin corresponds to the lower left corner of the VDC extent, with the X axis pointing to the right, and the Y axis pointing up. The following examples illustrate the correspondence between NVDC and VDC values for several WebCGM instances. While it's not the same as the units for "region", it does provide a single method for defining the region. Thx..Dave Technical Fellow - Graphics/Digital Data Interchange Boeing Commercial Airplane 206.544.3560, fax 206.662.3734 david.w.cruikshank@boeing.com -----Original Message----- From: Bezaire, Benoit [mailto:bbezaire@ptc.com] Sent: Tuesday, February 26, 2008 5:30 AM To: cgmo-webcgm@lists.oasis-open.org Subject: RE: [cgmo-webcgm] getAppStructureExtent() was getObjectExtent() If the main use case is to be able to align objects, then it would seem like getAppStructureExtent() needs to take into account the current transform. Would you agree? I think the same would be true for the zoom example; although we haven't seen any zoom API proposal from the group so far. The fact that it is two corners troubles me... it makes the script writer's job more difficult. But CGM's can be Y up and Y down, right? So x, y, width and height wouldn't be better I think :-( Ben -----Original Message----- From: Galt, Stuart A [mailto:stuart.a.galt@boeing.com] Sent: Monday, February 25, 2008 7:36 PM To: Lofton Henderson; cgmo-webcgm@lists.oasis-open.org Subject: RE: [cgmo-webcgm] getAppStructureExtent() was getObjectExtent() Hello, To answer Lofton's question: I think that we should use the same points as viewcontext (like you suggested) I just used the min/max points because that is what it said in the AI list - poor excuse but it is the one I am going to use. I think that the original use case was to be able align or move an APS relative to another one. (Being able to put a table_leg at the edge of the table_top object)? Another use that I thought of might be to be able to zoom into an APS but instead of making it full screen I want it to be only 90% of the available viewport. I don't think that it was intended to take line width or regions into account. -- Stuart Galt SGML Resource Group stuart.a.galt@boeing.com (206) 544-3656 > -----Original Message----- > From: Lofton Henderson [mailto:lofton@rockynet.com] > Sent: Monday, February 25, 2008 11:12 AM > To: Galt, Stuart A; cgmo-webcgm@lists.oasis-open.org > Subject: Re: [cgmo-webcgm] getAppStructureExtent() was > getObjectExtent() > > Stuart, All -- > > A question comes up. Which bounding box? Do you mean: > > 1.) the BB of the coordinates of the APS's graphical primitive > elements, as written in the metafile itself? > 2.) or, the effective BB, which would reflect a non-trival CTM > (current transformation matrix)? > 3.) or, something else (e.g., 'region' factored in)? > 4.) or, should it be parameter selectable (#1 or #2 or ...)? > > Related question: are things like line-width accounted for in the BB, > or not? > > (Does anyone recall our original use case(s)? That might help to > answer the questions.) > > -Lofton. > > At 10:45 AM 2/23/2008 -0700, Lofton Henderson wrote: > >Stuart -- > > > >Good job, especially the completeness by looking at every > section for > >needed changes. > > > >One small nit... > > > >At 04:09 PM 2/22/2008 -0800, Galt, Stuart A wrote: > >>Markups for getAppStructureExtent() > >> > >>Chapter 1 - no changes > >>Chapter 2 - no changes > >>Chapter 3 - no changes > >>Chapter 4 - no changes > >> > >>In 5.7.6 add to the IDL list > >> > >>WebCGMString getAppStructureExtent(); > >> > >>Add to the method descriptions: > >> > >>getAppStructureExtent() > >> Retrieves the bounding box rectangle of the > graphic elements > >>within an APS. The rectangle is defined the two corner points. > >>Parameters > >> None > >>Return Value > >> WebCGMString; the bounding rectangle min and max > pairs stored > >>in a string, or the empty string if the APS contains no > graphical elements. > > > >I seem to recall that we decided, about rectangles, that we would > >always parameterize as two diagonally-opposite corner points. So > >instead of > > > >xmin,xmax,ymin,ymax > >or > >xmin,ymin,xmax,ymax > > > >it would be: > >x1,y1,x2,y2 (the coordinates of P1,P2, which are two > >diagonally-opposite corner points). > > > >This looks similar to xmin,ymin,xmax,ymax, but it allows the use of > >either pair of diagonally-opposite corner points, whereas > the min-max > >only allows for the one pair. > > > >It is a small point. But it is at variance with present > (2.0) practice > >in > >Ch.3 and Ch.5, and I seem to recall some earlier resolution to stick > >with the way of CGM:1999 and WebCGM 2.0. > > > >Does anyone want to argue for min/max pairs? > > > >-Lofton. > > > >>Exceptions > >> None > >> > >>Chapter 6 - no changes > >>Chapter 7 - no changes > >>Chapter 8 > >> > >>Add to WebCGMAppStructure object methods: > >> > >>getAppStructureExtent() > >> This method has no parameters. > >> This method returns a String > >> > >> > >> > >>-- > >>Stuart Galt > >>SGML Resource Group > >>stuart.a.galt@boeing.com > >>(206) 544-3656 > >> > >> > >>------------------------------------------------------------ > --------- > >>To unsubscribe from this mail list, you must leave the > OASIS TC that > >>generates this mail. You may a link to this group and all > your TCs in > >>OASIS > >>at: > >>https://www.oasis-open.org/apps/org/workgroup/portal/my_work groups.php > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe from this mail list, you must leave the OASIS TC that > >generates this mail. You may a link to this group and all > your TCs in > >OASIS > >at: > >https://www.oasis-open.org/apps/org/workgroup/portal/my_workg roups.php > > > > > > > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]