Welcome to Daytona #128
Comments
|
to @akaKenSmith @am1t @papascott @mistersugar @sabre23t -- continuing the previous discussion... I decided I couldn't trade off linking and style against highlighting, i had to have both, so that's what i'm working on this morning. it seems to be possible. |
|
Bing! (I'm glad you guys are getting to watch the development process. That's how you keep your sanity while building something complex. You tell yourself you can't do this, so the problem is simplified, but eventually once it's working it becomes approachable. Now I hope this really works. It could prove that I missed an edge case. It happens.)
|
|
I wasn't much help during the Daytona testing, but I will report that
yesterday when I was wanting to find something I'd previously written, I
reflexively went to Daytona, searched, and found. Only then did I realize
what I'd done and what you've made. So thanks a million.
…---
*Anton Zuiker*
919.923.9491
Blogging again at zuiker.com
On Fri, Dec 10, 2021 at 10:43 AM Dave Winer ***@***.***> wrote:
to @akaKenSmith <https://github.com/akaKenSmith> @am1t
<https://github.com/am1t> @papascott <https://github.com/papascott>
@mistersugar <https://github.com/mistersugar> @sabre23t
<https://github.com/sabre23t> -- continuing the previous discussion...
I decided I couldn't trade off linking and style against highlighting, i
had to have both, so that's what i'm working on this morning. it seems to
be possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5LBHMJO5PL3JPOZBJTZ4DUQIN2PANCNFSM5JXWQCEA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Reporting a quirky behavior but no damage: Yesterday I was using Daytona. Then I noticed last night that Drummer had two tabs open and both were my blog.opml. One tab had the lightning bolt. I was very confused and worried that something had been overwritten, but determined that I had not lost anything. I just used Daytona and clicked the eye icon and was taken to Drummer where the same thing happened - a second tab opened with my blog.opml. I closed the second tab, went back to Daytona, and clicked the eye icon again, and this time a new browser window opened with Drummer and one tab for blog.opml and the other browser window switched to Drummer docs, as expected. |
|
When you write these, please edit out the fear. It makes it really hard for me to focus -- so emotional. That's a bug report about a bug report. ;-) Anyway the obvious question is maybe they were different files. There's a way to tell (it's too hard but it is there). Do a View OPML in the file menu and see what file it opens. This works for public files not private ones. Next time it happens, find out what they are. And just tell us the facts. ;-) |
|
@mistersugar, aren't the two tabs both with the blog explained in this way? The first is the editable blog file already open in Drummer. The second is a read-only instant outline copy sent to Drummer by Daytona. |
|
I was just able to reproduce this... in Drummer it's possible to have a public outline opened twice... once with the "Open…" menu for editing, then again with "Open URL…" as an Instant Outline. |
|
yup that's an area of drummer that needs work. i took a look at it a couple of weeks ago and decided to do daytona. it was too exciting an idea not to see through. |
|
This may be a nit, but I find how History and the Search input field interact, or actually don't interact confusing. Here is what do and see:
The overall display is confusing to me. What I expect to happen is that either when I select a search from History that search term is populared in to the search input field on the page or the input field is blanked out so there isn't a difference in appearance between what I see in the search input box and the actual search results. |
|
I think it would be useful that if a search results that show results from multiple docs that the doc file name or title be displayed somewhere in the result. If you added the doc file name or title to the right of the top level date nodes and then added Collapse All I think the result would appear more meaningful, right now a collapse all action would display a list of dates. |
|
@fmcpherson -- not sure if this is what you were reporting about the History menu, but I broke it in the change I made this morning. It's fixed now. |
|
@fmcpherson -- re only indexing typed nodes, that's the documented behavior. please, read the docs. thanks. ;-) |
|
@scripting I didn't see the docs until you published the search. Sorry. However, I think not including nodes that don't have a type attribute in search is creating an inconsistency with how you are handling such nodes in Old School. I referring to the situation prior when Old School would only publish nodes of type outline and you removed that constraint. |
|
@fmcpherson -- just read the docs ok. |
|
BTW the docs are linked into this post, it's the ONLY LINK in the post. This is an incredible feature -- never been done before, and we needed it. I declare a moratorium on nits for at least the next few days. I'm going to keep rolling and I refuse to become a support slave to people who won't even read the fucking manual. |
Daytona is search for outlines, and that includes:
Drummer docs.
Scripting News.
Your public Drummer outlines.
Read all about it here, and post questions, kudos and love here. ❤️
The text was updated successfully, but these errors were encountered: