> > name of the tiddler that you'll want them to appear in.
This assumes that the image is to appear in only one tiddler. What if
you want the same image to appear in more than one tiddler? Also, how
will you control placement *within* the flow of the tiddler content?
What about image display options like floatleft [<img[filename.jpg]],
floatright [>img[filename.jpg] and linked images [img[filename.jpg]
[URL]] ? How will those be specified?
> > Then, in //tiddler template//, perhaps at bottom, theres a
> > {{{[img[localpath/tiddlername]]}}} where the localpath is hard coded but
> > the tiddlername is a generic 'current' reference.
It seems like you are proposing to embed local path information within
the ViewTemplate. The purpose of the ViewTemplate is to control the
*layout* of the rendered tiddler (and also sometimes to trigger macros
that have side effects, so that programmed actions can occur whenever
a tiddler is displayed). To define configuration values that are used
throughout the document and need to persist across sessions, you
should store them as slices within the SystemSettings tiddler. (see
http://tiddlywiki.com/#PersistentOptions)
> > For multiple pics in one tiddler save pics in that local folder using eg.
> > format //name (1), name (2)// etc. In the tiddler template there's a script
> > that //if// the link {{{[img[localpath/tiddlername]]}}} exists, then also
> > check {{{...tiddlername+1}}} etc. (The suffix //"_(#)"// is Windows default
> > when a filename already exists in a folder. I assume other OS'es use
> > similar solution.)
This forces you to have multiple images with the same name (albeit a
different numeric suffix). This makes it really difficult to manage
those image files within that directory, without needing some kind of
image viewer to differentiate the files.
> > The main advantage is that you can save pics directly to you folder
> > (always the same one). There's no(?) extra hassle other than naming the
> > image upon saving it - which you're always asked to do anyway!
>
> > No image (or file for that matter!) with the current tiddlers name =
> > nothing displayed. And the idea does of course not exclude common/manual
> > {{{[img[..]]}}} use!
It seems to me that, except for your specific, narrowly-defined use
case, most people will still use the "common/manual" method of
embedding images.
> I think handling images (and videos etc) in TW is very under exploited
> considering the *extreme *popularity of these features in other services
> and web tools.
Consider these:
http://www.TiddlyTools.com/#ImagePathPlugin
http://www.TiddlyTools.com/#AttachFilePlugin
http://www.TiddlyTools.com/#FileDropPlugin
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
http://www.TiddlyTools.com/#Donations
Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
