we are building a customisable dashboard/widget type interface that can include any number of 'preinstalled' widgets.
i am looking into the best logic for how to store the assorted files that go into making a gadget. most of it is straightforward, but i need to establish the best way of 'installing' future widgets and any associated backend code that may be associated with them – ideally this is not by repeated deployment if one assumes a w3c widget spec object (or opensocial whatever) that is a package of files with a manifest that also were to include arbitrary backend code as well as the views and frontend stuff, would storing backend code in datastore and pulling it out at runtime for eval() be efficient? jonathon -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/ZPjjUusdDyUJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
