PMario wrote: > > There are several ways to achieve similar results, but if the core > dictates one approach we need to stick with it. In my opinion stuff like > this is perfectly fine as a plugin. >
>From a marketing perspective, this is almost a given. IMO this is one of those things that people expect in modern comparable systems. It is even so fundamental that much of it is part of HTML5. Integrating it into TW would only bring the functionality closer to the user for easy application. To use Josiahs term here above, "we're selling TW short" by not featuring this in the standard distro. If the core renders external links, they should behave like browser links. > They should open new tabs. .. I personally don't want to open a PDF inside > a tiddler. I want it to be a link to a new tab. > Ok, but again, which templates to include is another matter. If no template is identified for a link... then it's just a normal link. Actually, I'm reminded of the setting for tiddler titles - "show as text VS. show as link". External links could be "show embedded (where template exists) VS. show as plain link". So: No forced pinging and no forced display - which seem to be your main objections (and I agree with them!) Rather, only the "infrastructure", i.e the equivalents of the richlink main macro and the dictionary, to simplify custom templates. <:-) -- 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/dd0e307c-f744-499a-9639-e9835a91b08b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
