[Seaside] Making generated links more understandable

[Lawrence Kellogg]

Thanks Lukas and Phillipe.

  It looks like this: 

updateUrl: aUrl
	super updateUrl: aUrl.
	aUrl addToPath: self class name

will give me what I want. What do you think? Any drawbacks to doing this?

  Larry


On Mar 26, 2012, at 11:41 AM, Lukas Renggli wrote:

> Hi Larry,
> 
> See this FAQ entry: http://www.seaside.st/documentation/faq/how-to#229642197.
> 
> Then you can use #updateUrl: and #addToPath: to generate path segments
> that are picked up by GA
> (http://book.seaside.st/book/in-action/session/recovering).
> 
> For pure AJAX applications a slight different approach is needed. That
> is, everything is done programmatically. Have a look at
> TextLint-Seaside (http://www.squeaksource.com/textlint) for an
> example.
> 
> Lukas
> 
> On 26 March 2012 17:33, Lawrence Kellogg <mac.hive at me.com> wrote:
>> Hello,
>>   I am running Google analytics on my site and the page information is
>> useless because it just shows the generated links which do not bear any
>> relationship to the components being called. I thought I read about some way
>> to name all of the pages but I can't seem to find that information. Is it
>> possible for me to name all of my pages so that I can see where users are
>> going on my site?
>> 
>>   Thanks,
>> 
>>   Larry
>>   www.practicemusic.com
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
> 
> 
> 
> -- 
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside