I have heard many comments from new developers on wave who were trying to modify or add these kinds of pages struggling with figuring out how to use GXP. I guess this is in part due to the lack of documentation. Is GXP widely used outside of Google? I had not heard of it until I got involved with WiaB.
~Michael On May 14, 2011, at 4:31 PM, James Purser wrote: > I can +1 the bit about poor documentation > > On Sat, May 14, 2011 at 2:54 AM, Yuri Z <[email protected]> wrote: > >> I think that the main advantage is that GXP verifies the HTML so it ensures >> that if gxp templates compiles then the HTML is valid. Also it is more >> secure. >> The greatest issue with GXP is very poor documentation. >> 2011/5/13 Michael MacFadden <[email protected]> >> >>> All, >>> >>> I am not advocating a change at all, just looking for some info... >>> >>> I noticed that we use the Google XML Pages (GXP) technology for some of >> the >>> UI in WiaB. I understand why you would want to use a template based >>> solution rather than raw servlest writing HTML. I also know what the >>> benefits are over traditional JSP pages. >>> >>> However, what are the advantages of GXP over something like Apache >>> Velocity? Just looking to understand. Thanks. >>> >>> >>> ~Michael >> > > > > -- > James Purser > Collaborynth > http://collaborynth.com.au > Mob: +61 406 576 553 > Wave: [email protected]
