Hey, all —

You also should consider, to switch those plugins, that you want to be part 
> of the TiddlyWiki core, to be "BSD 3 clause"
>

I can do this the next time I make an update.  With formula in particular 
I'm expecting a period of maturation and conversation with core developers 
before it's considered for a merge.  I'm doing a lot of cowboy coding at 
this stage. 

I'm wondering if you'd be okay if I started another thread about developing 
> examples of usage? Not necessarily for you to answer on but also other folk 
> who are developing grasp of what it can do?
>

Makes perfect sense to me.  I would have some examples to contribute, 
myself.  And I might incorporate others into the formula wiki's repository 
of demos. 

It would be very useful for all potential plugin authors present and future 
> to please include an up to date license for your works. It really helps and 
> it is super important I believe.  This probably deserves its own thread. 
> Apologies. 


Also very sensible.  Make a PSA thread!

Don't know if your aware, or if it's useful, but Matt did some graph work 
> last year.
>

Neat!  I'm working to make formula powerful enough that graphs can be made 
by combining SVG and formula code.  Any input on that is welcome — I'm 
currently writing some complicated programs to test the programming 
capabilities and see what sort of walls I run into.

Just wondering, has IFERROR been implemented yet?
>

What, I have to implement things before I document them?  :)  But 
seriously, that one's my bad.  I think it's commented out in the 
implementation code.  I'll look into fixing that next update.

Because the complexity of what can be written in formula is rapidly 
increasing, I'm thinking about ways to improve the plugin's error 
reporting.  Specifically, it's often used in places (attributes, SVG) where 
error text won't be visible...  It's also useful to know when an error 
originates inside a certain function, LET value or transclusion...


On Wednesday, 17 January 2018 01:15:24 UTC-6, Evan Balster wrote:
>
> Announcing the second generation of my formula plugin for TiddlyWiki.
>
> See the *Formula wiki* for the latest documentation:  
> http://evanbalster.com/tiddlywiki/formulas.html
>
> *Report issues and view source GitHub*:  
> https://github.com/EvanBalster/TiddlyWikiFormula
>
>
> Formula lets you do computation in TiddlyWiki in the style of popular 
> spreadsheet apps Excel and Google Sheets, with the addition of TiddlyWiki's 
> own filter, transclude and variable systems.  Tiddlers can behave like 
> individual rows in a spreadsheet.  A large collection of built-in functions 
> is included, for use with text, numbers, dates, arrays and regular 
> expressions.
>
> Formula is implemented as a widget, with a special *(=* "mushroom 
> bracket" *=)* syntax for inclusion in WikiText, and can also be used in 
> widget/HTML attributes.  Formulas included via transclusion, filters and 
> variables are computed and refreshed like any other part of your wiki.
>
> (= ( sum([tag[Profits]get[value]]) - sum(tag[Expenses]get[value]]) ) * {{
> Tax!!rate}} =)
>
> The second generation of formula adds support for local variables, 
> comments, lambda functions and element-wise operations on arrays (such as 
> filter results), allowing more advanced computations to be expressed inside 
> TiddlyWiki.  Search the wiki for "demo" to see some of the things I've 
> built.
>
>
> The plugin is a work in progress and may have bugs.  Please report these 
> on GitHub or in this thread.
>

-- 
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/78634ebb-1545-4105-a013-0b6b489cc4d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to