Hi Chris,
thanks for the response, I will have to spend some time understanding more deeply how pygr.Data works before I could comment in more depth. For now here are some thoughts that popped in my head while I was reading your response. > In some ways I want to follow git's model, so you can see a > log of commits you've made in a given My first reaction here is that if you want to follow git's model and offer git-like functionality you might as well use git to manage the files: i.e. a proxy class that actually invokes git behind the scenes. I have heard of such efforts, for example GitShelve attempts to create versioned shelve with git: http://www.newartisans.com/blog_files/git.versioned.data.store.php Regarding the web interface the most important question that I can't myself answer at this point is: Who is the target audience? Who will be using the web rather than a directly pygr.Data and why? I could see the web as a way for a non-technical collaborator to deposit data in a place that we can both access in a convenient way. But in that case all they're interested in is upload and download and not the more advanced functionality. One suggestion that I have is to allow pygr.Data to represent "blobs", data does not have "standardzed" structure, simply returns a file handle either in text or binary mode( this disctinction is only needed for Windows). I found it very common to store intermediate or final results in simple tabular formats. Having them accessible by the same mechanisms would be very handy. I will test a few approaches and post some comments in the near future. best, Istvan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" 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/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
