Persoanlly I don't think I'll use T2. If T2 comes with T3 which it necessarily has to, what's the problem of whomever wants to use T2 getting it by downloading T3? My guess is that you'll end up using T3 anyway and eventually going a bit to a lower level here and there to achieve a bit more customization of your application. I don't know. Just my way of looking at the whole thing.
As for the name... massimo, I believe you're Italian right? Open source projects often come with funny/cute names of fruits, animals, dishes, etc. often in other languages. Since italian is a language with many open vowels and with may words that are quite easy to pronounce I would suggest some italian word. I don't know... like... which animal would web2py if it would be an animal? Then T3 could be called something after web2py... I don't something like web2py => cat T3 => tiger somthing like that... don't know. On 17 Dec, 20:38, "Paul D. Eden" <[email protected]> wrote: > +1 for adding a plugin system to web2py and making T2 a plugin. > > A standardised and documented plugin system will, in an of itself, be > a great boon to web2py. > - Plugins (modules) are the reason that drupal became as big as it > did. > > Now with that said, web2py already has applications. > > What exactly is the difference between plugins and applications? > - In my mind, applications are sets of files can run alone (and be > distributed via tar files (a great system is already in place for > doing this)) > and plugins would be meant as building blocks in applications or a > means of overriding and changing the default behaviour of web2py or an > application. > > On Dec 15, 12:48 pm, mdipierro <[email protected]> wrote: > > > So far nothing changed yet. > > > So far I did exactly what you said and I just reposted plugin_t2 > > making sure the t2.py is the same as the t3 one. > > > I just do not want to maintain two apps that share mostly the same > > files. > > > Let's keep this discussion going. I am not sure myself what the best > > way is. > > > Massimo > > > On Dec 15, 1:33 pm, Kacper Krupa <[email protected]> wrote: > > > > I agree with ceej, he's right. > > > > On 15 Gru, 20:27, ceej <[email protected]> wrote: > > > > > I understand what you are saying Massimo and Vince, but what I mean is > > > > I just think t2 should be kept separate and maintained as a sort of > > > >pluginand I think vince you proved my point by saying "web2py, T2 and > > > > T3 are quite confusing, i guess we may need a plugins system for > > > > web2py. " I don't think merging t2 with t3 and then adding t3 specific > > > > things into t2 was a good idea I think you should have extended t2 in > > > > a separate module for t3 specific things, because one I think it > > > > confuses things like Vince points out and two could cause a lot of > > > > trouble down the line when people just want toplugint2. > > > > > On Dec 15, 12:36 am, vince <[email protected]> wrote: > > > > > > i've been playing with T3, T3 actually is a sample wiki build on top > > > > > of T2 plus some extra features too. > > > > > > i think what Massimo mean is he will no longer distribute T2 itself as > > > > > you can find it on T3. right? > > > > > > web2py, T2 and T3 are quite confusing, i guess we may need a plugins > > > > > system for web2py. > > > > > > vince > > > > > > On Dec 15, 2:01 pm, mdipierro <[email protected]> wrote: > > > > > > > This is what I meant. t2 is contained and will be contained in t3. > > > > > > > On Dec 14, 4:11 pm, ceej <[email protected]> wrote: > > > > > > > > I like the idea of t3 but I also really like the idea of t2, I > > > > > > > feel t2 > > > > > > > should be separate from t3 and the extra features in t2 that are > > > > > > > specifically for t3 should be in a separate module extending t2. > > > > > > > Because t2 is a great module to plug into any application and > > > > > > > helps > > > > > > > speed up the development process. Which I think a lot of > > > > > > > developers > > > > > > > like the idea of. T3 is more of an application already for > > > > > > > someone to > > > > > > > build on top of and is ok for certain types of projects. So I > > > > > > > really > > > > > > > think we should consider "merging" t2 into t3. > > > > > > > > What are other peoples thoughts? > > > > > > > > On Dec 14, 9:51 am, Joe Barnhart <[email protected]> wrote: > > > > > > > > > In keeping with the web2py theme, a couple which come to mind > > > > > > > > are: > > > > > > > > > app2py > > > > > > > > > webapp2py > > > > > > > > > On Dec 10, 4:13 pm, mdipierro <[email protected]> wrote: > > > > > > > > > > This is not the final word. I think we need a better name. T3 > > > > > > > > > is not > > > > > > > > > easily identifiable. > > > > > > > > > > Suggestions? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
