<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>We need to figure out how we are going to deal with the connectors.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Summary</b><o:p></o:p></p><p class=MsoNormal>- We want to use the new pageList control in the wizard to allow users to create and use linkIDs behind the scenes. Users will simply select the name of the page they want to jump to from the pageList control. The pagelist control writes the linkID of the selected page to the attribute’s value.<o:p></o:p></p><p class=MsoNormal>- This means re-working the connector pages to use the linkID rather than pageID (I don’t think this is hard / lengthy)<o:p></o:p></p><p class=MsoNormal>- This brings a big improvement to the connectors in toolkits.<o:p></o:p></p><p class=MsoNormal>[so far so good<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The same thing would also work with a page templates project in standalone xerte. Project’s could still be round-tripped to toolkits and back again.<o:p></o:p></p><p class=MsoNormal>[so far so good still]<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Problem<o:p></o:p></b></p><p class=MsoNormal>The problem is with the page wizards. When using the wizard there, there is no way of getting a list of pages in the piece, or generating linkIDs for them, so this approach won’t work. Now there are many problems, because the page wizards share the code with the page templates models.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Considerations<o:p></o:p></b></p><p class=MsoNormal>Xerte standalone is pretty much at the end of its life. <o:p></o:p></p><p class=MsoNormal>Hardly anyone uses page wizards in standalone xerte.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Before we discuss options, is there anything else to add to this summary? Please keep comments short and to the point so that we can get a clear sight of the problem and the options we have available.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>