[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Franck DULUC=20 Technical Data Research Manager=20 Customer Services - SDND=20 AIRBUS France=20 Phone: +33 (0)5 61 18 19 16=20 Fax: +33 (0)5 61 93 59 44=20 mailto:franck.duluc@airbus.com=20 Address:=20 BP D0611, 316, route de Bayonne=20 31060 TOULOUSE Cedex, FRANCE=20 --Boundary_(ID_Op2+mnPi0i5FejE0TnaCjg) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2658.2"> <TITLE>RE: Re[2]: [cgmo-webcgm] DOM questions and implementation = feedbac k</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Ok for the use case: I did not think to that. It is = true that a user may want intentionally to temporarily increase the = size of a text to be able reading it (when the mouse is on for = instance). But I think the choice has to be let to the application to = override the bounding box when changing the font and/or font-size (our = discussion is for both cases I think).</FONT></P> <P><FONT SIZE=3D2>Then I suggest the overriding of the restricted box = can be controlled by the user. Looking at the DOM more carefully and = especially to setStyleAttr, I then asked myself how to do it as set = StyleAttr is a generic function used for multi-purpose, therefore the = adding of such parameter is not as esay as its saying.</FONT></P> <P><FONT SIZE=3D2>Regards,</FONT> </P> <P><FONT SIZE=3D2>Franck</FONT> </P> <P><FONT SIZE=3D2>-----Message d'origine-----</FONT> <BR><FONT SIZE=3D2>De : Dieter Weidenbrueck [<A = HREF=3D"mailto:dieter@itedo.com";>mailto:dieter@itedo.com</A>]</FONT> <BR><FONT SIZE=3D2>Envoy=E9 : vendredi 27 ao=FBt 2004 11:40</FONT> <BR><FONT SIZE=3D2>=C0 : DULUC Franck</FONT> <BR><FONT SIZE=3D2>Objet : RE: Re[2]: [cgmo-webcgm] DOM questions and = implementation feedbac k</FONT> </P> <BR> <P><FONT SIZE=3D2>All,</FONT> </P> <P><FONT SIZE=3D2>I think we have to consider the purpose of this = function, which is to increase readability on a computer screen.</FONT> </P> <P><FONT SIZE=3D2>The intention is to display an illustration that has = been prepared for printout using Times 8pt on screen using</FONT> <BR><FONT SIZE=3D2>Helvetica 10pt.</FONT> </P> <P><FONT SIZE=3D2>On the other side, let's look at the purpose for a = restricted text box.</FONT> <BR><FONT SIZE=3D2>Usually a text is positioned and sized by an = authoring tool. Alignment etc is set as well.</FONT> <BR><FONT SIZE=3D2>So all the details of the text are fully described = in the CGM.</FONT> <BR><FONT SIZE=3D2>As an additional security and help for the recipient = of the file, there is the restricted text</FONT> <BR><FONT SIZE=3D2>box. It is draw tightly around the text.</FONT> <BR><FONT SIZE=3D2>So the recipient opens the file, sets all text = parameters, and then checks the restricted text</FONT> <BR><FONT SIZE=3D2>box. In most cases, no or minor adjustments have to = be made these days.</FONT> </P> <P><FONT SIZE=3D2>Now after having read the file (and displayed) I see = no more reason to constrain the</FONT> <BR><FONT SIZE=3D2>text size to the box. In fact, you could increase = the character height without changing the display:</FONT> <BR><FONT SIZE=3D2>the box would basically "undo" the height = change.</FONT> <BR><FONT SIZE=3D2>To achieve the effect described at the top we must = override the effect of the restricted text box</FONT> <BR><FONT SIZE=3D2>in my opinion.</FONT> <BR><FONT SIZE=3D2>Technical solution:</FONT> <BR><FONT SIZE=3D2>A text element is in a well-defined state after = reading the CGM. Take this state and apply the</FONT> <BR><FONT SIZE=3D2>character-height change to the character height = found in this state.</FONT> </P> <P><FONT SIZE=3D2>Regards,</FONT> <BR><FONT SIZE=3D2>Dieter</FONT> <BR><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: DULUC Franck [<A = HREF=3D"mailto:franck.duluc@airbus.com";>mailto:franck.duluc@airbus.com</= A>]</FONT> <BR><FONT SIZE=3D2>Sent: Friday, August 27, 2004 11:02 AM</FONT> <BR><FONT SIZE=3D2>To: CGM Open WebCGM TC</FONT> <BR><FONT SIZE=3D2>Subject: RE: Re[2]: [cgmo-webcgm] DOM questions and = implementation feedbac k</FONT> </P> <BR> <P><FONT SIZE=3D2>Still listening to you guys !!! </FONT> <BR><FONT SIZE=3D2>BB>>> 3) Since WebCGM only = allows for restricted text elements, what is </FONT> <BR><FONT SIZE=3D2>BB>>> the usefulness of = changing the font-size? ie, it can't exceed the </FONT> <BR><FONT SIZE=3D2>BB>>> box height?! </FONT> <BR><FONT SIZE=3D2>CDW>> This is a question that occurred to me = when we initially </FONT> <BR><FONT SIZE=3D2>CDW>> talked about it in the Cleveland = meeting. Dieter was the one </FONT> <BR><FONT SIZE=3D2>CDW>> that introduced the change of font = size. I think the restricted </FONT> <BR><FONT SIZE=3D2>CDW>> text box ends up getting in the = same was as the character height </FONT> <BR><FONT SIZE=3D2>CDW>> does?? </FONT> <BR><FONT SIZE=3D2>BBAGAIN> It would be good to hear what others = think on this one? The spec will </FONT> <BR><FONT SIZE=3D2>BBAGAIN>have to be very clear here. Some = options could be: </FONT> <BR><FONT SIZE=3D2>BBAGAIN> 1) Increase RTEXT BBox by percentage = (but how to you place the new </FONT> <BR><FONT SIZE=3D2>BBAGAIN> box). </FONT> <BR><FONT SIZE=3D2>BBAGAIN> 2) Increase glyph size once layout = algorithm is done based on original </FONT> <BR><FONT SIZE=3D2>BBAGAIN> values (but the glyphs would overlap) = </FONT> <BR><FONT SIZE=3D2>BBAGAIN> 3) Determine text baseline according to = original values, but compute </FONT> <BR><FONT SIZE=3D2>BBAGAIN> text layout based on new values (I think = this one will give the best </FONT> <BR><FONT SIZE=3D2>BBAGAIN> result, but not sure.) </FONT> <BR><FONT SIZE=3D2>I am not the expert, but as a user I am too often = facing issues with overlapping text that I will ot be in favour of any = modification of the restricted text box, as it may affect the = readability of the graphic. For me the correct behaviour is to = increment the font size as requested and then compute text layout in = the bounding box. I think it is your option 3. From a user point of = view it is the safe way, and if the dummy user want a font increase = that is not complying with the restricted box this will be his fault = and only his. Maybe you can envision that your option 1 may be = accessible through a user specification (like a boolean parameter to = the function), but I am not sure the benefit will worth the effort to = specify and implement correctly this feature.</FONT></P> <P><FONT SIZE=3D2>Best Regards, </FONT> </P> <BR> <P><FONT SIZE=3D2>Franck DULUC </FONT> <BR><FONT SIZE=3D2>Technical Data Research Manager </FONT> <BR><FONT SIZE=3D2>Customer Services - SDND </FONT> <BR><FONT SIZE=3D2>AIRBUS France </FONT> <BR><FONT SIZE=3D2>Phone: +33 (0)5 61 18 19 16 </FONT> <BR><FONT SIZE=3D2>Fax: +33 (0)5 61 93 59 44 </FONT> <BR><FONT SIZE=3D2><A = HREF=3D"mailto:franck.duluc@airbus.com";>mailto:franck.duluc@airbus.com</= A> </FONT> <BR><FONT SIZE=3D2>Address: </FONT> <BR><FONT SIZE=3D2>BP D0611, 316, route de Bayonne </FONT> <BR><FONT SIZE=3D2>31060 TOULOUSE Cedex, FRANCE </FONT> </P> </BODY> </HTML>= --Boundary_(ID_Op2+mnPi0i5FejE0TnaCjg)-- --Boundary_(ID_T7/3KDnZ0Mqe/3KbHKgDEw)--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]