[Users] Advice regarding optimization and debugging
geographika
geographika at gmail.com
Mon Jan 24 17:17:15 CET 2011
Along with what others have said:
<http://www.jsonlint.com/>
* http://www.jsonlint.com/ - for validating any JSON that comes from
a server
* Fiddler - for rerunning Ajax calls
* http://code.google.com/closure/ - for minifying production code
(and as another check of code quality)
* making sure gzip is set up on your server.
* The ExtJS docs - http://dev.sencha.com/deploy/dev/doc
<http://dev.sencha.com/deploy/dev/docs/>s/
<http://dev.sencha.com/deploy/dev/docs/>
* Also I am testing a trial version of
http://www.illuminations-for-developers.com/product/debugger/
Plus writing:
debugger;
In JavaScript files to automatically create a breakpoint in FireFox to
check what exactly is happening.
Regards,
Seth G.
http://geographika.co.uk
On 24/01/2011 16:23, Matt Priour wrote:
> 1. Develop with full library, & I tend to use the full debug versions.
> Yes, it makes your code load much slower and the 20-30s page reload
> times can get tiresome, but if you encounter an error, using the debug
> versions will let you find where you are going wrong.
> 2. IE8 & IE9 have built-in debugger that is very similar to the WebKit
> (Safari / Chrome) Developer Tools. If you want even more control and
> want a full featured debug environment, Visual Studio Web Developer
> Express is an EXCELLENT debugger. VS WebDev Express is available for
> free from Microsoft (along with all their other "Express" products). I
> wish there was a way to get it to attach to non-IE browsers because it
> is a truly awesome debugger. You can use the VS debugger in IE7 &
> (good god, no!!!) IE6 as well which don't have an integrated debugger.
> Hope that helps
> Matt Priour
> Kestrel Computer Consulting
>
> *From:* Robert Buckley <mailto:robertdbuckley at yahoo.com>
> *Sent:* Monday, January 24, 2011 2:23 AM
> *To:* users at geoext.org <mailto:users at geoext.org>
> *Subject:* [Users] Advice regarding optimization and debugging
>
> Good Morning,
>
> Could someone please offer some advice regarding...
>
>
> 1. How to successfully reduce the loading time of a geoext/openlayers
> project.
> I am aware that the loading time of these libraries takes up to
> between 5 - 10 seconds. Therefore... should I look through my code
> after the project is completed and note which controls have been used
> and then create a customized openlayers js library or do you generally
> plan a project with the tools and controls already defined and create
> the openlayers.js before you start programming? In my experience
> (which is very limited) I start programming with the whole
> openlayers/geoext/ext libraries so that when I need to add something
> which was not planned before hand, I don´t have to worry about loading
> new code into the js library. Assuming this is the way most
> programmers start, which method do you use to remove unused scripts?
>
> 2. Debugging a project.
> I am using Aptana (free version) and firefox with firebug to develop.
> This combination works great....until I open the project with Internet
> Explorer and discover that nothing works! Does anyone have any tips
> regarding writing code which can be used to simultaneously debug in
> Firefox and IE? I find that most errors are forgotten commas, but
> occasionally there are undfined objects which show up in the ie
> developer tool bar as errors in the openlayers.js code. These errors
> are the worst as there is not direct link to the code in my own
> scripts? Does anyone have any IE debugging tools which help? How do
> you get around these problems? Anyone used Chrome to debug?
>
>
> Thanks for any replies/comments/suggestions,
>
> Yours,
>
> Robert Buckley
>
>
>
> ------------------------------------------------------------------------
> _______________________________________________
> Users mailing list
> Users at geoext.org
> http://www.geoext.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at geoext.org
> http://www.geoext.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.geoext.org/pipermail/users/attachments/20110124/0405dccc/attachment-0001.htm
More information about the Users
mailing list