On Dec 8, 1:37 pm, "mr.freeze" <[email protected]> wrote: > I have an app that contains all of my standard jQuery plugins, > scripts, images, css, modules, etc. Currently I manually copy and > rename this to create a new app. What I am talking about is having a > 'Copy Application' feature in admin. It wouldn't deal with .w2p at > all. Is that what you mean?
This is beyond what I was saying, and yet seems useful, consistent: I was starting from this: - if we do not version "derived files" (versioning derived files turns out to be bad repository behavior), then we _may_ need a way to re-visit the "default" *.w2p files, how they are used, what is needed. One thing I thought (just thinking out loud) about was to setup the "default template" application from which new applications are created as a *welcome.w2p" file (instead of copying some welcome app from the applications area - this seems more portable, lest restrictive to an installation; coming from Unix, I dislike the idea of "special names", preferring rather nothing special). My thought was, for a new install, first startup, web2py could check: - [1] is there a [web2py-install]/welcome.example.w2p? If not, create one from [web2py-install]/applications/welcome - [2] is there a [web2py-install]/welcome.w2p? If not, copy the welcome.example.w2p app to welcome.w2p - [3] web2py would now always create new apps from welcome.w2p What you are saying (it seems) is to add an admin function to: - Select an app to make the template *.w2p (might as well aslways be called welcome.w2p); - Revert the template for apps back to the default (that is, restore [web2py-install]/welcome.example.w2p to welcome.w2p) This sounds good to me. - Yarko > > On Dec 8, 10:22 am, Yarko Tymciurak <[email protected]> > wrote: > > > > > On Dec 8, 8:36 am, "mr.freeze" <[email protected]> wrote: > > > > Yes, but easier with (1) since you won't have to deal with unpacking, > > > modifying and repacking (unless I misunderstand (2)) > > > Should be no need - what I intended was a way for web2py to > > automatically "derive" the *.w2p (doesn't look like I made this very > > clear, but it was in my head ;-)). > > > if a clean distro, and welcome.w2p doesn't exist, web2py makes it for > > you. > > Then web2py always makes new apps from that *.w2p by default. > > > The only time you would need / want to make a welcome.w2p is to make > > > > On Dec 8, 12:54 am, Yarko Tymciurak <[email protected]> > > > wrote: > > > > > On Dec 7, 11:20 pm, "mr.freeze" <[email protected]> wrote: > > > > > > I agree. I think (1) would be a nice feature as it would give users a > > > > > way to easily create and customize their own template app. > > > > > ... that would be true with both (1) and (2); > > > > > > On Dec 7, 10:40 pm, Yarko Tymciurak <[email protected]> > > > > > wrote: > > > > > > > On Dec 7, 10:06 pm, "mr.freeze" <[email protected]> wrote: > > > > > > > > So the options seem to be: > > > > > > > > 1) Copy the uncompressed welcome app when creating a new app and > > > > > > > let > > > > > > > people know the ramifications of modifying welcome. > > > > > > > .... this could be a "feature" - but the problem: getting to a > > > > > > "clean" place with it; if you clone, and modify, then you will > > > > > > always > > > > > > be getting merges - seems to me this could be confusing, hard to get > > > > > > to the "default" welcome when you want to. > > > > > > > > 2) Have admin pack the welcome app into welcome.w2p if it doesn't > > > > > > > exist upon visiting the 'site' function. > > > > > > > ... maybe better to have admin make new apps from welcome.w2p, and - > > > > > > like routes.py - if there is no welcome.default.w2p, then make one; > > > > > > second, if there is not welcome.w2p (from which to make new apps) > > > > > > then > > > > > > make one from the current welcome app. > > > > > > > What this would afford: you could always get back to the default > > > > > > quickly / easily (welcome.default.w2p); you could resurrect the > > > > > > default any time; > > > > > > > > 3) Have admin download welcome.w2p from web2py.com if it doesn't > > > > > > > exist. > > > > > > > ... I don't see the benefit nor sense of this: if welcome comes > > > > > > from > > > > > > the repository, then why get it from somewhere else? If it is > > > > > > derived, why not get the sources to derive it from (instead of what > > > > > > [3] suggests); I don't like this one... > > > > > > > > What else? > > > > > .... -- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
