Re: [tw] Is there a Widget Guideline ?

2014-06-03 Thread Jeremy Ruston
Hi Andreas

Good questions, I'll try to write up some more docs and a longer reply over the 
next couple of days.

Many thanks,

Jeremy

--
Jeremy Ruston
jeremy.rus...@gmail.com


> On 3 Jun 2014, at 16:16, Andreas Hahn  wrote:
> 
> Hi,
> 
> I am more or less new to TW and I may not have a good overview or a good 
> understanding, but there is something I have been wondering about and maybe 
> your answers will help me to deepen my understanding of TW.
> 
> From what I can tell widgets are a way to enhance WikiText with the goal of 
> displaying content that it would not normally be able to display by default. 
> A good example would be the list widget. Many of these widgets also provide a 
> little bit of functionality that would otherwise not exist. Examples here are 
> the widgets that provide the typical HTML-Form elements like a button, a 
> checkbox/radiobox, textareas, etc..
> 
> But I notice that an increasing number of widgets just exist to do a purely 
> functional task which mostly does not involve rendering things or doing 
> something with the child elements of that widget. And most of these are not 
> designed to play exceptionally well together.
> 
> For example the checkbox widget works on tags, the edit widget on fields. To 
> use them for something else, you usually have to do something extra, like 
> transcluding the field or checking for tags.
> Also widgets make use of different concepts, the $mangletags widget from 
> Matabele follows his stacking mechanism where high-level functionality is 
> archieved by wrapping AROUND a source element, which propagates the target UP 
> the stack. Other widgets like the core set widgets propagate variables DOWN 
> the stack and are used to provide the necessary parameters for the high-level 
> functionality INSIDE the stack. Some use messages as parameters, others 
> solely rely on their attributes as input.
> 
> Now my question: Is there a guideline or a core concept which is meant to 
> ensure that widgets work well together ? Are widgets even supposed to work 
> together ? (How will they do this in the future ?) And finally: what was the 
> idea/purpose behind widgets when TW was created ?
> 
> I would love a short explanation of the more or less theoretical background 
> and concepts of this part of TW.
> 
> Thanks
> /Andreas
> 
> -- 
> 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.

-- 
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] Is there a Widget Guideline ?

2014-06-03 Thread Andreas Hahn

Hi,

I am more or less new to TW and I may not have a good overview or a good 
understanding, but there is something I have been wondering about and 
maybe your answers will help me to deepen my understanding of TW.


From what I can tell widgets are a way to enhance WikiText with the 
goal of displaying content that it would not normally be able to display 
by default. A good example would be the list widget. Many of these 
widgets also provide a little bit of functionality that would otherwise 
not exist. Examples here are the widgets that provide the typical 
HTML-Form elements like a button, a checkbox/radiobox, textareas, etc..


But I notice that an increasing number of widgets just exist to do a 
purely functional task which mostly does not involve rendering things or 
doing something with the child elements of that widget. And most of 
these are not designed to play exceptionally well together.


For example the checkbox widget works on tags, the edit widget on 
fields. To use them for something else, you usually have to do something 
extra, like transcluding the field or checking for tags.
Also widgets make use of different concepts, the $mangletags widget from 
Matabele follows his stacking mechanism where high-level functionality 
is archieved by wrapping AROUND a source element, which propagates the 
target UP the stack. Other widgets like the core set widgets propagate 
variables DOWN the stack and are used to provide the necessary 
parameters for the high-level functionality INSIDE the stack. Some use 
messages as parameters, others solely rely on their attributes as input.


Now my question: Is there a guideline or a core concept which is meant 
to ensure that widgets work well together ? Are widgets even supposed to 
work together ? (How will they do this in the future ?) And finally: 
what was the idea/purpose behind widgets when TW was created ?


I would love a short explanation of the more or less theoretical 
background and concepts of this part of TW.


Thanks
/Andreas

--
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.