Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Hegart Dmishiv]

Hi Mat,

That's right, I remember you showing me that trick before I even started 
with the *{{DesignWrite}}* course. It might well be time I went back to 
doing it that way. Thanks for reminding me!

Hegart. 

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/19e38308-3e52-47de-9a69-edfdea098c8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Matabele's Transparent overlay palette

[Pau Deluca]

Hi Matabele! I know! It was so freaking evident when Evolena said it, I 
felt ashamed.

Now I (almost) got it. Thanks, pal.

P.-)


El miércoles, 6 de abril de 2016, 7:26:14 (UTC+2), Matabele escribió:
>
> Hi Pau
>
> I used alpha values in rgba() color codes -- the last value corresponds to 
> the transparency (1=opaque, 0=invisible.) First convert your hex code to 
> rgb() -- then add an alpha value to get the rgba() code.
>
> Here are a couple of useful links:
> http://www.colorizer.org/
> http://www.css3.info/introduction-opacity-rgba/
>
> Hope this helps.
>
> regards
>
>
>
>
>
>
> On Tuesday, 5 April 2016 09:16:02 UTC+2, Pau Deluca wrote:
>>
>> Hi there! It's been a lng time!
>>
>> I've been searching around for some inspiration, when I fell on 
>> Matabele's wiki and discovered that playing with transparences in TW5 was 
>> possible.
>>
>> Trying to understand how that was done, I see that the trick is done not 
>> in the styles, as I first thought, but in the palette.
>>
>> http://gwiz.tiddlyspot.com/#%24%3A%2FControlPanel:%24%3A%2FControlPanel
>>
>> Indeed, the only thing I needed to get the transparent effects in a fresh 
>> empty TW was importing the palette $$:/palettes/Universe 
>>  and changing 
>> to this one in the PanelControl/Appearence/palette.
>>
>> However, I'm not able to understand how should I do to adjust the opacity 
>> of the overlay, nor how this effect is accomplished only by the palette. 
>>
>> I cannot find Matabele's contact info anywhere, to directly ask. Does 
>> anyone know either how the palette generates the transparencies, or 
>> Matabele's contact details?
>>
>> Thank you very much in advance.
>>
>> P.-)
>>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e7393346-5b37-419b-a9e3-3c13da2c4ed9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Preferential Caption/Title from list

[Eric Shulman]

On Thursday, April 7, 2016 at 1:35:17 PM UTC-7, Andrew wrote:
>
> Is there a way to do:
> <$view field='caption'><$view field='title'/>
> using some kind of modifed version of
> {{{ [list[$:/TiddlerNameWithListField]] }}}
> ???
> The transclusion lists all the titles that are in the list field but what 
> I want is IF the title listed has a caption, show the caption instead of 
> the title but still have the final output sorted.
>

To get custom output from a filter, use the $list widget.  Something like 
this:

<$list filter="[list[$:/TiddlerNameWithListField]]">
   <$view field='caption'><$view field='title'/>


enjoy,
-e

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/07cade0f-a1ae-40a4-a877-dbd552310f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Preferential Caption/Title from list

[andrew harrison]

Is there a way to do:
<$view field='caption'><$view field='title'/>
using some kind of modifed version of
{{{ [list[$:/TiddlerNameWithListField]] }}}
???
The transclusion lists all the titles that are in the list field but what I
want is IF the title listed has a caption, show the caption instead of the
title but still have the final output sorted.

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAL0r7zv%2B3UJ8ea2%2B1jhH9_CNH6MjJa%3DK7pUiZGhHkeOA9JrrQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [tw5] Evolving from private thoughts to public posts

[Mat]

Lyn,

Yes, I do something similar to what you describe with TWaddle 
. Basically, I use another tiddlyspot where 
I put the drafts ("the thoughts") and occasionally, I transfer that whole 
TW to TWaddle. Unfortunately the process for transferring is less than 
optimal which is a reason why I rarely publish anything these days.

The ideal would be like this: I'd use the admin tiddlyspot, like a regular 
tiddlyspot i.e click save to upload like usual. When I have articles ready 
for publication, these are tagged or befielded with a "Publish". Then I'd 
ideally simply choose another "publish to TWaddle" saving button.

(Ok, the *absolutely ideal *would be if one could publish only single 
tiddlers that merged into the existing TWaddle, but that's... well, another 
story).

So, anyway, the above is not possible so the actual workflow is instead 
like this:

In my admin tiddlyspot, I do and save and do stuff like usual. When I 
eventually feel like publishing, I use a special saving filter kindly 
provided by Jeremy, here 
. 
This  filters out tiddlers, i.e I must keep unfinished tiddlers marked 
(tagged Unfinished). (Again, it would be nicer if I could tag what should 
be published rather than not-published... but this would mean I must also 
somehow include all surrounding non-article tiddlers.)

Now, I've put a separate button in the sidebar for saving with this filter;

<$button> 
<$action-sendmessage $message="tm-download-file" 
$param="$:/_TWaddle/PublishFilter" filename="twaddletopublish.html"/>
Publish



Unfortunately, this doesn't save the filtered file to TWaddle but instead 
downloads it. And I must then go into this downloaded file and enter 
password etc for TWaddle and upload (now from my disc).

It works but it has turned out to hampered the joy of actually publishing 
stuff.


<:-)

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e531296c-145d-4831-9ee2-ddd4b2065981%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Incorporating Exhibit/JSON within Tiddlywiki

[Mat]

I can't answer your question, but it sounds interesting so I just want to 
make sure I understand; Are you asking to use the JSON file as a database 
and have TW (i.e TW5) load and display this data? And without intermediary 
conversions? And to have the data be presented as actual wikitext, i.e with 
links to other tiddlers etc?

And, btw, is the JSON file and the TW file to be stored on the same server?

<:-)

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/aa49d03f-1d1d-4971-87fb-fa8ab56f4f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Incorporating Exhibit/JSON within Tiddlywiki

[Alex Hough]

Hi Vikas,

You can export a tiddler or set of tiddlers to JSON.

The screenshot below show how you'd do it with a filter
[image: Inline images 1]
I have played around with Zotero, the reference manager. It exports a
flavour of JSON designed for bibliographic data, CSL [1]


You can import JSON into TiddlyWiki [2]

I don't know if this helps.

I am interested in TW as a research tool. To me it seems like a natural
development from a note taking application, organised note taking is
research right?

At the moment there seems to be no way to get bibliographic data into TW in
an automated way from Google Schoolar or in a way similar to Zotero or
Mendeley etc.

My hunch is that we are "nearly there": TiddlyClip seems to be attracting
some serious attention. Search this group and you will find an attempt at
clipping complex data and converting it into tiddlers with multiple fields.



best wishes

Alex

[1]
https://github.com/citation-style-language/schema/blob/master/csl-data.json
[2] http://tiddlywiki.com/#JSONTiddlers:JSONTiddlers%20DropzoneWidget

On 7 April 2016 at 18:31, Vikas Singh  wrote:

> Hi everyone,
>
> Is there a way to get Tiddlywiki to use a JSON file to show a list of
> publications such as the one here
> http://people.csail.mit.edu/karger/papers.html
>
> within a publications tiddler? I am redoing my Tiddlywiki based
> homepage first designed in the early/mid 2000s using the newer version
> and would like to have the capability of dynamically loading content
> from a JSON file.
>
> thank you!
>
> --
> 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 https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/CAMBuDxgzTX0aEbfwabxZT1B%2BJ3NVxuQQwA3RMvSVx1O2ni%2B4wA%40mail.gmail.com
> .
> 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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CALc1hYfo5OAGEdabsMmRXWCbWd5ETo_zM%2Bmni8MUQ8W_jrnBiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Mat]

> If it's any use to anyone, I'm currently storing two collections of 
> tiddlers externally to my wiki as JSON files, and I just pull them in when 
> I need them. The tiddlers contained within each are all tagged, so I can 
> quickly purge them again by filtering for that tag. This has been very 
> useful for me as I'm generating my tiddlers in a Google Sheet, and 
> exporting them as CSV, then converting the CSV to JSON 
> . Whenever I've created a new 
> batch of data in my spreadsheet, I just go through the steps and, voilà! I 
> have a whole new set of tiddlers in my TiddlyWiki.
>

Hegart - (or anyone interested) - if I didn't refer to it already, here's a 
probably quicker and easier method than what you're describing to go from 
google sheets to tiddlers:

http://twaddle.tiddlyspot.com/#Import%20data%20using%20Google%20Sheets

<:-) 

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3a5d52cb-abc1-4498-a6cd-e6473dbc32b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Filter tiddlers by date: today and in the past

[Arkady Grudzinsky]

On Wednesday, April 6, 2016 at 1:54:00 AM UTC-7, Rustem wrote:
>
> Examples (after the patch) 
>
> today:
> <>
>
> ​
>

Does this include the dates in the past as well?  My problem with your code 
was that if used with an argument, the filter returned an open-ended 
interval, but when the argument was 0, it returned strictly the same-day 
dates.  No past or future dates were included.  I had to set my due dates a 
day in the future or a day in the past to circumvent this issue and ended 
up stripping down your code to get my simple filter.

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/28b70880-ba3e-45c3-853b-ddd8b7347e5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Filter tiddlers by date: today and in the past

[Arkady Grudzinsky]

On Wednesday, April 6, 2016 at 1:54:00 AM UTC-7, Rustem wrote:
>
> *Note:* TiddlyWiki always uses UTC . 
> If you are populating your date field by hand, keep that in mind. Although 
> the exact time does not matter, since days operates with whole days, it’s 
> important to know what hour your midnight falls on in UTC. Say, you put 
> “20160410” in your date field. That’s Apr 10 00:00 UTC. If you are in 
> Pacific time zone, that’s actually Apr 9 5:00 PM. If you want your date to 
> be Apr 10, you need to enter a time between “201604100700” and 
> “201604110659”.
>
Want to share this excellent plugin to set date fields 
http://kixam.github.io/TW5-datePicker/

The author has fixed the UTC problem at my request and added the ability to 
set the time as well.  Using this plug-in, you can set the local date and 
time, and it will set the field of your choice to UTC corresponding to your 
input.

Also, if you need a simple filter that would return "TRUE" for a date field 
in the past and "FALSE" for the date fields in the future (including the 
time), you can use the code below.  This is a stripped-down days.js, but 
without any arguments - just comparison to Date().


/*\
  title: $:/core/modules/filters/passed.js
  type: application/javascript
  module-type: filteroperator


  Filter operator that selects tiddlers with a specified date field in the 
past.


  \*/
(function(){


/*jslint node: true, browser: true */
/*global $tw: false */
"use strict";


/*
  Export our filter function
*/
exports.passed = function(source,operator,options) {
 var results = [],
 fieldName = operator.suffix || "modified",
 isInThePast = function(dateField) {
 return new Date(dateField) < new Date();
 };


 if(operator.prefix === "!") {
 source(function(tiddler,title) {
 if(tiddler && tiddler.fields[fieldName]) {
 if(!isInThePast($tw.utils.parseDate(tiddler.fields[fieldName]))) {
 results.push(title);
 }
 }
 });
 } else {
 source(function(tiddler,title) {
 if(tiddler && tiddler.fields[fieldName]) {
 if(isInThePast($tw.utils.parseDate(tiddler.fields[fieldName]))) {
 results.push(title);
 }
 }
 });
 }
 return results;
};


})();

​
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e5bb461d-6617-47ef-8ede-95bf159d07ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Incorporating Exhibit/JSON within Tiddlywiki

[Vikas Singh]

Hi everyone,

Is there a way to get Tiddlywiki to use a JSON file to show a list of
publications such as the one here
http://people.csail.mit.edu/karger/papers.html

within a publications tiddler? I am redoing my Tiddlywiki based
homepage first designed in the early/mid 2000s using the newer version
and would like to have the capability of dynamically loading content
from a JSON file.

thank you!

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAMBuDxgzTX0aEbfwabxZT1B%2BJ3NVxuQQwA3RMvSVx1O2ni%2B4wA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Combobox

[Eric Shulman]

On Thursday, April 7, 2016 at 8:18:59 AM UTC-7, Hegart Dmishiv wrote:
>
> I'm making a start on that idea of cascading the selection from one 
> *<>* into the filter for the options of another. However, in 
> the second example on this experiment tiddler 
> ,
>  
> I'm stuck with a bit of a problem. Despite having specified field:"city" 
> as the field from which the *option value* should be stored, it still 
> seems to be storing the *title* of the selected option, rather than the 
> *city*. The *option labels* are being populated properly, using your 
> example above of template:"{{!!city}}", but the *option values* aren't 
> respecting the field: parameter.
>

The built-in (hardcoded) combobox list "click" handler performs this action:
<$action-setfield $tiddler="""$tiddler$""" $field="""$field$""" 
$index="""$index$""" $value=<>/>
i.e., when you click a list item, it sets the target field (or index) to 
the <> value (which is the title of the selected tiddler).

To set a different value when an item is clicked, you can specify a custom 
"clickaction" param in the macro call so that after the current title value 
is set, you can overwrite it with the value from the desired field instead.

First, to avoid nested use of """, define the click action as a separate 
macro:

\define myaction() 
<$action-setfield $tiddler="""$tiddler$""" $field="""$field$""" 
$index="""$index$""" $value={{!!fieldname}}/>
\end

Note that this macro is performing the same handling as the built-in click 
handler, but sets the value from a specified field, rather than using 
<>.

Then, to use this "action macro", add this param to your combobox macro 
call:
clickaction:"""<>"""

Note the use of the tripled-quotes so that the call to <> is NOT 
parsed, but is simply passed as literal text that is inserted into the 
combobox code and only invoked when an item is actually clicked upon.

let me know how is goes...

enjoy,
-e

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/02f3cb5b-9b6a-4cf2-a59d-42c62101d10d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Hegart Dmishiv]

Hi,

If it's any use to anyone, I'm currently storing two collections of 
tiddlers externally to my wiki as JSON files, and I just pull them in when 
I need them. The tiddlers contained within each are all tagged, so I can 
quickly purge them again by filtering for that tag. This has been very 
useful for me as I'm generating my tiddlers in a Google Sheet, and 
exporting them as CSV, then converting the CSV for JSON. Whenever I've 
created a new batch of data in my spreadsheet, I just go through the steps 
and, voilà! I have a whole new set of tiddlers in my TiddlyWiki.

Hope that is useful somehow,

Hegart.

On Friday, 8 April 2016 03:24:30 UTC+12, Tristan Kohl wrote:
>
> Hi Alex,
>
> I just asked because I was curious, there is no workflow in my head 
> regarding JSON. I was just wondering why Jeremy chose the HTML approach 
> over JSON as I myself use JSON for transfer (and sometimes storage) like 
> many other people.
>
> Anyways thanks for your hint, I will think about a usecase with JSON ;)
>
> Cheers
> Tristan
>
> Am Donnerstag, 7. April 2016 13:21:47 UTC+2 schrieb AlexHough:
>>
>> Tristan,
>>
>> You can export tiddlers to the JSON format.
>>
>> This could open up a workflow where the JSON could be used by a framework 
>> of your choice to deliver a static website
>>
>> best wishes
>>
>> Alex
>>
>> On 7 April 2016 at 11:26, Tristan Kohl  wrote:
>>
>>> Hi Jeremy,
>>>
>>> thank you for your explanation, this helped me a lot. I also figured it 
>>> could correlate with TWC but thought there might be some performance 
>>> reasons for choosing the HTML method over JSON.
>>> I will keep digging into TiddlyWiki and look forward to learn more about 
>>> JavaScript so one day I can do something with my knowlege :)
>>>
>>> Cheers
>>> Tristan
>>>
>>> Am Mittwoch, 6. April 2016 15:49:27 UTC+2 schrieb Jeremy Ruston:

 Hi Tristan

 I got a little deeper look into TiddlyWiki and came to wonder why the 
 storage of Tiddlers is implemented the way it is. As I understand it every 
 Tiddler is a single  which are all stored in the "Tiddler Area". But 
 since every Tiddler is a object with its own properties ("created", 
 "author", etc.), wouldn't it be a logic decision to keep them as 
 JavaScript 
 objects and store everything as a big JSON string in the storage area so 
 we 
 do not need to parse it back again?


 The serialisation format of tiddlers with the standalone HTML file is 
 indeed as a bunch of DIVs with custom attributes. The origin of the format 
 was TiddlyWiki Classic back in 2004 (before JSON was discovered). 
 Technically, it would be quite easy to change the format to something 
 else, 
 but in general we don’t see sufficient payback to make it worth the 
 effort, 
 and the inevitable backwards compatibility problems it would cause.

 Having said that, using HTML as the basis for the serialisation format 
 does provide some interoperability with HTML/XML tooling, which is also 
 sometimes useful.

 Best wishes

 Jeremy


 My only clue is that there are some performance thoughts which I (with 
 my limited JavaScript skills) do not get. Any hint or link would be very 
 much appreciated.


 Thanks guys
 Tristan

 -- 
 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/03eeba93-0901-489e-a3cc-803559418c91%40googlegroups.com
  
 
 .
 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+...@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/4d533999-f203-49fd-8cb1-661d76795dfd%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> 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 rece

Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Tristan Kohl]

Hi Alex,

I just asked because I was curious, there is no workflow in my head 
regarding JSON. I was just wondering why Jeremy chose the HTML approach 
over JSON as I myself use JSON for transfer (and sometimes storage) like 
many other people.

Anyways thanks for your hint, I will think about a usecase with JSON ;)

Cheers
Tristan

Am Donnerstag, 7. April 2016 13:21:47 UTC+2 schrieb AlexHough:
>
> Tristan,
>
> You can export tiddlers to the JSON format.
>
> This could open up a workflow where the JSON could be used by a framework 
> of your choice to deliver a static website
>
> best wishes
>
> Alex
>
> On 7 April 2016 at 11:26, Tristan Kohl > 
> wrote:
>
>> Hi Jeremy,
>>
>> thank you for your explanation, this helped me a lot. I also figured it 
>> could correlate with TWC but thought there might be some performance 
>> reasons for choosing the HTML method over JSON.
>> I will keep digging into TiddlyWiki and look forward to learn more about 
>> JavaScript so one day I can do something with my knowlege :)
>>
>> Cheers
>> Tristan
>>
>> Am Mittwoch, 6. April 2016 15:49:27 UTC+2 schrieb Jeremy Ruston:
>>>
>>> Hi Tristan
>>>
>>> I got a little deeper look into TiddlyWiki and came to wonder why the 
>>> storage of Tiddlers is implemented the way it is. As I understand it every 
>>> Tiddler is a single  which are all stored in the "Tiddler Area". But 
>>> since every Tiddler is a object with its own properties ("created", 
>>> "author", etc.), wouldn't it be a logic decision to keep them as JavaScript 
>>> objects and store everything as a big JSON string in the storage area so we 
>>> do not need to parse it back again?
>>>
>>>
>>> The serialisation format of tiddlers with the standalone HTML file is 
>>> indeed as a bunch of DIVs with custom attributes. The origin of the format 
>>> was TiddlyWiki Classic back in 2004 (before JSON was discovered). 
>>> Technically, it would be quite easy to change the format to something else, 
>>> but in general we don’t see sufficient payback to make it worth the effort, 
>>> and the inevitable backwards compatibility problems it would cause.
>>>
>>> Having said that, using HTML as the basis for the serialisation format 
>>> does provide some interoperability with HTML/XML tooling, which is also 
>>> sometimes useful.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>> My only clue is that there are some performance thoughts which I (with 
>>> my limited JavaScript skills) do not get. Any hint or link would be very 
>>> much appreciated.
>>>
>>>
>>> Thanks guys
>>> Tristan
>>>
>>> -- 
>>> 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/03eeba93-0901-489e-a3cc-803559418c91%40googlegroups.com
>>>  
>>> 
>>> .
>>> 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+...@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/4d533999-f203-49fd-8cb1-661d76795dfd%40googlegroups.com
>>  
>> 
>> .
>>
>> 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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b3e53a52-a9ee-43c0-a041-aa6b30f62a5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Combobox

[Hegart Dmishiv]

Hi Eric,

I'm making a start on that idea of cascading the selection from one 
*<>* into the filter for the options of another. However, in the 
second example on this experiment tiddler 
,
 
I'm stuck with a bit of a problem. Despite having specified field:"city" as 
the field from which the *option value* should be stored, it still seems to 
be storing the title of the selected option, rather than the city. The *option 
labels* are being populated properly, using your example above of 
template:"{{!!city}}", but the *option values* aren't respecting the field: 
parameter.

Thanks in advance,

Hegart.


On Thursday, 7 April 2016 19:34:41 UTC+12, Eric Shulman wrote:
>
> On Wednesday, April 6, 2016 at 11:48:43 PM UTC-7, Hegart Dmishiv wrote:
>>
>> We've run into a little snag with the *goaction* parameter. We can't 
>> seem to get it to work, neither in your example in the documentation 
>> ,
>>  
>> nor in our own experimental tiddler 
>> .
>>  
>> Any idea what's going on? This is something we'd really like to use, for 
>> all sorts of purposes in our TiddlyCRM project.
>>
>
> If you specify field:"text" in the macro call, it works.
>
> Originally, the macro had a default field name of "text" automatically 
> assigned as a fallback.  However, this prevented the underlying $edit-text 
> widget from being able to handle set of values in data tiddlers (using 
> index:"..."), because the field:"..." param takes precedence if not left 
> blank.
>
> Note: the documentation was also incorrect in using the "list" param, 
> which was renamed "filter" (but you apparently found that on your own, 
> since your experiment is correctly using filter:"..."
>
> Also... although you correctly used the "okaction" param in your 
> experiment, in your posting here, you called it "goaction".  I just want to 
> make sure others reading this don't get confused by the mistaken param name 
> in the message.  Also note that, separate from the "okaction" is an 
> optional (and currently undocumented) "clickaction" param, which allows you 
> to extend the default action that occurs when you click an item in the list 
> (i.e., in addition to setting the clicked item value into the edit-text 
> field, you can have other "side-effect" actions performed when the item is 
> clicked).
>
> enjoy,
> -e
>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f6f47721-96c1-4550-a475-8dc10f0cdadb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Tag "alias" in connection with a navigating TOC

[RichardWilliamSmith]

Hi The Bo,

If you overwrite the core tiddler $:/core/ui/DefaultSearchResultList, you 
can add a section to make it search the caption field too.

\define searchResultList()
> //{{$:/language/Search/Matches/Title}}//
> <$list 
> filter="[!is[system]search:title{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/core/ui/ListItemTemplate"/>
> //Caption Matches//
> <$list 
> filter="[!is[system]search:caption{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/core/ui/ListItemTemplate"/>
> //{{$:/language/Search/Matches/All}}//
> <$list 
> filter="[!is[system]search{$(searchTiddler)$}sort[title]limit[250]]" 
> template="$:/core/ui/ListItemTemplate"/>
> \end
> <>


This is quite hacky - you'd need to re-do it each time you upgrade to a new 
version - but I'm not sure what the preferred way to over-ride the UI 
actually is.

Regards.
Richard

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/49c47e35-9256-468c-a29d-945a477091f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: A View Mode Editor and a simple Calcualtor

[Hegart Dmishiv]

Hi *c pa* and *Vincent*,

Thanks for the replies, both of you. I've got two ideas from all of this, 
and I'd like to run them both by you all, to see which one you think is 
better.

*Option A*

We could copy all the fields from the current tiddler (in our example, it 
would be a specific Person, for instance) and copy them to a temporary 
system tiddler. We then *delete the current tiddler*, so that we don't end 
up with an orphan if the user edits the tiddler title (thereby effectively 
creating a new tiddler). Then we copy the values in the fields from the 
temporary system tiddler into our "Edit Person" tiddler using *<$vars>* 
variables, to basically back up the current state of the Person, in the 
event that the user decides to cancel editing half-way through. The tiddler 
we deleted can then be re-created from the backed-up values. This "Edit 
Person" tiddler contains the *<$edit-text>* widgets and other controls we 
need, and they're linked back to the fields in the same temporary system 
tiddler. When the user is satisfied with their edits, we just create a new 
tiddler based on those fields, exactly as we did from our "Add Person" 
tiddler when the old (now deleted) tiddler was created originally.

*Option B*

Similar to Option A above, except we don't need to delete the existing 
tiddler, because we don't give the user any opportunity to edit the title 
of the tiddler at all. Where currently our tiddler titles are created from 
a combination of the Person's first and last names, we would replace this 
instead with a GUID at creation time, so *all Person tiddlers would have a 
GUID for their tiddler title*. The first and last name fields can then be 
edited freely without it affecting the title of the tiddler, and no orphan 
is produced. We plan to hide the tiddler title and tags anyway, so the 
nasty GUIDs should never be seen by the end-user.

What do you think? Which is the better plan of attack here?

Hegart.

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/685f31fe-e610-42db-9c92-4a99013cbdb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Alex Hough]

Tristan,

You can export tiddlers to the JSON format.

This could open up a workflow where the JSON could be used by a framework
of your choice to deliver a static website

best wishes

Alex

On 7 April 2016 at 11:26, Tristan Kohl  wrote:

> Hi Jeremy,
>
> thank you for your explanation, this helped me a lot. I also figured it
> could correlate with TWC but thought there might be some performance
> reasons for choosing the HTML method over JSON.
> I will keep digging into TiddlyWiki and look forward to learn more about
> JavaScript so one day I can do something with my knowlege :)
>
> Cheers
> Tristan
>
> Am Mittwoch, 6. April 2016 15:49:27 UTC+2 schrieb Jeremy Ruston:
>>
>> Hi Tristan
>>
>> I got a little deeper look into TiddlyWiki and came to wonder why the
>> storage of Tiddlers is implemented the way it is. As I understand it every
>> Tiddler is a single  which are all stored in the "Tiddler Area". But
>> since every Tiddler is a object with its own properties ("created",
>> "author", etc.), wouldn't it be a logic decision to keep them as JavaScript
>> objects and store everything as a big JSON string in the storage area so we
>> do not need to parse it back again?
>>
>>
>> The serialisation format of tiddlers with the standalone HTML file is
>> indeed as a bunch of DIVs with custom attributes. The origin of the format
>> was TiddlyWiki Classic back in 2004 (before JSON was discovered).
>> Technically, it would be quite easy to change the format to something else,
>> but in general we don’t see sufficient payback to make it worth the effort,
>> and the inevitable backwards compatibility problems it would cause.
>>
>> Having said that, using HTML as the basis for the serialisation format
>> does provide some interoperability with HTML/XML tooling, which is also
>> sometimes useful.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> My only clue is that there are some performance thoughts which I (with my
>> limited JavaScript skills) do not get. Any hint or link would be very much
>> appreciated.
>>
>>
>> Thanks guys
>> Tristan
>>
>> --
>> 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/03eeba93-0901-489e-a3cc-803559418c91%40googlegroups.com
>> 
>> .
>> 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 https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/4d533999-f203-49fd-8cb1-661d76795dfd%40googlegroups.com
> 
> .
>
> 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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CALc1hYd0v04WMt4q%3DYWLLU7rqsm9uyP%2BdP1m2grK_42M-OOR4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5][Offtopic] Why not JSON for storage?

[Tristan Kohl]

Hi Jeremy,

thank you for your explanation, this helped me a lot. I also figured it 
could correlate with TWC but thought there might be some performance 
reasons for choosing the HTML method over JSON.
I will keep digging into TiddlyWiki and look forward to learn more about 
JavaScript so one day I can do something with my knowlege :)

Cheers
Tristan

Am Mittwoch, 6. April 2016 15:49:27 UTC+2 schrieb Jeremy Ruston:
>
> Hi Tristan
>
> I got a little deeper look into TiddlyWiki and came to wonder why the 
> storage of Tiddlers is implemented the way it is. As I understand it every 
> Tiddler is a single  which are all stored in the "Tiddler Area". But 
> since every Tiddler is a object with its own properties ("created", 
> "author", etc.), wouldn't it be a logic decision to keep them as JavaScript 
> objects and store everything as a big JSON string in the storage area so we 
> do not need to parse it back again?
>
>
> The serialisation format of tiddlers with the standalone HTML file is 
> indeed as a bunch of DIVs with custom attributes. The origin of the format 
> was TiddlyWiki Classic back in 2004 (before JSON was discovered). 
> Technically, it would be quite easy to change the format to something else, 
> but in general we don’t see sufficient payback to make it worth the effort, 
> and the inevitable backwards compatibility problems it would cause.
>
> Having said that, using HTML as the basis for the serialisation format 
> does provide some interoperability with HTML/XML tooling, which is also 
> sometimes useful.
>
> Best wishes
>
> Jeremy
>
>
> My only clue is that there are some performance thoughts which I (with my 
> limited JavaScript skills) do not get. Any hint or link would be very much 
> appreciated.
>
>
> Thanks guys
> Tristan
>
> -- 
> 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/03eeba93-0901-489e-a3cc-803559418c91%40googlegroups.com
>  
> 
> .
> 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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4d533999-f203-49fd-8cb1-661d76795dfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Feedback for TiddlyClip

[BJ]

It maybe useful to have keyboard short cuts if you have a small number of 
entries in your tiddlyclipconfig, however they would have to fit in with 
all the other keyboard shortcuts from other pages/addons. I will have a 
look to see if it is possible, but this is a low priority issue for me (I 
have too many entries in my tiddlyclipconfigs for shortcuts!!).

bj

On Monday, March 28, 2016 at 10:39:39 PM UTC+1, Julio Cantarero wrote:
>
> Hi BJ,
>
> Related to the last request, I just thought that another enhancement to 
> TiddlyClip would be to have direct access keys for the TiddlyClip entries 
> in the Context menu (I mean the right-click menu in FireFox). This could 
> speed up TiddlyClip operations when the user wants to record small text 
> chunks in the tiddler fields.
> Not sure if this is feasible. I was playing with a FireFox Addon (named 
> "Menu Wizard") that allows you to set these direct access keys per menu 
> entry, but it was only possible to do so in the first context menu level of 
> TiddlyClip, maybe because the others entries are created dynamically.
> In any case, it is just an idea, it is still very cool to be passing info 
> to TW with one click of the mouse.
> Thanks,
>
> Julio
>
> El sábado, 26 de marzo de 2016, 14:58:02 (UTC+1), Mark S. escribió:
>>
>> Hi BJ,
>>
>> Thanks for writing such a useful utility!
>>
>> I'm late to this conversation, but I wanted to add my thought.
>>
>> The main reason I don't use TC more is the docking. Having to check on 
>> docking, dock, and then do the clipping is only slightly faster than cut & 
>> paste. So it's mostly useful if I'm starting a session where I will be 
>> doing lots of clipping.
>>
>> Is there any way, maybe with cookies, that TC can remember where it is 
>> docked between browser shut-downs? I almost always dock to the same TW. I 
>> guess you could call it "Lock the Dock" ;)
>>
>> Thanks!
>> Mark
>>
>>
>>
>> On Tuesday, January 26, 2016 at 7:19:16 AM UTC-8, BJ wrote:
>>>
>>> Hi all,
>>> I am working on necessary changes to tiddlyclip in order support future 
>>> versions of firefox. As I am current focused on tiddlyclip, this would be a 
>>> good time to let me know of anything that you think could be improved or 
>>> added to tiddlyclip or its documentation, or maybe you have a particular 
>>> use or setup to share that could be added to tiddlyclip's website?
>>>
>>> all the best
>>>
>>> BJ
>>>
>>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9993d421-9b99-437b-954f-5aa8cb8019d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Tag "alias" in connection with a navigating TOC

[The Bo]

Hey Eric,

my first idea was, this works perfect for me. 
But now I see that if I search for "personal management" I will get no hit. 
Even if I search for "01" I won't see the caption.

Regards
The Bo

Am Mittwoch, 6. April 2016 14:54:18 UTC+2 schrieb Eric Shulman:
>
> On Wednesday, April 6, 2016 at 5:32:44 AM UTC-7, The Bo wrote:
>>
>> in this case I would miss the titles of open tiddlers.
>>
>
> You could tweak the $:/core/ui/ViewTemplate/title and replace
> <$view field="title"/>
> with
> <>
> so that the caption text is also displayed at the top of the open tiddler.
>
> -e
>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/039b6fb6-2a1c-4225-acca-9e3381ac8c8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Tip: Alternative to Tiddlydesktop for an independent alt-tab tiddlywiki

[Jeremy Ruston]

Hi Taylor

Good stuff, thank you for sharing. Would you be interested in preparing a pull 
request on GitHub to add it to the tw.com documentation?

Many thanks,

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
http://jermolene.com

> On 7 Apr 2016, at 03:23, Taylor Worthington  
> wrote:
> 
> I apologize if somebody else has already offered this solution.
> 
> This solution involves setting up what is called a Firefox profile in order 
> to create an independent tiddlywiki "app"-like usage.
> 
> Disadvantages I can think of compared to tiddlydesktop are:
> no convenient tiddler selection
> still requires the tiddlyfox extension
> Mozilla might soon be phasing out extensions of this kind
> Potential memory overkill compared to tiddlydesktop
> Advantages compared to tiddlydesktop
> Firefox is easy to install on all platforms. It is part of the basic repos in 
> prettymuch any Linux distribution.
> All standard browser keystrokes and features (like tabbing) are still 
> available.
> All settings of Firefox for tiddlywiki can be independently set one way or 
> another, such as "Offline Mode", without effecting other Firefox instances 
> with normal browser settings.
> Still maintains a simple, minimalist experience. Appears to simply open and 
> run tiddlywiki, similar to tiddlydesktop.
> Steps for Linux:
> Install Firefox
> Open the Firefox profile creator in terminal
> firefox -P
> Create a profile name of your liking such as "tiddlywiki"
> Install plugins:
> Tiddlyfox
> Toolbar Autohide
> Set all Firefox settings to your liking
> Homepage to your tiddlywiki file
> the "Open File" button
> Toolbar Autohide plugin settings
> Offline mode
> Zoom
> Homepage
> Create a Linux desktop launcher that will launch your tiddly app with all of 
> its settings separately from other Firefox instances.
> firefox -P tiddlywiki --no-remote //.htm
> -- 
> 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 https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/53ca8ef2-18bc-477b-a239-9191674324b1%40googlegroups.com.
> 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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/C8AE2EA7-BAFD-482B-B299-7CC9DC952C79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tip: Alternative to Tiddlydesktop for an independent alt-tab tiddlywiki

[PMario]

Hi Taylor,

That's a nice idea. Thx for sharing!

-m 

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ba0370ae-f43e-4efa-b69b-97189577c41f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: ActionNavigate Widget based on Select Widget

[Hegart Dmishiv]

Hi all,

I think we've got this sorted now, using Eric's *<>* macro 
solution.

Hegart.


On Thursday, 7 April 2016 19:38:35 UTC+12, Andrew Myers wrote:
>
> Hello all,
>
> My question is if you have a select function that lists tiddlers, how can 
> you take the result of the selection and have ActionNavigate and/or 
> EditText focus to it? 
>
> In a project (CRM application) that a colleague and I are working on we 
> have a list of 'people' tiddlers that we want an individual to be able to 
> select from, from there we want them to be able to edit the various fields 
> of the tiddler. We are stuck at the point of which the option of the list 
> is selected and EditText sets focus. 
>
>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/38edc11f-6678-41c2-bbc3-f1b3e363d0ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Combobox

[Hegart Dmishiv]

Hi Eric,

Thanks for the quick reply. I've corrected my mistake on the parameter name 
now, sorry about that. It's not the first time I'm made that same mistake 
now, haha.

Your solution works perfectly, thanks for that.

Hegart.


On Thursday, 7 April 2016 19:34:41 UTC+12, Eric Shulman wrote:
>
> On Wednesday, April 6, 2016 at 11:48:43 PM UTC-7, Hegart Dmishiv wrote:
>>
>> We've run into a little snag with the *goaction* parameter. We can't 
>> seem to get it to work, neither in your example in the documentation 
>> ,
>>  
>> nor in our own experimental tiddler 
>> .
>>  
>> Any idea what's going on? This is something we'd really like to use, for 
>> all sorts of purposes in our TiddlyCRM project.
>>
>
> If you specify field:"text" in the macro call, it works.
>
> Originally, the macro had a default field name of "text" automatically 
> assigned as a fallback.  However, this prevented the underlying $edit-text 
> widget from being able to handle set of values in data tiddlers (using 
> index:"..."), because the field:"..." param takes precedence if not left 
> blank.
>
> Note: the documentation was also incorrect in using the "list" param, 
> which was renamed "filter" (but you apparently found that on your own, 
> since your experiment is correctly using filter:"..."
>
> Also... although you correctly used the "okaction" param in your 
> experiment, in your posting here, you called it "goaction".  I just want to 
> make sure others reading this don't get confused by the mistaken param name 
> in the message.  Also note that, separate from the "okaction" is an 
> optional (and currently undocumented) "clickaction" param, which allows you 
> to extend the default action that occurs when you click an item in the list 
> (i.e., in addition to setting the clicked item value into the edit-text 
> field, you can have other "side-effect" actions performed when the item is 
> clicked).
>
> enjoy,
> -e
>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d453ba14-0651-481c-8fa5-2857aca2f8ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] ActionNavigate Widget based on Select Widget

[Andrew Myers]

Hello all,

My question is if you have a select function that lists tiddlers, how can 
you take the result of the selection and have ActionNavigate and/or 
EditText focus to it? 

In a project (CRM application) that a colleague and I are working on we 
have a list of 'people' tiddlers that we want an individual to be able to 
select from, from there we want them to be able to edit the various fields 
of the tiddler. We are stuck at the point of which the option of the list 
is selected and EditText sets focus. 


-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/682fe973-712c-40da-8f61-9d84614c3e0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Combobox

[Eric Shulman]

On Wednesday, April 6, 2016 at 11:48:43 PM UTC-7, Hegart Dmishiv wrote:
>
> We've run into a little snag with the *goaction* parameter. We can't seem 
> to get it to work, neither in your example in the documentation 
> ,
>  
> nor in our own experimental tiddler 
> .
>  
> Any idea what's going on? This is something we'd really like to use, for 
> all sorts of purposes in our TiddlyCRM project.
>

If you specify field:"text" in the macro call, it works.

Originally, the macro had a default field name of "text" automatically 
assigned as a fallback.  However, this prevented the underlying $edit-text 
widget from being able to handle set of values in data tiddlers (using 
index:"..."), because the field:"..." param takes precedence if not left 
blank.

Note: the documentation was also incorrect in using the "list" param, which 
was renamed "filter" (but you apparently found that on your own, since your 
experiment is correctly using filter:"..."

Also... although you correctly used the "okaction" param in your 
experiment, in your posting here, you called it "goaction".  I just want to 
make sure others reading this don't get confused by the mistaken param name 
in the message.  Also note that, separate from the "okaction" is an 
optional (and currently undocumented) "clickaction" param, which allows you 
to extend the default action that occurs when you click an item in the list 
(i.e., in addition to setting the clicked item value into the edit-text 
field, you can have other "side-effect" actions performed when the item is 
clicked).

enjoy,
-e

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/954ba69a-18a8-40f2-a18b-28353c286f94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.