Hello Gaetan, Good to hear from you. It's a pity that you don't do any more database work, we would all benefit from it ;)
About the copyright/thanks, those will be added should I release the code of course. It was my original intention to simply write a compatibility layer for Elixir code to Declarative, but when diving into it I saw the added value Elixir still provides on top of Declarative, and then started to copy/paste parts and unit tests, and it evolved to a modified copy. The original documentation would indeed only need some changes. I've removed things that were marked as deprecated and changed to setup steps a little bit (but those were not documented). Regards, Erik On Wed, Sep 12, 2012 at 10:26 AM, Gaëtan de Menten <[email protected]> wrote: > On Wed, Sep 5, 2012 at 10:13 AM, [email protected] <[email protected]> wrote: >> Hello, >> >> As part of the Camelot project http://www.python-camelot.com/, >> and to migrate our existing applications from Elixir to Declarative, >> I've reworked Elixir to be a layer on top of Declarative. Most >> of the existing Elixir unit tests pass with the new code. > > Ah! You've done what I dreamed to do but never found the > time/motivation to do it (since I don't use Elixir or any database > stuff for work, Elixir now competes with many other activities for my > free time). My ultimate goal was in fact to clean it up enough to > propose it for inclusion into SQLAlchemy. > >> Elixir is still very useful in that way because it's much easier to >> define relationships with Elixir than with pure Declarative. Also, >> it's a good basis to implement custom usage patterns. (which >> was the original purpose of Elixir) > > Indeed. > >> This code is now part of the Camelot codebase, but it could be >> useful for non gui projects as well. >> >> So if somebody is prepared to take this code and release it >> as Elixir 0.8 and do the project maintenance (packages, >> documentation, etc), I'm willing to cooperate and split this code >> out of Camelot. > > Packages is no big deal. Documentation can be but most of the current > Elixir documentation should apply. I can't commit any time to Elixir > these days for various reasons but I could have some in the future. > I'll come back to you if that is ever the case. I had also a few > features in my local copy waiting for cleanup and commit but well... > no time. > >> If nobody steps in, the code will just remain where it is now. > > That's a bit sad but perfectly understandable. > >> Any thoughts or ideas ? > > Just a small deception: I found no trace of any copyright or even > "thanks" to the original Elixir developers on your code/modified > version of Elixir. > > -- > Gaëtan de Menten > > -- > You received this message because you are subscribed to the Google Groups > "SQLElixir" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sqlelixir?hl=en. > -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en.
