Did you find this? http://tiddlywiki.com/#MakeDataUriMacro
--
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
Hi
Some related info here:
https://groups.google.com/forum/#!searchin/tiddlywiki/link$20icons/tiddlywiki/2Ph1RGBrbIo/2nSNcUDyzx4J
On Wednesday, July 9, 2014 11:44:45 PM UTC+2, CB wrote:
I am trying to modify the bullet for some ul tags to an included image.
I have dragged and dropped an
Am Donnerstag, 10. Juli 2014 10:50:59 UTC+2 schrieb Matabele:
Hi
Some related info here:
https://groups.google.com/forum/#!searchin/tiddlywiki/link$20icons/tiddlywiki/2Ph1RGBrbIo/2nSNcUDyzx4J
Thanks! I KNEW it exists but couldn't find it.
--
You received this message because you are
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 div around the whole tagpill
template. The results for all of the other options I tried were horrible.
But
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
My overall question is how to be able to manipulate shadow tiddlers and
still have them upgrade easily. Both keeping and eating the cake, in deed.
Is the following possible:
In TWC (and maybe also TW5, I haven't explored yet) you can nest
stylesheets. I.e you simply add links to other
I made use of fields for 'system' purposes in my QD 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
Hi Mat
Is the following possible:
In TWC (and maybe also TW5, I haven't explored yet) you can nest
stylesheets. I.e you simply add links to other stylesheets inside a
stylesheet and the processing will ripple through them all in sequence.
Could this idea be applied also to shadow/system
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
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
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
On Thu, 10 Jul 2014, 9600 wrote:
On Wednesday, 9 July 2014 14:05:53 UTC+1, Chris Dent wrote:
Small scale manufacturing sounds very steampunk to me! ;)
Hah! Hoping to get a discount on a top hat festooned with brass cogs, eh?
Only if I can get a free monocle with that?
I think I'd like to
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[]]
option value=currentTiddler$view field='title'//option
/$list
/$select
Where 'layout-demo'
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
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,
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
TiddlyWiki Hangout #54 will be on Tuesday 15th July at 4pm BST:
https://plus.google.com/events/cb2ogh25af5m4u59c61nc4of1to
Please post any questions or topics for discussion here, or via the QA
button on the video preview above.
Best wishes
Jeremy
--
Jeremy Ruston
Thanks pointing out the links. But, unfortunately I am not able to get it
to work. I think I am not clear about the syntax and where to
put makedatauri part. I tried replacing url() with following and none
of them worked:
list-style-image:url($macrocall $name=makedatauri
18 matches
Mail list logo
