36.0 Beta 3 (36.0.715)

To change Logos to the beta channel, enter the command Set update channel to beta in the Command Box. (Please see beta warnings and risks.)
To immediately update Logos (if it is already set to beta channel), enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Comments
-
I've only played around with it for a few minutes, but wow - I am highly impressed with the Dynamic Resource Toolbar!
Looking forward to learning it more. Great job, Logos folks!
Macbook Air (2024), Apple M2, 16gb Ram, Mac Sequoia, 1TB storage
0 -
When I open the library by clicking on the toolbar icon, and have the detail view on, then use the trackpad on my Mac Book Pro to swipe to the furthest right of the columns it doesn't reach the end but bounces back quickly only showing half of the column on the far right. If I dock the library pane it allows to me swipe over and view the entire column on the far right of details view.
👁️ 👁️
0 -
In the vertical three dots, at the upper right, the tool for linking through htlm, L4, etc. has disappeared. Where do I find it?
0 -
Marco Ceccarelli said:
In the vertical three dots, at the upper right, the tool for linking through htlm, L4, etc. has disappeared. Where do I find it?
Copy as URL is available under the Share menu
but, as mentioned here, the other copy options seem to be missing.
0 -
Marco Ceccarelli said:
In the vertical three dots, at the upper right, the tool for linking through htlm, L4, etc. has disappeared. Where do I find it?
In the new toolbar under Share
Have joy in the Lord!
0 -
Thank you. But ... "copy special" in my Windows PC doesn't appear
0 -
Marco Ceccarelli said:
Thank you. But ... "copy special" in my Windows PC doesn't appear
Please post a screenshot - and I suggest this is best discussed in the thread at https://community.logos.com/forums/t/224537.aspx or in a separate thread
0 -
Marco Ceccarelli said:
Thank you. But ... "copy special" in my Windows PC doesn't appear
Are you looking for the create slides option?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Graham Criddle said:
I don't have a machine to do beta testing on, but I wanted to ask if in the new toolbar if there is still the possibility to create an L4 Link.
Why is this important? Because this gives us who use the MacOS linking system the possibility to create a deep system based link from a programme like Obsidian.
So an L4 link looks like this in default: logosres:lgcystndrdbblsb;ref=Bible.Mt23.1;off=36
What we have to do is edit it into a markdown compatible link in Obsidian: [Mat 23:1](logosres:lgcystndrdbblsb;ref=Bible.Mt23.1;off=36)
A bit of a friction in a workflow to manually edit... but it at least allows for one to create one way links from other MacOS programmes to Logos resources and notes.
In an ideal world, they would be bi-directional, AND would be compliant with MacOS standards so that apps like HookMark could be used along with many other apps.
Regardless, it would be a step backwards to lose L4 links and I hope in this feature update to preserve the current functionality.
0 -
Donovan R. Palmer said:
I don't have a machine to do beta testing on, but I wanted to ask if in the new toolbar if there is still the possibility to create an L4 Link.
We're not currently sure - I can see the option - so we are asking the question
0 -
I don't find anymore the button to switch from a bible to others or from a commentary to others ... annoyed
0 -
Marco are you a Logos Pro subscriber or signed up for the Beta License? If not, that may be the reason that others can see the option but you do not see it...
I'm neither, so I can't test and or verify myself - but the dynamic toolbar has one of those requirements based on the Release info
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Marco Ceccarelli said:
I don't find anymore the button to switch from a bible to others or from a commentary to others ... annoyed
If you are talking about the old Parallel Resources option to hop to another resource (bible, etc.) I don't see it either (I am Pro). I do have Add Parallel Text on the bar, it only has Multiple Book View underneath. Not under Tools either.
0 -
Solved!
0 -
Marco Ceccarelli said:
In the vertical three dots, at the upper right, the tool for linking through htlm, L4, etc. has disappeared. Where do I find it?
We decided to remove L4, HTML, WIKI, and RL from the toolbar given the very low amount of usage.
UPDATE: We removed HTML, WIKI, RL from the new toolbar. We noticed that these were rarely used, so we removed them. L4 was removed because of other plans we tentatively have for future development. Even though they are removed, any existing L4 links will still continue to work. That being said, we hear you all on the L4 links and are having discussions around this.
Ali Pope | Logos Desktop and Mobile Program Manager
0 -
I used it almost daily
0 -
Ali Pope said:
We decided to remove L4
Wow! This is one of the few things that allows researchers to bust up the walled garden that Logos is when you are working in collating materials in other apps on your computer. The problem is, Logos is set up pretty much to only do Logos, so if you are working with PDFs, ebooks on other platforms, etc... this there is no way to bring Logos into your workflow other than use the L4 link. Would it be possible to reconsider this?
0 -
Marco Ceccarelli said:
Solved!
Your picture isn't very large - where is this? EDIT: NVM, found it - the drop down left of the verse!
0 -
Morgan said:
What will this mean for existing L4 links in the future? I have relied on them exclusively in hyperlinking my notes to other resources.
I have a bazillion L4 links as well.
0 -
Morgan said:
What will this mean for existing L4 links in the future? I have relied on them exclusively in hyperlinking my notes to other resources.
To be clear, existing L4 links will continue to function. We have no intention to break existing links.
0 -
Donovan R. Palmer said:
The problem is, Logos is set up pretty much to only do Logos, so if you are working with PDFs, ebooks on other platforms, etc...
I don't know what this means, sorry.
Donovan R. Palmer said:this there is no way to bring Logos into your workflow other than use the L4 link. Would it be possible to reconsider this?
The ref.ly link (which is copied by the Share button) will work in other applications (and is otherwise equivalent to L4). In fact, it works better in many applications than the L4 "private protocol", which is not always recognised as a hyperlink.
(I would like us to use "universal links" or similar to intercept ref.ly links so they open directly in the application rather than opening a web browser first, but I don't know how soon we can implement that.)
0 -
Bradley Grainger (Logos) said:
(I would like us to use "universal links" or similar to intercept ref.ly links so they open directly in the application rather than opening a web browser first, but I don't know how soon we can implement that.)
That would be a nice feature!
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
MWW said:
I have over 100 workflows set up that utilize the L4 linking. I have spent many hours setting up those workflows. Please do not remove them!!
We're not removing the ability to use L4 links.
Nick Mueller said:To be clear, existing L4 links will continue to function. We have no intention to break existing links.
0 -
I am liking this. Good job!
I was determined to break something and couldn't. It just works.0 -
Bradley Grainger (Logos) said:
I don't know what this means, sorry.
Bradley - check out this link, as this explains a whole research system that is built around deep system links of which Logos is part of.
https://community.logos.com/forums/p/221356/1291426.aspx#1291426
There are other threads on the forums which highlight how Logos is being used this way, with programmes like DevonThink, but here's a few.
https://community.logos.com/forums/p/223010/1299176.aspx#1299176
https://community.logos.com/forums/p/220457/1284904.aspx#1284904
https://community.logos.com/forums/p/220457/1283132.aspx#1283132
Logos was far ahead of its time in providing ubiquitous linking, and more apps are working this way. Here is a current list that HookMark, a MacOS utility, that helps with research connections between apps using URI links.
https://hookproductivity.com/what-mac-apps-are-compatible-with-hook-app
My request is please do not break this functionality, not without at least some consultation which will allow us to make plans on what we are going to do.
0 -
Bradley Grainger (Logos) said:
We're not removing the ability to use L4 links.
Bradley, I am glad for that, but utilizing L4 links is an ongoing process. For instance, I have recently utilized L4 links to access AI All and AI Books searches. As Logos adds features or as my study and preaching focus changes, I will need to access L4 links.
0 -
Ali Pope said:
We decided to remove L4, HTML, WIKI, and RL from the toolbar given the very low amount of usage.
Apologies! I misspoke in my previous reply. The HTML, WIKI and RL were removed from the toolbar because of the low amount of usage. L4 was removed because of other plans we tentatively have for future development. That being said, we hear you all on the L4 links and are having discussions around this.
Ali Pope | Logos Desktop and Mobile Program Manager
0 -
Ali Pope said:
We decided to remove L4, HTML, WIKI, and RL from the toolbar given the very low amount of usage.
L4 is very useful in some external apps to avoid going thru a web browser. Please restore.
There is also a case for WIKI with Personal books.
Dave
===Windows 11 & Android 13
0 -
Donovan R. Palmer said:
My request is please do not break this functionality, not without at least some consultation which will allow us to make plans on what we are going to do.
We're not breaking this functionality.
(I'm not sure why everyone thinks that removing a menu item means we're stripping away the ability to deep link into the application?)
0 -
MWW said:Bradley Grainger (Logos) said:
We're not removing the ability to use L4 links.
Bradley, I am glad for that, but utilizing L4 links is an ongoing process. For instance, I have recently utilized L4 links to access AI All and AI Books searches. As Logos adds features or as my study and preaching focus changes, I will need to access L4 links.
The new "Copy link" button on the Share "ribbon" copies a link that you can paste into any other application to open the current panel or resource. (This is exactly the same as the previous "Copy location as URL" panel menu command; we have not removed this functionality.)
0 -
Donovan R. Palmer said:Graham Criddle said:
So an L4 link looks like this in default: logosres:lgcystndrdbblsb;ref=Bible.Mt23.1;off=36
What we have to do is edit it into a markdown compatible link in Obsidian: [Mat 23:1](logosres:lgcystndrdbblsb;ref=Bible.Mt23.1;off=36)
A bit of a friction in a workflow to manually edit... but it at least allows for one to create one way links from other MacOS programmes to Logos resources and notes.
In the new system, just click "Copy link" on the toolbar (next to "Copy special"). This generates https://ref.ly/logosres/lgcystndrdbblsb?ref=Bible.Mt23.1&off=36. Paste that into Obsidian and it "just works" without any manual editing, because it's a "real" URL. When you click it, Logos should open up directly to that location.
IMO, this change is an improvement because we've reduced the friction of using links in other applications.
0 -
Bradley --
I really appreciate you interacting with us on this. I am not a beta tester, but somehow picked up on this development.
The two reasons I think I understand for this change are:
1. Low usage - unless Logos can monitor remotely how many L4 links I have built, I am not sure how this can be gauged. If it can be gauged, then perhaps a question to ask is that if this is a useful feature for including Logos into overall research workflows, perhaps it should be developed and promoted.
2. Security - this was a complete surprise to me. Apple is far from perfect and who knows, they may very well decide to break this part of MacOS due to security concerns, but even the standard Apple apps Chrome, Mail, Contacts, support this as a hard baked system feature. Third party apps like DevonThink, Obsidian, Agenda, Fantastical, all use this convention. It is in their menus and they have promoted and refined it.
Bradley Grainger (Logos) said:IMO, this change is an improvement because we've reduced the friction of using links in other applications.
I tried it and and it does appear to work offline. This is great news. However, there is still friction because Logos does not play well or dance to the same tune as all these other apps.
1. First, I can't use standard MacOS linking conventions between Logos and other apps. As I mentioned earlier, there is no way that I am aware of that I can put a link in a Logos Note. I can't use HookMark and I believe from what I understand, this will break using this feature with Alfred.
2. Because it is the not standard URI, it's integration and rendering manifests in different ways. For example DevonThink will show me incoming links from other apps. Logos is always the odd one out on the playground.
Unless I am missing something, I was hopeful that the next time there was any development around L4 links, we would move forward with current app linking conventions. From my point of view, this proposal to use ref.ly might slightly adjust some friction, but it is mostly a sidewise move. Don't get me wrong, I am grateful that you are not doing away with this feature all together!
I would still urge Logos to consider examining the standards around this for the sake of academic research and advances in Personal Knowledge Management (PKM) thinking. The more that Logos can play nicely with other research and knowledge management platforms, the greater value it is of assisting in studies that ultimately connects to Logo's vision. It takes what is otherwise a walled garden, and opens up new possibilities for Logos to maintain its distinctive features while contributing to an overall ecosystem. See the Manifesto for Ubiquitous Linking
I can't speak so much to HTML, Wiki, etc... I have used them occasionally, but I do pick up on forums from time to time that these features are relied on by specialists in a number of use cases. I guess the question is, unless this is really bogging down the code or the UI, is it really that bad to keep them in and refine them?
0 -
In my opinion the pop-up menus opens too slow. And not smooth enough on Mac.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Fabian, can you provide details about your hardware, OS version, and the performance characteristics being observed? Additionally, what CPU/RAM utilization you have (Activity Monitor) when the menus are slow (e.g. is nothing else running, or are other programs using a lot of resources, or, is Logos, etc).
We do have improvements to the smoothness of these menus that will ship in v37 (beta).0 -
Donovan R. Palmer said:
2. Security - this was a complete surprise to me. Apple is far from perfect and who knows, they may very well decide to break this part of MacOS due to security concerns, but even the standard Apple apps Chrome, Mail, Contacts, support this as a hard baked system feature. Third party apps like DevonThink, Obsidian, Agenda, Fantastical, all use this convention. It is in their menus and they have promoted and refined it.
I'm lost, sorry. It sounds like you're talking about a common UI convention? I'm not seeing the connection to L4 links and security.
Donovan R. Palmer said:1. First, I can't use standard MacOS linking conventions between Logos and other apps. As I mentioned earlier, there is no way that I am aware of that I can put a link in a Logos Note. I can't use HookMark and I believe from what I understand, this will break using this feature with Alfred.
Are you reporting that other apps' private protocols don't work in Logos Notes? If so, I'm not completely surprised. In my experience, private protocols have poor interoperability support between applications. The lack of support (particularly on macOS) was why we added refly in the first place: https://community.logos.com/forums/t/66752.aspx.
IMO, those other apps should use https: URLs, which would "just work" in Logos Notes, on the web, and in many other applications. If they don't/won't, we can consider adding support on a case-by-case basis. (Or maybe you're saying that there's some kind of system registry where our application could look up all installed protocols?)
Donovan R. Palmer said:2. Because it is the not standard URI, it's integration and rendering manifests in different ways. For example DevonThink will show me incoming links from other apps. Logos is always the odd one out on the playground.
I'm lost again. You're saying this doesn't work because logos4: is not a standard URI, but you also don't want us to change to a more standard URI, such as https://ref.ly?
Donovan R. Palmer said:Unless I am missing something, I was hopeful that the next time there was any development around L4 links, we would move forward with current app linking conventions. From my point of view, this proposal to use ref.ly might slightly adjust some friction, but it is mostly a sidewise move.
It sounds like you wish logos4: URIs, or the private protocol handler, or some "conventions" (I'm not sure what those are) were improved. That sounds like a new feature request with requisite discovery and a plan for how it would be implemented across macOS, Windows, iOS, Android, and Web. In the meantime, refly has 1-1 compatibility with logos4:, so this isn't a backwards move. Maybe it's sideways, like you're saying, but IMO this is a step forward to simplify the UI (just one "Copy link" button) and generation of links that, by default, work everywhere (because they're https).
(Sorry if I've greatly misconstrued your post; I feel like there's a terminology or background gap that's making it hard for me to understand what you're trying to say here.)
0 -
Donovan R. Palmer said:
See the Manifesto for Ubiquitous Linking
I just read this. We've essentially been doing this since 2009 (or earlier, if you count libronixdls: URIs).
We invite software developers to do their part, by
- ensuring their users can conveniently obtain a link to the currently open or selected resource via a user interface; and
- providing an application programming interface (API) to obtain or construct a link to that resource (i.e., to get its address and name).
No API, but the "Copy link" button satisfies (1).
A link is a reference to an information resource (data) that the user can access by interacting with the link. It consists of an address of that resource and the name of the resource. Typically the address has the form of a Uniform Resource Identifier (“URI”), as described in RFC-3986,
scheme:[//authority]path[?query]
. Web URIs are common but there are also custom, app-specific URIs.We use a Web URI.
Developers of software that processes information resources should strive to:
- Ensure that each user-accessible resource (object or entire document) that their software creates and processes can be identified and accessed via links.
- Enable identification of – and access to – deeply nested selections, such as a region of text or a node within a hierarchical object (e.g. a node in a mind map, or a task in a project).
- Ensure that links to information resources are robust. For instance, they should still be useful if the addressed resource is renamed or moved.
- When applicable, ensure that there is a clearly documented separation between the top-level (primary) resource (such as a document) and the deep (secondary) identifier within the resource, so that the user can choose whether to access the overal resource or a nested item within it (e.g., at a particular anchor, page and/or character location).
- Make the user interfaces for copying links and accessing linked resources as easy and convenient to use as copying and pasting, keeping accessibility considerations in mind (such as providing keyboard shortcuts and ensuring menu items are easy to reach).
- Provide an application programming interface (“API”) to:
- obtain the link, address or other unique identifier and name of the currently selected or open resource, and of the deeply nested selection (if any)
- open or reveal a resource by its address — and to a location or item within the resource if a deep link is provided
- If users can create resources with the software’s user interface, then provide an API to create a resource with user-specified parameters (such as name), which returns the address of the newly created resource.
- If the resources created by the software are accessible both from a browser app and a special-purpose app, then publish a scheme for converting local addresses to web addresses. This should allow conversion of local URLs or IDs to web URLs and vice-versa. Using universal links may avoid the need for two different addresses for web and local access to information resources.
- Yes
- Yes
- Yes
- Yes
- Yes (improved with the new Copy link button)
- No (API support not planned)
- No (no API support)
- We are moving towards using universal links to avoid the need for two different addresses
0 -
I apologise, I am certain that some of the confusion is that I am not a subject matter expert. So I am probably punching air above my head. LOL!
Bradley Grainger (Logos) said:I just read this. We've essentially been doing this since 2009 (or earlier, if you count libronixdls: URIs).
I totally agree. Logos was cutting edge and ahead of its time.
What has been my observation, is even with this, there has been two shortfalls.
1. Links can only be made from Logos to my other apps. There has been no ability to create a link back in a Logos note.
2. Even with this early implementation, links from Logos don't perform or render the way that others do in interactions with apps like DevonThink or HookMark.
If this web URI can bridge that gap, then bravo. So far in my testing, it seems limited. In DevonThink it is a bunch of jibberish. Yes, there is a link, and it works (offline thankfully), but it does not work the same way that the other apps on my computer do.
With all this said, I think I have made my case as best as I can. I really appreciate you hearing me out, and I am grateful that you all aren't killing linking. If nothing else, perhaps it is useful that there are some users that are working in this way?
Blessings.
0 -
Matt Preucil said:
Fabian, can you provide details about your hardware, OS version, and the performance characteristics being observed? Additionally, what CPU/RAM utilization you have (Activity Monitor) when the menus are slow (e.g. is nothing else running, or are other programs using a lot of resources, or, is Logos, etc).
We do have improvements to the smoothness of these menus that will ship in v37 (beta).Hello Matt,
MacBook Pro 2018 with the T2, Intel i7 16GB 1Tera.
What I see is: If I open the same menu again, right after the first one, then it is much faster and it doesn't stuck in the middle of the opening.
Another issue: I got in the testing.
Thanks
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Donovan R. Palmer said:
1. Links can only be made from Logos to my other apps. There has been no ability to create a link back in a Logos note.
Those other apps should implement Universal Linking and use HTTPS URLs, just like Logos. Then links will "just work", in all applications.
Have you tried putting an obsidian:// link into Google Docs? You can't. But you can use Refly. (The same goes for logos4:, which is why we're switching.)
Donovan R. Palmer said:2. Even with this early implementation, links from Logos don't perform or render the way that others do in interactions with apps like DevonThink or HookMark.
This sounds like a feature request to integrate better with Hookmark. I'm not familiar with that program, but it seems like we need to expose APIs to create URIs. I don't think logos4: is necessary for that; we would create Refly URIs. (Because they're better. 😀) That's a feature request we can put on the backlog, but it's probably not going to happen soon.
Donovan R. Palmer said:In DevonThink it is a bunch of jibberish. Yes, there is a link, and it works (offline thankfully), but it does not work the same way that the other apps on my computer do.
Since I'm not a DevonThink user, I don't understand what's not working, nor why. Refly URIs are just regular URIs, so I don't know why they wouldn't work, or why they would produce gibberish. (Are you sure it's not a DevonThink bug...?)
0 -
Hi Bradley --
I appreciate the time you have taken to understand my use case of Logos and how it fits into my ecosystem of research.
I can't comment on what happens at a functional level in MacOS with HookMark, except that I know that standard Apple apps interface with it. Whether Apple has an API which it leverages or not, I don't know. I was simply advocating for what I perceive as 'normal' (which is probably dangerous) behaviour with links in the operating system. As the L4 link was so close to the types of links in other apps and I have been able to use L4 links in other apps such as Obsidian with MarkDown, I was under the assumption that Logos was very near.
What I can say about DevonThink is that my guess is that it is only able to display what Logos is telling it about the link. As I mentioned, it is the only app on my computer with links that behaves this way. In the screenshot that I provided from DevonThink, you can see that a link exists, it is just not user friendly. Fortunately in this case I can see in the URL the text Mat 23:1 mixed in with other characters, so it gives me a hint that it is a link to a verse in one of my Bibles. It is useable, but less than ideal as it increases the cognitive load to determine what the link is pointing to in Logos. It is, however, better than nothing though, which is why I use it!
So, why have I gone to the trouble to advocate for L4 links? Logos is well positioned to be a leader in Biblically focused academic and research studies by interacting in small, but significant ways in an area like links. The introduction of the L4 link was well ahead of its time and it is easy to see this now with the developments around personal knowledge management, 'second brain' or contextual computing methodologies. In the effort to simplify the interface with this toolbar, my hope has been to advocate that Logos does not throw out the baby with the bath water with 'simplifying' links. When I read things like lack of usage or security risk as part of the rationale, I have raised questions about them.
With all this said, I really appreciate you hearing me out. You guys are the experts and all I can do is raise questions. I can't participate in the beta test of the new toolbar or ref.ly links, so I have to take your word at it that this is a huge improvement. I know technology moves on, so I will look forward to seeing what it does.
While I am at it and I have your attention, there is a feedback item on sending highlights to ReadWise. Similar to links, being able to send small snippets of information that you can aggregate with snippets (a.k.a atomic notes) from other platforms is very powerful. I hope that Logos continues to keep an eye on this space in relation to the evolution of how people study and process information. I suggest Logos has so much to offer and its position will only be strengthened by being relevant to the evolution of research and studies.
Thanks again and blessings.
0 -
I pray L4 links stay in unless there is something better for linking. Please!
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
xnman said:
I pray L4 links stay in unless there is something better for linking. Please!
There is: the Refly links copied by the new "Copy link" button are equivalent to L4 links (in terms of capabilities) but are supported by a wider range of applications (for linking to Logos).
0 -
Donovan R. Palmer said:
What I can say about DevonThink is that my guess is that it is only able to display what Logos is telling it about the link. As I mentioned, it is the only app on my computer with links that behaves this way. In the screenshot that I provided from DevonThink, you can see that a link exists, it is just not user friendly. Fortunately in this case I can see in the URL the text Mat 23:1 mixed in with other characters, so it gives me a hint that it is a link to a verse in one of my Bibles. It is useable, but less than ideal as it increases the cognitive load to determine what the link is pointing to in Logos. It is, however, better than nothing though, which is why I use it!
OK, I see what you mean now.
I can't tell (from the screenshot) if DevonThink just has special logic for parsing "obsidian:" links (to make them look pretty), or if there's some inter-app API/communication that lets Obsidian tell DevonThink the human-readable title for the link.
If the latter, then it seems plausible that we could (eventually) support that, too, as long as DevonThink knows about Apple's Universal Links and understands that local apps can handle "web" URLs. But again, that would be new feature development, and IMO is completely unrelated to L4 vs Refly.
All we're doing with this change is changing what's going on the clipboard from "logos4:Something;Another=ThingHere" to "https://ref.ly/logos4/Something?Another=ThingHere". It's still a "logos4" link if you look at the path in the URI! The capabilities are the same, thanks to Universal Links. (It's actually better, because this hyperlink will immediately work if you paste it into Obsidian or Google Docs.)
Showing titles in DevonThink or any other improvements would have to be future development work, whether we staying with "logos4" L4 or switch to Refly L4. I don't think this change should affect that at all.
0 -
Bradley Grainger (Logos) said:
If the latter, then it seems plausible that we could (eventually) support that, too, as long as DevonThink knows about Apple's Universal Links and understands that local apps can handle "web" URLs.
I just realised that HookMark has Universal Links capabilities - https://hookproductivity.com/help/more/universal-links/ I think this is a good excuse for me to re-look at Apple's Universal Links and what impacts in general this will have in my research workflows. I assume it will result in better, but then again, Apple has broke some stuff over the last four years which I relied on!
Thanks again for taking the time to engage.
0 -
Is it recommended to continue using L4 links for linking sources within Logos for the time beeing until they will disappear?
0 -
NichtnurBibelleser said:
Is it recommended to continue using L4 links for linking sources within Logos for the time beeing until they will disappear?
No. My recommendation is to switch to Refly for everything. (If you find a place inside the software that doesn't handle a Refly link, that is a bug that we need to fix; please report it.)
0 -
Bradley Grainger (Logos) said:NichtnurBibelleser said:
Is it recommended to continue using L4 links for linking sources within Logos for the time beeing until they will disappear?
No. My recommendation is to switch to Refly for everything. (If you find a place inside the software that doesn't handle a Refly link, that is a bug that we need to fix; please report it.)
This is something I've never learned to do. What are its uses and is there a training or help file someone can point me to?
Macbook Air (2024), Apple M2, 16gb Ram, Mac Sequoia, 1TB storage
0 -
Bradley Grainger (Logos) said:
In the new system, just click "Copy link" on the toolbar (next to "Copy special"). This generates https://ref.ly/logosres/lgcystndrdbblsb?ref=Bible.Mt23.1&off=36. Paste that into Obsidian and it "just works" without any manual editing, because it's a "real" URL. When you click it, Logos should open up directly to that location.
When I use a link like this, it opens the Logos Web page in a browser and then it opens the same thing in the Logos Desktop program. Is there a way to force a link only to open in the Desktop program?
0