I agree. We could make a plugin for distribution without renaming the files inside. web2py admin would be able to unpack the plugin over the existing app thus updating the files but it would not recognize the content as plugin files (because appadmin does not start with plugin_*) therefore the content would not be listed under the plugin section.
Is this the same that you have in mind? Massimo On Dec 16, 4:17 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > On Dec 16, 2009, at 12:28 PM, mdipierro wrote: > > > On the one side it may be a good idea to have some of the generic > > views and appadmin be implemented as a plugin. And this will happen in > > the future. > > > On the other side we do not guarantee backward compatibility for those > > since they become part of your application. We only guarantee that the > > framwork continues to work with them. In fact as you change the layout > > you may need to edit web2py_ajax and or appadmin. In general if your > > app works you do not want to upgrade those files. > > Of course, just because it's a plugin (if it/they were) doesn't mean that I'd > have to update them; it would just make it easier. And it's likely that they > wouldn't have been edited, so upgrading would be straightforward. > > As for wanting to upgrade them, it might well be unnecessary, of course, but > if I wanted my app to take advantage of new features (primarykey in the > recent case), I'd need to. And personally, I prefer to keep that kind of > stuff up to date on (admittedly vague) general principles. > > In any event, I'll wait for the future to show up... > > > > > Massimo > > > On Dec 16, 12:30 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > >> I was updating a small web2py app this morning, after moving to 1.74.2, > >> and in doing so I diffed some of its files against the current welcome > >> app, and noticed that a lot of the appadmin code (that I hadn't modified) > >> had been updated (primarykey support, for example). > > >> Likewise, web2py_ajax.html was considerably changed. > > >> I haven't been following the plugin discussion very closely, so I'm not > >> sure that it's quite the right mechanism, but it seems to me that it might > >> make sense for appadmin, and perhaps web2py_ajax, to be implemented/named > >> as plugins, to make it more obvious that it's generic web2py functionality > >> that might want to be updated along with the rest of the framework. > > >> Along those lines, another thing that would have come in handy would have > >> been a virgin copy of the template (welcome) app that I used to build my > >> own app. If I had that, it'd be easier to diff the current template app > >> against the one I used, and to distinguish between changes made to the > >> web2py distribution from the changes I had made. I could do that manually, > >> of course, but it didn't occur to me at the time. > > > -- > > > 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.
