How to automatically edit a field in a tiddler?

[Surya]

Hi,

again I work in my ToDo-Lists.
And now it gets like I originally wanted- YEAH :-)

I made ToDo-Tiddlers with to fields: due & date.
In the due-field I write for example 25.01.18.
In the date field of that tiddler I write then 18.01.25

The due-field is visible and editable in view mode. The format DD-MM-YY is better readable for me.
The date-field is only for sorting in my ToDo-lists.

Is it possible to automatic edit the date-field, when I edited the due-field?
For example, when I edit the due-field of this tiddler to 01.02.18 that then the date-field is automatically edited to 18.02.01?
I mean to tell the automatic "please edit the date-field (date-format DD-MM-YY) to the same date as in the due-field (date-format YY-MM-DD), but in the format DD-MM-YY".

If yes, how to do?

I couldn't find out how I could solve that.
Please help- thanks, Surya

[TonyM]

Hi,

I am away from my computer but my advice is always store dates in the tiddlywiki date serial number format and use the format to display as desired. Plugins and more can usualy use tiddlywiki dates not bespoke date formats.

I use the date picker plugin.

If as in the past you now have a set of dates you need bulk reformatting ask for help in the forum.

Regards
Tony

[Surya]

Hi Tony,

...my advice is always store dates in the tiddlywiki date serial number format and use the format to display as desired. Plugins and more can usualy use tiddlywiki dates not bespoke date formats.

>>> I am sorry, I don't really understand, what I can do with this information...

I found this: ActionSetField-RemoveField (http://tobibeer.github.io/tw/batch/#ActionSetField-RemoveField).
Maybe my wish could be possible with that (modified)?

The command is written with this:

<$button>
<$action-setfield $field="due" $value="18.01.01"/>
set: due => 18.01.01
</$button>
<$button>
<$action-setfield $field="due"/>
delete: due
</$button>
''due'': {{!!due}}

With this command I can automatically create the field "due" and write into it "18.01.01". I tried it, it works :-)


Could I modify it to build the following?:

When I modify the value of the field "due", then that value should be copied into the field "date", but not in the format YY-MM-DD, but in the format DD-MM-YY.
For example: If I modify the value "18.01.01" in the field "due" to the value "19.01.01", then the value in the field "date" is automatically edited to "01.01.19" (or even better to "1. Nov. 19").


Is that possible (and how to build that command?)?

Thanks in advance! Surya

[Mark S.]

What Tony is saying, and I agree, is to use something like the datepicker plugin or the <<now>> macro (with the [UTC]YYYY0MM0DD0hh0mm0ssXXX option) to save your dates. Then use <$view format=...> to display your dates however you want. If you store your dates in native TW5 format you will find more code and plugins that can use that format.  I sympathize with wanting to use dates like 01.20.2018, but there's not a lot of good tools for splitting text. The various filters for date functions built into TW5 expect dates in the native TW5 format.

> When I modify the value of the field "due", then that value should be copied into the field "date", but not in the format YY-MM-DD, but in the format DD-MM-YY.
> For example: If I modify the value "18.01.01" in the field "due" to the value "19.01.01", then the value in the field "date" is automatically edited to "01.01.19" (or even better to "1. Nov. 19").

What you would probably need to do is to build your own input field and button that could populate both fields at once. But it would be better to just store the date once in TW5 format as mentioned above.

Good luck,
-- Mark

[Surya]

Hmmmm,

I have this in the Task-Tiddlers:

<$edit-text tiddler=<<currentTiddler>> field="due"/>

That shows me the value of the field "due" and I can edit the value in this shown field in vew mode. It is automatically saved.

In this field I have for example the value "18.01.01".

I added <$view format=DD-MM-YY> into that command, but it didn't change anything.

I don't want a plugin for that. And I don't want to change the date, when I edited the tiddler (or did I misunderstood something?)


[TonyM]

Use datepicker to enter or select dates from a popup calendar, it's really cool. You can even allow time selection if you want. The resulting field will contain a TW date just like created and modified.

The all the plugins can handle these dates, including Evans formula plugin with a little conversion.

Many date related plugins use the tiddlywiki date.

One way to think of it is if a fields value is not simple text, you need something to help you. Dates are an example, if I add 1 to a day of the month it could be a new month even a new year.

Fortunately all the tools exist to display a twdate anyway you want.

I plan to publish a plugin for easy date field use but have some travel that may delay me.

If I can share a component that helps I will.

Tony

[Surya]

Hi Tony,

thanks for your answer.
But I don't want a plugin (except it is really small in size), in order to keep my wiki as small as possible to avoid problems.

I had already the datepicker, but I couldn't find any advantage in using it compared to my solution I have now.

I write now in the field "due" for example "18.01.01 (1. Januar 18)". The first one for sorting by date, the second one for better readability.
I only thing I'd like to be more comfortable & nicer looking is the thing with the better readability.
I mean, to avoid writing additionally "(1. Januar 18)" for better readability, but to solve it like my question (Having two fields: One for sorting with "18.01.01", not visible in view mode. And another one for better readability with "01.01.18" or even better "1. Januar 18", visible and editable in view mode). The first one should be automatically edited by editing the second one.

But it seems to me, there is no solution for this automatically editing of the first field.

So, I think, I will let it stay like it is with "18.01.01 (1. Januar 18)", visible and editable in view mode. It is easy to edit. It's not great, but okay.

Thanks, Surya

[Mark S.]

If you really want to have 2 fields then just use 2 input fields in your Input tiddler.

The advantage of the datepicker plugin is that it stores dates in TW5 format. Then you can use a view widget like:

<$view field="myfield" format="date" template="DD. MMM YY" /> to display the field in your preferred format.

Have fun,
-- Mark

[Surya]

Hi Mark,

ahhh, okay :-)
Sounds nice, looks nice :-)

But, it increases the size of my wiki a lot- I just tested it again.

I will stay with my solution :-)
When editing my field "due", it feels like "Oh that's a really very unsophisticated solution".
But it's easy & fast to edit (in most cases even a lot faster than with the datepicker!), looks simple but okay and doesn't increase the size of my wiki a lot.

Surya

[ste...@gmail.com]

Hi,

Maybe this code helps:

<$select tiddler="Form Data" field="date-day">
<$list filter="01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31" variable="number">
<option value=<<number>>><<number>>.</option>
</$list>
</$select>
<$select tiddler="Form Data" field="date-month">
<$list filter="01 02 03 04 05 06 07 08 09 10 11 12" variable="number">
<option value=<<number>>><<number>>.</option>
</$list>
</$select> <$edit-text tiddler="Form Data" field="date-year" size="6"/>
<$button>
<$wikify name="sortableDate" text="{{Form Data!!date-year}}{{Form Data!!date-month}}{{Form Data!!date-day}}">
<$action-setfield $tiddler="My Tiddler" sortable-date=<<sortableDate>>/>
Enter Date
</$wikify>
<$wikify name="displayDate" text="{{Form Data!!date-day}}.{{Form Data!!date-month}}.{{Form Data!!date-year}}">
<$action-setfield $tiddler="My Tiddler" display-date=<<displayDate>>/>
</$wikify>
</$button>


Sortable date: {{My Tiddler!!sortable-date}}


Date for display: {{My Tiddler!!display-date}}

I have used something like this in the past. Two issues are hard to avoid:

1.) You need to split up the date into three components.

2.) You need an extra button to save the date.

Nowadays, I prefer the date picker plugin, though (like the others in this thread).

Cheers,

Stef

[ste...@gmail.com]

On Sunday, January 21, 2018 at 11:39:51 PM UTC+1, ste...@gmail.com wrote:

Maybe this code helps:

Bonus: Apparently, TiddlyWiki accepts the field sortable-date, which is created by my code, as a regular date (even if some trailing zeros are missing). Therefore you could use the $view widget to display your date in additional ways, e. g.:

<$view field="sortable-date" format="date" template="DD. MMM YY" />

I think you might even be able to create a regular TiddlyWiki date field manually by entering your date this way:

20180121

The $view widget could then get used to display it in different ways (see above). Maybe this is another (quick) solution to your problem?

Cheers,

Stef

[Surya]

Hi Stef,

uiui puhhh... -don't know that in english ;-)

I'll have a look at it tomorrow :-)
Looks interesting...

Surya

[TonyM]

Surya,

Your concern about saving space! is this a perception or do you have real evidence of the wiki being too large?

I never worry about this and have not hit any limitations so far. It is the data such as images or thousands of records that threaten to make a wiki too large, much less the plugins and options.

Typically a plugin offers such advantages that the solution can be developed more effectively and ultimately be more effective on many grounds, from  saving space to processing speed and ease of update or maintenance.

Even if you have a space sensitive solution you are developing, it is wise to discover the "best practice" approach for you other and future wikis.

If I were you I would build the solution first and if and when the size looks like its a limiting factor (Unlikely)  then target the items contributing to the excessive size. Otherwise you are making it harder for yourself. This thread demonstrates that. 

Regards

Tony

[Birthe C]

Hi Tony,

Maybe size is not limiting you, but I have two tiddlywikies about 10 mb and problems running them on my computer. Tiddlywiki is in it self growing, and I really want a language plugin also. I just updated a tiddlywiki that was about 1½ year old. Afterwards it was 1.1mb bigger. So growing happens with no images at all. 

You are right of course that the right plan and setup can be saving time and size in use. But we have to learn it first. 

For me a big part of TW charm is that we can get a fresh tiddlywiki as often as we like and use it right away. That we can change it and make it better little by little as we find out what we need and wants. Small errors that gets you looking for the cause of it till your eyes are popping out, but when you found it or worked out a solution that suits you it is like after a childbirth..you forget it all and want to have a soccer tearm LOL.

I think that is what makes TW5 attractive for programmers and normal end users alike - just on different levels of using.

@Stef thank you for your solution above. I have been trying something similar for some time, but did not really have success. Your solution works like a charm.

Birthe

[Surya]

Hello all,

I have been experimenting a lot again. My ambition to find the perfect solution & to learn raised again...

@Mark and Stef:
maybe I'll come back to your suggested solutions. At the moment I experiment again with ToDoNow.

@Tony:
I have been asking (I think even more than one time) some time ago, if it is true, that a big wiki can cause problems. I read somewhere, that it can begin on mobile devices at about 4MB. I asked in this group, if this information is correct. But no one answered.

So I ask now again: At which size does a wiki begin to make problems (on mobile devices AND on computer)?

I need my wikis at both- mobile AND computer.


And: You're talking like I would be able (having the knowledge) how to develop things in TW. But I don't have any knowledge. For me it is like with an unknown language, say turkish. I understand the facial expression, and I know about ten words. So when people talking in this language I understand only very small fragments and even this fragments I missunderstand often.
In TW the language are the codes, commands, css, and so on and so on. Additionally everything is in english. I can talk in english with people, not very deep, but it's okay. But english in TW and in this group is concerning to computer- not everyday-english.
I don't know what all the < > $ { / and so on mean. I don't know in which sequence everything needs to be written. And I found nowhere any documentation about these things. Also I don't how the language of TW is called, to eventually google it for learning.
Okay, complained enough ;-)



Because of what you said, I experimented again with ToDoNow.
Even if it is not my solution (because of size or other reasons), it is / was a good thing to learn a little bit.

And I found out now, how I can display my ToDo-list with ToDoNow in that way I would like.

In my wiki for such experiments I have now these plugins: ToDoNow + Listreveal + Datepicker + Checklist + ToDoNow Outlook Addon.

In the Outlook Addon I found a way to display my wanted ToDo-list with this:

\define teBigSaveButton(class:"te-third")

 

<$vars tv-config-toolbar-icons="yes">

@@.te-btn-big.$class$ {{$:/core/ui/Buttons/save-wiki}}@@

</$vars>

\end

\define teBigNewTaskButton(class:"te-first")

<$wikify name="tt" text=<<telang New-ToDo-Item>>><$button tooltip=<<tt>> message="tm-new-tiddler" param="ToDo Item" class="te-btn-big te-create $class$">{{$:/core/images/new-button}}</$button></$wikify>

\end

<<teBigNewTaskButton>>


 

!! <<telang "This-week">>


 

<$set name="listfilter" value="""[all[]tag[ToDo]][all[]tag[ToDoNow]] +[days:todo-deadline[700]sort[todo-deadline]]""">


 

<ul class="te-list">

<$list filter=<<listfilter>> emptyMessage="<li class='todo-empty'><<telang 'Relax-Nothing-to-do'>></li>">

 <<todonowShowListItem>>

</$list>

</ul>


 

</$set>

In another experiment I managed successfully to show me tasks which are today or on past days with a red marker „late“ with this:

<ul>

 

 <$list filter="[all[]tag[ToDo]][all[]tag[ToDoNow]] +[days:todo-deadline[700]sort[todo-deadline]]">

 <li>

 <$link><$view field="title"/></$link>

 <$list filter="[<currentTiddler>days:todo-deadline[+60]]"> @@color:red;^^late^^@@</$list>

 </li>

 </$list>

</ul>

How could I integrate this „late marker“ in the first mentioned solution?

And 2. question:

In which tiddler should I write my wanted view format for the field "todo-deadline"?

So that the deadline-dates which are shown in the ToDo-List in ToDoNow are shown like I want?

Best regards, Surya

[TonyM]

Surya,

I understand the difficulties you are facing, my point on the space issue is do not concern yourself until you experience the problems you fear. 

It is not possible to to give a clear statement about TiddlyWiki working sizes as there are many variables, since mobile use is somewhat new we do not have a long history to work from. 

In addition mobile can be impacted by the phone itself and the browser you are using perhaps even more than technical issues in TiddlyWiki.

I use a 17MB+ TiddlyWIki Classic on TiddlyDesktop, and a number of 10Mb+ TW5s in FireFox via TiddlyServer with no issues.

It is amazing what you have achieved with the language differences and technical inexperience its is a testament to your determination, and the support of this forum that you have achieved so much. You must be congratulated.

I for one have found coding TiddlyWiki difficult despite my experience because in some ways it is still a "work in progress" and not always well documented, a lot of us are working to improve it for new users.

The key piece of experience I am trying to share is "be careful not to make it too complicated for yourself by holding onto concerns such as space requirements".  At this stage of your learning it is best to use existing tools and plugins and deal with space issues when they arise.

As I have not being pushing the mobile wiki size much perhaps others have tips, My mobile use has being with mobile dedicated wikis on top of Turmux allowing me to view the wiki from the desktop over the local area network. My Mobile apps are so far designed to meet specific mobile needs, not every need. 

I plan to release some plugins that may help you but others need to help you with the above technical questions.

Best of luck

Tony

[Surya]

Hello Tony,

thanks for your nice answer :-)

I understand what you mean and I really would like to do it like this.
But I have fear, when the wiki makes problems one time in the future and the reason would be because of the size of ToDoNow, I would then have to edit hundreds of tiddlers....

My wishes for improving documentation and tutorials for newbies would be: A lot of examples, all with examples "how it looks like in view mode". And testing possibilities are also always very helpful.
And some basic help "what means $ " / ( { > and so on.
Also: Is something only for TWClassic or only for TW5 or for both compatible.
And another main problem is, that there are hundreds of sites with tutorials, documentations, plugins and so on. No one is complete, and I didn't find any site, where at least is listed, where to find ALL tutorials, plugins, descriptions, documentations and so on. With links to them and a description what to find there, listed by categories for endusers. I mean, not listed like macros / widgets / CSS and so on. But listed like Calendar / Lists / Design / ... Categories like macros / widgets / CSS and so on in addition- this is already for little bit advanced users. As a newbie you have a goal like "I want to see a calendar" "I want to make calculations" "I want to make a ToDo-List".
I think the project of Dave Gifford targets that need. I really hope, that it will be a complete list of everything. And then it should be mentioned, when you first read about tiddlywiki, in the first or second tiddler. With that you know immediately where to look for something.
And, all the tutorials, documentations and so on in german ;-) And I think, other languages are missing too.

My wishes.... ;-)

The other questions I'll ask in new threads.

Have a nice evening,
Surya