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.
On Dec 7, 10:40 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > On Dec 7, 10:06 pm, "mr.freeze" <nat...@freezable.com> 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? > > > On Dec 7, 9:33 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > > No, we should not version .w2p files, it is not needed, and a waist of > > > overhead. > > > > Perhaps admin should be altered to just "copy" an existing app, or > > > download a welcome.w2p from web2py.com. > > > > -Thadeus > > > > On Mon, Dec 7, 2009 at 9:18 PM, Yarko Tymciurak > > > > <resultsinsoftw...@gmail.com> wrote: > > > > On Dec 7, 9:03 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > >> yes, I was actually under the impression that is what admin did. > > > > >> -Thadeus > > > > >> On Mon, Dec 7, 2009 at 8:28 PM, mr.freeze <nat...@freezable.com> wrote: > > > >> > Why not just pull the files directly from the version controlled > > > >> > welcome app files? Isn't admin trying to unpack and get those files > > > >> > anyway? > > > > > This is a bit counter to how you want to store in a version control > > > > system: "derived" files should be made, not stored. > > > > > One of the reasons that cloning the revision was so long was that > > > > these huge, binary files were versioned. > > > > This is one of the reasons that a distribution had a compressed tar > > > > file (not called *.w2p files) - so that they would be smaller. > > > > The only problem, for checkout, e.g. "clone", "pull", "update", > > > > "merge" operations this results in an unusually long activity > > > > (especially for clone, where the changesets - which in the case of > > > > binary files will just be the entire, long list of *.w2p versions). > > > > > For web2py to behave by trying to find *w2p file reflects the concept > > > > that "smaller" distribution files are what is distributed. > > > > > Recent discussions that people might modify their welcome apps is > > > > reason to consider if the change in web2py should be to 'make', or > > > > build a distribution-like installation (that is, if there is no *.w2p > > > > file, then make them). This makes senes for welcome app, perhaps lest > > > > for admin, and is really most questionably as to utility for examples. > > > > > One thing that is clear: it is not desirable (for several reasons, in > > > > general) to version derived files. > > > > > This discussion should probably center on: is it worthwhile to > > > > distribute / build *.w2p files in any of these cases anymore. > > > > > Your thoughts? > > > > > - Yarko > > > > >> > On Dec 7, 8:23 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > >> >> Probably should, I say a central copy of welcome.w2p should be > > > >> >> placed > > > >> >> on web2py.com and urllib to download it if it doesn't exist, this > > > >> >> way > > > >> >> it still does not need to be distributed with the SCM. > > > > >> >> -Thadeus > > > > >> >> On Mon, Dec 7, 2009 at 8:17 PM, mr.freeze <nat...@freezable.com> > > > >> >> wrote: > > > >> >> > Should the admin app be modified then? It still looks for > > > >> >> > welcome.w2p > > > >> >> > then fails when creating a new app. > > > > >> >> > On Dec 7, 8:11 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > >> >> >> the .w2p files are no longer included, but version-ed > > > >> >> >> directories of > > > >> >> >> the examples and welcome apps are. > > > > >> >> >> The consensus was that you would create a new app instead of > > > >> >> >> using the > > > >> >> >> welcome app to make modifications. > > > > >> >> >> -Thadeus > > > > >> >> >> On Mon, Dec 7, 2009 at 7:55 PM, mr.freeze <nat...@freezable.com> > > > >> >> >> wrote: > > > >> >> >> > I've switched from svn to mercurial (SubClipse to > > > >> >> >> > MercurialEclipse) > > > >> >> >> > and most everything seems to be working. One question though: > > > >> >> >> > Where > > > >> >> >> > is welcome.w2p now? Creating a new app fails because it is > > > >> >> >> > missing. I > > > >> >> >> > don't see an hgignore file anywhere so I don't think it is > > > >> >> >> > getting > > > >> >> >> > excluded. Has it been removed from source control? > > > > >> >> >> > Thanks for any help and sorry if this was already discussed, > > > >> >> >> > google > > > >> >> >> > groups search is abysmal. > > > > >> >> >> > -- > > > > >> >> >> > 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 > > > >> >> >> > athttp://groups.google.com/group/web2py?hl=en. > > > > >> >> > -- > > > > >> >> > 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 > > > >> >> > athttp://groups.google.com/group/web2py?hl=en. > > > > >> > -- > > > > >> > 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 > > > >> > athttp://groups.google.com/group/web2py?hl=en. > > > > > -- > > > > > 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 > > > > athttp://groups.google.com/group/web2py?hl=en. > > -- 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.
