Hi Gordon, Thanks for stepping forward! The Directory is an area that would benefit from some enhancements.
Here are the RFEs that we have in stock :) "Add minimal support for WebDAV in Directory" http://restlet.tigris.org/issues/show_bug.cgi?id=346 "Improve default directory listing design" http://restlet.tigris.org/issues/show_bug.cgi?id=665 "Directory listing should support XHTML" http://restlet.tigris.org/issues/show_bug.cgi?id=667 "Provide an XML directory listing representation" http://restlet.tigris.org/issues/show_bug.cgi?id=420 Note that in SVN trunk the relationship between API and Engine has been greatly simplified. Directory instantiates DirectoryResource directly now. Part of DirectoryResource code are really touchy. I would recommend to stay away from those parts if possible :) If you have some specific refactoring in mind, we should discuss them first with you, ideally in the [email protected] list, or via an issue in the tracker. Regarding the header and footer, I'm not sure that we want to support that explicitly. It is already possible to provide a customized index/listing representation if necessary. Maybe allowing to specify a CSS stylesheet would be better? Regarding paging or editing via a textarea, I don't feel like it should be supported by the Directory class directly. Maybe we could propose an extension with sort of file explorer Web UI, but I'm not sure it should be part of the Restlet project as it would probably impose too much in the presentation logic area. We want to keep Restlet agnostic in the UI and persistence area. We can discuss this more if you want. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Gordon Mohr [mailto:[email protected]] Envoye : jeudi 29 janvier 2009 08:28 A : [email protected] Objet : Extending Directory, etc.? I'm interested in enhancing the Directory restlet. For example (though I may not get to all of these): - displaying size and modification-time in listings - allowing a customizable header/footer in listings - supporting paging through certain file types (probably through query-string parameters that cause a non-default representation) - supporting editing of certain file types (most simply, via a textarea full-file editor) Some aspects of the current code flow are daunting. (In particular, delegation to the Engine to create a DirectoryResource, and long twisty methods like DirectoryResource's constructor.) Any tips? Would it break any core assumptions for my Directory subclass to instantiate a DirectoryResource itself, skipping the detour through Engine.createDirectoryResource()? Would refactorings of Directory or DirectoryResource be welcome in the core project? Thanks for any guidance, - Gordon @ IA ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1067321 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1075010
