On Wed, Dec 2, 2009 at 22:04, mdipierro <mdipie...@cs.depaul.edu> wrote: > For the future version of web2py.... > > > should we (1) continue to distribute admin.w2p, welcome.wp2, > examples.w2p and unpack them on startup (and require --upgrade=yes on > upgrade) or (2) should we just distribute the applications folder with > unpacked apps? > > The case (2) would simplify lots of stuff and avoid lots of problems. > > I originally choose (1) because I thought people were going to modify > admin and did not want an automatic upgrade of it. Some people for > example edit /applications/admin/models/access.py > > Pros? Cons?
I prefer (2) - it will require less space to have web2py installed, too. One point is that we should modify 'create app' in gluon/admin.py as it uses welcome.w2p - but it'll be really cool: if I modify my welcome app, this modified version will be my scaffolding, so it can help developers a lot (and companies too). > -- > > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to web...@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. > > > -- Álvaro Justen Peta5 - Nós fazemos TV digital http://www.peta5.com.br/ 21. 3021-6001 / 9898-0141 -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@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.
