Yes @Joshua : that one did catch my eye -and, now that you mention it, i can see how much overlap there is between this particular problem space, and the one that TW eBooks app solves. In both cases, it's about using TW to load and browse these long docs (whether eBook or API endpoint), and then leverage TW's magic powers of annotating, transcluding w/ backlinks, etc.
In fact: seeing as how OpenAPI standard is delivering content in JSON format, which is native to TW core, this one should be a breeze for TW5 to handle, right? After all: we're not talking here about full CRUD interactions w/ a db (i mean: Post, Get, Put, Delete) via API; i just want to use it to browse my app's API, so i can understand & annotate it. Perhaps my naive (i.e. non-dev) user perspective is overly simplistic, but still, the question remains: is this an ugly problem or a juicy opportunity? Bottom line: If anyone here sees this as either an opportunity they can see themselves solving, or else a problem that they see as too hard for some technical reason, i would love to hear more about it! /walt On Monday, July 19, 2021 at 4:18:40 AM UTC+1 [email protected] wrote: > Hi walt, > > A french ebook company worked with Jeremy to develop plugins that allow > you to dynamically render only the text that is "onscreen", and also allows > you to highlight a section of text & leave annotations attached to that > highlight. > > See: https://groups.google.com/g/tiddlywiki/c/_VLufc4Svp8/m/jALzYZ09BAAJ > > Have fun. > Best, > Joshua F > > On Thursday, July 15, 2021 at 9:10:22 AM UTC-7 ludwa6 wrote: > >> Catching up on TW news (busy times down here on the farm!), i was >> rewarded by yet another serendipitous find in this little gem from Mario >> <https://groups.google.com/g/tiddlywiki/c/ODEleDkUOss/m/pW7AmKJmBwAJ>, >> with an embedded link to the TiddlyWeb API Explorer >> <https://tank.peermore.com/tanks/tiddlyweb/explorer> -what looks on the >> face of it like just the solution to the biggest problem i've got sitting >> on my desk right now. >> >> The problem is: the farmOS system <https://farmos.org/> i use for >> operational record-keeping is undergoing a major upgrade to version 2.0; >> this presents a data migration challenge for me & the agronomist i'm >> working with that would be greatly facilitated by an API Explorer. Good >> news is: farmOS has an OpenAPI that can be easily explored using this >> open-source farmOS.py library <https://github.com/farmOS/farmOS.py> -by >> anyone with adequate python chops, that is. If only that were me! But >> really: wouldn't it be so much nicer to explore the API using something >> like that TiddlyWeb API Explorer -a python project, as it happens. >> >> So following Mario's pointer, i reached out to developer Chris Dent, who >> confirmed: not only is interface written in TW Classic, it is moreover >7 >> years old now, and he has had nothing to do w/ it (or TW, for that matter) >> in the years since (typical story of funding having run out). Finally: >> code being targeted to the TiddlyWeb API itself -which uses the same >> OpenAPI standard, but is a very different data model- it's a project that >> the developer has no capacity to take on right now. Still: source code >> is online <https://github.com/tiddlyweb> and available for anyone to run >> with. >> >> All that being said: i'm just captivated by the notion of using TW5 as >> the ultimate OpenAPI Explorer. In such a front end, one might not only >> browse, but also mark-up and annotate such a typically complex document, >> writing & sharing comments & scripts in a most digestible & reusable form. >> >> So while i believe the developer that this would be no trivial >> undertaking, i am sufficiently intrigued by the possibility that i have to >> tap this collected wisdom here just to ask: Do you think like me that TW5 >> would make a very good OpenAPI Explorer? Whether using any of this code or >> some other language, i'd just like to know if this is a likely prospect, or >> just my wishful thinking, over-estimating the synergy between these >> softwares. ? >> >> /walt >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2070a2fb-51a4-46f6-9a3a-9e9f43531fcan%40googlegroups.com.
