Might PapaParse be used to "live import" and/or "live conversion" non Wikified content into individual tiddlers? Even by simply providing an url? A kind of RSS reader?
Can I make a simple copy-pasting into TW editor be automatically parsed into something nicer, when I save the tiddler? For instance if I copy a html-table from a website, i.e select+copy, this removes all formatting and all that is left is tab spaced rows. So... TW should be able to do something with this. Or, even simpler, just a plain text list. Instead of having the parser disregard the linebreaks, I should at least be allowed to choose if I want it to appear as a bullet list.
This is actually related to some ideas touched on here (see post 11/24/14, the thread starts out with other ideas), about building content communities with lists presented as topical "addon stores", e.g "url-list: best TW addons for authors",or "thumbnail gallery of [img[urls]]", etc. An entry in a list for a "top-plugins" could be;|[img[url]]||[pluginname|url]|Description]| or with html markup...however, with this "automatic parsing" idea, e.g for a simple copy-pasted text, I am hoping the input can be simplyimageurl pluginname pluginurl descriptionthose are tab spaces, and the parsing would automatically convert things to add htmlmarkup and CSS. And any pre-added wikitformatting woudl be parsed like normal, I guess.
So that is when I found the info to PapaParse, It sounds like it for sure would do this, but so much more and so much more powerfully. From what I understand it's purely javascript based and open source. Maybe it's even possible to use it as a streaming RSS/ATOM feed convert-to-TW tool. Put up a TW that displays your favorite feeds... as tiddlers... so that as you read, you can easily add meta data and save stuff. (If there is autolinkification/autoweaving, you could probably build up an incredible referencing database automatically! Whoa!)
Could PapaParse be used to stream individual tiddlers from external TWs too? Is we talkin' twederation thingies?
Anyway, if anyone else is interested; for the lighter ideas I initially had in my search, to convert plain tab-delimited text into nicer tables, I found the following that I intend to look closer at.<:-)
--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bb610b52-57b0-4d4b-98a1-e36ff9fca0e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Accessing external URLs from a local HTML page is pretty much disabled by browsers these days.
Can I make a simple copy-pasting into TW editor be automatically parsed into something nicer, when I save the tiddler? [...]
One could certainly imagine such a thing: a simple way to do it would be a text box into which the user pastes their content with a "submit" button that kicks off the conversion process. It's JS plugin territory, but perfectly straightforward.
we've already got a viable mechanism for client-side federation: the plugin library.
That library, and also your CSV-JSON hack, seem to be for node-js TW, but I see no mention of node-js in PapaParse - do you think it might work in vanilla TW?
Accessing external URLs from a local HTML page is pretty much disabled by browsers these days.Hm, I was kind of assuming RSS was some type of exception (maybe using some ifram'ish mechanism but with a modifiable "parsing filter" inside). But what might PapaParse mean when they talks about download remote files to parse then? Shared servers? (Would maybe e.g a tiddlyspot-to-tiddlyspot work, or because the TW is presented locally, it wouldn't?)
Is there any place where I can read up on how this works in more detail? I'm too bad at coding to understand it that way. I know it's been discussed in the hangouts but it would be great if is some explanatory text that mentions it's key parts so that I can look at the code and identify them, and read what they actually do.
I'm guessing the plugin library only permits importing of tiddlers/plugins, right?
...And node-js individual tiddlers, at that, right?
...And is there some way to insert any url to such a tiddler and have it imported on command?
Thanks for your patience Jeremy. At least I think these may be issues of wider interest, at least if I or anyone can make prototypes to show what could be achieved. Talk about RSS, not to mention federation, has of course been up before but so far we haven't come very far from a user perspective, other than the plugin importing which, to a simple end user like, seems like a special case where it's difficult to understand the greater implications.
<:-)
I need more time to work on the federation stuff...
I really like your enthusiast but, are you conscious of how many things have you proposed? Some times looks like you are victim of a good marketing department of certain libraries.
I'll ask, because federation will probably have such big consequences for the whole TW project: Are there any parts in this that you think others might have capabilities of working on? Is there any particular problem that needs solving?
Thank you!<:-)
But of course the parsing would be tied to a set of rules? That is exactly what parsing is, no? "Read from left to right, if you hit this character, do this, if you hit this string, to that". I have not said or even implied anything else, have I? Or do I misunderstand what you are referring to?
Thank you Danielo! From looking at it briefly I can tell I will for sure start to use this right away!!! :-)<:-)