Well, it was a bit secret, but I was starting on my free time to setup some
ci jobs to build automagically all the opendbx libraries + test them.

https://ci.inria.fr/dbxtalk/

Now my problem is that my free time for hacking on non phd stuff -> 0
lately... :/


On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <asta...@gmx.de> wrote:

> And Sven insist on still cutting/copying/evaluating one-liners
> in the age of a configuration browser where loading is just mouse
> clicking ;)
>
> But putting jokes aside - it would IMHO be really important to
> have DBXTalk running for Pharo 3.0. Without good database
> support one would loose any argument for Pharo in the
> business world...
>
> It would also be a real bonus if the necessary support DLL's/shared libs
> could be easily provided or installed.
>
> For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides
> the current binaries on Github https://github.com/mumez/PunQLite
>
> Or the NaCl (a binding for Crypto-Nacl library) directly downloads
> and installs them when you install the config (see ConfigurationOfNacl in
> config browser of Pharo 3.0).
>
> Easy access without much hazzle is always a plus... install, connect to
> the DB and go!
>
> Thx
> T.
>
> > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr
> > Von: "Sven Van Caekenberghe" <s...@stfx.eu>
> > An: "Pharo Development List" <pharo-dev@lists.pharo.org>
> > Cc: dbxt...@googlegroups.com
> > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0?
> >
> > Ah, it is just because you insist on using old school two line code ;-)
> >
> > On 06 Feb 2014, at 11:38, Tudor Girba <tu...@tudorgirba.com> wrote:
> >
> > > Gofer new
> > >     smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
> > >     package: 'ConfigurationOfOpenDBXDriver';
> > >     load
> > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge
> > >
> >
> > Gofer new
> >   smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
> >   configurationOf: 'OpenDBXDriver';
> >   loadVersion: #bleedingEdge.
> >
> > Just joking,
> >
> > Sven
> >
> >
>
>

Reply via email to