Bonjour, I thank you all for numerous reactions.
My motivation for storing on the file system needs to be clarified obviously. My concern is mid-term and long-term storage of information. Being cross-platform is a good point, but being cross-time, cross-years is important as well. Incoming messages are part of a workflow for some time, normally a short time. Afterwards, either it gets deleted, or stored as knowledge or memory. Knowledge management and project info management along the time and among several partners/networks is important in my sector (Architecture agencies). In this case, I think that a MSG (and its attachments !) should be readable without any proprietary software. I was hoping Mahogany was on that track, as it claims to make use of standard formats. You never know how Mahogany (and Mahogany's formats) can evolve on a few years; you also have to foresee a LAN with different versions of Mahogany, or team members not willing to make use of Mahogany. In this perspective, mouse-drag-dropping messages straight from Mahogany GUI to WinExplorer or Linux Explorer would be very efficient. A MSG found in a fileSystem should then be openable easily from the Explorer. If a class extension is needed for this (like *.eml in MS Outlook Express), it should be implemented. Why not ? And if the mail happens to have an attachment , a second improvement (optional) would be to save the attachment outside of the MSG plain text, in a dedicated folder of 2 objects (Msg + attachment).(By the way, some add-ons for MS Outlook do this � well) I understand reactions about storage efficiency ([EMAIL PROTECTED]). But also I see that the next version of Windows OS (Longhorn) is anticipating on this issue, and confirming its importance, even if the MS Longhorn solution is proprietary : MS LongHorn will avoid duplicate storage of messages contents as the File System Database will be common to classical files and messages. In Longhorn, you will organize and fetch your mails and contacts in symbiose with other files related to your jobs, projects, clients.. And straight from the file system shell (Win Explorer,...) you will be able to start composing, editing items. >From a Knowledge Management point of view, this is the good way on, unless it will be ... MS proprietary. For Workflow applications (think of light groupware for building-projects, document follow-up, tasks planning and management, signaling and notifying ...), Mahogany could be used as a very good base for developing a customized cross-point for workflowing between workers acting on different parts of an information system. But the dual management of messages and attached documents is puzzling. My hope is not to rely on [?]forthcoming Longhorn OS, but to extend progressively Mahogany (with Python) for several applications, and to keep more independent from MS, and from its RoadMap). About this, from ([EMAIL PROTECTED]) : > Could it be that you want to have a shell extension, > like the zip utility or the TortoiseCVS, > that treats a mahogany message store like a standard shell folder? Could you gear me towards more info on this solution ? Thanks on forward for your feed-back ___________________________________________________ P-Y Delens, Manager LIENTERFACES - PY Delens, sprl mail : [EMAIL PROTECTED] ___________________________________________________ ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Mahogany-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-users
