slices to slides

144 views
Skip to first unread message

Jan

unread,
Jan 30, 2017, 6:27:48 PM1/30/17
to TiddlyWiki
Hi Thomas,
Now I want to use the slices to trigger the slides in a slideshow.
I made a tiddler called
http://slidesnstories.tiddlyspot.com/#Slices%20in%20Focus which so far
displays the slices in the tiddler which currently has the focus.
If you navigate to the SourceTiddler you see this.

<$list variable="tiddler"
filter="""filter='[{$:/HistoryList!!current-tiddler}]'>""">
<<extract tiddler:$(tiddler)$ start:"<sli" end:"</sli" limit:"no"
rmQuotes:"y">>
</$list>

Is there a way to make the list of slices behave like the list widget in
order to create a set of buttons to trigger the slides?
Well at least this was my idea for a mechanism...I beginn to sense this
could be far more difficult than I thought...

Good Night!
Jan

Thomas Elmiger

unread,
Jan 31, 2017, 2:11:50 AM1/31/17
to TiddlyWiki
Good morning Jan,

I didn’t grasp your concept of slides yet, so I will explain mine. The most TW-like version I can imagine:
– slideshow = story(river)
–– slide = tiddler
––– slide text: place slice in tiddler

Your remote control can allready switch tiddlers, you could find/list them by tag or field as usual. (So you would not need to call slices here.)

My second and more special concept:
– slideshow = one single tiddler
–– slide = tbd (e.g. a div or a reveal widget)
––– slide text: content of a slide*

* big advantage here: the slides could be generated as a list, like our footnotes in the footer tiddler at the end of the story. Disadvantage: We would have to invent a new mechanism to control slide appearance.

What do you think? Can you explain your ideas please?

Have a nice day!
Thomas

Jan

unread,
Jan 31, 2017, 4:51:17 AM1/31/17
to tiddl...@googlegroups.com
Good morning Thomas, wonderful to find your mail.

Thinking about the mechanism I have two things in mind which in
combination will make it a little compicated.
- A possible future visualization of the slideshow with
Tiddlymap...which gives us a specific use of the storyriver.
- The possibility to create slideshows on-the-fly by creating a list o
tiddlers... which means there could be a combination of short Tiddlers
without slices and long Tiddlers with slices in this list which should
both be displayed.
(I built a tool for this in
http://slidesnstories.tiddlyspot.com/#About%20SlidesnStories )

I think your second concept will be the clue:
-In slideshow Mode the Tiddler in focus should generate the slides as a
list (if no slice is marked the tiddler Text should be used as one slide)
--It would be great if the slides were ordered by the numbers of
the slicemacro but that is a secondary question.
-After the last slide is displayed of the current Tiddler is displayed,
the next-button should navigate to the next tiddler in the list.

I hope this does not sound too complex. If you get the extract macro to
work like the list-widget the rest should be a solvable task...

Have a nice day
Jan

Thomas Elmiger

unread,
Jan 31, 2017, 2:04:19 PM1/31/17
to TiddlyWiki
Hi Jan


I have two things in mind which in
combination will make it a little compicated.
I think you are absolutely right here ;–)
 
-  The possibility to create slideshows on-the-fly by creating a list o
tiddlers... which means there could be a combination of short Tiddlers
without slices and long Tiddlers with slices
Until here, this sounds like the first concept:
– slides = tiddlers

I think your second concept will be the clue:
-In slideshow Mode...
How would this mode be activated?
 
the Tiddler in focus should generate the slides as a list
This indeed sounds like the second concept
– one tiddler contains all the slides in the form of a list
– is this a special kind of tiddler?
– I guess it would contain the list permanently (as opposed to generate in the moment it gets the focus)?
 
(if no slice is marked the tiddler Text should be used as one slide)
– this is the opposite of what extract does: the macro collects marked slices. No marks => no output.
But of course you could mark the whole text as one slice.
 
     --It would be great if the slides were ordered by the numbers of
the slicemacro but that is a secondary question.
Standard of order of extraction would be
– order of tiddlers in the list (story river in your case)
–– order of slices within tiddlers
 
-After the last slide is displayed of the current Tiddler is displayed,
the next-button should navigate to the next tiddler in the list.
– and what would happen there?
 
I hope this does not sound too complex.
Bluntly: Yes it does. But maybe it is just me … or the fact that I am not familiar with tiddlymap? I am afraid you want to put a slideshow (all slices from one tiddler) into a slideshow (all tiddlers in the story river)? Wouldn’t it be easier to collect all slices from all tiddlers in one list (concept two) istead of mixing the two concepts?

Excuse me if I am not able to see the advantage of your strategy (yet) or if I missunderstood someting!
 
If you get the extract macro to
work like the list-widget
I would recommend to use the extract macro inside the existing list widget as the footnote demo does.

Have a nice evening,
Thomas

Jan

unread,
Jan 31, 2017, 6:14:10 PM1/31/17
to tiddl...@googlegroups.com
Hi Thomas,
Thanks for your critique...
I see my concept is still quite confusing...I will try to explain
Triggering the slideshow would reveal a special view mode consisting of either of a tiddlylifemap or another fullscreen background and a set of buttons to trigger slides in a special wrapper.
These buttons could either be decent in the corner of the screen or on special panel if you have the luxury of a moderator screen.
The buttons to display slices would indeed be produced in the moment a tiddler gets into the focus. A list filter could be used to decide wheter the tiddler contains slices or not a thus display different buttons.
To build the buttons to trigger the slices it would be necessary to wrap the slice in some code...this is why I would have loved to use the extract widget like the list widget because it makes procedures like this so comfortable...but it could be sufficient to add a prefix and a suffix to perform this.
We could also think of generating temporary Tiddlers out of the slices which are deleted when navigating to the next tiddler...but I think for the use of tiddlymap to visualize the slideshow this is not as neat.
Being able to reorder the slices by numbers would give users more freedom to sort the slices in the tiddlers...I thought this would not be easy and we can well live without that.
When the last slice is displayed the next button should navigate to the next tiddler in the list and thus display the buttons for the next slides, if no tiddler is left it would unreveal the slideshow mode.

I hope all this does not sound totally crazy to you.

So good night
Yours Jan
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
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/72495b5a-6936-4b31-95db-278a9d83e15c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thomas Elmiger

unread,
Feb 1, 2017, 1:55:18 AM2/1/17
to TiddlyWiki
Hi again

Sounds not crazy at all, but ambitious for a late-night project ;–)

The part I would be interested in – in addition to your usage of slices – is how we can turn a list into a little slideshow. I have already tried to load a little script into the head of TW5 but was not able to use it: https://github.com/pawelgrzybek/siema

Maybe there are other ways or existing solutions like the reveal widget or some kind of filter logic with numbers we could use …

Good luck!
Thomas

Jan

unread,
Feb 1, 2017, 7:15:28 PM2/1/17
to tiddl...@googlegroups.com
Hi Thomas,
sorry for waiting an entire day, I just came home...
Throughtout the day I thought about the concept.
I think it would be terrific if we could use the extract macro to produce temporary tiddlers out of all slices with numbers of the next tiddler in the list when navigating to it.
It would be great if they could be named something like $:temp/Slide/(Number of the slice) and contain the slice as text and if they were created silently in the background without showing up in the storyriver. Could you do this, because you know your extractMacro so much better?
I think the logic for the "next" button (and the other buttons depending on the type of display...) can be made with list and reveal widget. I would like to do that part in the course of the next week.
All slices revealed the next button would delete all temporary tiddlers

I think this basis would be very flexible: It would work with or without a "slidemap", moderator version or small navigation elements...and also a version which uses lists insteat of slices should be possible (with the difference that  numbers would have to be generated)

I hope you like this Idea
I wish you a nice week, I'll be off till sunday

Jan

PS. Thanks for the Tip for the stickytoolbar...I saw the focus problem in Chrome on my SE as well. I hope/guess so did you. Chrome is still a little problematic with that css expression...which seems to be changing at the moment. In FF Desktop it works fine.
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
Reply all
Reply to author
Forward
0 new messages