new T2 and new T3

[mdipierro]

I have just reposted a new T2

http://mdp.cti.depaul.edu/examples/static/web2py.app.plugin_t2.tar

and a new T3

http://mdp.cti.depaul.edu/examples/static/web2py.app.t3.tar

The new T3 you can see here:

http://web2py.appspot.com/t3/default/wiki/main

- includes T2 so you do not needs to install the plugin separately
- has different configuration menus for settings/models/procedures/
styles via the web interface
- this means you can customize everything via the web based interface
including colors.
- if your code has errors, debug information appear in a nice zoom
popup. Give it a try!

I could use help on the following todo:

- replace the configure/settings page with sqldesigner
- include a mechanism for importing/exporting data in CSV. Everything
is in datastore but importing will break references. Needs thought

[BearXu]

new T3 has fixed all issues I found before

2008/12/7 mdipierro <mdip...@cs.depaul.edu>

[Tito Garrido]

The barchart feature is from t2 or t3?

--
Linux User #387870
.........____
.... _/_õ|__|
..º[ .-.___.-._| . . . .
.__( o)__( o).:_______

[mdipierro]

both

On Dec 7, 3:46 pm, "Tito Garrido" <titogarr...@gmail.com> wrote:
> The barchart feature is from t2 or t3?
>
>
>
> On Sun, Dec 7, 2008 at 10:34 AM, BearXu <bearx...@gmail.com> wrote:
> > new T3 has fixed all issues I found before
>

> > 2008/12/7 mdipierro <mdipie...@cs.depaul.edu>

[Fran]

On Dec 7, 12:11 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> I have just reposted a new T2

web2py.js is not Internationalised, unlike the equivalent code in
web2py's web2py_ajax.html
Can I assume this is a bug & not deliberate?

F

[Fran]

On Dec 8, 7:54 pm, Fran <francisb...@googlemail.com> wrote:
> web2py.js is not Internationalised, unlike the equivalent code in
> web2py's web2py_ajax.html
> Can I assume this is a bug & not deliberate?

I see it is deliberate, because, of course files in 'static' aren't
pre-processed unlike those in 'views'
I still see it as a bug to have user-visible strings not
Internationalised hence it seems better to have t2 use the same
approach as base Web2py...is there any big reason why this shouldn't
be done?

F

[Tokyo Dan]

I'm confused...
Is this new T2, T3 stuff to with web2py something like what Pinax is
to django?

[Tokyo Dan]

Also is there a tutorial / manual on T2 & T3?

On Dec 7 2008, 9:11 am, mdipierro <mdipie...@cs.depaul.edu> wrote:

[Tokyo Dan]

Disregard this. I guess I should refer to the readme section on the T3
website.

[mickgardner]

A couple of questions:

1, is there a change log?
2. What (if anything) has this release to do with the up coming new
web2py release?

[mdipierro]

There is changelog for T3.

Massimo

[Fran]

On Feb 2, 4:01 am, mickgardner <mickgard...@gmail.com> wrote:
> A couple of questions:

> 2. What (if anything) has this release to do with the up coming new
> web2py release?

This predates the new work in gluon/tools.py.
The 2 are independent of each other...each stands alone.
T2/T3 are more mature & featureful.
Tools.py will be a stable API once completed, but won't have the full
scope of T2
e.g. no plans AFAIK to include Wiki/Comments/etc functionality - those
higher-level widgets will stay in T2 (basically anything which
requires support from stuff in /static will not move down to gluon)

F