I don't know if my suggestion was a good idea or not, but your comments
appreciated. What I specifically suggested:
Currently, "welcome" app is used as template for new (tier-1) applications.
I suggested that is t3 (which, as currently, includes t2 module) were to be
treated as a "high" tier template of the same sort, and also (like
"welcome") included with web2py, then:
1 - new app could be either high-tier (use t3 as template), or low-tier (use
welcome as template). Not sure which would be the less confusing "default"
for new-comers.
2 - t2 would always "be there" in web2py, so any app could "straddle" and
use as much control as they wanted.
3 - this "solves" (in an in-elegant sort of way) the version problem for
modules (your app always has a copy of it's own modules).
Thoughts (this far)?
Going further:
What I'd really like (instead) is a "modules" (directory?) at the (?)
applications level to hold modules, eg:
applications/t3
would include something like
applications/modules/t2
BUT - I'd like a way to also keep track of versions, and preserve (not
upgrade) modules that existing applications refer to (have a reference
count?), so that you would have something like:
applications/modules/t2/rev12345
and a way for migrating modules - that is, only keeping around [1] newest
version, and [2] legacy versions that apps still used (but provide a way to
migrate). I can think of a couple of schemes for accomplishing this, none
of them "great".
What would this (modules part) do? It would allow people to distribute
modules, and people running websites (e.g. clients) a recoverable way to
upgrade. It would also eliminate copies & copies of modules in every
application (e.g. like shared libraries).
Thoughts?
Thanks,
Yarko
On Tue, Dec 9, 2008 at 3:59 PM, mdipierro <[EMAIL PROTECTED]> wrote:
>
> I can't keep up either. There is much stuff that is undocumented. It
> is getting difficult to maintain T2 and T3 separately. Yarko suggested
> merging. I think it may be a good idea. Perhaps we need a new name
> (suggestions?).
> Should T3 be included with the standard web2py distribution? Why not?
> there are two known bugs to fix: CSV-IO, type='time' on GAE.
>
> Massimo
>
>
> On Dec 9, 2:57 pm, pedro <[EMAIL PROTECTED]> wrote:
> > Wow!
> > Like someone said before, it should be something you put in your
> > coffee. I feel tempted to say: "slow down with the creation of awesome
> > development tools, I can't keep up". I mean... I've been working here
> > and there (in my spare time) on a web2py project and then I see T2 and
> > think if I should switch, now T3, and it looks like I will still save
> > some work if i restart from zero using T3.
> >
> > T3 is beautiful. It introduces a totally new concept of web
> > development.
> > Anyway, what I have to say is: Massimo, thank you for such great
> > pieces of software.
> >
> > On 7 Dec, 21:45, mdipierro <[EMAIL PROTECTED]> wrote:
> >
> > > Posted yet another version. Fixed some minor issues and now when you
> > > edit "configure/procedures" you can do:
> >
> > > ## for example:
> > > def add(a,b): return a+b
> >
> > > ## or define rss feeds
> > > def news():
> > > return dict(title='news',
> > > link=settings.host_url,
> > > description='bla '*100,
> > > created_on=self.now,
> > > entries=[dict(title='news item',
> > > link=settings.host_url,
> > > description='bla '*100,
> > > created_on=self.now)])
> >
> > > ## make is accessible as /app/default/rss/news
> > > settings.rss_procedures.append('news')
> >
> > > ## or expose funtions
> >
> > > def date_future(days=0):
> > > import datetime
> > > return str(datetime.date.today()+datetime.timedelta(int(days)))
> >
> > > ## make is accessible as /app/default/run/date_future/1
> > > ## make is accessible as /app/default/run/date_future?days=1
> > > settings.exposed_procedures.append('date_future')
> > > ## as json at /app/default/json/date_date_future/1
> > > ## as json at /app/default/json/date_future?days=1
> > > settings.json_procedures.append('date_future')
> > > ## or as xmlrpc service at /app/default/xmlrpc/date_future
> > > settings.xmlrpc_procedures.append('date_future')
> >
> > > Massimo
> >
> > > On Dec 7, 7:39 am, BearXu <[EMAIL PROTECTED]> wrote:
> >
> > > > Yes, T3 is like Django's Admin, but the difference is T3 combines two
> > > > interface(Front and Admin) into one.It's more easy to use.
> >
> > > > 2008/12/7 Jonathan Benn <[EMAIL PROTECTED]>
> >
> > > > > Hi Massimo,
> >
> > > > > On Dec 5, 10:26 am, mdipierro <[EMAIL PROTECTED]> wrote:
> > > > > >http://web2py.appspot.com/t3
> >
> > > > > Wow, this is pretty cutting edge stuff. So if I understand
> correctly,
> > > > > T3 is a web2py application that lets you interactively transform it
> > > > > into whatever application you want. This seems really handy for
> quick-
> > > > > starting projects, and I'd see it as especially useful to help
> > > > > beginners get started and for students.
> >
> > > > > Nice job!
> >
> > > > > --Jonathan
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
