[TurboGears] Re: Is Identity too much? I think so.

Mon, 24 Apr 2006 13:25:32 -0700



On 4/24/06, Jorge Godoy <[EMAIL PROTECTED]> wrote:

Em Segunda 24 Abril 2006 16:35, Jorge Vargas escreveu:

> NO i never said move the provider just the classes which are 4 with a total
> of 20 lines or so, which will be 100% SQLObject declarations.

I did that as an example of how simple it can be.

And what about people using SQL Alchemy instead of SQL Object?  This is what I
asked:

It was an example you will have 1 template for each "provider backend"

>>  SQLObject? SQLAlchemy?  Both?
>
>
> No just the relevant one, that is why we need a tg-admin quickstart
> template for that.

Both are there.  You just change on line on your app.cfg to choose the new
provider (SQL Object or SQL Alchemy for now are in TG Core).

yes that will still be the same, but it will be a little harder to move from a SA quickstarted project to a SO quickstarted project

> TG_VisitIdentity 240-246
>
> TG_Group 249-272
>
> TG_User 284-306
>
> TG_Permission 343-355
>
> that's 6+23+22+12 = 63 lines with a space in between lines and all the
> deprecaded stuff we are talking about 20 at most

I suppose you're counting SQL Object alone.  Since SQL Alchemy syntax is
different then you'd have to add it to the model as well.  Both are supported
today by TG and the intention is to go towards SQL Alchemy, but keeping SQL
Object compatibility.

NO you will have one model.py in one template for SA and another for SO, and yes the SA one will be bigger.

> I finally end up writing a possible model.py from the template , total 30
> lines and it's MUCH more cleaner then the one in soprovider.py because we
> don't have to force it to be TG_*

And nothing prevents you, today, from doing that.  Or publishing it.  We can
ask Kevin for some "templates" entry points and tags to make it available at
CogBin, so other people know it exists and it becomes available within a
standard TG application *today*, without any patch or any change to the
core...

The reason why I think we should take the "default" out of the controller is that most people will just go with it, defaults are the root of all evil :)

About the templates I was thinking of doing that myself. I just need to learn how to work with nose, paste, adn tg templates.

> I prefer that then having this magic email address that I don't want :)  or
> having two tables! with user data.

You can always use a custom model to prevent that.

> No they will use the correct template went creating their project, and yes
> I know someone will say, what if I change my mind,etc. then you must change
> it, (hint create one with the new template and move your other classes, or
> the other way around) that is a rare case anyway.

Is it rare?  I dunno.  Why not a new plugin for quickstart templates? ;-)  I
prefer this approach since it would allow much more things than just a new
model for identity.

I HAVE BEEN SAYING THAT FOR A COUPLE OF POSTS! sorry search for my name with tg-admin quickstart identity

--
Jorge Godoy      <[EMAIL PROTECTED] >



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to