hey erik, while I am tempted, I think I have to pass...at least for now.
Unfortunately, I have a bad case of tendonitis, which means I'm just barely able to do my regular work day :S maybe down the road I can pick it up tho cheers Jarrett Chisholm Prylynx Corporation IT should be this simple [email protected] www.prylynx.com T: (519) 895-0600 On 05/09/12 09:01 AM, Erik Janssens wrote: > Hello Jarrett, > > Creating releases, making sure the docs are on a website, > integrating patches, etc. of a project is always some > work. > > I cannot afford to do this for another project on top of > doing this for Camelot, so for me the easiest thing to do > is to leave the code in Camelot, and then it's no additional > work. > > So you don't need to do code maintenance per se (although > that would be nice of course). > > The Elixir code for setting up the relationships correctly > is pretty nifty, so creating something new is a surprising > amount of work (I tried that first as well, but later on > decided it was easier to change Elixir itself) > > Also Elixir is a good basis to implement custom patterns, > this is actually not documented, I only saw the pieces falling > together when studying the code. > > So ... > > Cheers, > > Erik > > On Wed, 2012-09-05 at 08:36 -0400, Jarrett Chisholm wrote: >> 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.
