Gothic Alpha - Revision history

Adamcolton at 19:36, 1 February 2016

2016-02-01T19:36:28Z

← Older revision		Revision as of 19:36, 1 February 2016
Line 6:		Line 6:

	https://github.com/mitchellh/mapstructure		https://github.com/mitchellh/mapstructure

			I'll use [http://www.gorillatoolkit.org/ Gorilla] for most of the web stuff.

	== Thought Experiment ==		== Thought Experiment ==

Adamcolton at 15:50, 22 January 2016

2016-01-22T15:50:17Z

← Older revision		Revision as of 15:50, 22 January 2016
Line 6:		Line 6:

	https://github.com/mitchellh/mapstructure		https://github.com/mitchellh/mapstructure

			== Thought Experiment ==
			From a dev-dashboard, a user should be able to define a simple schema. This will include fields, types and validation rules. This schema will then be implemented as an Entity. This will produce:

			* Go Struct
			* Lapiz Class
			* REST CRUD API
			* Views
			** form partial
			** edit wrapper
			** create wrapper
			** view many
			** view one

	== Objects ==		== Objects ==

Adamcolton at 15:35, 22 January 2016

2016-01-22T15:35:29Z

← Older revision		Revision as of 15:35, 22 January 2016
Line 4:		Line 4:

	https://github.com/boltdb/bolt via https://www.specto.io/replacing-redis-with-boltdb-a-pure-go-keyvalue-store/		https://github.com/boltdb/bolt via https://www.specto.io/replacing-redis-with-boltdb-a-pure-go-keyvalue-store/

			https://github.com/mitchellh/mapstructure

	== Objects ==		== Objects ==

Adamcolton at 00:48, 22 January 2016

2016-01-22T00:48:13Z

← Older revision		Revision as of 00:48, 22 January 2016
Line 14:		Line 14:
	=== Indexing ===		=== Indexing ===
	One of the big challenges is indexing. I think the right approach is not do it right away, but see what comes up.		One of the big challenges is indexing. I think the right approach is not do it right away, but see what comes up.

			=== Derive from Go ===
			I could derive anything I need form the Go structs. Using reflect, I could get the fields and types. From there I could generate a schema. I'd need a way to modify it for the db and for JS. But for a basic object graph with simple validation, it could be very easy.

	== JS ==		== JS ==

Adamcolton at 16:55, 11 January 2016

2016-01-11T16:55:08Z

← Older revision		Revision as of 16:55, 11 January 2016
Line 3:		Line 3:
	The goal here is to get something that works, but maybe not everything I want.		The goal here is to get something that works, but maybe not everything I want.

	https://github.com/boltdb/bolt		https://github.com/boltdb/bolt via https://www.specto.io/replacing-redis-with-boltdb-a-pure-go-keyvalue-store/

	== Objects ==		== Objects ==

Adamcolton at 16:54, 11 January 2016

2016-01-11T16:54:54Z

← Older revision		Revision as of 16:54, 11 January 2016
Line 2:		Line 2:

	The goal here is to get something that works, but maybe not everything I want.		The goal here is to get something that works, but maybe not everything I want.

			https://github.com/boltdb/bolt

	== Objects ==		== Objects ==

Adamcolton at 20:07, 29 December 2015

2015-12-29T20:07:32Z

← Older revision		Revision as of 20:07, 29 December 2015
Line 7:		Line 7:

	I think for this, I will start with [https://capnproto.org/index.html Capn Proto]. Pair that with and Entity system. The Entity interface just needs to return an ID.		I think for this, I will start with [https://capnproto.org/index.html Capn Proto]. Pair that with and Entity system. The Entity interface just needs to return an ID.

			The other option would be protocol buffers. On the server, I can extend them by embedding.

			=== Indexing ===
			One of the big challenges is indexing. I think the right approach is not do it right away, but see what comes up.

	== JS ==		== JS ==

Adamcolton at 20:00, 29 December 2015

2015-12-29T20:00:18Z

← Older revision		Revision as of 20:00, 29 December 2015
Line 14:		Line 14:

	I may also pull in GopherJS, but that needs a little further exploration.		I may also pull in GopherJS, but that needs a little further exploration.

			[[Category:Code]]
			[[Category:Project]]

Adamcolton: Created page with "Laying the ground work for Gothic. The goal here is to get something that works, but maybe not everything I want. == Objects == This is the core of the whole thing. I wa..."

2015-12-29T19:57:03Z

Created page with "Laying the ground work for Gothic. The goal here is to get something that works, but maybe not everything I want. == Objects == This is the core of the whole thing. I wa..."

New page

Laying the ground work for [[Gothic]].

The goal here is to get something that works, but maybe not everything I want.

== Objects ==
This is the core of the whole thing. I want a simple way to have objects on the server be stored or sent to the client.

I think for this, I will start with [https://capnproto.org/index.html Capn Proto]. Pair that with and Entity system. The Entity interface just needs to return an ID.

== JS ==
I need to support as much JS integration as possible. Objects should be automatically exported, so that the only JS work is adding front-end features.

I'll probably use some Lapiz here too - the event system work well with websockets.

I may also pull in GopherJS, but that needs a little further exploration.