Plugin Permission (new plugin)

[Konstantinos Kostarellis]

Hi,

 I'd like to release a new plugin. Its basically a resources wrapper for jGrowl.

It offers an resource definition and a taglib both providing the needed resources.

The plugin provides the resources uncompressed in dev-mode and compressed else ways.

Sources and docs:

https://github.com/delight/grails-jgrowl

grais.org-username is: kosta

Thnx,

   Kosta

[Konstantinos Kostarellis]

Approved / Denied ??

2012/8/13 Konstantinos Kostarellis <[hidden email]>

Hi,

 I'd like to release a new plugin. Its basically a resources wrapper for jGrowl.

It offers an resource definition and a taglib both providing the needed resources.

The plugin provides the resources uncompressed in dev-mode and compressed else ways.

Sources and docs:

https://github.com/delight/grails-jgrowl

grais.org-username is: kosta

Thnx,

   Kosta

[pledbrook]

> Approved / Denied ??

Sorry, missed this. Is the plugin significantly different from
http://grails.org/plugin/growler ?

--
Peter Ledbrook
Developer Advocate
VMware

t: @pledbrook

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Konstantinos Kostarellis]

Hi Peter,

looked into the growler-plugin >> It is not significantly different.

I just got a bit cleaner approach to the resources and I'm not extending g.remoteFunction.

In the SoC-Sense I'd prefer a separation of the plugin into jgrowl (simply resources) and growler (a plugin with dependency on jgrowl extending the remoteFunction functionality + possibly more). I can do this refactoring/maintenance if it is desired. The growler plugin itself seems unmaintained and has some open issues...

If you think this is not appropriate, then thats good too ;)

Cheers,

   Kosta

2012/8/17 Peter Ledbrook <[hidden email]>

> Approved / Denied ??

Sorry, missed this. Is the plugin significantly different from
http://grails.org/plugin/growler ?

--
Peter Ledbrook
Developer Advocate
VMware

t: @pledbrook

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> looked into the growler-plugin >> It is not significantly different.
> I just got a bit cleaner approach to the resources and I'm not extending
> g.remoteFunction.
>
> In the SoC-Sense I'd prefer a separation of the plugin into jgrowl (simply
> resources) and growler (a plugin with dependency on jgrowl extending the
> remoteFunction functionality + possibly more). I can do this
> refactoring/maintenance if it is desired. The growler plugin itself seems
> unmaintained and has some open issues...

I don't know that there is a significant advantage to splitting them,
but whatever you'd prefer. It would be good to reach out to the
Growler folks if possible. If we can't get a response out of them, we
can give you permission to release a new version.

Peter

--
Peter Ledbrook
Developer Advocate
VMware

t: @pledbrook

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email