Making the gem a general purpose gem.

[khaledrepos]

I have been using motion-kit-events for a while now. I am currently building a messaging app and thought it would be nice if I can integrate this gem's functionality into a class that is not a layout. For example, when a message is received, I would trigger a :message_received event to the controller. I mean, I don't think the functionality of this gem should depend on the object being kind_of?(MK::Layout).

[jamonholmgren]

I like this idea.

[dchersey]

Is this gem still maintained? It looks very useful; the conflation of presentation and state manipulation in the standard architecture has always bugged me. While I still don't like having to write the glue code needed to surface events to the controller, I can also see how this provides another layer of indirection under my control. Perhaps a convention-over-configuration pattern could be introduced based on the control names and typical events?

[colinta]

It's maintained, though I'm stalled on working on a 2.0 version. It was probably too big of a change anyway.

But if you find bugs I'm definitely here to fix em!

On Feb 20, 2016, at 10:46 AM, David Hersey [email protected] wrote:

Is this gem still maintained? It looks very useful; the conflation of presentation and state manipulation in the standard architecture has always bugged me. While I still don't like having to write the glue code needed to surface events to the controller, I can also see how this provides another layer of indirection under my control. Perhaps a convention-over-configuration pattern could be introduced based on the control names and typical events?

―
Reply to this email directly or view it on GitHub.

[dchersey]

Awesome, thanks!
On Sat, Feb 20, 2016 at 12:24 PM Colin T.A. Gray [email protected]
wrote:

It's maintained, though I'm stalled on working on a 2.0 version. It was
probably too big of a change anyway.

But if you find bugs I'm definitely here to fix em!

On Feb 20, 2016, at 10:46 AM, David Hersey [email protected]
wrote:

Is this gem still maintained? It looks very useful; the conflation of
presentation and state manipulation in the standard architecture has always
bugged me. While I still don't like having to write the glue code needed to
surface events to the controller, I can also see how this provides another
layer of indirection under my control. Perhaps a
convention-over-configuration pattern could be introduced based on the
control names and typical events?

―
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.