I'm tempted, but I don't think I can commit to maintenance. I was actually doing something similar (actually creating a new abstraction layer on top of declarative)...so if this takes off I'll probably use it instead.
Jarrett Chisholm Prylynx Corporation IT should be this simple [email protected] www.prylynx.com T: (519) 895-0600 On 05/09/12 04:13 AM, [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. > > 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) > > 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. > > If nobody steps in, the code will just remain where it is now. > > Any thoughts or ideas ? > > Cheers, > > Erik > -- 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.
