191–200 of 233 posts
I created a doc just now with three different pieces of content:
1. Text - stayed within the text margins, as expected
2. Table with lots of columns - used the full window (i.e. ignored text margin)
3. Wide image - stayed to the right of the left margin (i.e. ignored only the right text margin)
So the image only used 60% of the browser width.
I'm not a huge google fan but I write a ton and I use google docs extensively, and I have to say I'm crying tears of joy seeing this update. Just yesterday I was complaining to a colleague about how a table he put in a google doc was hard to read because a page-break in one of the rows made it look like two rows when it was only one. Ask and you shall receive! Thank you google docs devs!!!
Earlier quoted context omitted.
I'm one of the original authors of Writely / Google Docs, and worked on relatively heavy-duty word processors in an earlier life. I'd agree with you, and add that there are are a lot of other details that make Notion nicer to use. We made the move from Docs to Notion at work a year or two ago, and I've recently switched for personal use as well. Some of the differences are power-user things (e.g. easier to manage cer…
I preferred notion initially, for many of the same reasons you outlined, but eventually I just couldn’t stand how slow notion is. Google Docs is so much faster. I’m interested to try Google’s new tables product when I get a chance.
Earlier quoted context omitted.
Have you ever tried to print a Notion document? It feels like they made the "Export to PDF" in a weekend. It's hugely underpowered and under-featured. It feels like Notion's demographic just dont need to share documents as documents. Notion would likely have put more effort into that feature if they did.
> It feels like they made the "Export to PDF" in a weekend Ah well, I built it in my first week or so as part of a hiring trial process, back when the company was 16 people in a remodeled auto body shop. Before that, the “PDF Export” feature just opened the browser print dialog. One fun thing about working at a startup is that you solve a problem for 90% of your users, but after a while of user growth and demographic…
https://twitter.com/NotionHQ/status/1103069853252911104
It sure would be nice if I could make all pages "small text" and "full width".
Earlier quoted context omitted.
Pretty sure database is also isomorphic to XML, in that sense. I agree that Notion-ish documents are more structured than Word-ish, though.
A SQL database, with indexing configured correctly, allows you to look up a row in O(log(n)). A bag of XML bytes doesn't give you that. It takes, at best, a SAX parser to do an O(n) scan through the whole document to find stuff. Most DOM implementations give you O(1) indexing by ID, but they require you to parse it first, and that's going to take O(n).
While creating and editing a database, it is SOP to create/maintain and save data structures that provide fast access later.
Is there some reason why you couldn't do the same for XML?
> If your document contains elements like footnotes, headers and footers, or watermarks, and it is converted to pageless, those elements will not be visible. Headers and footers are print-oriented, but losing footnotes is not ok. They could have displayed on the side, or highlighted in some way to display on mouse over or click. Whatever, just make them available...
Then don't use the pageless feature and you will not have any issue
But I don't think this should stop us from discussing a way to possibly improving a product.
Welcome to 2022, Google Docs. Unfortunately there's still a long way to Notion or Dropbox Paper.
It's utterly bizarre just how much Google docs seems to have dropped the ball. It really feels like they haven't developed the product in the past 10 years. This is the first significant feature change that I can recall in a very long time other than minor UI tweaks.
Earlier quoted context omitted.
I wish. One of my clients wants it for everything (typically text, stats, and graphs), and typically views it as just an "add a button" sort of feature, when it winds up being a "reimplement the layout in a different language" sort of thing. (leaving apart the thing where basically they want a gigantic lovecrafian horror of an excel file translated to the web) PDFs have the ability to be a fixed, baked reference of a…
I never quite understood why PDFs are considered to be fixed baked references. Plenty of software can edit pdfs. I have used affinity designer in past to fix up issues in PDFs received from designers. Seems like this can be better addressed by versioning and audit logs or checksums.
Earlier quoted context omitted.
I wish. One of my clients wants it for everything (typically text, stats, and graphs), and typically views it as just an "add a button" sort of feature, when it winds up being a "reimplement the layout in a different language" sort of thing. (leaving apart the thing where basically they want a gigantic lovecrafian horror of an excel file translated to the web) PDFs have the ability to be a fixed, baked reference of a…
I never quite understood why PDFs are considered to be fixed baked references. Plenty of software can edit pdfs. I have used affinity designer in past to fix up issues in PDFs received from designers. Seems like this can be better addressed by versioning and audit logs or checksums.
Notion could implement a feature like "permalink to the content as it was at this point in time". Maybe they already have. But for me to be sure that's an immutable record, I at least have to trust Notion.
I don't see where checksums come into it - either I trust Notion to tell me I'm getting the same document we agreed on, or I need to be able to download the document in a readable form and compute the hash on my client. In which case we're back at PDF again.