On Sep 10, 2:10 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> T3 is harder to explain. There is a video on vimeo. It is a handy app,
> it's only problem is that it still use T2 stuff. It should be
> rewritten. It will not take long so perhaps it is one of the first
> things I would do.

I just started developing a very simple website in Plone which was
taking me ages, despite being familiar with the product from before.
It took a lot of server resources & was ugly & difficult to style.

I had a fresh play with T3 just now & found it *so* much nicer:
really, really quick to setup, looks a lot nicer & will be easier to
maintain being in Web2Py.

The one thing that I'm missing right now is the ability to restrict
functionality based on group membership.
Currently there are just 3 roles: anonymous, authenticated, admin.
So currently I can hide pages to just authenticated users, but not
decide which subset can see which hidden pages & not allow a subset to
be able to edit individual pages.
Am I missing something in current T3 to be able to resolve this or
will this require extra development?

I'm started a T3 branch to start the update to current Web2Py - so far
I've mainly done the DAL syntax updates & PEP8 cleanups:
https://code.launchpad.net/~flavour/+junk/t3

The big job, of course, is to use gluon/tools.py instead of modules/
t2.py.
I guess you'll do a complete rewrite to capture the same idea rather
than migrate incrementally?

The only bit that actually gave a failure was missing the cron/
crontab...the rest works fine, but obviously can use a refresh to make
it easier to maintain/extend in future.

Best Wishes,
Fran.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to