so, gone over it and found the issue in you code.... it's not related to liquid. the idea is that the data you give is not what you expect.
in your table, true and false are words... not logic! values. So, either you use #[true] #[false] or you reduce the block before searching within.
btw, I'm having fun re-writing it quickly.
Josh
Sweet, thank you. Not sure I fully grok it, but I'll keep an eye for that in the future. Love to see your version
Josh
I think I got ya:
>> if true [print 2] 2 >> if false [print 2] == none >> b: 3 == 3 >> b: [3 true] == [3 true] >> if (second b) [print 1] 1 >> c: [3 false] == [3 false] >> if (second c) [print 1] 1 >> if (do second c) [print 1] == none >> if (do second b) [print 1] 1
Kaj
Yep
The difference is not so much DO, but BIND
Endo
c: [3 false] ; this should c: reduce [3 false] ; to get desired result
Maxim
Endo yes, that is the prefered method.
Josh
Got it. I have a better working version now! Generates a new schedule that shows for each hour who is available
Anyways, to keep on topic with !liquid, I have a !plug that generates the schedule of availability, it's of a particular type, can I just link it to another type to process data from that? I ask this because I'm not sure what the following line does at the end of the Process(plug,inputs) function
plug/liquid: available
week=> weak
Cyphre
Endo, IMO the best method is to use :
c: [3 #[false]]
Endo
But it leads problems when encapping the script.
Maxim
Hi Josh, here is your inital example rewritten. I put three versions for you and all to compare.
you will have to update your repository, as It doesn't contain fluid and there have been a few fixes since you forked my libs.
and in my scripts, I'll thus use do %../slim-libs/slim.r
(btw, in the above scripts, the scripts where in a subdir of the project, so they have %../../ instead of %../
Maxim
Endo, yes, serialized values are the death of many encaps and the encap system being extremely faulty led me to write a String parsing equivalent which doesn't LOAD scripts.
Josh
Maxim, nice! I will rearrange the libs and adapt my code to match the style of yours if I have time tonight
Maxim
happy it helps you. There will be some improvements to the fluid dialect again this week for sure. We will start using it at the office, so it should be solid (pun intended ;) very quickly.