The main difference in the port of DBXTalk to Gemstone is that FFI part. Fortunately, DBXTalk design makes it easy to adapt.
Just make your own subclasses of OpenDBX class. Right now we have PharoOpenDBX and its subclasses OpenDBXUnix and OpenDBXWin32.
You should create a subclass of OpenDBX called GemstonOpenDBX or something like that, and implement all the API methods (abstract methods in OpenDBX class) to use Gemstone FFI instead of the Pharo FFI. Of course, you could also copy/paste/modify the PharoOpenDBX subclasses and change them for Gemstone FFI.
My recommendation is to ask in Gemstone mailing list which is the equivalent FFI version of one particular example, like odbx_bind. And then you write the rest.
Let me know how it works. I would really love to have DBXTalk working on Gemstone.
Keep us informed,
On Thu, Apr 4, 2013 at 11:05 AM, Dario Trussardi <[hidden email]> wrote:
You received this message because you are subscribed to the Google Groups "DBXTalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
|Free forum by Nabble - Scala forum||Edit this page|