I'm trying to implement an internal feature at the moment on new entry UI that lets you upload pictures and insert them onto Xhina w/o having to leave the screen. As I figure out how to list the weblog resources I stumble upon this line of thinking and I'm interested in hearing your thoughts on it.
I found a bug in the FORM action for the create sub-dir and wanted to fix it in the RC3, but I was not aware we were not doing subfolders at all before (is this correct?) If so, maybe we should think more about the design of the WeblogResource interface a bit more. The main thing I'm trying to do is avoid having a tree-like navigation for a user to find a photo to insert into their entry. I'm toying with the idea of "recursing" down via the FileManager to get all resources and list them as in a photo-well approach (all photos in one view). I know that this might be insane for large amount of files, but the alternative is also rather painful to navigate back and forth between folders until they find what they are looking. Recently, I was playing with Amazon's S3 (simple storage service) and their file system abstraction is done via buckets and entries. A user can create n buckets and m files inside those buckets. If the user decides to name their files "2006/10/me.jpg" then some API client could recreate a folder structure for that given bucket. Maybe what I'm suggesting is that we use this instead of the isDirectory()/getChildren() approach and still have the current filesystem listing in the Upload Files JSPs we have. Allen, is this a bad idea/too much work/too late? -Elias PS. I would like the user to pick out an image from an iframe listing of pictures like this: http://torrez.us/photolog/index.php?x=browse
