[Greasemonkey] Introducing Monkeygrease: The Server-Side
Greasemonkey
Rich Manalang
rich.manalang at gmail.com
Mon Nov 7 17:31:47 EST 2005
I think you're right about the server-side vs. proxy concept. Thanks for the
advice.
Rich
On 11/7/05, Jeremy Dunck <jdunck at gmail.com> wrote:
>
> On 11/7/05, Rich Manalang <rich.manalang at gmail.com> wrote:
> > simple little
> > servlet filter I've been working on called Monkeygrease (
> > http://monkeygrease.org). It's basically a server-side Greasemonkey for
> J2EE
> > web apps.
> ...
> > Anyway... just thought some in the Greasemonkey community might be
> > interested.
>
> Yep, I am. My company has several closed-source J2EE consultantwares
> and I can see this being useful for improving UI for productivity.
> Greasemonkey doesn't work so well in that context because 1) the apps
> are IE-only, 2) the users go through Citrix, which I don't have
> control over, and 3) they're freaked out by the flicker of late
> injection.
>
> One piece of advice, though... the concept of a server-side GM (as
> opposed to proxy GM) didn't fit my brain at first.
>
> As the elevator pitch, how about:
> "Monkeygrease allows you to alter the output of closed-source J2EE web
> apps before it is sent to the client." Then list the examples.
>
> I don't think the "like greasemonkey, but not in the user's control"
> will go over well. :)
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkey at mozdev.org
> http://mozdev.org/mailman/listinfo/greasemonkey
>
More information about the Greasemonkey
mailing list