and for browsers without a console.log, use Firebug Lite:
http://getfirebug.com/firebuglite
--
http://twitter.com/broady
On Thu, Jun 23, 2011 at 1:37 PM, James McGill wrote:
> Consider developing in Chrome with the Chrome developer tools. I find
> them much more responsive.
>
> Regards,
> Jam
Consider developing in Chrome with the Chrome developer tools. I find
them much more responsive.
Regards,
James
On Tue, Jun 21, 2011 at 5:46 PM, RoyHB wrote:
> Thanks Larry - back to the buggy world of Firebug for me
>
> Roy
>
> --
> You received this message because you are subscribed to the Go
Thanks Larry - back to the buggy world of Firebug for me
Roy
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To post to this group, send email to google-maps-js-api-v3@googlegroups.com.
To unsubscribe from this group, send emai
On Jun 21, 12:01 am, RoyHB wrote:
> I'm in the heat of battle adapting our complex application from V2 to V3.
>
> It seems that GLog.write didn't make it into the new API.
> In the past I found GLog.write to be a very handy low tech debugging tool.
> I understand I can
> do the same thing with F
