If we would parse the file name as markdown, clicking the name there would instead follow the link. I am talking about the workflow (when using double-click to open) of clicking on the name of a file to start inline renaming. When enabled, they can’t click on the side of it to invoke the file.Īnother basic functionality one would lose is inline renaming when using double-click mode. For one, Dolphin still allows users to disable the full row clickable area in Dolphin’s details view mode settings. clickable links as a file name “wouldn’t impair usability, since the user can just go to the right of the filename to invoke the file.” I don’t think this is true. So working on markdown support for file comments is a somewhat worthy goal IMO.įor file names it is a different story though IMO. There editing already opens a separate window. If we were to support a markdown view of this, we would have to separate the viewing presentation from the editing presentation.ĭisplaying the comment as markdown makes some sense in Dolphin’s information panel for example. in Gwenview which allows both modifying and viewing the comment. No need for advanced, finnicky solutions like Ĭurrently file comments are displayed as a simple text field e.g. This would! tagging would become cross-FS, and as simple as #tag. Just being in parseable XML doesn’t help someone comprehensively programmatically poll for consistent metadata. This brings me onto my next part of this point - although tags are supported by most formats that really need them, it’s always as custom metadata. If you’re a bit of an organizational perfectionist like myself, you will know that purely hierarchical organization doesn’t work at scale - search somewhat rectifies this, but it isn’t foolproof, especially for binary files like images. Some more impressive features that are specifically relevant to file storage that I can see it add, however, would be: #Tags for tag organization It allow non-technical users to want to highlight a file to not have to put ! or A before it (it would instead allow them to bold the filename) However, despite the existence of that filesystem-specific property, filenames in Linux are multiline. Plonk the Kate KPart in there, or have inode comments open in the user’s default text editor, and now they’re a popular part of file management. Which is currently sorely underused, would become genuinely viable, since I’d be able to store full notes in it – it’d be just pure text underneath, after all. This is because novice users can use the basic text accentuation that they’re used to ( *, **, and >, which Markdown was designed to improve) and have them automatically parsed by Markdown, Markdown support nowadays includes almost full pure HTML support. A better option than traditional file systems.Summarily, I think that #Dolphin should support markdown processing in directory and file Comments and Names because I believe that it would allow some genuinely incredible innovation in file system management.The documents can be retrieved easily as all the files are properly sorted and tagged.This can help in better data processing in later stages of the organization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |