On 7 Jul 2008, at 19:29, Isaac Csandl wrote:
- remove obsolete reference to tesla project
It's not dead, it's merely pinin' for the fjords :-) I'm in the process of bringing tesla up to date with Pylons 0.9.7 and Elixir 0.6. Tesla is basically working (including the migrate augmentation) both the default and basic identity options are functional. I haven't yet looked at the row-level auth option. FWIW, I am planning to add an rdfalchemy option.
- migrate + Elixir docs really need a more complete example that shows a project in steps: (1) here's a project without migrate (2) how to add migrate to the project (3) several examples of adding/removing tables & columns, including more complex migrations that involve doing something to existing data as part of a migration ... suggest using the movie example we already have and adding migrate to it as a continuation of that example. That would also encourage its adoption as a smart way to do things.
I did have a go with migrate, it didn't seem to be very happy with sqliite, I had a lot more success when I switched the persistence to PostgreSQL. A very short time afterwards, there was a refactoring and I haven't got round to having another go.
Personally, I don't need the rigour of migrate and miruku looks temptingly lightweight.
And for the truly oblique, there's always xmldiff applied to exported ArgoUML XMI files.
- suggest contributing your Pylons-specific docs to the documentation work that is already underway for Pylons (http://docs.pylonshq.com/),
I did actually have an elixir section in the new-style sphinxified docs but Ben preferred that the docs concentrated on the Pylons core.
AND posting it directly on the Elixir wiki. It's much easier for everyone when it's all in one place, or at least fewer places.
I have put a pointer in the wiki. These days, I author directly in Docbook XML. Life's too short to spend refactoring docs from one wikiML to another.
Cheers, Graham
PGP.sig
Description: This is a digitally signed message part
