[Seaside] debugging javascript within browsers is hard when the browser show the response on a single line

[Johan Brichau]

But apart from that, I think it would be a great option to be able to choose for 'minified' or 'non minified' generated javascript in Seaside…

On 07 Aug 2011, at 13:18, Johan Brichau wrote:

> Hi Nick,
> 
> Ah yes...
> It's not missing. It's now called 'pretty print' and is the '{ }' button in the bottom bar of dev tool.
> 
> Prior to that, I had no workarounds, but most (90%) of our javascript code is contained in external files, which show nicely in the scripts pane (when not minified).
> 
> Johan
> 
> On 07 Aug 2011, at 13:11, Nick Ager wrote:
> 
>> Hi Johan,
>>  
>> In the latest Chrome, you can choose to 'de-obfuscate source' in the context menu of the script tab in the developer tools.
>> That solves it mostly for me.
>> 
>> Hmm I'm using Chrome version 13.0.782.107 which doesn't seem to include 'de-obfuscate source' option and it seems it's missing for others: http://www.google.com/support/forum/p/Chrome/thread?tid=648734bd79c17a69&hl=en
>> 
>> Pior to the 'de-obfuscate source'  option - did you have any other work-arounds?
>> 
>> Nick
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110807/3ecaf190/attachment.htm