[twdev] Re: Propose: Simple date validation operator
Post Script;
I believe this proposed validatedate operator would would unlock the
possibility of a lot of date handling without the inclusion of more complex
date handling plugins etc...
Just to explain a little further using nested range operators it would be
possible to generate any number of years, months and days such as from 1 to
31 days and have the proposed validate eliminate invalid dates. This would
be good for producing date tiddlers or rejecting invalid date entries eg
[{date}is[validdate]]" emptyMessage="Invalid date"
- Then the valid date(s) can be used to test for the existence or list
tiddlers.
- One could even use a generated list of valid dates to do relative
dates such as +45 days later using the set widget index parameter
The inability to format a variable as a date is still a restriction
Regards
Tony
On Wednesday, March 4, 2020 at 10:25:11 AM UTC+11, TonyM wrote:
>
> Folks,
>
> In this thread
>
> David asks how to generate a range of dates.
>
> This made me ask myself what if we had an operator that given a date input
> of the standard TiddlyWiki form MMDD+
> it was able to filter out invalid dates according to calendar rules
>
> That is if 20200229 or 20200229231215828 is filtered eg "is[validdate]"
> it would be passed through as there is a 29th of february this year.
> That is if 20210229 or 20210229231215828 would not be because there is no
> leap year in 2021
>
> This may be a simple javascript date function already available in
> tiddlywiki.
>
> It would then become possible to do the following;
>
> <$list filter="[range[1,31]addprefix[202002]is[validdate]]">
>
>
> to generate a list of February 2020 valid days of the month
> *I have not complicated the above with the need to zero fill the range
> value*
>
> From this proposed filter it would be very easy to generate date ranges or
> test any YYYMMDD for validity
>
> This could as easily extend to time as well if required is[validtime]
> HHMMSS
>
> What do you think?
> Can someone help me make this so?
>
> Regards
> Tony
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/72cc6675-667d-49e6-8552-d98906e48e7a%40googlegroups.com.
[twdev] Re: How to use WebServer without Node.js?
Post Post Script, I just wanted to add there are two ways to Host or Serve a Wiki, one is the file/folder content, the other is to provide the HTML access to the server. What I mean is if the servers files are shared online you can have node JS run against those files. Ie you take your server with you. Of course you can run the server node session off the cloud version but only one at a time however I think (unsure) Jed was looking at the ability for multiple node servers against the one repository. finally, I think there may be value using a VPN to access a node hosted bob, ie keep it as a LAN based solution secured inside a VPN to make it internet accessible. Regards Tony On Thursday, March 5, 2020 at 9:40:59 AM UTC+11, TonyM wrote: > > Bimlas, > > Others may have an answer. > > The key method to host online for me is php and tw-receiver but for single > file wikis only, this rest on top of a standard html server and there > numerous ways to build or host such servers. It would be great if we had a > php saver for tiddlywiki that operated like node.js ie folder based wiki. > > At present only bob on node has the multi-user multi-access solution > typically needed for an online server, although the method used by NoteSelf > may be an alternative; > >- I think a php solution would ether need this added functionality >multi-user multi-access or at a minimum the ability for a group of users >with read/write access to serialy edit, ie; lock the wiki in their name. >- I also wonder if a html put and get server and saver version could >be built. > > Of course sometimes you could package node inside something like a virtual > machine, Docker container and serve it that way instead. > > *One thing you could add to this discussion is why you want individual > tiddlers* because there are increasingly more opportunities to meet some > of the requirements that separate files satisfy but now within the wiki? Ie > what is driving your desire for a alternative server platform beyond not > node. > > PS I have a control panel hosting environment and whilst they did not > document it a technician showed me how to host a nodejs instance, I did not > continue because even bob presents security risks on the internet, although > Jed has implemented a secure version with other technology involved. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/568ff7cd-d0ce-4a8b-8ed5-6c32450b4477%40googlegroups.com.
[twdev] Re: How to use WebServer without Node.js?
Bimlas, Others may have an answer. The key method to host online for me is php and tw-receiver but for single file wikis only, this rest on top of a standard html server and there numerous ways to build or host such servers. It would be great if we had a php saver for tiddlywiki that operated like node.js ie folder based wiki. At present only bob on node has the multi-user multi-access solution typically needed for an online server, although the method used by NoteSelf may be an alternative; - I think a php solution would ether need this added functionality multi-user multi-access or at a minimum the ability for a group of users with read/write access to serialy edit, ie; lock the wiki in their name. - I also wonder if a html put and get server and saver version could be built. Of course sometimes you could package node inside something like a virtual machine, Docker container and serve it that way instead. *One thing you could add to this discussion is why you want individual tiddlers* because there are increasingly more opportunities to meet some of the requirements that separate files satisfy but now within the wiki? Ie what is driving your desire for a alternative server platform beyond not node. PS I have a control panel hosting environment and whilst they did not document it a technician showed me how to host a nodejs instance, I did not continue because even bob presents security risks on the internet, although Jed has implemented a secure version with other technology involved. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/a8d7ee1d-68f2-4a86-8278-4b6a652d94e9%40googlegroups.com.
