Looking at modernizing Asqare and Nerdkill using the look and feel of Puzzle. Ideally these should be made on top of a generic app shell, customized using assets and scripting.

Step 1: This is different from a live editor. Here the script and assets would be transformed into a native android app , directly in studio.

Step 2 is the robot game idea where a game editor app is used to produce mini games.

Need to better spec those. Step 1 can be combined with Ikaria. Testing should be a first class citizen, especially to abstract all ui using some kind of MVP pattern.

Finished Set Puzzle phase 1.

• Created a full features MVP (phase 1), presented it.
• Could make a variation of such, from the same base. Code name is "taz".

Reworked LibUtils:

• Googlecode main branch is the C# version Lib1+Lib2 with AndroidAppSkeleton.
• Googlecode "android-lib" is the java lib for Studio that provides Serial + utils.
• ⇒ Implement new file-storage class with possible direct access.

Idea: use Nerdkill to experiment with Google Play Game APIs.

• Revamp app to have the holo-light look & organization from Set puzzle.
• Add leaderboards.
• Add ludicrous achievements ("played the app for 5 minutes", "launched the app".)
• Multi-player.
• Add ludicrous IAB items.

Want to rework on the foundation of black-editor.

Pending projects that need some love…

Web App idea: Val clone

• Web based (phase 0)
• Optional android client (phase 2)
• 2 implementations strategy in mind:
• As an Go or Java/GWT based AppEngine app, with AppEngine data store.
• As a GDrive app using a specific Drive document as the backend.
• As a learning tool, I could do the following:
• Full HTML5 (?)
• A Gdrive-app
• Use Dart (which has google-drive APIs libs)
• Custom drive document type
• Note: gdrive API no longer provides a spreadsheet API.
• Offline Chrome App would be nice but seems like a security risk.
• Make it a Chrome extension. No local storage, no full listing, just a little popup for keyword search => result.
• Random bits:
• Model is a pure key/value list: name ⇒ { password, date when set }.

For the fun/obscure reference, call it "Slowdive… because it ain't no bloody Valentine".

It's time again to take a state of the union and look at my various toy projects, their scope & state, how they intersect and what/where to go next. I'd like to take one and finalize it. But the first question is what am I trying to achieve, and how these project fulfil that?

Side note: this is a summary. I need to organize my project management too (yet another task) and maybe something like Trello or docs would be useful. Main issue to solve here is fragmentation of the info in different silos and lack of cross-linking.

Projects, in no particular order:

• Timeriffic 2
• Ikaria
• Cloud Bus
• Timer2 (aka T3 the reboot)
• Pixel game
• JS chrome offline app
• Home Music
• Home monitor
• Monitor webcam proxy
• Rig4mm

What I want/need, mostly in this order:

• Useful: Fix Music because I need it, not for the tech itself.
• Useful: Write the webcam proxy because I need it too, although it's a P2 at most.
• Only useful if I follow up with the HMon app rewrite.
• Write CloudBus phase 0 as a base foundation, not much to learn here..
• It's not clear how successful phase 0 would be, so interesting part is understand limitations & usage first. That is, have concrete usage scenarios for it.
• Ikaria is essentially a learning project. It's all about creating a base foundation that I can reuse whilst respecting guidelines and experimenting with testing.
• Same as with CloudBus, part of the design is understanding applications of it.
• Pixel game is the main "client" of Ikaria at this point.
• Timer2 as a T3-reboot is mostly a no-go for now.
• Timeriffic2 has been closed for a while.

Ikaria should merge with Black Editor and Hint-0.

Current project list, by descending priority.

• Finish Timer2 proto as a pure demo-proto:
• T2:
• GeoLoc personal app.
• LibStorage
• HMon
• Home Music App
• Hint: delayed again.

Linux Kernel is now in version 6.something.

The first version of Linux I used was Kernel 0.99, which I ran on my 286 PC back then. My machine was pretty beefy -- I had a full 1 MB of RAM, way more than the meager 640 kB needed by DOS !

We didn't have Internet at home back then. With a friend, we used the FTP at the university to download and write the 30 floppy 3 1/2 disks required to install it.

We used one of the classrooms and basically used 20 computers in parallel to fill the floppies, one copy for each of us.

Then at home I had to feed the 30 floppies back to back to install it. It was... something.

Now that may seem unusual but back then Windows 3 was distributed on a handful of floppies, and Office required up to a dozen floppies at some point.

That was way before we could afford CD readers.

A few years before that, I actually got a copy and ran MINIX on my Atari 1040STF. That only booted from 2 floppies, not bad.
(MINIX was a precursor from Linux, which Torvald learned from).
It was slow like molasses to get to the shell.
It was amazing but…
Then I realized... Why the heck am I using a multi-user environment on my home 16-bit computer?

The idea of having the computer do more than *one* thing at a time did not even make sense to me back then.