Search Ideas
2122 ideas match your query.:
I’ve since been able to reproduce the issue after all. Running a raw SQL query in Idea.tree in combination with the inclusion of the Live module seems to mess with Rails’s reloader.
After resetting my working directory and beginning to implement streams a second time, I can no longer reproduce this issue, despite reasonable attempts to reproduce it.
A slow developer experience will slow down all further development, including bug fixes and feature rollouts, which hurts UX as well.
Fast UX is more important than fast developer experience.
Including that module significantly slows down hot reloads on all pages. I need a tight feedback loop in dev.
I could use ActionController::Live to stream ideas to the page one by one. Instant page load.
Ah, but I can reproduce when I manually make the selection by clicking and dragging to cover the entire quote.
… copying extra stuff above and below the box quote, and neither gave me the > sign.
Cannot reproduce, neither on iPad nor macOS.
I tried copying the entire quote…
Cannot reproduce. If I triple-click a word in a box quote, then copy/paste, I get the > sign.
To be clear, if you copy the entire box quote and paste it into a textarea, it will start with the > sign. I just double checked.
This doesn't work for me the way it does for you. I tried copying the entire quote, and also in a separate attempt, copying extra stuff above and below the box quote, and neither gave me the > sign.
I have tried on my windows computer and my iPad.
A single new idea somewhere down the tree could invalidate the cache and slow things down again.
To be clear, if you copy the entire box quote and paste it into a textarea, it will start with the > sign. I just double checked.
You’re saying you’d still want the > if you only copy/pasted part of the box quote, right?
Cache invalidation for user-based caching sounds like a nightmare.
When copying a box quote from Veritula, the box quote formatting (>) is lost.
On initial page load, I could just load the first ten or so top-level ideas and their immediate children, just to reduce wait times and populate the page. Then load the rest asynchronously.
I could lazy load ideas: only load the parts of the page that would be visible on the current viewport. Then load more parts as the user scrolls.
I could cache ideas so deeply nested trees can be rendered at once.
I could cache ideas so deeply nested trees can be rendered at once.
Discussions are getting slower to render as they grow. It’s a rendering issue (not a db issue).
Feature idea: page at /ideas/:id/guide which shows you an idea and helps you address all pending criticisms one by one, if any. At the end, it shows a message ‘You’re all set!’ or something like that.
On iPad, the footer doesn’t extend all the way to the bottom of the page.
Changing the query on the search page moves the cursor to the start of the query input. It should move to the end or, ideally, keep its position.
On the search page, there should be a button to clear the query input.
Feature idea: a page that shows you a random idea of yours that has pending criticisms and then helps you address them all.