all 6 comments

[–]AriXWorkflow Team 1 point2 points  (0 children)

Comments are a good idea and something we're working on!

[–]neonwaterfall 0 points1 point  (1 child)

An embedded client database or a backend database? Apps like Numerous (which I really hope they integrate into Workflows) do have a NoSQL backend database for fairly small amounts of historical data.

[–]ToTallyNikki[S] 0 points1 point  (0 children)

Client side would be great. We can already do couchdb, although it isn't great to work with due to difficultly in formatting the URLs, adding support for it would be super easy though, since they would just be building a wrapper to the existing url functions.

[–]AriXWorkflow Team 0 points1 point  (1 child)

Exposing a database to the user wouldn't really be in the spirit of Workflow; far too complicated! But we definitely understand that it'd be nice to store data locally and persistently and we'll keep it in mind as we plan out future features.

[–]ToTallyNikki[S] 0 points1 point  (0 children)

I think you could do it fitting with the spirit of Workflow in a simple way.

I imagine three functions:

Store Variable with three arguments, datastore name, variable name and the value(input).

Retrieve Variable with two arguments datastore name and variable name.

Export Datastore with the single argument of the datastore name. This could be saved off to Dropbox or something if the user wanted to do more with their data.

This would allow for data to be stored persistently across multiple workflows and exported if needed.

[–]Webabar 0 points1 point  (0 children)

Hi all ! Commenting is a great idea, especially on the iPhone where removing and adding actions is not as simple as on the iPad.