Suggestions Box ...

[@TiddlyTweeter]

There are so many great programmers here I thought it might be a useful idea to have a general "Suggestions Box" for stuff that has not been (as far as I know) been implemented they might be interested in ...

[@TiddlyTweeter]

Suggestion #1: Stylesheet Toggler

Aim: A button that cycles through different CSS stylesheets ($:/tags/Stylesheet)

Workings: Simply adds and removes the tag activating stylesheet through a cycle. Each click on the button advancing one. A Data Tiddler holds the addresses of styling Tiddlers included in the cycle.

Benefits:
1 - Lets users modify layout easily.
2 - Aids CSS design.

Best wishes
Josiah

[Thomas Elmiger]

Hi Josiah

This was simply a great idea – and relatively simple to build. I didn’t like the cycle though.
So here’s my Stylesheet Manager: http://tid.li/tw5/hacks.html#Stylesheet%20Manager

Changing the filter at the top (e.g. the search part) allows you to show only the stylesheets you want to juggle with:
 

\define myfilter()
[tag[$:/tags/Stylesheet]search[vanilla/base]sort[title]]
\end

Have fun!
Thomas

Am Dienstag, 10. Oktober 2017 11:36:29 UTC+2 schrieb @TiddlyTweeter:

Suggestion #1: Stylesheet Toggler

[...]

[Mark S.]

If you don't mind a selection drop-down and and an activate button.

Obviously potential developers need to do the volley-ball thing and call "mine" if they're doing something.

Mark

[Thomas Elmiger]

Ouch! Collision while catching the ball :–)
Ex-volley-ball-player here, Mark. But I have to admit that my VB-level was only very amateur-ish, just as my development-skills.
Cheers, Thomas

[TonyM]

I replied late last night (Sydney time) on my Mobile only to loose my post to the digital grave yard.

I wanted to say this should be generalised rather than made specific to stylesheets. It should be quite easy to use a list field and step through each named tiddler removing then applying a named tag to the next in the list. It could be used to indicate one or more positions in a list,

It would be like using the list for OR rather than AND items.

Such a solution may let us use drag to drag a tag from one tiddler to another. More like a tag in the real world.

This would be helpful since so much of TiddlyWiki is driven by tags on tiddlers.

Tony

[Mark S.]

On Tuesday, October 10, 2017 at 2:48:26 PM UTC-7, Thomas Elmiger wrote:

Ouch! Collision while catching the ball :–)
Ex-volley-ball-player here, Mark. But I have to admit that my VB-level was only very amateur-ish, just as my development-skills.
Cheers, Thomas

Mine too, though I did manage to break someone's foot ... when they landed on mine!

[Arlen Beiler]

Popups that scroll if they are longer than the window. I remember implementing this in TiddlyWiki Classic, but I'm not sure if I ever got it for TiddlyWiki Five. Also center them in the window when the screen is narrower than a certain amount. :)

--
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+unsubscribe@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/43cf2be1-d335-426c-b379-76e19d9164c5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Riz]

I would like to see an 'attributes' parameter for widgets. The parameter should point to a tiddler that holds all the attributes of that widget which will be mapped to html "as is".

For eg: <$button attributes="myatttiddler">Hello</$button>

and myatttiddler should have text like

{
"class": "myclass",
"style": "background:blue;",
"tabindex": 0
}

This has two advantages.
a) It will help to decrease repetition of these attributes for various widgets.
b) It will help to include the html properties not yet supported for that widget like "tabindex" in the above example.

Kixam already implemented this for his date picker widget. I hope this will become norm for all the widgets.

[codacoder...@outlook.com]

IMO, the UI for fields could do with some love, care and attention.  I have frequently wanted to copy/move a set of fields from one tiddler to another.  A way to do that without going through the standard UI would be very helpful.  Imagine "marking" the required fields (via checkboxes, perhaps?) then clicking a button "Copy" or "Move".  Open the target tiddler and click "paste".  The marked fields are then copied/moved into the target tiddler. Done.

[PMario]

On Wednesday, October 11, 2017 at 8:51:06 AM UTC+2, Riz wrote:

I would like to see an 'attributes' parameter for widgets. The parameter should point to a tiddler that holds all the attributes of that widget which will be mapped to html "as is".

IMO that's what macros are made for.

 

For eg: <$button attributes="myatttiddler">Hello</$button>

and myatttiddler should have text like

{
 "class": "myclass",
 "style": "background:blue;",
 "tabindex": 0
 }

IMO this can already be done with macors, without any new invention.

-m

 

[TonyM]

All,

I would like tags, who have matching tiddlers, which contain a tooltip field, to display that tooltip on hovering over a tag pill

Simple But powerful.

I have plenty of other ideas, but I do not want to scare anyone.

Tony

[TonyM]

PS

Genralise that to any link to a tiddler or tag display the tooltip field in that tiddler or tag if it has a value.

Tony

[Riz]

IMO this can already be done with macors, without any new invention.

-m

 

Can you provide an example? So far I failed to replicate the intended results. When I write <$button <<myparams>>> Hello </$button> it returns an error.

Moreover, macros are not taking care of the second part, which is support for unknown parameters. 

 For eg: I type

<$button tabindex=0>My Button</$button>

and the generated html fails to show the tabindex property. Tabindex is not yet supported as a property of button widget. Currently if we want to add it, we need to modify button.js. I was hoping the widgets like button, edit-text etc will map all unknown parameters to the generated html counterpart without modification. In the above example, it would generate 

<button tabindex="0">My Button<button>

[PMario]

On Thursday, October 12, 2017 at 10:41:37 AM UTC+2, Riz wrote:

Moreover, macros are not taking care of the second part, which is support for unknown parameters. 

 For eg: I type

<$button tabindex=0>My Button</$button>

and the generated html fails to show the tabindex property. Tabindex is not yet supported as a property of button widget. Currently if we want to add it, we need to modify button.js. I was hoping the widgets like button, edit-text etc will map all unknown parameters to the generated html counterpart without modification. In the above example, it would generate 

<button tabindex="0">My Button<button>

You are right, that's a new behaviour, which could be implemented for every widget, that creates DOM elements. ...

The only problem would be to avoid parameter names, that will be implemented into future HTML specs, which are unknown at the moment of this writing.

-m

 

[PMario]

On Thursday, October 12, 2017 at 10:41:37 AM UTC+2, Riz wrote:

IMO this can already be done with macors, without any new invention.

-m

Can you provide an example? So far I failed to replicate the intended results. When I write <$button <<myparams>>> Hello </$button> it returns an error.

 The call I had in mind looks like this:

<<myButton myParamTiddlerTitle>>

A heavily simplified macro implementatoin would be similar to - eg:

title: myButtonMacro

tag: $:/tags/Macro

\define myButton(params label:"click me")
<$button to={{$params$##to}} class={{$params$##class}}>"""$label$"""</$button>
\end


title: params
type: application/json

{
"class": "myclass",
"to": "params"
 }

call: <<myButton params>>

have fun!

mario

 

[Rizwan Ishak]

The usual way to avoid that would be to attach the "data" prefix,  say "data-myparam", right? 


I like your macro trick. However,  it adds a second step to the workflow. The idea was to make multiple varying widget calls with same parameters easy.  With macros we will have to define each widget separately before using it. Anyway,  sans such a solution,  this would have to do I guess. 

...

[@TiddlyTweeter]

This was a really interesting thread for me.

When I made the initial post I had NO idea that it would get interest about deeper (& some fundamental?) issues--maybe they should rather be addresses on Github? Though also maybe need working through a bit more first to be able to do that?

I do think there is maybe a missing "bridge" somewhere.

I'm still convinced Google Groups is sup-optimal for what we need. Though realise its harder to think through to a way ahead that would be better than I first thought.

Best wishes
Josiah