codexa / firetext

[NOT MAINTAINED] Word Processing App 📝 📖
https://marketplace.firefox.com/app/firetext
38 stars 28 forks source link

Document width discussion #239

Open twiss opened 9 years ago

twiss commented 9 years ago

After we have #235, we could set a width or a max-width on the editor.

width max-width neither
Pros WYSIWYG out of your printer [desktop] WYSIWYG out of your printer
Cons [mobile] Crammed, or you have to scroll [desktop] Leads to the impression that the document has constant width [desktop] Very wide documents are ugly
Responsive layout is cool and html is good at it [desktop] hard to layout, e.g., a right-floating image
ferndot commented 9 years ago

I think that the width should only apply to document formats that are intended to be paginated, such as ODT and DOCX. Other formats, such as HTML and plain text, might not be improved by this change.

Your width suggestion appears to be the best approach for desktop devices. Mobile is more difficult. How do popular mobile word processors like Documents to Go and Microsoft Office implement this?

[UPDATE] Apparently, Documents to Go does not have a set page width or pagination.

twiss commented 9 years ago

Google Docs, Microsoft Office Mobile, Zoho Docs and Quip all also don't have a width, except Zoho Docs in read mode (i.e. before you press "edit").

ferndot commented 9 years ago

So, max-width might be the best approach.

twiss commented 9 years ago

Notes about #241:

ferndot commented 9 years ago

Should we default to a max-width for HTML?

twiss commented 9 years ago

Well, I'm not sure, it's just that any document at 1920px width looks awful. Also, often when you're writing a document, you want it to look exactly like this, and don't care about responsive design aficionados.

Why do prefer no max-width for html?

ferndot commented 9 years ago

I guess it depends on our objective. If we want the HTML format to primarily be a "document" format, then the max-width is a good choice. For use cases like #214, the max-width might not be beneficial.

Somewhat relatedly, maybe we should put the max-width in the generated html file.

That might solve our dilemma!

ferndot commented 9 years ago

@twiss: does this sound good?

For new html files:

For opened html files:

Additionally, we may want to provide two different html "formats": document (max-width, etc...) and developer (vanilla HTML). And, we might want to put these into templates so that we don't have to include them in the JS.