I don't know what the definition of a plugin is but it seems to me
that T2 is what it says, a tier (or level) on top of web2 py.

I have familiarised myself with it a little and it seems to have 2
major characteristics:

1) if SQLFORM and form.accepts() is one level of abstraction then
t2.create() and other T2 methods are a further level of abstraction
combining elements like SQLFORM and form.accepts() to give a very
short controller/action.

2) a basic set of tables is added to the model (hence its
initialization in the model?) to support "common" webapp functionality
out-of-the-box, e.g. login/verification.  As in 1) theT2 functionality
combines existing web2py functionality to provide very short
controller actions.

IMHO T2 is not a major architectural change; it basically provides
shortcuts to common functions.  If it doesn't do what you want out-of-
the-box or with simple adjustments (see the thread about extending t2
tables) then don't use it - no problem - T2's main function is to make
Massimo's life simpler.

As Massimo says: "I do not know myself T2 is the best way to go but it
is a necessary step towards what I am working on: T3." Whatever T3
is :-)

I think the concept of interoperable plugins would be preferable to
the T2 approach but would require specs/docs that are an order of
magnitude more developed than anything the web2py project has been
capable of up to now (apologies if that is incorrect/unfair/offensive
to anyone).  One could envisage an RPM type of dependency checking
being required.  Would it be possible to extend plugin tables (e.g. a
"person" table managed by an authentication plugin)?  Or do people see
plugins as simpler, easier-to-implement things?



On Nov 7, 6:08 am, "Yarko T" <[EMAIL PROTECTED]> wrote:
> I have no Drupal experience per se;  concise point(s) about what stands out,
> is good would be useful...  there a lots of good ideas about!
>
> On Thu, Nov 6, 2008 at 10:53 PM, voltron <[EMAIL PROTECTED]> wrote:
>
> > Apples to oranges? Its the same thing IMHO. Besides I think its harder
> > to sell a "shrink wrapped" T2  plugin/component to someone of no
> > web2py experience, this is not the case for other frameworks, and I am
> > not using Drupal as the only example here.
>
> > oh well
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to