Thanks for this David. I spent a few hours adapting your Om tutorials to an
app that reads and edits ID3 media tag metadata coming from the server
side, I'll try adapting it to use om-sync.
Good to see obviously reusable stuff such as your edn-xhr helper getting
the "util" treatment as well.
Thanks for the note about operational transform (OT). I had not heard of it
before. From some casual reading, OT appears to focus on the problem of
collaborative document editing. I assume that Share.js extends this to
structured json? This is definitely something I think a lot of people would
I'm interested in this thread, it does seem however that DerbyJS is farther
ahead in this type of work though. I was looking for a similar JVM stack,
but not sure how to put it together as well. Atmosphere seems like it fits
for the basic communication even including pubsub. Derby updates the v
(Dave and I work together).
I suspect it will be easy to come to a reasonable license. My own
preferences would be EPL or MIT, and EPL only because it's common in the
community.
Beyond that, something like chord isn't actually the big problem in a
scheme like this. The real issue is ensuring
On Thursday, 20 February 2014 13:56:29 UTC+8, David Della Costa wrote:
>
> > It's not clear to me that the server side should be tied to Om
> > specifically. It seems like the requirement is more to have a server
> > component that can pass messages / state changes in a generic way to
> > clie
> It's not clear to me that the server side should be tied to Om
> specifically. It seems like the requirement is more to have a server
> component that can pass messages / state changes in a generic way to
> clients (probably using core.async channels, with the ability to use
> websockets etc. as
Conrad,
Ui library modeled after bootstrap or foundation with rewritten widgets
compatible with advanced mode.
Or Pure from yahoo.This one does not comes with js and it is very light
On Saturday, February 15, 2014 11:26:18 PM UTC-2, Conrad Barski wrote:
> On Thursday, February 13, 2014 8:55:00
On Sunday, 16 February 2014 09:26:18 UTC+8, Conrad wrote:
>
> On Thursday, February 13, 2014 8:55:00 PM UTC-6, David Nolen wrote:
> > I've been banging the drum about Om & modularity for a while now and
> I've come up with the very beginning of a simple reusable component that I
> think demons
On Thursday, February 13, 2014 8:55:00 PM UTC-6, David Nolen wrote:
> I've been banging the drum about Om & modularity for a while now and I've
> come up with the very beginning of a simple reusable component that I think
> demonstrates the power of Om's emphasis on modularity and application wid
I've been banging the drum about Om & modularity for a while now and I've
come up with the very beginning of a simple reusable component that I think
demonstrates the power of Om's emphasis on modularity and application wide
state management:
http://github.com/swannodette/om-sync
The whole point
10 matches
Mail list logo