Closed okdistribute closed 8 years ago
I like the dropbox way of showing the file preview full-screen. Allows the user to see a lot of the file content at once, and leaves a lot of space to display metadata or actions on the file.
See video: https://cl.ly/3E1Y46470M2F
For the use case of just wanting to browse and preview a lot of files quickly, a split-screen or slide-in layout would be more convenient (no need to close and open a fullscreen view for each file).
See video: https://cl.ly/3Z1H2L430M3b
Updated mockups. Not sure if we still need (file size related) error states like this? Attaching for reference anyway.
What does the user see when they preview a file from dat in the browser or on the desktop app?
This could be useful on the desktop app because you might want to see the file before downloading it, or only download one of 100 files (some repos/files could be very large).
Right now, dat viewer supports many different kinds of files (including video, photo, audio, geojson, txt, json, etc).
If the file can't be rendered by http://github.com/karissa/render-data, it appends a div with class
render-error
that looks like thisFeatures
Examples
GitHub
When file is too big, it won't render. (need example)
When a file is using git large file storage (dat competitor), it displays some jargon nonsense:
.csv file searching:
clicking 'raw' opens up raw file data into a new screen, no chrome.
'open file in github desktop button' seems a bit off to the side and hidden. they don't like their desktop app.
Can also edit and remove file with small buttons. Right now in dat, only the owner can edit or remove a file.
.yml file with syntax highlighting:
geojson example:
DropBox:
viewing a csv:
clicking 'open' on upper right opens it in the desktop app/finder on local machine.
clicking the 'more options' gives you