<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content=text/html;charset=iso-8859-1>
<STYLE type=text/css><!-- DIV {margin:0px;} --></STYLE>
<META content="MSHTML 6.00.6002.18332" name=GENERATOR></HEAD>
<BODY id=MailContainerBody
style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px" leftMargin=0
topMargin=0 CanvasTabStop="true" name="Compose message area">
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Hope that helps</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Matt Priour</FONT></DIV>
<DIV><FONT face=Arial size=2>Kestrel Computer Consulting</FONT></DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=robertdbuckley@yahoo.com
href="mailto:robertdbuckley@yahoo.com">Robert Buckley</A> </DIV>
<DIV><B>Sent:</B> Monday, January 24, 2011 2:23 AM</DIV>
<DIV><B>To:</B> <A title=users@geoext.org
href="mailto:users@geoext.org">users@geoext.org</A> </DIV>
<DIV><B>Subject:</B> [Users] Advice regarding optimization and
debugging</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 8pt; FONT-FAMILY: arial,helvetica,sans-serif">Good
Morning,<BR><BR>Could someone please offer some advice
regarding...<BR><BR><BR>1. How to successfully reduce the loading time of a
geoext/openlayers project.<BR>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?<BR><BR>2. Debugging a project.<BR>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?<BR><BR><BR>Thanks for any
replies/comments/suggestions,<BR><BR>Yours,<BR><BR>Robert
Buckley<BR> <BR>
<DIV><BR></DIV></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Users mailing
list<BR>Users@geoext.org<BR>http://www.geoext.org/cgi-bin/mailman/listinfo/users<BR></BODY></HTML>