brroseOP•

Hey guys,

I put together a quick meteor + easel.js example where I wrap the existing easel.js classes to permit for persistent entities in mongodb.

It sounds a lot more complex than it actually is and it's somewhat sloppy (and stage isn't even wrapped properly) but I wanted to get some feedback on this because I think it could be neat.

It would allow for regular entities to be drawn and not persisted to the database as well as entities that have attributes persisted. Everything could be reactive (only x,y and src are for now) and I included a server side rule just for laughs.

Thoughts? Has anyone done this yet?

6
FreefallGeek•

You just saved me so much time. I was wondering how I was going to do this and you've laid a lot of groundwork. Thanks for sharing.

2
brroseOP•

Feel free to fork and/or discuss ideas with me!

I feel like it'd be harder to not capture a lot of the initial complexity in the framework.

I'd be thrilled to have people helping take this from an example to a v0.0.1 :)

1
FridaG•

i haven't done that, pretty cool!

2
svenhof•

Please correct me if I'm wrong but are you saving the x and y to the database on every mouseMove event?

1
brroseOP•

Yup. If you were making a real app, this wouldn't be a good example. A better example would be a game of tic-tac-toe.

1
Hapistoric•

I haven't looked at the app but couldn't you save x,y to a local collection and then save it every x ms in the real database for efficiency?

Surprisingly smooth!

In localhost, but would it work as a real app?

1