Standard Drawer Structure for Files
Posted: Mon Jun 03, 2013 7:22 pm
Hello,
Every other OS now has Standard Drawers for End-Users to save their common media files, e.g. Documents, Downloads, Applications (sure not as essential), Music and Videos and excuse my french, but its about bloody time AmigaOS did the same for the sake of not only End-Users, but developers alike!
Push4Dock on OS4Depot, if you ignore the Dock tool itself, includes a great example of how the structure could be laid out.
Just imagine Sketchbloch, user goes to Save an Image, Sketchblock runs for the first time and suggests the 'Image Drawer' - it knows where the path lies because its in a standard location, AmigaAmp/TuneNet/<insert your favourite music player here> brings up a requester at a starting point of 'Music Drawer' - again it knows where the path lies because its in a standard location. Timberwolf defaults to 'Downloads Drawer - it knows where the path lies because its in a standard location, in a future LibreOffice release, the user decides to save that Spreadsheet or Document a request appears suggesting a 'Document Drawer' - again it knows where the path lies because its in a standard location - etc.... etc... I think you get the point I am trying to make here. Standards.
These Common Drawers could potentially be tracked in similar fashion to the 'AppDir' mechanism, they should be forced upon on the computer and non-negotiated and any attempt to delete 'Common Drawers' should also be frown up or simply made Undeleteable. Easier said than done am sure.
Standards are the absolute way forward even if many in the community think otherwise.
Every other OS now has Standard Drawers for End-Users to save their common media files, e.g. Documents, Downloads, Applications (sure not as essential), Music and Videos and excuse my french, but its about bloody time AmigaOS did the same for the sake of not only End-Users, but developers alike!
Push4Dock on OS4Depot, if you ignore the Dock tool itself, includes a great example of how the structure could be laid out.
Just imagine Sketchbloch, user goes to Save an Image, Sketchblock runs for the first time and suggests the 'Image Drawer' - it knows where the path lies because its in a standard location, AmigaAmp/TuneNet/<insert your favourite music player here> brings up a requester at a starting point of 'Music Drawer' - again it knows where the path lies because its in a standard location. Timberwolf defaults to 'Downloads Drawer - it knows where the path lies because its in a standard location, in a future LibreOffice release, the user decides to save that Spreadsheet or Document a request appears suggesting a 'Document Drawer' - again it knows where the path lies because its in a standard location - etc.... etc... I think you get the point I am trying to make here. Standards.
These Common Drawers could potentially be tracked in similar fashion to the 'AppDir' mechanism, they should be forced upon on the computer and non-negotiated and any attempt to delete 'Common Drawers' should also be frown up or simply made Undeleteable. Easier said than done am sure.
Standards are the absolute way forward even if many in the community think otherwise.