[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-user
Subject:    RE: [groovy-user] Reverse compiling a markup builder?
From:       "Jeremy Sager" <jsager () chessys ! com>
Date:       2007-01-31 18:23:55
Message-ID: 200701311317195.SM02196 () JASLAPTOP
[Download RAW message or body]

I thought about that as well, the concern is whether you'd be getting
hostile code from someone, which I guess would be totally possible inside of
GUI code anyway, so I haven't really gained anything.

I'm envisioning in my mind a groovy browser similar to a web browser, where
you'd type in an address and a program would launch.

-----Original Message-----
From: Pascal DeMilly [mailto:list.groovy@newgenesys.com] 
Sent: Wednesday, January 31, 2007 1:04 PM
To: Groovy User
Subject: Re: [groovy-user] Reverse compiling a markup builder?

Very similar idea to what I have been working on in my spare time.

Why not just send the groovy code (as source) and have groovy compile it in 
place on the client. The only thing you would need is groovy on the client 
which can be pushed by webstart or OSGi.

On Wednesday 31 January 2007 08:46, Furash Gary wrote:
> Wouldn't it be better to use complex combinations of javascript and
> server side code like we do with ajax :-)
>
> -----Original Message-----
> From: Jeremy Sager [mailto:jsager@chessys.com]
> Sent: Wednesday, January 31, 2007 9:32 AM
> To: user@groovy.codehaus.org
> Subject: RE: [groovy-user] Reverse compiling a markup builder?
>
> I have an interesting idea.
>
> Using that technique to get the string back, I could then prepend a
> couple of lines of groovy code, switching out a swing or swt builder in
> place of the Markup builder and evaluate the string as groovy code.
>
> This would allow me to launch a swing/swt user interface in a "thin"
> fashion, assuming that the XML was coming from some remote place.
>
> I find it very interesting, because it would take a lot of the
> advantages of a thin client (always guaranteeing the client is on the
> latest version, not having to actually install anything outside of the
> "groovy application browser", not having the terrible "up front" costs
> of Java Web Start), yet give me all the power that rich clients such as
> SWT and Swing have to offer.
>
> Sending little XML files via something like RMI shouldn't be any worse
> than loading web pages.
>
> -----Original Message-----
> From: Dierk Koenig [mailto:dierk.koenig@canoo.com]
> Sent: Wednesday, January 31, 2007 10:50 AM
> To: user@groovy.codehaus.org
> Subject: RE: [groovy-user] Reverse compiling a markup builder?
>
> I haven't checked, but from the top of my head I would say you can use
> XmlParser and NodePrinter.
>
> ciao
> Dierk
>
> > -----Original Message-----
> > From: Jeremy Sager [mailto:jsager@chessys.com]
> > Sent: Mittwoch, 31. Januar 2007 16:12
> > To: user@groovy.codehaus.org
> > Subject: [groovy-user] Reverse compiling a markup builder?
> >
> >
> > I was wondering if there is any way to "reverse compile" the XML
> > generated by markup builder.
> >
> > Let me explain.
> >
> > The code:
> >
> > Builder.a{
> > 	b(key:"value")
> > }
> >
> > Should generate the xml
> >
> > <a>
> > <b key=value>
> > </b>
> > </a>
> >
> > Unless I'm mistaken, anyway. Is there any already existing way to
> > examine the XML file and get back a string containing the code that
> > would have generated the markup?
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >     http://xircles.codehaus.org/manage_email
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email


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

    http://xircles.codehaus.org/manage_email

[prev in list] [next in list] [prev in thread] [next in thread]