390 lines
24 KiB
HTML
390 lines
24 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<!-- saved from url=(0022)http://rcml/rudeqa.htm -->
|
|
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><head><title>RCML - RUDE Q&A</title>
|
|
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
|
|
<meta content="Tue, 04 May 1999 21:29:02 GMT" http-equiv="Expires"><link href="test/rcml.css" rel="stylesheet" type="text/css"><!--[if gte mso 9]><xml><mso:CustomDocumentProperties><mso:Assigned_x0020_To msdt:dt="string">MarkCarr</mso:Assigned_x0020_To></mso:CustomDocumentProperties></xml><![endif]-->
|
|
|
|
<meta content="Microsoft FrontPage 4.0" name="GENERATOR">
|
|
<link href="rcml.css" rel="stylesheet" type="text/css">
|
|
|
|
</head>
|
|
|
|
<body><!-- Martian Text -->
|
|
<table border="0" cellPadding="0" cellSpacing="0" height="39">
|
|
<tbody>
|
|
<tr>
|
|
<td> <a class="logo" href="http://rcml/">RCML</a> <span class="logodot">.</span> <span class="logohead">RUDE
|
|
Q&A</span></td></tr></tbody></table>
|
|
<hr>
|
|
|
|
<p class="section"><span class="section">What is RCML?</span>
|
|
<p>Rcml is an XML based resource file format, based on the GUI
|
|
requirements of Win32 applications.
|
|
<!-- The Document --></p>
|
|
|
|
<p class="section"><span class="section">How do I generate RCML files? </span>
|
|
<p>You can automatically generate RCML files from existing
|
|
Applications or Windows that you see on the screen. As part of the SDK we
|
|
provide a tool called "RCMLGen.Exe". <a href="http://rcml/Help/doc/UsingRCML/from_rc_to_rcml.htm">Click Here</a>. If you have VC installed try
|
|
out our <a href="http://rcml/Help/doc/rcml_home_page.htm">Tutorial</a>!
|
|
|
|
<p class="section"><span class="section">What new features are there in RCML?</span>
|
|
<p>Simplicity! We designed RCML to be a simple file format. You should be able
|
|
to design more realistic dialogs without writing code!</p>
|
|
<ul>
|
|
<li>Pre-fill list boxes and combo boxes using <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENT_ITEM">ITEM</a>s</li>
|
|
<li>Add <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENT_COLUMN">COLUMN</a>s
|
|
to list views</li>
|
|
<li>Have dialogs automatically resize using <a href="http://rcml/Schema/RCMLSchema.xml#ATTRIBUTE_RESIZE">RESIZE</a></li>
|
|
<li>Set the <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENT_RANGE">RANGE</a>
|
|
on a slider</li>
|
|
<li>Layout your dialog using <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENT_RELATIVE">RELATIVE</a>
|
|
positioning, not absolutes.</li>
|
|
<li>Adhere to style guides easily by using simple <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENTATTRIBUTE_RELATIVE_ALIGN">ALIGN</a>ment
|
|
like "BELOW" and "RIGHT".</li>
|
|
<li>Prevent clipping of text in controls using <a href="http://rcml/Schema/RCMLSchema.xml#ATTRIBUTE_CLIPPED">CLIPPED</a></li>
|
|
<li>Use <a href="http://rcml/Schema/RCMLSchema.xml#ATTRIBUTE_COLOR">COLOR</a>s
|
|
and <a href="http://rcml/Schema/RCMLSchema.xml#ATTRIBUTE_FONT-FAMILY">FONT</a>s
|
|
quickly and easily in the <a href="http://rcml/Schema/RCMLSchema.xml#ELEMENT_STYLE">STYLE</a>
|
|
element</li>
|
|
</ul>
|
|
|
|
<p class="section"><span class="section">How does the resize work?</span>
|
|
<p>There are two different reasons for a user to want to resize a dialog.
|
|
<ol>
|
|
<li>They want to see more content, e.g. more items in a list. <a href="http://rcml/DROP/ResizingDemos/resize.exe">Click Here</a>
|
|
<li>The dialog is too small and they want to 'zoom in' and get bigger fonts. <a href="http://rcml/DROP/ResizingDemos/FontReSize.exe">Click Here</a>
|
|
</li></ol>
|
|
<p>In essence the resize code works out a table of rows and columns from the
|
|
location of the controls on the dialog. It then places the controls into the
|
|
cells - like 'reverse engineering' a TABLE layout in HTML.</p>
|
|
<p>Once the table has been determined, it then proceeds to find which controls
|
|
resize and which don't. This can be <a href="http://rcml/Schema/RCMLschema.xml">overridden</a> by RCML authors.</p>
|
|
<p><p class="section">How do I work out why my layout is wrong?</p>
|
|
<p style="margin-top: 0; margin-bottom: 0">Simply use the <a href="http://rcml/Schema/RCMLSchema.xml#ATTRIBUTE_ANNOTATE">ANNOTATE</a>
|
|
attribute and it will visually show you the resizing being used.</p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
|
|
<p class="section"><span class="section">What platforms will you support down level?<span>
|
|
</span>When will this support be available?</span></p>
|
|
<p>We will support down level platforms. The great
|
|
thing about RCML is that we are not platform specific. We do not make any
|
|
WinNT specific calls. That means you do not have to be reliant on the
|
|
OS. </p>
|
|
|
|
<p class="section">
|
|
|
|
<span class="section">When will the specs be frozen?</span><p>
|
|
The specs are supposed to be at least 90% complete by M1 (August 13). So probably a few weeks after, but definitely before M2. <a href="http://rcml/scheduleupdate.htm">http://rcml/scheduleupdate.htm</a> </span></p>
|
|
<p>When can we start coding to it?</p>
|
|
<p>July 20 is the
|
|
first official SDK drop of our M0 build. <a href="http://rcml/drops.htm">htt</a><a href="http://rcml/drops.htm">p://rcml/drops.htm</a>
|
|
<p><span class="section">When will tools be available and how stable will they be?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0">We will be getting some type of support in VC 7. Essentially it will be a dialog editor and text editor.
|
|
This is a huge step for RCML. It
|
|
provides an opportunity for anyone to easily edit an RCML file.
|
|
We will have extended support in VC 7.5. Also, just as in the early
|
|
days of HTML, notepad can be used to edit RCML files.</p>
|
|
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
|
|
|
|
<span class="section">When will support be in LocStudio?</span>
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0">The LocStudio
|
|
XML 2.0 parser is set to come out in Dec/Jan 1999 timeframe.<span style="mso-spacerun: yes">
|
|
</span>We might get some sort of minimal support by then.<span style="mso-spacerun: yes">
|
|
</span>Most likely we will have extended support in the XML 3.0 parser which is
|
|
schedule for April/June 2000.</p>
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<span class="section">What is RCML going to do about hotkeys?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span>Most
|
|
likely RCML will not support hotkeys in version 1.<span style="mso-spacerun: yes">
|
|
</span>The reason is that it is a localization nightmare according to the Text+
|
|
team (David C. Brown).<span style="mso-spacerun: yes"> </span>Furthermore,
|
|
there isn’t any scheme proposed by MSAA to provide automatic hotkeys.<span style="mso-spacerun:
|
|
yes"> </span>Hotkeys need consistency, so it’s VERY hard to generate at
|
|
runtime.<span style="mso-spacerun: yes"> </span>We’ll leave this for
|
|
now, but perhaps log if we find duplicates or missing keys.<o:p></span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"></o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<span class="section">What is your packaging scheme? Since MUI+ will only be ready in the NT6 timeframe, what will
|
|
you do for NT 5.1?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span>Once
|
|
the RCML file is final, it can be referenced from the .RC file and bound into
|
|
the EXE that way.<span style="mso-spacerun: yes"> </span>Furthermore we
|
|
will do nothing to prevent us from implementing MUI+ when it is ready in the NT6
|
|
timeframe.<span style="mso-spacerun: yes"> </span><o:p></span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"></o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<span class="section">What type of control changes are necessary?</span><p>None!
|
|
RCML can work without any additional changes to the existing controls.
|
|
However, to get added functionality we would like to make a few changes.
|
|
Please look at this document. It is a work in progress. <a href="http://rcml/prelimcontrolchanges.doc">http://rcml/prelimcontrolchanges.doc</a> ></span></p>
|
|
|
|
<span class="section">How do you deal with the plethora of problems when you use DLUs? They are supposed
|
|
to scale with fonts etc, but don’t.</span>
|
|
|
|
|
|
<p>Here is an
|
|
informative email thread. The simple answer is that we do support
|
|
DLU's along with other units such as pixels.</p>
|
|
|
|
|
|
<p/>
|
|
<a href="doc/GMLSpec.msg"><img border="0" src="test/wpe1D.gif" v:shapes="_x0000_i1025" width="102" height="66"></a><!--[if gte mso 9]><xml> <o:OLEObject Type="Embed" ProgID="Package" ShapeID="_x0000_i1025" DrawAspect="Icon" ObjectID="_993893088"> </o:OLEObject></xml><![endif]-->
|
|
>
|
|
<p <span style="font-size:10.0pt;font-family:Verdana"> Label<span style="mso-tab-count:1">
|
|
</span>[edit control]<o:p>
|
|
</o:p><br>
|
|
<span style="font-size:13.0pt;font-family:Verdana">?<span style="mso-tab-count:1">
|
|
</span></span><span style="font-size:10.0pt;
|
|
font-family:Verdana">[edit control]<o:p>
|
|
</o:p>
|
|
</span></p>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-left: 73.0pt; margin-top: 0; margin-bottom: 0"><span style="font-size:8.0pt;font-family:"MS Shell Dlg""> <o:p>
|
|
</o:p>
|
|
</span></p>
|
|
<p>As we should all be able to see,
|
|
the line height changed to accommodate the taller character in the second line.<span style="mso-spacerun: yes">
|
|
</span>This doesn't happen with controls, my explanation as to why went along
|
|
these lines:
|
|
<p>A dialog unit is the average of
|
|
the width and height of a set of characters (A-Za-z). As a result, if you use a
|
|
character which is 'taller' or 'wider' the characters will likely be clipped.</span>
|
|
</p>
|
|
<p>NOW: Use real numbers inside the DLU scaling algorithm - the
|
|
current code uses integers and jumps in steps of 10 to 15 % at a time, thus
|
|
causing up to 15% clipping.
|
|
<p>
|
|
FUTURE: Stop recording dialog item positions as absolute
|
|
coordinates, and start recording the alignment operations the designer used.
|
|
Apply those alignments at run time to the actual measurements of each control.
|
|
For edit controls the designer must choose the <span>languages</span> to be supported and
|
|
accept that more languages means taller controls.
|
|
Averaging the size of A-Z a-z is a low quality compromise at best -
|
|
the more languages and scripts we handle the sillier it looks.
|
|
<p class="section">
|
|
|
|
<span class="section">Will there be 64-bit support in RCML?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Yes.<span style="mso-spacerun:
|
|
yes"> </span>RCML will follow the guidelines set forth by NT USER in order
|
|
to comply with 64-bit code.<span style="mso-spacerun: yes"> </span>Depending
|
|
on when USER sets their specs, we might have support in version 1, but
|
|
definitely by v2.<o:p>
|
|
</font>
|
|
</o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="mso-spacerun: yes"> </span></p>
|
|
<p class="section">
|
|
<span class="section">Will you support the GML spec?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Yes.<span style="mso-spacerun:
|
|
yes"> </span>Supporting the GML Spec is an M1 goal.<span style="mso-spacerun:
|
|
yes"> </span>Please look at our timetable here </font> </span><font color="#000000" size="3"><a href="http://rcml/scheduleupdate.htm">http://rcml/scheduleupdate.htm</a></font></p>
|
|
<p>What font support do you have?</p>
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">We
|
|
migrate the CCS Styles for fonts to a logfont.<span style="mso-spacerun: yes">
|
|
</span>Here is an email thread on the subject.<o:p>
|
|
</font>
|
|
</span></p>
|
|
|
|
<p style="margin-top: 0; margin-bottom: 0"><!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75" style='width:76.5pt;height:49.5pt' o:ole=""> <v:imagedata src="file:///C:/DOCUME~1/T-KIRA~1/LOCALS~1/Temp/msoclip1/01/clip_image003.wmz" o:title=""/></v:shape><![endif]-->
|
|
<a href="doc/GMLSpec.msg"><img border="0" src="test/wpe1E.gif" v:shapes="_x0000_i1026" width="102" height="66"></a><!--[if gte mso 9]><xml> <o:OLEObject Type="Embed" ProgID="Package" ShapeID="_x0000_i1026" DrawAspect="Icon" ObjectID="_993893089"> </o:OLEObject></xml><![endif]-->
|
|
</p>
|
|
<p class="section">
|
|
<span class="section">Do you have Wizard/Property Sheet support? How extensive?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Currently
|
|
we have wizard/property sheet support for Win32 Developers.<span style="mso-spacerun: yes">
|
|
</span>We are creating a new Wizard/PropSheet schema which will contain all the
|
|
pages in one file (as opposed to the one dialog per file we have implemented
|
|
today).<o:p>
|
|
</o:p>
|
|
</font>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">We
|
|
have converted intl.cpl (Regional Settings in the Control Panel) over to RCML.<span style="mso-spacerun: yes">
|
|
</span>Look here <insert link to intl.cpl conversions><o:p>
|
|
</font>
|
|
</o:p>
|
|
</span></p>
|
|
<p>What kind of testing do you have in place? For down level?
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Currently
|
|
we have one dedicated full-time tester on RCML.<span style="mso-spacerun: yes">
|
|
</span>If we decide to go down level in version one, we can expect to get more
|
|
testing resources.<span style="mso-spacerun: yes"> </span>The test
|
|
schedule is approximately dev schedule + one month.<span style="mso-spacerun: yes">
|
|
</span>This means that whenever the dev’s finish a milestone, they will get
|
|
test sign-off approximately one month later.<o:p>
|
|
</font>
|
|
</o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p>
|
|
|
|
</p>
|
|
<p class="section">
|
|
<span class="section">What are your dates?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><font color="#000000" size="3">Please
|
|
look at </font> <font color="#000000" size="3"><font size="3"><a href="http://rcml/scheduleupdate.htm">http://rcml/scheduleupdate.htm</a></font></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p>
|
|
</o:p>
|
|
</p>
|
|
<p style="margin-top: 0; margin-bottom: 0">What customers do you have lined up
|
|
already?</font>
|
|
</p>
|
|
<font size="3">
|
|
<font size="3">
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Window
|
|
NT 5.1 and Exchange Server are our primary customers for V1.<span style="mso-spacerun: yes">
|
|
</span>We do expect the list to grow considerably since many groups have
|
|
expressed interest in RCML as a format that solves their problems with the
|
|
current RC format.<o:p>
|
|
</font>
|
|
</o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p></o:p>
|
|
</p>
|
|
<p class="section">
|
|
<span class="section">How do you handle clipped text?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">We
|
|
work out how big the content is and then re-size the control accordingly.<span style="mso-spacerun: yes">
|
|
</span>Currently the code cannot handle any tricky designs, however, we have
|
|
come up with an elegant solution that will be coded in by M1.</font></span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p class="section">
|
|
<span class="section">What type of runtime support do you have? Can you change the layout of the dialog on the fly?</span>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-top: 0; margin-bottom: 0"><font color="#000000">We
|
|
provide the ability to do string substitution on WM_INITDIALOG. You can use entity substitution. This makes your
|
|
code a lot easier too. Here is an example<span style="font-family: Tahoma; color: blue">
|
|
</span></font><span style="font-family: Tahoma; color: blue">
|
|
<font color="#000000" size="3">
|
|
<a href="http://rcml/examples.htm">http://rcml/examples.htm</a> Another
|
|
dynamic issue is interacting with the dialog while the text or controls
|
|
change. Currently we do not have that support available, but it should be
|
|
in our version 1.<o:p>
|
|
</font>
|
|
</span><span style="font-size:10.0pt;font-family:Tahoma;color:blue">
|
|
</o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p></o:p>
|
|
</p>
|
|
<p class="section">
|
|
<span class="section">How do you deal with commenting (for localization people)?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue"><font color="#000000" size="3">Currently
|
|
any comments made in the RC file are lost at compile time.<span style="mso-spacerun: yes">
|
|
</span>Therefore the developer cannot tell the localizer what strings should and
|
|
should not be localized.<span style="mso-spacerun: yes"> </span>RCML will keep all comments in the file so the localizer can access it.<span style="mso-spacerun: yes">
|
|
</span>Since RCML is an XML based application,<span style="mso-spacerun: yes">
|
|
</span>it provides the ability for any group to easily add comments during any
|
|
stage of the product cycle.<span style="mso-spacerun: yes"> </span><o:p>
|
|
</font>
|
|
</o:p>
|
|
</span></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><span style="color:blue">
|
|
</span></p>
|
|
<p class="section">
|
|
<span class="section">What are your performance numbers?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><font size="3" color="#000000">We scale pretty well. My test with 300 controls comes up in a blink</font></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><font size="3" color="#000000">The working set hit at startup is
|
|
not that bad and it comes mainly from OLE32 and msxml. GDI+ and video
|
|
are delay-loaded and USER32 and the DLLs that depend on them are loaded as well in the non-rcml version of the app.</font></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"><font size="3" color="#000000">Here are some mails:</font></p>
|
|
|
|
<p><font size="3" face="Times New Roman"><span style="font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family:
|
|
"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US;
|
|
mso-bidi-language:AR-SA"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"/> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"/> <v:f eqn="sum @0 1 0"/> <v:f eqn="sum 0 0 @1"/> <v:f eqn="prod @2 1 2"/> <v:f eqn="prod @3 21600 pixelWidth"/> <v:f eqn="prod @3 21600 pixelHeight"/> <v:f eqn="sum @0 0 1"/> <v:f eqn="prod @6 1 2"/> <v:f eqn="prod @7 21600 pixelWidth"/> <v:f eqn="sum @8 21600 0"/> <v:f eqn="prod @7 21600 pixelHeight"/> <v:f eqn="sum @10 21600 0"/> </v:formulas> <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> <o:lock v:ext="edit" aspectratio="t"/></v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:1in; height:56.25pt' o:ole=""> <v:imagedata src="file:///C:/DOCUME~1/T-KIRA~1/LOCALS~1/Temp/msoclip1/02/clip_image001.wmz" o:title=""/></v:shape><![endif]-->
|
|
<a href="doc/RCMLPerf.msg"><img border="0" src="test/RCML_-1.gif" v:shapes="_x0000_i1025" WIDTH="96" HEIGHT="75"></a><!--[if gte mso 9]><xml> <o:OLEObject Type="Embed" ProgID="MailMsgAtt" ShapeID="_x0000_i1025" DrawAspect="Content" ObjectID="_993906093"> </o:OLEObject></xml><![endif]--></span></font></p>
|
|
<p class="section">
|
|
<span class="section">Do you have any version info?</span>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-top: 0; margin-bottom: 0"> </p>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-top: 0; margin-bottom: 0"><font color="#000000" size="3">
|
|
We have 'partial' version information. This is not in sync with NT5 version
|
|
information (a few reasons, mainly enlisting, and confusing people into thinking
|
|
this was an NT5 component).<o:p>
|
|
</o:p>
|
|
</font></p>
|
|
<p style="mso-layout-grid-align: none; text-autospace: none; margin-top: 0; margin-bottom: 0"><font color="#000000" size="3>
|
|
</o:p>
|
|
</span></font></p>
|
|
<p class=" style="margin-top: 0; margin-bottom: 0" MsoBodyText"><font size="3">To
|
|
get the version information, get properties on RCML.DLL or RCMLGen.EXE. We have
|
|
updated the TESTINFO element to get the version information.</font></p>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p></o:p>
|
|
</p>
|
|
<p class="section">
|
|
<span class="section">When I use your generator, my statics come up empty and sometimes my
|
|
icons/images don't show up. Why?</span>
|
|
<p>Currently we display the dialogs outside the
|
|
</font>
|
|
</font></font><font color="#000000" size="3>
|
|
</o:p>
|
|
</span></font></p>
|
|
<p class=" style="margin-top: 0; margin-bottom: 0" msobodytext">application
|
|
</font>
|
|
<font size="3" color="#000000" style="margin-top: 0; margin-bottom: 0" MsoBodyText">
|
|
for testing
|
|
purposes. That means when we generate RCML files from your EXE, we do not
|
|
currently use your applications dialog proc. So any controls that are
|
|
changed during runtime will not work during the test phase. However, once
|
|
the dialogs are bound back into the EXE or simply displayed from within the
|
|
application, the dialog will display correctly. </p>
|
|
<p class="section">
|
|
<span class="section">If the files are separate does that mean that localization has twice as many files in their database?</span>
|
|
<p>Not necessarily. The designer will probably keep the RCML files
|
|
external to the EXE when they are editing the dialogs. However, they can
|
|
always bind it back into the EXE and send it to the localizer.
|
|
<p class="section">
|
|
<span class="section">What type of Unicode support do you have?</span>
|
|
<p>We support both ANSI and UNICODE rcml files. Internally the binaries are
|
|
UNICODE and provide UNICODE and ANSI entry points. For down-level platforms,
|
|
we're building an ANSI version of the DLL and generator (this last one not
|
|
implemented, but no big deal in doing it). If the nls+ project JulieB is
|
|
pursuing gets approved, we're going to use those wrappers and ship one set of
|
|
UNICODE binaries that will work on all platforms. As you know the GML stuff is
|
|
not implemented yet, so we don't know to choose the right strings based on
|
|
locales yet.</p>
|
|
<p class="section">
|
|
<span class="section">Will this cause a proliferation of resource files?</span>
|
|
<p>No. Although we currently have it as one RCML file per dialog, this is
|
|
not very difficult to handle since RCML is just basically a text file. In
|
|
fact it is probably easier to handle RCML files than it is to walk the current
|
|
resource tree.</p>
|
|
<p>When you finally ship your product, the RCML files should be bound INTO the
|
|
executable the same way bitmaps and icons are bound </p>
|
|
<p class="section">
|
|
<span class="section"><style="margin-top: 0; margin-bottom: 0">How do you deal with bidi and orientation changes?
|
|
</span>
|
|
<p>We are currently working with various localization teams
|
|
from across MS to come up with a viable solution. </o:p>
|
|
</p>
|
|
<p class="section"><span class="section">Are you working with COM+? Is there some common ground you can reach on an XML format?</span>
|
|
<p style="margin-top: 0; margin-bottom: 0"> <o:p>
|
|
</p>
|
|
<p style="margin-top: 0; margin-bottom: 0">We have spoken with
|
|
members of the COM+ team and have decided that at least for now, we are two
|
|
separate file formats. Perhaps in the future we can reach some middle
|
|
ground in how we deal with string tables and maybe even use the same binary
|
|
format, but currently there are no plans.
|
|
</p>
|
|
</font>
|
|
</body></html>
|