coolbloke1324

Oh forgot to add the URL to the github repo: https://github.com/Irrelon/nextjs-morph-page

Just a quick post to show a new library I put together built on top of the work here: https://github.com/illinois/next-page-transitions

This modifies the existing library and adds element morphing between pages. The elements only require the same id across pages, they do not need to be children of the same component.

It's not perfect yet but thought I'd release what I've done so far.

The link is in a serverless container that ramps up and down based on usage so if the page takes ages to load its because the container hasn't been hit in a while.

But that is the point... you don't have to store it in an underlying browser db. It runs as an in-memory store if you don't use an underlying engine. The persistence module is an optional extra and doesn't even need to be included in the library.

Should probably check the query syntax and capabilities before making a judgement?

It is similar to pouch yes, but is more mongo query friendly right now. Also ForerunnerDB includes data-binding which is a pretty useful thing for web app devs.

It's really not a wrapper around indexeddb at all. It doesn't even communicate with indexeddb except to save and load data for storage and that is optional. The main use here is for allowing web app developers to be able to load a dataset from a server and then query it dynamically on the client-side, as well as display that data automatically via data-binding.

Does sqlite run in a browser via JavaScript? I didn't think they had a JavaScript version...

Not sure I get that... localforage is a minor part of ForerunnerDB, it's certainly not "based" on it! In fact you can use ForerunnerDB entirely without localforage.

Imagine if we had to acknowledge every different module we pulled in on NPM for every project we wrote... do you do that?

> Or you might want the rich querying ability of SQL to produce detailed reports.

That is one of the best reasons for a browser based database. Imagine that your web application needs to show a list of users and then allow that list to be filtered with search or by user type or age or whatever. Instead of having to write complex logic to loop your array of user objects that you got back from your server, or ask the server directly, you can instead apply a query to the list you already have on screen and it instantly updates to reflect the query you specified...

This allows you to use an MVC pattern when creating your web applications instead of littering your code with complex locked-in logic that will suffer instant code rot and be generally a pain to maintain after a month or two of development.

Primarily I've been focussed on getting the browser side solid and reliable in production, sync is definitely on the way though. Don't forget that PouchDB is designed to work with CouchDB and not MongoDB so Mongo lovers are somewhat in the cold right now with client-side counterparts.

It includes views, triggers / change events, transforms, collection joins and data binding. Also this allows you to spend more time on interacting with data than worrying about what browser supports what storage. It is also useful even for apps that have no use for storage because looping over JS objects for specific matches in a number of areas of an app will get dirty pretty quickly.

We've built it to be compatible with Node but have focussed on browser usage for this version. Our plans (see roadmap in readme) include all the node goodness you'd expect :)

> if it's not as good at updating the DOM as other libraries

ForerunnerDB is actually very efficient at updating the DOM, only making changes to the parts of the DOM that link to altered sections of an object / document.

> Is it doing more than wrapping over IndexedDB / LocalStorage?

Yes much more... it includes views, triggers / change events, transforms, collection joins and the obvious big one - data binding.

> Maybe the value prop only really shows up when you integrate the data binding? So it's sort of like reactive programming but based on a structured data store, instead of raw JS objects?

This is correct and because we've been using it in production for some time we would definitely say it makes web app development a lot simpler!

Ooops, sorry about that, rookie mistake pulling a template and using it without going through all the sections properly. I've pulled it from the page... apologies!

Hey, could you let me know what bugs you saw and what browser you were using? Cheers!

Hey guys, appreciate the comments... I'm the dev over at www.isogenicengine.com. The demos are still works in progress and mobile support is coming soon.

I'm just one guy working on this in my spare time (I have a full-time day job too) so things move a little slower sometimes that I would like! Currently looking for investment to get a full team to help!

Regarding the Node.js requirement, there is an offline version of the engine that runs on any standard web-host. It has all the network and server-side code stripped out.

Agree that the demo page has a lot to read, but it's written for developers rather than players so tech info is there to explain what the demo is showing (and what it's not).

A much more complete demo is on it's way I promise! :)