You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Al Sutton <al...@alsutton.com> on 2008/08/26 16:04:05 UTC
Google Dev Day
Guys,
I'm going to be going to Googles Dev Day in London in mid-September, is
there anything anyone wants me to get info on given the recent GXP
discussions, etc.?
Al.
--
Al Sutton
W: www.alsutton.com
B: alsutton.wordpress.com
T: twitter.com/alsutton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Google Dev Day
Posted by Al Sutton <al...@alsutton.com>.
Unfortunately I didn't get to meet any GXP guys, but I did see some very
interesting GWT and Gears demos which mean I'm definately going to take
a deeper look at them.
Musachy Barroso wrote:
> Yes, take a look here:
>
> http://svn.apache.org/viewvc/struts/sandbox/trunk/struts2-gxp-plugin/src/main/resources/template/simple/
>
> To create an image tag with gxp you could do something like:
>
> <img src="user.gif">
> <gxp:attr name='alt'>
> <gxp:eval expr="user.getName()"/>
> </gxp:attr>
> </img>
>
> now, in the start tag file we would have:
>
> <img src="user.gif">
> <gxp:attr name='alt'>
> <gxp:eval expr="user.getName()"/>
> </gxp:attr>
>
> and in the end tag file we would have:
>
> </img>
>
> GXP doesn't like that. We could get rid of the opening/closing tag and
> just have one tag file that inserts the tag body. Does that make some
> sense?
> musachy
>
>
> On Tue, Aug 26, 2008 at 2:55 PM, Al Sutton <al...@alsutton.com> wrote:
>
>> Have you got your code up somewhere, I'd like to take a look so I know what
>> I'd be commenting on (and I can take a copy on a laptop).
>>
>> Thanks,
>>
>> Al.
>>
>> Musachy Barroso wrote:
>>
>>> Yes, in fact I have been having some trouble trying to implement the
>>> tags with gxp. The problem is that out tags are splitted in 2 files,
>>> the open tag is in one and the close tag is in the other. GXP doesn't
>>> like this, as the xml won't be well formed on each individual
>>> template. You could get some suggestions on what would be the best way
>>> of doing this.
>>>
>>> musachy
>>>
>>> On Tue, Aug 26, 2008 at 10:04 AM, Al Sutton <al...@alsutton.com>
>>> wrote:
>>>
>>>
>>>> Guys,
>>>>
>>>> I'm going to be going to Googles Dev Day in London in mid-September, is
>>>> there anything anyone wants me to get info on given the recent GXP
>>>> discussions, etc.?
>>>>
>>>> Al.
>>>> --
>>>> Al Sutton
>>>>
>>>> W: www.alsutton.com
>>>> B: alsutton.wordpress.com
>>>> T: twitter.com/alsutton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Google Dev Day
Posted by Musachy Barroso <mu...@gmail.com>.
Yes, take a look here:
http://svn.apache.org/viewvc/struts/sandbox/trunk/struts2-gxp-plugin/src/main/resources/template/simple/
To create an image tag with gxp you could do something like:
<img src="user.gif">
<gxp:attr name='alt'>
<gxp:eval expr="user.getName()"/>
</gxp:attr>
</img>
now, in the start tag file we would have:
<img src="user.gif">
<gxp:attr name='alt'>
<gxp:eval expr="user.getName()"/>
</gxp:attr>
and in the end tag file we would have:
</img>
GXP doesn't like that. We could get rid of the opening/closing tag and
just have one tag file that inserts the tag body. Does that make some
sense?
musachy
On Tue, Aug 26, 2008 at 2:55 PM, Al Sutton <al...@alsutton.com> wrote:
> Have you got your code up somewhere, I'd like to take a look so I know what
> I'd be commenting on (and I can take a copy on a laptop).
>
> Thanks,
>
> Al.
>
> Musachy Barroso wrote:
>>
>> Yes, in fact I have been having some trouble trying to implement the
>> tags with gxp. The problem is that out tags are splitted in 2 files,
>> the open tag is in one and the close tag is in the other. GXP doesn't
>> like this, as the xml won't be well formed on each individual
>> template. You could get some suggestions on what would be the best way
>> of doing this.
>>
>> musachy
>>
>> On Tue, Aug 26, 2008 at 10:04 AM, Al Sutton <al...@alsutton.com>
>> wrote:
>>
>>>
>>> Guys,
>>>
>>> I'm going to be going to Googles Dev Day in London in mid-September, is
>>> there anything anyone wants me to get info on given the recent GXP
>>> discussions, etc.?
>>>
>>> Al.
>>> --
>>> Al Sutton
>>>
>>> W: www.alsutton.com
>>> B: alsutton.wordpress.com
>>> T: twitter.com/alsutton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Google Dev Day
Posted by Al Sutton <al...@alsutton.com>.
Have you got your code up somewhere, I'd like to take a look so I know
what I'd be commenting on (and I can take a copy on a laptop).
Thanks,
Al.
Musachy Barroso wrote:
> Yes, in fact I have been having some trouble trying to implement the
> tags with gxp. The problem is that out tags are splitted in 2 files,
> the open tag is in one and the close tag is in the other. GXP doesn't
> like this, as the xml won't be well formed on each individual
> template. You could get some suggestions on what would be the best way
> of doing this.
>
> musachy
>
> On Tue, Aug 26, 2008 at 10:04 AM, Al Sutton <al...@alsutton.com> wrote:
>
>> Guys,
>>
>> I'm going to be going to Googles Dev Day in London in mid-September, is
>> there anything anyone wants me to get info on given the recent GXP
>> discussions, etc.?
>>
>> Al.
>> --
>> Al Sutton
>>
>> W: www.alsutton.com
>> B: alsutton.wordpress.com
>> T: twitter.com/alsutton
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Google Dev Day
Posted by Musachy Barroso <mu...@gmail.com>.
Yes, in fact I have been having some trouble trying to implement the
tags with gxp. The problem is that out tags are splitted in 2 files,
the open tag is in one and the close tag is in the other. GXP doesn't
like this, as the xml won't be well formed on each individual
template. You could get some suggestions on what would be the best way
of doing this.
musachy
On Tue, Aug 26, 2008 at 10:04 AM, Al Sutton <al...@alsutton.com> wrote:
> Guys,
>
> I'm going to be going to Googles Dev Day in London in mid-September, is
> there anything anyone wants me to get info on given the recent GXP
> discussions, etc.?
>
> Al.
> --
> Al Sutton
>
> W: www.alsutton.com
> B: alsutton.wordpress.com
> T: twitter.com/alsutton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org