> > > I think a descriptive text would be good. There's a cheap way to do > it, and a more complicated way. > > Cheap > > http://www.example.com/##For example > > just decide that anything following a double hash in the URL is the > descriptive string. This could be pointed out by the popup into which > URLs are entered. It would display as > > For example http://www.example.com/ > > To change an URL or it's description, you'd have to delete and replace, > when you click a link it appears in the Log pane, so you can copy from > there if you're replacing something existing. > > Complicated > > Store URL and description separately and add UI for editing. > > Kind of think if you're comfortable with getting UNLs (text) from other > files, the ## way is probably sufficient. >
I think the 'cheap' way should work fine. > > So I could do that and remove any attempt to guess the most informative > part of the URL (what it does now with basename @ full url) and leave > descriptions up to the user. > > I think though when it automatically creates the reverse link in the > target file, it should use the node name in the source file as the > descriptive text for the reverse link. > > Sound reasonable? > > Yes, that works for me. Rob......... -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
