<br><br><div class="gmail_quote">On Tue, Oct 6, 2009 at 1:18 PM, Juan <span dir="ltr"><<a href="mailto:smalltalker.marcelo@gmail.com">smalltalker.marcelo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mariano folks<br>
<div class="im"><br>
<br>
On Tue, Oct 6, 2009 at 7:00 AM, Mariano Martinez Peck<br>
<<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>> wrote:<br>
> Hi folks: There is some interest in porting SqueakDBX to different<br>
> Smalltalks. Jan Vrany wants to port it to Smalltalk/X and Marcelo Cortez to<br>
> Dolphin. So, the idea is to discuss here the necessary things I should<br>
> modify so that this task is easier for you.<br>
><br>
> I have been talking with Jan in ESUG and he found a couple of things I<br>
> should do. In addition, I already did the stable release, so I can break<br>
> whatever I want :)<br>
><br>
> About the code, I will do these things:<br>
<br>
><br>
> 1) Create the abstract class SqueakDBXSmalltalkDialect with all of the<br>
> messages like self subclassResponsibility. This class will be in the core.<br>
<br>
</div>like template pattern?.<br></blockquote><div><br>yes<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
><br>
> 2) Create a package in my monticello repo called SqueakDBX-Dialect-Squeak<br>
> and I will create there the class SqueakDBXSqueakDialect (subclass of<br>
> SqueakDBXSmalltalkDialect ) . Now, for Squeak and Pharo users they will need<br>
> not only the core, but also this package. If you want to put here packages<br>
> like SqueakDBX-Dialect-SmalltalkX or SqueakDBX-Dialect-Dolphin, there is no<br>
> problem. But I don't know if this is useful for you.<br>
><br>
</div>Dolphin don't support monticello, changeset is more appropiated. i think.<br></blockquote><div><br>Ok. We can create a changeset instead of monticello<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> 3) FFI calls. This is dialect dependent, but the current design is perfect<br>
> for this :)<br>
> I will keep the class abstract class OpenDBX in the core and that will be<br>
> the API. As you can see there are all the messages with a self<br>
> subclassResponsibility. I will then move my current subclasses of OpenDBX to<br>
> the package SqueakDBX-Dialect-Squeak.<br>
> Then, what you should to in your dialects is to create a subclass of it and<br>
> use that. See the message OpenDBX class>>ffiImplementationForOS<br>
<br>
</div>ok.<br>
<div class="im"><br>
><br>
> 4) WeakRegistry and GC: As you may know, we keep the connections in the<br>
> WeakRegistry so that we can release the database connection when the GC<br>
> collects a DBXConnection object.<br>
> But this, again, is dialect dependent. So, the piece of code that was doing<br>
> this, now it will delegate to the current SqueakDBXSmalltalkDialect<br>
> subclass. In my case it will be SqueakDBXSqueakDialect but in your case it<br>
> will be other.<br>
><br>
</div>Dolphin don't have weak collections.<br></blockquote><div><br>Ok, but there is a way you can register an object somewhere so that the GC send a particular message to it when it is being garbage collected?<br><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> 5) Now, all the things that are dialect specific should be in<br>
> SqueakDBXSmalltalkDialect and subclasses.<br>
><br>
> 6) The core is thought in an ANSI Smalltalk. So, it will be difficult if for<br>
> every message or class you don't have in your dialect I have to change<br>
> something. That would be part of the port work :) Anyway, we can discuss<br>
> each of these situations and evaluate what to do.<br>
><br>
><br>
> Now, about the procedure, as I talk with Marcelo, I think the best way to do<br>
> this is to do something like TDD:<br>
><br>
> - First you port the tests<br>
> - You port the rests of the things until the tests are green :)<br>
</div>Yes agree ,then refactoring for Dialect's support/<br>
<br>
in shot:<br>
make it works.( green test)<br>
refactoring ( plugability of dialects)<br></blockquote><div><br>ok, but the idea is: if you will be the maintainer of the port of SqueakDBX to another dialect, it would be excellent if this port takes the less time as possible. If you have to change a lot, you won't want to do more ports anymore hahaha. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
make run faster.<br>
<br>
Best<br>
Mdc<br>
<div class="im"><br>
<br>
><br>
> What do you think about this?<br>
><br>
> Best,<br>
><br>
> Mariano<br>
><br>
><br>
><br>
><br>
><br>
><br>
</div>> _______________________________________________<br>
> SqueakDBX mailing list<br>
> <a href="mailto:SqueakDBX@lists.squeakfoundation.org">SqueakDBX@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx</a><br>
><br>
><br>
_______________________________________________<br>
SqueakDBX mailing list<br>
<a href="mailto:SqueakDBX@lists.squeakfoundation.org">SqueakDBX@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx</a><br>
</blockquote></div><br>