05-19-2022, 04:26 PM
(05-19-2022, 02:47 PM)madscijr Wrote:(05-18-2022, 05:53 PM)CharlieJV Wrote: Everything is interesting to me. And everything is intertwingled.
Everywhere, everything I see is a squirrel.
I love that you did this using TiddlyWiki!
This makes me think of some awesome possibilities!
Write plugins in BASIC
How about a TiddlyWiki where you can program your own plugins & embed automation in tiddlers using QB64 or BASIC, instead of JavaScript?
The objects and OOP they use in TiddlyWiki was very complicated and hard to understand for a simple BASIC programmer like me!
They lost me when they moved from the classic 2.x TiddlyWiki to the new engine.
I much preferred the old format,
and had a million plugins and customizations which took me years to get working just right,
that just didn't seem compatible anymore.
All the good stuff I used was missing or hidden from the new version, and I just didn't have time to re-learn everything.
If it used QB64 or BASIC for the customizations, and stayed backward-compatible, that would make the learning curve much easier...
No Web browser
The other reason I got away from using TiddlyWiki was too many headaches with browser security getting tighter.
It just kept getting more and more complicated to configure my PC and browser to let TiddyWiki save changes.
But who needs a Web browser when we could write our own desktop app in QB64?
A native TiddlyWiki engine would get us around all these browser security headaches.
Picture a TiddlyWiki or Jupyter Notebook but native to QB64 instead of JavaScript or Python!
Native built-in WYSIWYG rich text editor
The final thing that TiddlyWiki was missing (at least when I was using it)
was you couldn't copy rich text & images from your clipboard directly into a tiddler (a page in the notebook).
That was a very important feature that Microsoft OneNote could do, and I ended up using OneNote instead.
But you can't customize OneNote with VBA macros like you can with Excel/Word.
The other advantage TiddlyWiki has is, with OneNote your files are stored God knows where,
but with TiddlyWiki everything is in one file that you can copy, backup, etc.
Syncing to iPhone - via dropbox?
One final thought - the other thing that makes OneNote supremely useful is that
it syncs to my iPhone seamlessly! I know QB64 doesn't run on iPhone,
but there are TiddlyWiki readers for iOS (at least there used to be).
This is a while ago and back then if you wanted to share notes,
you had to manually sync your TiddlyWiki on your PC with your phone using iTunes (gag).
I vaguely recall there was also some TiddlyWiki site that hosted people's notebooks online,
that they could access from other devices, but I'm not sure I would trust a company
other than a big one like Microsoft, to host the kind of personal data that I keep in my notes.
I'd be more comfortable using dropbox to sync them with dropbox, and also more convenient.
Anyway enough of my ramblings...
This all just reminded me of my TiddlyWiki days, and hopes and dreams! lol
I kid you not: please don't ever stop rambling. That is good stuff. I've got ADHD, so one reading has my old sponge going down a million rabbit holes. I'm going to needed repeated readings to sort out everything in my head.
My return volley:
FYI:
I embedded and am heavily modifying wwwBASIC for this TiddlyWiki I created called BASIC Anywhere Machine. Supported by this other TiddlyWiki: Programming Reference. Supported by this portal site, these YouTube videos, and this blog.
Primary interest: TiddlyWiki and BASIC working together. BASIC to give TiddlyWiki the things TiddlyWiki isn't particularly good at, TiddlyWiki for the things BASIC isn't particularly good at. (Examples: BASIC Anywhere Machine as Embedded Graph Server for TiddlyWiki, and work-in-progress ASCII Art Anywhere Machine)
One of the many things I had in mind was BASIC Anywhere Machine as a sidekick for QB64, for creating and testing segments of code in BASIC Anywhere Machine, using BASIC Anywhere Machine ( and whatever TiddlyWiki native features + plug-ins) as QB64 source code repository, and for exporting simple QB64 as stand-alone BASIC programs in single-file html (Easter Eggs example)
Since I think QBJS will really be the cat's meow for serious QB64 apps to work on the web, I've paused my efforts to make BASIC Anywhere Machine as compatible as reasonably possible with QB64 (well, QB64 Phoenix Edition !)
Instead, I am now focused on getting BAM as compatible as reasonably possible with GW-BASIC.
Then I'll return to efforts at making BASIC Anywhere Machine a small sidekick to QB64 Phoenix.
Something like that. Hard to get it all straight and organised in my head.
All while bouncing back and forth between all my projects and reading again your rambling good stuff.