Huginn as a mountable engine?

[oponder]

Hi, I love this project and the direction its going in. Very cool!

I was wondering, is there any place in its future for turning it into a gem that is mountable as an engine?

That way we could add huginn awesomeness to already existing rails applications. It would allow for a great standardised way to let users add and configure behaviour that the developer didn't think of yet.

Like imagine if you could add huginn to locomotivecms, which lets admins set up a quick contact form. Then you could suddenly expand what that contact form could do. Right now it just sends an email to the admin, but with huginn mounted on locomotive, it could do something more interesting!

Anyways, I realise that this is a pretty big restructuring of things, but just wanted to start a conversation.

I feel like this kind of automated tasks configurability is super handy, and it would be awesome to make it easy to use in other projects too.

Another possibility of course is to have huginn turn into a centralised event receiver (as alluded to in the future of huginn / huginn protocol discussion), and then creating a separate gem which makes it easy for any rails apps to generate events.

But what I really like is the interface, and that it lets a non programmer define what happens. I think that it's a very powerful and understandable concept.

[0xdevalias]

I believe @cantino was thinking about this concept at one point. I definitely think it's a cool idea!—
Sent from Mailbox

On Tue, Aug 12, 2014 at 2:52 AM, Oliver Nicolaas Ponder
notifications@github.com wrote:

Hi, I love this project and the direction its going in. Very cool!
I was wondering, is there any place in its future for turning it into a gem that is mountable as an engine?
That way we could add huginn awesomeness to already existing rails applications. It would allow for a great standardised way to let users add and configure behaviour that the developer didn't think of yet.
Like imagine if you could add huginn to locomotivecms, which lets admins set up a quick contact form. Then you could suddenly expand what that contact form could do. Right now it just sends an email to the admin, but with huginn mounted on locomotive, it could do something more interesting!
Anyways, I realise that this is a pretty big restructuring of things, but just wanted to start a conversation.
I feel like this kind of automated tasks configurability is super handy, and it would be awesome to make it easy to use in other projects too.
Another possibility of course is to have huginn turn into a centralised event receiver (as alluded to in the future of huginn / huginn protocol discussion), and then creating a separate gem which makes it easy for any rails apps to generate events.

But what I really like is the interface, and that it lets a non programmer define what happens. I think that it's a very powerful and understandable concept.

Reply to this email directly or view it on GitHub:
#438

[cantino]

Welcome @oponder! That is something we're thinking about. We're also thinking about the future of Scenarios here: c7cd070

[oponder]

I'm gonna go ahead and close this, seeing as it is a bit old, and I don't have anything concrete to add :)