<div dir="ltr">We have release process but it's a little complicated.<div><a href="http://etoys.squeak.org/svn/trunk/Documentation/Release-HowTo.txt">http://etoys.squeak.org/svn/trunk/Documentation/Release-HowTo.txt</a><br>
</div><div><br></div><div>Karl</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 5:34 PM, Gustavo Duarte <span dir="ltr"><<a href="mailto:gduarte@activitycentral.com" target="_blank">gduarte@activitycentral.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Bert,<div><br></div><div>I saw the commit to fix the sugar interaction was done.</div>
<div><br></div><div>To generate the deb package of Etoys with the last changes, without wait for the upsream release: It is right the following procedure ?:</div>
<div><br></div><div>1) Run Etoys, and from unnamed project, update from server code.</div><div>2) Save the changes</div><div>3) Copy etoys.image and etoys.changes to my source code tree</div><div>4) Generate the deb package.</div>
<div><br></div><div><br></div><div>My doubt, is meanly if only etoys.image and etoys.changes are needed to copy ?</div><div><br></div><div><br></div><div>Thanks.</div><span class=""><font color="#888888"><div>Gustavo.</div>
<div><br></div><div><br></div></font></span></div><div class=""><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 17, 2014 at 5:52 PM, Gustavo Duarte <span dir="ltr"><<a href="mailto:gduarte@activitycentral.com" target="_blank">gduarte@activitycentral.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Bert, thank a ton for the fix.<div><br></div>
<div>I added the bug to the tracker and upload the fix.</div>
<div><br></div><div><a href="http://tracker.squeakland.org/browse/SQ-1200" target="_blank">http://tracker.squeakland.org/browse/SQ-1200</a><br>
</div><div><br></div><div>I gonna wait, to be included on upstream.</div><div><br></div><div>I hope procedure followed was be right.</div><div><br></div><div>Thanks.</div><span><font color="#888888"><div>Gustavo</div>
</font></span></div><div><div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Fri, Jan 17, 2014 at 9:51 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi Gustavo,<div><br></div><div>the problem is not in the XMLDomParser, but how it it used. Apparently the way gconf stores its values changed. Previously both numeric and string values had a separate entity inside, like you discovered. Now it appears int values are stored in a more compact way.</div>
<div><br></div><div>The problem is in the SugarLauncher>>gconfPropertiesAt: method. It treats strings and int properties the same way. </div><div><br></div><div>Instead of "entry elements first contentString" it might use "entry attributeAt: 'value' ifAbsent: [entry elements first contentString]". This should work with both the old and the new format. Here's the full method, patched (but untested):</div>
<div><br></div><div><div><div>gconfPropertiesAt: aString</div><div><span style="white-space:pre-wrap"> </span>| dir |</div><div><span style="white-space:pre-wrap"> </span>"search up tree to guess home dir"</div>
<div><span style="white-space:pre-wrap"> </span>dir := Project squeakletDirectory.</div><div><span style="white-space:pre-wrap"> </span>[dir pathName = '/'] whileFalse: [</div><div><span style="white-space:pre-wrap"> </span>dir := dir containingDirectory.<span style="white-space:pre-wrap"> </span></div>
<div><span style="white-space:pre-wrap"> </span>[FileStream</div><div><span style="white-space:pre-wrap"> </span>readOnlyFileNamed: dir pathName, '/.gconf', aString, '/%gconf.xml'</div><div><span style="white-space:pre-wrap"> </span>do: [:f |</div>
<div><span style="white-space:pre-wrap"> </span>| props |</div></div><div><div><span style="white-space:pre-wrap"> </span>props := Dictionary new.</div><div><span style="white-space:pre-wrap"> </span>(XMLDOMParser parseDocumentFrom: f)</div>
</div><div><span style="white-space:pre-wrap"> </span>tagsNamed: #entry do: [:entry |</div><div><div><span style="white-space:pre-wrap"> </span>props at: (entry attributeAt: 'name')</div></div>
<div><span style="white-space:pre-wrap"> </span>put: (entry attributeAt: 'value'</div><div><span style="white-space:pre-wrap"> </span>ifAbsent: [entry elements first contentString])].</div><div>
<div><span style="white-space:pre-wrap"> </span>^props].</div><div><span style="white-space:pre-wrap"> </span>] on: FileDoesNotExistException do: [:ignore | ].</div><div><span style="white-space:pre-wrap"> </span>].</div>
<div><span style="white-space:pre-wrap"> </span>^self error: 'cannot find gconf path ', aString</div></div></div><div><br></div><div>This document describes how to publish a fix for Etoys:</div><div><br></div><div>
<a href="http://etoys.squeak.org/svn/trunk/Documentation/Developer-HowTo.txt" target="_blank">http://etoys.squeak.org/svn/trunk/Documentation/Developer-HowTo.txt</a></div><div><br></div><div>If you just want to fix it in the distro rather than waiting for an upstream release, you should be able to change the method, enter the <span style="white-space:pre-wrap">hidden unnamed top-level project, and save the image from that project (it is important to be in that project when saving the image).</span><div>
<br></div></div><div>- Bert -</div><div><div><div><br><div><div>On 16.01.2014, at 15:54, Gustavo Duarte <<a href="mailto:gduarte@activitycentral.com" target="_blank">gduarte@activitycentral.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Hi Georg,<div><br></div><div>The xml file content is:</div><div><br></div><div><div><?xml version="1.0"?></div><div><gconf></div><div> <entry name="color" mtime="1389708067" type="string"></div>
<div> <stringvalue>#9A5200,#FF2B34</stringvalue></div><div> </entry></div><div><br></div><div> <entry name="birth_timestamp" mtime="1389708044" type="int" value="-849347955"/></div>
<div><br></div><div> <entry name="ip" mtime="1389708044" type="string"></div><div> <stringvalue>1.2.3.4</stringvalue></div><div> </entry></div>
<div><br></div><div> <entry name="SugarBuddyOwner" mtime="1389708044" type="string"></div><div> <stringvalue>1234</stringvalue></div><div> </entry></div>
<div><br></div><div> <entry name="nick" mtime="1389708044" type="string"></div><div> <stringvalue>estudiante</stringvalue></div><div> </entry></div>
<div></gconf></div></div><div><br></div><div>I don't know much about xml format, but seemingly it hasn't XML schema specification, right ? </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jan 16, 2014 at 11:11 AM, Georg Gollmann <span dir="ltr"><<a href="mailto:gollmann@zid.tuwien.ac.at" target="_blank">gollmann@zid.tuwien.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><br><div><div>Am 16.01.2014 um 13:10 schrieb Gustavo Duarte <<a href="mailto:gduarte@activitycentral.com" target="_blank">gduarte@activitycentral.com</a>>:</div><div><br>
<blockquote type="cite"><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
I guess that XMLDOMParser doesn't support the xml line format: </div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<entry name="birth_timestamp" mtime="1389708044" type="int" value="-849347955"/>.</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
I don't know much about xml format, but i think that is valid format entry, so XMLDOMParser has bug.</div></blockquote></div></div><div><br></div>Whether the bug is in the parser or the file depends on the XML schema specified in the file.<div>
<br><div>
<span style="border-spacing:0px;text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:Helvetica;word-spacing:0px"><div>
Kind regards</div><span><font color="#888888">Georg</font></span></span></div></div></div><br></blockquote></div></div></blockquote></div><div>
</div>
<br></div><br><br></div></div><span><font color="#888888"><div>
<span style="border-spacing:0px;text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:'Lucida Grande';word-spacing:0px"><div style="font-family:Helvetica">
<span style="font-family:Helvetica">- Bert -</span></div><br></span>
</div>
<br></font></span></div><br><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br><br>
<br></blockquote></div><br></div></div>