New Journal - tremho/thunderbolt-common GitHub Wiki

New Journal notes

Ramblings at this point are shared between this project space and the Dragons of Winter project since we're using Jove to create that app.

DoW makes a weird choice for this framework. As a single-page game, it doesn't really utilize much of the features of Jove, and the architecture for the animation engine is hampered by the high-level abstraction of the paradigm. A 'real' game would be down at the core level.

(this is where I want to check in with Triniwiz on his canvas work. This could form a common canvas API for desktop/mobile that I can use in Jove to make a graphic-intensive solution. Not sure I'm going to do that any time too soon, but it could be a big plus, and it might even become necessary, depending upon how DoW proceeds).

I learned about Capacitor the other day. This is going to give me some par-level benchmark goals for sure. It's already a little different in that it relies "too much" on the web paradigm. So in a nutshell, I guess you could say that Capacitor allows you to make web apps that also run on desktop and mobile devices. Jove lets your write applications that will run on the web, desktop, and mobile devices. A subtle difference, but it's there.

I'm curious what the {N} community thinks of Capacitor and what the consensus pro/con breakdowns are. Also need to get more feedback on the pros/cons of React to Riot and who's paying attention.

I think marketing Jove will always have to take the position of 'road less travelled', but we need to make sure that this alternate path is scenic and rewarding.

In that vein, check out my thoughts for a test-release staging site

Community support will be a big thing. Need to put more thought into bootstrapping that. Current strategy is:

  • Create a forum site with community supplied resources and tips
  • I'm thinking this should be a series of articles and/or tutorials and a Q&A section that refers to these.
  • Forum questions can have specific answers, of course, but the better form is to link to a article or snippet. Specific answers should be used to clarify the process outlined in an article with specific examples to match the question.
  • Blog and reach out to bloggers and reviewers (introducing Jove)
  • try to get them to pre-populate the community site

Prerequisites before any of that

  • Get wherever we seem to be going with DoW, and establish the workflow to test-release (even if it's just an email distro)
  • Implement the CLI Init feature and use this to start Alcaeus and Prepared (Prepared For Dinner) and start marching through those page requirements for any standard components we will need.
  • Make the list of the standard components. Save the weird ones for forum articles / blog posts.
  • Implement Doc and Test
  • Implement Telemetry
    • should include screenshot capture and xmit

This todo list hasn't changed much. We keep pecking away at it. Jove will mature in it's time, but if I'm in a race with Ionic, I've already lost. I think we can still get a share of the market as the odd one out, even from a late-comer stance.

Revisiting notes

Looks like the last entries were nearly 6 months ago.

Suffice it to say that although I've been working on this continually since then, not much has really changed, except that things have gotten better and tighter overall. Book of Jove is coming along.

Currently, I'm diverted to finish Doc-Holiday so that I can return to documenting Jove.

In continuation and addition to the list above, here's my current take:

  • Finish Doc-Holiday [Mar]
  • Complete API docs and Book of Jove [Apr]
    • This includes finishing moon info for planet facts

Revisit and fold in

  • Date and Time -- I think this was basically ready. doc it and npm publish. [Apr]

  • Unit Types -- I think this still needs some work. clean, doc and npm publish. [Apr]

  • Internationalization -- I think this is close, and it is on npm. Revise and republish. [May]

  • Formatting -- Should tie all the above together [May]

  • Logging -- Uses formatting; configurable output and color options; inter-process messaging. [Jun]

  • Telemetry -- like Sniff. Core events and custom events. Consider a subscription service. [Jun]

  • Build in Doc-Holiday. [Jul]

Extending

  • Look into canvases; contact Triniwiz. [Jul]
  • Explore C coding support. [Aug]
  • Look at other language support, at least architectural plan / PoC. [Sep]

I'm assuming I will be working a real job soon, so my [Mon] estimates here are an optimistic spin with that in mind. Which puts us to [October 2022] for a jove Beta.

I should star Alcaeus before that. Serially, that would be in, say [jul], but I think I can do it in parallel in say [Apr] and have it done by [Aug]