[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Thanks Mario, much appreciated. Best wishes Jeremy On Sun, Aug 3, 2014 at 1:35 PM, PMario wrote: > An interesting one :) > > video: https://www.youtube.com/watch?v=amoSCysVyY4 > annotations: http://pmario.tiddlyspace.com/#2014-07-08-TW-hangout-53 > > Nice to see, that someone else also saw all the hangouts (several times :)) > > have fun! > mario > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
An interesting one :) video: https://www.youtube.com/watch?v=amoSCysVyY4 annotations: http://pmario.tiddlyspace.com/#2014-07-08-TW-hangout-53 Nice to see, that someone else also saw all the hangouts (several times :)) have fun! mario -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy
On Thursday, July 10, 2014 1:42:25 PM UTC+2, Jeremy Ruston wrote:
In my case, the system tags I used unnecessarily cluttered the UI with
>> meaningless tagpills. This is not usually a problem for layout tiddlers, as
>> the tagpill swarm is not visible in the UI (other than when the layout
>> tiddler is shown in the main story river.)
>>
>
> Can you explain the context a little more?
>
> System tiddlers are supposed to be generally hidden from view until one
> delves into the sidebar lists.
>
I had a number of display panel tiddlers, each panel displayed abstracts of
all tiddlers matching a filter expression (in this case, tagged with the
title of the display panel.) The display panels, however, needed to be
categorised in order that several different tagpill swarms could be
assembled for the UI (one swarm for each type.)
Using tags, this necessitated the use of a tag or system tag for each type.
These tags had little semantic meaning to the user, but showed in the tag
swarm at the top of the display panels; thus presenting an unnecessary
distraction.
I replaced the use of tags with a single system field, with a value
representing the type. The panels could easily be filtered on the value of
this field, but ordering of the pills in the tag swarms proved troublesome.
I resorted to sorting by 'modified', and creating the panel tiddlers in the
sequence I wished them to be displayed. This is not ideal, as to change the
order, they must all be re-created in the desired sequence (or the
'modified' fields of every panel must be updated by another mechanism.)
I have a workaround, but ideally, I would like to filter the panels by
field value, then sort them according to an ordered list. Ordering of the
titles would then require manipulation of this ordered list only, without
having to re-set the 'modified' field in the desired sequence.
Using fields, my requirement is to sort a list of titles generated by a
filter expression (other than by tag) by the order in which the titles
appear in another list.
<$list filter="[field:category[type1]sortbylist{!!my-ordered-list}]" ...>
-- but there might be a cleverer way of doing this.
> I think you are indeed asking for a separate tags field that you can use
> instead of using system tags in the main tags field.
>
That, I believe, sums up the requirement -- an alternative 'hidden' system
tags field, which does not display its tags in the tag swarm in the main
story river and doesn't clutter the user tag editor. This would be more
convenient than the use of a field, as all of the tools provided for the
'tags' field would become available for this field.
The problem is, that system tags still show in the tag swarms at the top of
tiddlers displayed in the main story river, and they have no semantic
meaning to the user as they are used only to arrange the UI.
Either system tags should be filtered from the tag swarm and user tag
editor, or system tags should be placed in another field entirely. I kind
of like the second option -- I think the idea of a system tags field makes
some sense. Separate system tags field, separate system tags display
(hidden from default display), separate system tags editor.
-- this might provide a more intuitive scheme for users (separates the
'clutter' of system tags from the usual UI, rendering both more
understandable)
-- enables the use of 'cleaner' tags for system purposes (no longer
restricted to $:/blah-blah)
-- reduces the number of tags in both lists (users will likely migrate a
number of tags into the system tags field)
I don't know -- what do others think?
regards
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy Appears this can't be done with a filter as your system tag names don't follow a suitable pattern -- must be excluded explicitly. Ideally, also need different images for different parts of the layout -- some parts need a button, others a filled area. regards On Thursday, July 10, 2014 1:39:24 PM UTC+2, Jeremy Ruston wrote: > > Hi Matabele > > Good idea. I think we can still do this with the present system of system >>> tags. >>> >> >> Works quite well with: >> >> <$select tiddler="layout-demo" field="tags"> >> <$list filter="[all[shadows]tags[]]"> >> >><$view field='title'/> >> >> >> >> Where 'layout-demo' contains an image. With a little tweaking this should >> prove useful to the documentation. >> > > We'd want to somehow restrict it to the tags that control layout (and not > $:/tags/stylesheet or $:/tags/Macro). > > Best wishes > > Jeremy > > >> >> >> regards >> > > > > -- > Jeremy Ruston > mailto:jeremy...@gmail.com > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
> > > The list mechanism could be used to order the tiddlers identified by their >> layout field, but I'm not sure that all of this is worth it. What's the >> advantage over using tags? >> > > In my case, the system tags I used unnecessarily cluttered the UI with > meaningless tagpills. This is not usually a problem for layout tiddlers, as > the tagpill swarm is not visible in the UI (other than when the layout > tiddler is shown in the main story river.) > Can you explain the context a little more? System tiddlers are supposed to be generally hidden from view until one delves into the sidebar lists. > In my application I set out to reserve all tags for the user, so that all > tags displayed in the main story river had semantic meaning to the user. An > alternative would be to remove system tags from the standard tagpill swarm > and tag editor, and move them into a tab in the 'info' button. > What is the situation where system tags are being applied to user tiddlers? > My original concern about a proliferation of system tags applies also if >> we use the layout field: we'd have a proliferation of possible values for >> the layout field. >> > > My idea was to reserve system tiddlers for a reduced and less confusing > list by moving the more specialised settings into a field. This, however, > introduces problems for the ordering of the standard layout. > > I think that ordering and manipulation of lists of tiddler titles other > than in the 'tags' field would be of general utility. Ideally, any field > should be capable of being used like the 'tags' field i.e. a facility for > alternative and multiple 'tags' fields. > I think you are indeed asking for a separate tags field that you can use instead of using system tags in the main tags field. I'd like to understand the motivation here a little more; system tags are supposed to be the solution to the problem you describe. Best wishes Jeremy > > regards > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Matabele Good idea. I think we can still do this with the present system of system >> tags. >> > > Works quite well with: > > <$select tiddler="layout-demo" field="tags"> > <$list filter="[all[shadows]tags[]]"> > >><$view field='title'/> > > > > Where 'layout-demo' contains an image. With a little tweaking this should > prove useful to the documentation. > We'd want to somehow restrict it to the tags that control layout (and not $:/tags/stylesheet or $:/tags/Macro). Best wishes Jeremy > > > regards > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy On Thursday, July 10, 2014 11:11:10 AM UTC+2, Jeremy Ruston wrote: > > > A Layout section in tiddlywiki.com could illustrate the various options >> for the value of this tag -- for example a select widget populated with >> valid options for the value could be tied to the 'layout' field of a >> 'test-layout' tiddler whose content is a a black and yellow chevron >> (screenshots could also be provided.) >> > > Good idea. I think we can still do this with the present system of system > tags. > Works quite well with: <$select tiddler="layout-demo" field="tags"> <$list filter="[all[shadows]tags[]]"> >><$view field='title'/> Where 'layout-demo' contains an image. With a little tweaking this should prove useful to the documentation. regards -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy On Thursday, July 10, 2014 12:23:24 PM UTC+2, Jeremy Ruston wrote: The list mechanism could be used to order the tiddlers identified by their > layout field, but I'm not sure that all of this is worth it. What's the > advantage over using tags? > In my case, the system tags I used unnecessarily cluttered the UI with meaningless tagpills. This is not usually a problem for layout tiddlers, as the tagpill swarm is not visible in the UI (other than when the layout tiddler is shown in the main story river.) In my application I set out to reserve all tags for the user, so that all tags displayed in the main story river had semantic meaning to the user. An alternative would be to remove system tags from the standard tagpill swarm and tag editor, and move them into a tab in the 'info' button. My original concern about a proliferation of system tags applies also if we > use the layout field: we'd have a proliferation of possible values for the > layout field. > My idea was to reserve system tiddlers for a reduced and less confusing list by moving the more specialised settings into a field. This, however, introduces problems for the ordering of the standard layout. I think that ordering and manipulation of lists of tiddler titles other than in the 'tags' field would be of general utility. Ideally, any field should be capable of being used like the 'tags' field i.e. a facility for alternative and multiple 'tags' fields. regards -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy On Thursday, July 10, 2014 11:12:19 AM UTC+2, Jeremy Ruston wrote: > > > But the problem as originally stated was to get tagpill dropdowns working > within a scrollable div. So we need a solution that works within scrollable > divs. > The problem also arises in the sidebar -- if a tagpill is placed to the RHS of the sidebar, the tagpill popup truncates at the RH edge of the screen. One possible solution for this problem is to float the popup to the LHS of the rather than anchoring its LH edge to the tagpill. When I tried to avoid truncation on the lower edge, I was forced to fix the height of the scrollable , which looked messy. My solution was to put the scrollable within the tagpill and so avoid placing the tagpill within a scrollable (my tagpills were on the LHS of the screen, so the popup could overlay the main story.) regards -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
> > > I made use of fields for 'system' purposes in my Q&D gTiD and have been > pondering the same issue for the listing order of tiddlers filtered on a > field value -- currently, I can do no better than sorting by 'modified'. > > Perhaps a similar mechanism can be provided for tiddlers filtered by field > using a list elsewhere. Where do I find the code whereby tiddlers are > automatically ordered by the 'list' field of the 'tag' tiddler? > It's here: https://github.com/Jermolene/TiddlyWiki5/blob/master/core%2Fmodules%2Fwiki.js#L440 The list mechanism could be used to order the tiddlers identified by their layout field, but I'm not sure that all of this is worth it. What's the advantage over using tags? My original concern about a proliferation of system tags applies also if we use the layout field: we'd have a proliferation of possible values for the layout field. Best wishes Jeremy. > > regards > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy On Thursday, July 10, 2014 11:11:10 AM UTC+2, Jeremy Ruston wrote: > > > The trouble with this approach is that we don't have a mechanism for > determining the rendering order for the tiddlers that have the layout field > value. It's that capability of tagging that makes it attractive for this > purpose. > > I made use of fields for 'system' purposes in my Q&D gTiD and have been pondering the same issue for the listing order of tiddlers filtered on a field value -- currently, I can do no better than sorting by 'modified'. Perhaps a similar mechanism can be provided for tiddlers filtered by field using a list elsewhere. Where do I find the code whereby tiddlers are automatically ordered by the 'list' field of the 'tag' tiddler? regards -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Matabele > The method that seems to work is to change the styling of the class > "tw-drop-down" used in '$:/core/ui/TagTemplate' to include a scroll > overflow -- not to apply a scrollable around the whole tagpill > template. The results for all of the other options I tried were horrible. > But the problem as originally stated was to get tagpill dropdowns working within a scrollable div. So we need a solution that works within scrollable divs. Best wishes Jeremy > > regards > > > On Wednesday, July 9, 2014 6:50:58 PM UTC+2, Jeremy Ruston wrote: > >> Hi Matabele >> >> >> >>> No, won't work this way -- after trying many other approaches, I >>> modified the code in the tagpill template and included a scrollable >>> around the list items. Tried the scrollable widget without success. The tag >>> pills on the gTiD tab use this modified template for the pills -- the >>> tagpills in the main story use the standard tagpill template. >>> >> >> The problem as originally reported was with the dropdown being clipped if >> a tagpill is within a div with overflow:scroll or overflow:hidden: >> >> https://www.youtube.com/watch?v=amoSCysVyY4#t=1947 >> >> All that the <$scrollable> widget in my example is doing is being a >> shorthand for creating a DIV with overflow:scroll. >> >> Best wishes >> >> Jeremy >> >> >> >>> >>> regards >>> >> >> >> >> -- >> Jeremy Ruston >> mailto:jeremy...@gmail.com >> > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Matabele > Another idea with respect the proliferation of system tags. Many of these > relate to inserting tiddlers as sections or tabs in the layout -- all of > these could be replaced with the use of a single 'layout' field. The value > of this field could then determine the position of a tiddler in the layout > using a filter expression such as [field:layout[ViewTemplate]] rather than > [tag[$:/tags/ViewTemplate]] for example. > The trouble with this approach is that we don't have a mechanism for determining the rendering order for the tiddlers that have the layout field value. It's that capability of tagging that makes it attractive for this purpose. > This might be clearer to users than the current system. A Layout section > in tiddlywiki.com could illustrate the various options for the value of > this tag -- for example a select widget populated with valid options for > the value could be tied to the 'layout' field of a 'test-layout' tiddler > whose content is a a black and yellow chevron (screenshots could also be > provided.) > Good idea. I think we can still do this with the present system of system tags. Best wishes Jeremy In the interim -- filter expressions could AND together both tag and > 'layout' field options -- new and obscure layout features offering only the > 'layout' field option. > > regards > > On Monday, July 7, 2014 1:46:28 PM UTC+2, Jeremy Ruston wrote: > >> TiddlyWiki Hangout #53 will be tomorrow, Tuesday 8th July at 4pm BST: >> >> https://plus.google.com/events/cb9dr8725aaajqhoha9nljekslg >> >> If you've any questions or topics for discussion, please reply here, or >> use the Q&A button on the video preview at the page above. >> >> Best wishes >> >> Jeremy >> >> >> -- >> Jeremy Ruston >> mailto:jeremy...@gmail.com >> > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi The method that seems to work is to change the styling of the class "tw-drop-down" used in '$:/core/ui/TagTemplate' to include a scroll overflow -- not to apply a scrollable around the whole tagpill template. The results for all of the other options I tried were horrible. regards On Wednesday, July 9, 2014 6:50:58 PM UTC+2, Jeremy Ruston wrote: > > Hi Matabele > > > >> No, won't work this way -- after trying many other approaches, I modified >> the code in the tagpill template and included a scrollable around the >> list items. Tried the scrollable widget without success. The tag pills on >> the gTiD tab use this modified template for the pills -- the tagpills in >> the main story use the standard tagpill template. >> > > The problem as originally reported was with the dropdown being clipped if > a tagpill is within a div with overflow:scroll or overflow:hidden: > > https://www.youtube.com/watch?v=amoSCysVyY4#t=1947 > > All that the <$scrollable> widget in my example is doing is being a > shorthand for creating a DIV with overflow:scroll. > > Best wishes > > Jeremy > > > >> >> regards >> > > > > -- > Jeremy Ruston > mailto:jeremy...@gmail.com > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Another idea with respect the proliferation of system tags. Many of these relate to inserting tiddlers as sections or tabs in the layout -- all of these could be replaced with the use of a single 'layout' field. The value of this field could then determine the position of a tiddler in the layout using a filter expression such as [field:layout[ViewTemplate]] rather than [tag[$:/tags/ViewTemplate]] for example. This might be clearer to users than the current system. A Layout section in tiddlywiki.com could illustrate the various options for the value of this tag -- for example a select widget populated with valid options for the value could be tied to the 'layout' field of a 'test-layout' tiddler whose content is a a black and yellow chevron (screenshots could also be provided.) In the interim -- filter expressions could AND together both tag and 'layout' field options -- new and obscure layout features offering only the 'layout' field option. regards On Monday, July 7, 2014 1:46:28 PM UTC+2, Jeremy Ruston wrote: > > TiddlyWiki Hangout #53 will be tomorrow, Tuesday 8th July at 4pm BST: > > https://plus.google.com/events/cb9dr8725aaajqhoha9nljekslg > > If you've any questions or topics for discussion, please reply here, or > use the Q&A button on the video preview at the page above. > > Best wishes > > Jeremy > > > -- > Jeremy Ruston > mailto:jeremy...@gmail.com > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Matabele > No, won't work this way -- after trying many other approaches, I modified > the code in the tagpill template and included a scrollable around the > list items. Tried the scrollable widget without success. The tag pills on > the gTiD tab use this modified template for the pills -- the tagpills in > the main story use the standard tagpill template. > The problem as originally reported was with the dropdown being clipped if a tagpill is within a div with overflow:scroll or overflow:hidden: https://www.youtube.com/watch?v=amoSCysVyY4#t=1947 All that the <$scrollable> widget in my example is doing is being a shorthand for creating a DIV with overflow:scroll. Best wishes Jeremy > > regards > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Jeremy
On Wednesday, July 9, 2014 6:32:02 PM UTC+2, Jeremy Ruston wrote:
>
>
> I tried creating a tiddler with the following content on
> wills.tiddlyspot.com but found that the dropdown was still clipped:
>
> <$scrollable>
>
> {{done||$:/_tagpill-template}}
>
>
>
No, won't work this way -- after trying many other approaches, I modified
the code in the tagpill template and included a scrollable around the
list items. Tried the scrollable widget without success. The tag pills on
the gTiD tab use this modified template for the pills -- the tagpills in
the main story use the standard tagpill template.
regards
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi Matabele
Finally managed to view the hangout -- many thanks for covering stacked
> widgets -- nice to know I'm not heading off down a blind alley.
>
Great, I hope you'll be able to come to a hangout soon.
>
> I have a fix for truncation of scrollable tag pills -- using css though,
> not the scrollable widget. See '$:/_tagpill-template' at:
> http://wills.tiddlyspot.com/
> -- placed a around the listitems with this css style:
>
I tried creating a tiddler with the following content on
wills.tiddlyspot.com but found that the dropdown was still clipped:
<$scrollable>
{{done||$:/_tagpill-template}}
> Would be interested in the twin story river shown toward the end -- would
> prefer separate stories that scroll independently of one another, rather
> than a twin column display of the main story river.
>
Multiple columns is on my list too.
> Appears to be a consensus that the tag editor needs attention -- also some
> useful ideas in the show and tell at the end.
>
Yes, I'd love to see some experimentation and proposals in this area,
Best wishes
Jeremy
>
> regards
>
> Hi
>>>
>>> There was discussion with respect the limitations of button widget
>>> messaging in Hangout #52. I have been investigating the idea of stacking
>>> widgets around a button widget and linking them together with widget
>>> messages -- the widgets may be found at: http://gwiz.tiddlyspot.com/
>>>
>>> The approach appears to be working out well and has several advantages:
>>> -- each widget is kept simple
>>> -- intelligent choice of defaults is, therefore, possible
>>> -- avoids unnecessary complexity in the parameters to the button widget
>>> -- resulting buttons can carry out quite complex user actions.
>>>
>>> I won't be able to join the discussion due to the poor quality of my
>>> internet connection, but would appreciate discussion with respect the
>>> concept of stacking widgets around a button; especially any foreseen
>>> limitations of this approach.
>>>
>>> I don't wish to go too far down a road that might, in the long run,
>>> prove to be wasted effort (and drag others with me who are now adopting
>>> some of these widgets.)
>>>
>>>
>>>
--
Jeremy Ruston
mailto:jeremy.rus...@gmail.com
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi
On Tuesday, July 8, 2014 4:56:05 PM UTC+2, Jeremy Ruston wrote:
>
>
> Matabele - we'll make sure to cover your concerns about widget stacking.
>
Finally managed to view the hangout -- many thanks for covering stacked
widgets -- nice to know I'm not heading off down a blind alley.
I have a fix for truncation of scrollable tag pills -- using css though,
not the scrollable widget. See '$:/_tagpill-template' at:
http://wills.tiddlyspot.com/
-- placed a around the listitems with this css style:
div.tagpill {
max-height:200px;
min-width: 280px;
border: 1px solid #99;
background-color: #FF;
padding: 7px 0 7px 0;
margin: 4px 0 0 0;
white-space: nowrap;
overflow:auto
}
Would be interested in the twin story river shown toward the end -- would
prefer separate stories that scroll independently of one another, rather
than a twin column display of the main story river.
Appears to be a consensus that the tag editor needs attention -- also some
useful ideas in the show and tell at the end.
regards
Hi
>>
>> There was discussion with respect the limitations of button widget
>> messaging in Hangout #52. I have been investigating the idea of stacking
>> widgets around a button widget and linking them together with widget
>> messages -- the widgets may be found at: http://gwiz.tiddlyspot.com/
>>
>> The approach appears to be working out well and has several advantages:
>> -- each widget is kept simple
>> -- intelligent choice of defaults is, therefore, possible
>> -- avoids unnecessary complexity in the parameters to the button widget
>> -- resulting buttons can carry out quite complex user actions.
>>
>> I won't be able to join the discussion due to the poor quality of my
>> internet connection, but would appreciate discussion with respect the
>> concept of stacking widgets around a button; especially any foreseen
>> limitations of this approach.
>>
>> I don't wish to go too far down a road that might, in the long run, prove
>> to be wasted effort (and drag others with me who are now adopting some of
>> these widgets.)
>>
>>
>>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
The hangout is about to start over at: https://plus.google.com/hangouts/_/hoaevent/AP36tYeg5OTzNYIVX5vIA70ksLxjguFKminQ6d15hWYk3GeINohWaQ Matabele - we'll make sure to cover your concerns about widget stacking. Many thanks, Jeremy On Tue, Jul 8, 2014 at 1:58 PM, Matabele wrote: > Hi > > There was discussion with respect the limitations of button widget > messaging in Hangout #52. I have been investigating the idea of stacking > widgets around a button widget and linking them together with widget > messages -- the widgets may be found at: http://gwiz.tiddlyspot.com/ > > The approach appears to be working out well and has several advantages: > -- each widget is kept simple > -- intelligent choice of defaults is, therefore, possible > -- avoids unnecessary complexity in the parameters to the button widget > -- resulting buttons can carry out quite complex user actions. > > I won't be able to join the discussion due to the poor quality of my > internet connection, but would appreciate discussion with respect the > concept of stacking widgets around a button; especially any foreseen > limitations of this approach. > > I don't wish to go too far down a road that might, in the long run, prove > to be wasted effort (and drag others with me who are now adopting some of > these widgets.) > > regards > > On Monday, July 7, 2014 1:46:28 PM UTC+2, Jeremy Ruston wrote: > >> TiddlyWiki Hangout #53 will be tomorrow, Tuesday 8th July at 4pm BST: >> >> https://plus.google.com/events/cb9dr8725aaajqhoha9nljekslg >> >> If you've any questions or topics for discussion, please reply here, or >> use the Q&A button on the video preview at the page above. >> >> Best wishes >> >> Jeremy >> >> >> -- >> Jeremy Ruston >> mailto:jeremy...@gmail.com >> > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Hi There was discussion with respect the limitations of button widget messaging in Hangout #52. I have been investigating the idea of stacking widgets around a button widget and linking them together with widget messages -- the widgets may be found at: http://gwiz.tiddlyspot.com/ The approach appears to be working out well and has several advantages: -- each widget is kept simple -- intelligent choice of defaults is, therefore, possible -- avoids unnecessary complexity in the parameters to the button widget -- resulting buttons can carry out quite complex user actions. I won't be able to join the discussion due to the poor quality of my internet connection, but would appreciate discussion with respect the concept of stacking widgets around a button; especially any foreseen limitations of this approach. I don't wish to go too far down a road that might, in the long run, prove to be wasted effort (and drag others with me who are now adopting some of these widgets.) regards On Monday, July 7, 2014 1:46:28 PM UTC+2, Jeremy Ruston wrote: > > TiddlyWiki Hangout #53 will be tomorrow, Tuesday 8th July at 4pm BST: > > https://plus.google.com/events/cb9dr8725aaajqhoha9nljekslg > > If you've any questions or topics for discussion, please reply here, or > use the Q&A button on the video preview at the page above. > > Best wishes > > Jeremy > > > -- > Jeremy Ruston > mailto:jeremy...@gmail.com > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TiddlyWiki Hangout #53 is tomorrow, Tuesday 8th July at 4pm BST
Again I will not join. Family comes first. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
