Co-incidentally, I was just reviewing the forum code, and thinking about how I would describe what it does for you structurally... In my mind T2 is just that - a tier (not a specific solution).
It is an experiment in (perhaps) a DSL - in the experriment, that is web2py and bringing the concepts to a higher level of abstraction. I recognize what you say when you say "feels weird" - it's almost as if it does SO much for you, there's not much to do - and that feels like not much lattitude to do what you might want to do.... But that misses the point, I think. Just because Massimo knows, has been breathing / eating / living web2py, don't miss a more important thing being developed here: it's not the generic web2py.t2 that's the real product here - it's the flushing out of how web applications will use and share something LIKE this.... We have a few more things to flush out: - how to have different versions of a "plugin" (or module) co-resident in a web2py deployment, so different apps are not forced to upgrade when a new rev of plugin comes out; - how different plugins will cooperate, interact accross the possibility of different applications using them What we need now, I think, is for us / you to look at and understand t2, how it works in terms of plugging into web2py, what you like about the level of abstraction it exposes and what you don't. For the items I listed that I think need to be worked out, it would be interesting for someone to modify (even if trivially) Massimo's t2, and then work out what it would take for 2 apps in one web2py instance to share / use either. If it's a version of web2py, how will you handle the app knowing it has the right version? (minimal version? exact version?) What needs to happen to have 2 versions co-exist on web2py? The real "news" here is not _this_ t2 (although it is interesting by itself), but the STRUCTURE it flushes out so we can each write (and sell???) plugins like this, and even more so - plugins that can act like building blocks - that can interact with themselves. Think of a FORUM plugin, for making it easy to implement a forum with whatever specifications your client might need. Say the same for shoping cart; and wiki... and blog and charge card interface and calendar and.... .....THIS is the point of T2 I think. SO - I encourage you to take T2, and add / take away / somehow change it, and then use it in a demo app on a web2p that (for example) has Massimo's forum code which depends on the original t2... This will be useful! I'm just thinking out loud. What do you think? Regards, Yarko On Thu, Nov 6, 2008 at 12:15 PM, voltron <[EMAIL PROTECTED]> wrote: > > Now I really wonder how many really use or want to use T2 in > production sites? I , like Timothy have also decided against using it > inits present form because it "feels" strange( initializing it in the > model for example). It would be a pity if the component/plugin is not > discussed and finalzed and web2pys core dev stagnates as a result too. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
