<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi<br><br>The Seasude compatability layer will address portability between pharo to squeak; my interest is that I like Seaside on Squeak but thevPharo team do not want to, and should not want to , imho, maintain Squeak compatability.<br><br><br>From this thread, I read that task depends on Filetree,, which I have no understanding of, but, I will delve into that to support flawless Seaside support on Squeak.<br><br>Hth.<br><div id="message"></div><br id="br3"><div id="signature"></div><div id="content"><br> ---- On Tue, 11 Aug 2020 16:30:06 -0400 <b> dale.henrichs@gemtalksystems.com </b> wrote ----<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin-left: 5px;"><meta>
<div>
<p>Not quite sure what you mean by "Seaside compat" ... <br>
</p>
<p>Perhaps you are referring to the disk format? Filetree supports
multiple disk formats and not storing Monticello meta data is one
format. Since 2012 I think there have been something like 10
(slightly) different disk formats and probably 6 of them occurred
during the first 6 months of Filetrees life ... the others evolved
across the last decade ... so there isn't just one disk format
that needs to be supported ...</p>
<p>With that said, I can help provide examples and pointers to code
(modulo my current work load:). <br>
</p>
<p>Dale<br>
</p>
<div class="x_496686096moz-cite-prefix">On 8/11/20 11:59 AM, gettimothy wrote:<br>
</div>
<blockquote>
<div><span style="color: rgb(0,0,0);font-family: Lato;font-size: 14.0px;font-style: normal;font-weight: 400;letter-spacing: normal;orphans: 2;text-indent: 0.0px;text-transform: none;white-space: normal;widows: 2;word-spacing: 0.0px;background-color: rgb(255,255,255);display: inline;float: none;">If "branch per release with
conditional platform code.." is the model for the Seaside
compat, shouldn't we bite the bullet and make Filetree the
same?</span><br>
</div>
<div><br>
</div>
<div><span style="color: rgb(0,0,0);font-family: Lato;font-size: 14.0px;font-style: normal;font-weight: 400;letter-spacing: normal;orphans: 2;text-indent: 0.0px;text-transform: none;white-space: normal;widows: 2;word-spacing: 0.0px;background-color: rgb(255,255,255);display: inline;float: none;">If <span style="color: rgb(0,0,0);font-family: Lato;font-size: 14.0px;font-style: normal;font-weight: 400;letter-spacing: normal;orphans: 2;text-indent: 0.0px;text-transform: none;white-space: normal;widows: 2;word-spacing: 0.0px;background-color: rgb(255,255,255);display: inline;float: none;">"branch per release with conditional platform
code.." is NOT the model for the Seaside compat, somebody
please inform me. </span></span><br>
</div>
<div><br>
</div>
<div><span style="color: rgb(0,0,0);font-family: Lato;font-size: 14.0px;font-style: normal;font-weight: 400;letter-spacing: normal;orphans: 2;text-indent: 0.0px;text-transform: none;white-space: normal;widows: 2;word-spacing: 0.0px;background-color: rgb(255,255,255);display: inline;float: none;"><span style="color: rgb(0,0,0);font-family: Lato;font-size: 14.0px;font-style: normal;font-weight: 400;letter-spacing: normal;orphans: 2;text-indent: 0.0px;text-transform: none;white-space: normal;widows: 2;word-spacing: 0.0px;background-color: rgb(255,255,255);display: inline;float: none;">thx.</span></span><br>
</div>
<div><br>
</div>
</blockquote>
</div></blockquote></div></div><br></body></html>