Hi, I've been aiming to do a similar thing recently, although as I'm using it as an exercise to learn python (and pylons) it's nowhere near as good as this.I tried it out and it worked well, although I have a few initial comments (I realise it's an alpha though :-)
- It seems like the objects you are able to edit are only used to get the underlying schema, so you are effectively mapping straight on to the database without using the ORM, so relations do not show up. I have been trying to work out where these fields are stored and as far as I can tell they are in MyObject.mapper.props could an SQLAlchemy expert confirm (or correct) this? - It would be good to not be able to edit the primary key of the object - Perhaps Mako could be made to run in parallel with any other templating engine (see http://docs.pythonweb.org/display/pylonscookbook/Using+Mako+templating+language ) - Perhaps the list of editable object types could be a dict containing other dicts that could define which object fields are editable - Need to be able to pass a limit and an offset to the list view, I tried it with a table of 5000 rows and it took a little while :-) I am happy to help with some stuff on this if you would like, I have already built a method for adding relations so could look at adding this in if you would like, though it would be good to talk about the architecture of how this should be done though - good way of learning. It does seem like something like this is missing from pylons. All of the other web frameworks seem to have some kind of 'instant admin' tool, although the modular nature of pylons makes the idea of a standalone and easily installable ORM content editor which could work with any ORM. Thanks for this, BJPirt On Apr 16, 9:51 am, "nyo" <[EMAIL PROTECTED]> wrote: > Hi, Pylons users and developers! > > I just started a project to develop a pylons controller that > implements automatic database administration (something like Django's > one or may be like Rails dynamic scaffolding). > > There's a very quick (one-day) implementation and it currently depends > on SQLAlchemy mapper (assign_mapper and Elixir will work) and Mako > (that currently needs to be default project's template engine). It > lacks many features (no relationship management and there's only > String/Integer/Unicode field editing for now), but I hope it will > develop into something usable soon. > > I'm not an expert in Pylons and even in SQLAlchemy (and in Python as > well), so my code for sure is somewhat lame. But I'm learning as I > develop and a appreciate any help, advices and comments. > > I set up a project's Trac and Subversion (thanks to > DevjaVu!):http://adminpylon.devjavu.com/ > > Thanks for attention. :) > > PS I'm not a native english speaker, so sorry for my poor English. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
