Jeremy, This email is to you but I would hope that others may want to respond.
I am about to begin working on this "My Scriptures" TW. My wife and I will be leaving in August to serve a one year mission teaching the gospel at a small college. We are hoping to have the TW available for all of our students to study and keep their notes and annotations. We know that this will need to be kept simple and I like the now tools and look of TW5 however since this will be a sizable job an I hope that it will be something that all of our students can use for a long time, I need to know if you feel that TW5 or classic TW will be the best product. Since it does need to be simple, the idea of having a tiddler for each verse and transcluding them into chapters will be too complicated for new users. I feel we can get around that with teaching them to put their notes and simple links inline with a chapter size tiddler. The only thing that I wished I had was the ability to simply link to anchors in the body of a tiddler. I haven't found that ability in TW5 or Classic TW. I am not a coder and have been satisfied using TW for years relying on the feature that are easily available. I figure that if I can create this thing preloaded with a few plugins that it will be easy enough to everyone to use it quickly. I see great value in using TW to provide a way for individuals to take books like the scripture or manuals and make them their own. Any thoughts about other plugins that will help would be appreciated. I have already got some great comments back from the community and I am very grateful. I hope others will also give me their thoughts about this project and let me know which platform to use. Thank you for your great product and your vision. Marc Ferguson On Fri, Mar 4, 2016 at 2:54 AM, Jeremy Ruston <[email protected]> wrote: > Hi Tom > > I (perhaps lazily) have a number of TW5s in the same folder. I like them > all in the same folder because it's the root of my Google Drive, and they > are all equally important to my day-to-day. > > I keep them in 'pinned' tabs in Firefox, and so the only distinguishing > feature is the favicon -- so I'd love to not rely on the default > /favicon.ico. > > > There are three ways to set the favicon for a TW file: > > * Use an icon file called "favicon.ico" in the same folder as the > TiddlyWiki HTML file. This is the only technique suffers from the problem > of having to share the same icon between all files in the same folder > * Use separate icon files for each TW file, linking them using the <link> > tag as described by Ton > * Within each wiki, import a tiddler containing the favicon image, with > the title $:/favicon.ico > > I'd recommend the latter technique wherever possible as it keeps > everything neatly in the single file. > > Best wishes > > Jeremy > > On 1 Mar 2016, at 18:25, Tom Bush <[email protected]> wrote: > > Hi all > > I (perhaps lazily) have a number of TW5s in the same folder. I like them > all in the same folder because it's the root of my Google Drive, and they > are all equally important to my day-to-day. > > I keep them in 'pinned' tabs in Firefox, and so the only distinguishing > feature is the favicon -- so I'd love to not rely on the default > /favicon.ico. > > Ton's answer seems to fit the bill perfectly. Just wanted to give my use > case and say thanks :) > > Tom > > PS is there anything functionally inadvisable about keeping multiple TWs > in the same folder? If so that solves my problem a different way because > I'll have to move them ;) > > On Wednesday, 15 October 2014 19:36:33 UTC+1, Ton Gerner wrote: >> >> Hi Jeremy, >> >> Normally I do use the $:/favicon.ico mechanism. I just came across one of >> my classic TWs using an embedded icon and thought: Maybe it works in TW5 >> when using the $:/tags/RawMarkup tag and it did. >> The <link rel="shortcut icon" href="Images/Favicon.ico"> did not work as >> I reported. >> >> So it was just experimenting for fun ;-) >> >> Cheers, >> >> Ton >> >> On Wednesday, October 15, 2014 8:26:26 PM UTC+2, Jeremy Ruston wrote: >>> >>> Hi Ton >>> >>> Why wouldn't you just use the $:/favicon.ico mechanism? It automatically >>> inserts a link element for the specified image, base64 encoding as needed. >>> The icon itself can be image/x-icon, image/png and I think jpegs work too. >>> >>> The only reason for using <link rel="icon"> would be if you wanted to >>> use an external image as the favicon. >>> >>> Best wishes >>> >>> Jeremy. >>> >>> >>> >>> On Wed, Oct 15, 2014 at 6:52 PM, Ton Gerner <[email protected]> wrote: >>> >>>> Hi all, >>>> >>>> Experimenting with favicons I came across another way of using a >>>> favicon in TW5 (instead of just using $:/favicon.ico). >>>> >>>> In TW classic MarkupPreHead contains default: >>>> >>>> <link rel='alternate' type='application/rss+xml' title='RSS' href= >>>> 'index.xml'/> >>>> >>>> You can add a favicon by adding: >>>> >>>> <link rel="shortcut icon" href="Images/Favicon.ico"> >>>> >>>> or for an embedded base64 type ico": >>>> >>>> <link href="data:image/x-icon;base64,..." rel="icon" type= >>>> "image/x-icon" /> >>>> >>>> Copying the above embedded code into a tiddler in TW5 displays a >>>> favicon, but *only* when the tiddler is open. >>>> After tagging the tiddler with $:/tags/RawMarkup the favicon persists >>>> when the tiddler is not open. >>>> >>>> A few sidenotes: >>>> >>>> * I could not get <link rel="shortcut icon" href="Images/Favicon.ico"> >>>> working with or without the $:/tags/RawMarkup tag. >>>> * Tagging a "normal" image with $:/tags/RawMarkup did not work either. >>>> >>>> One of my classic TWs uses an embedded favicon, an image of a floppy >>>> disk. >>>> If you want to experiment with an embedded floppy icon, this is the >>>> code: >>>> >>>> <link href= >>>> "data:image/x-icon;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QAAAAAAAD5Q7t/AAABiUlEQVQ4y6WQPWsUURSGnxm3sVDCWgSxkClSCImFjV3AysZCO4OFGBasxJ+Q1t+QYKGVf0BBO7dRa8XGYrCw2AyLRZb7Mfeccy0mzg4pNgs51eXA+5znvXDBKQA+//ybzTLb0yOyKmQjm4EqmJFNQbXbmTHdfYHlzN69qhgBpKQ8e/yADydf17r66fIjdm9vAjACEFEevjxk+/nOWgB9NSUlAaAEaJOiktburSK0rSwNUlJUuoWZrQyXZYmmdAYg0gPKsjzXwFRp0wDQtoKKAlDX9cpwVVWICG1MQ4NlhaqqzjcQIbYDQGcgPDn4SPhxuDp8cw8zIw4N4ikgmzGZTDh6/ZZw7T4H+7eIMeKcw3uP9553XwQzO1MhnQJyZmNjDBRQXGI+nxNCwDmHc44QAqpjsmXaYYUYUw9YLBa97mw26wHe+w6QrpKzEUK7BPyua1RGZMs0TcP1zTHHzXua5g4hBLz3OOdQVUSEnI0YO0Dx/9rW3acZYOfGycpP/P7nSv/+9e1NwUXnHwUjFmcJkeMEAAAAAElFTkSuQmCC" >>>> rel="icon" type="image/x-icon" /> >>>> >>>> Cheers, >>>> >>>> Ton >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "TiddlyWiki" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at http://groups.google.com/group/tiddlywiki. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Jeremy Ruston >>> mailto:[email protected] >>> >> -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/E028BFD3-B467-4D41-A721-5D52C00B92FD%40gmail.com > <https://groups.google.com/d/msgid/tiddlywiki/E028BFD3-B467-4D41-A721-5D52C00B92FD%40gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CADVaPKCWzsGKCqEzSN9T3XzJ0KTG2LQHsBDOhQq5xHhKnN8i0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
