[OpenLayers-Users] why is your code entirely lacking in whitespace

[Tim Langlois]

There is always a silver lining.  Because of this thread, I learned how
to create the compressed js file :)  Now, I can check that off my list
of things to do :)

On Tue, 2007-05-15 at 10:34 -0400, Michael Frumin wrote:
> No, I'm just an idiot who still hasn't learned the lesson of going to
> sleep when it's actually his bedtime.  I had actually downloaded the
> distribution and was looking for code with something like "find
> OpenLayers-2.4-rc3/ | xargs grep Icon | grep new" which  was yielding
> bits of good code from lib/* in between masses of compressed code from
> the OpenLayers.js files.  
> 
> Hasty as usual, so I hope everyone will accept my apology.  I can only
> hope to redeem myself by noting that I'll be publishing what I'm
> working on as an example of how to subclass the WFS and do something
> app-specific, in this case make a WFS layer for geocoded pictures,
> where the icon is the picture itself.
> 
> thanks, and sorry again,
> mike
> 
> crschmidt at metacarta.com wrote: 
> > On Mon, May 14, 2007 at 10:05:15PM -0700, mfrumin wrote:
> >   
> > > > it is often useful to look at the code in the libraries to figure out how to
> > > >       
> > > do do stuff.  unfortunately, it lacks any sane whitespacing scheme, and is
> > > impossible to peruse.  eg (from
> > > http://openlayers.org/api/2.4-rc3/OpenLayers.js or the OpenLayers.js that
> > > comes in the download):
> > >     
> > 
> > The OpenLayers code is a set of 98 files, in the 'lib' directory of the
> > distribution. What you are looking at is the 'compressed' version of the
> > code -- due to the way browsers work, downloading those 98 files will
> > take in excess of 60 seconds. Compressing it into one file saves those
> > 60 seconds, making it more like 2 or 3.
> > 
> > If you make a modification to the code in the 'lib' directory, then run
> > the './build.py' script in the build directory, you will get the
> > 'compressed' version you are looking at, suitable for deployment, rather
> > than for readability. If you wish to modify code, you should *not* touch
> > the compressed code, and instead edit what is in lib/ and run
> > ./build.py. (The functionality of this script is described in
> > http://trac.openlayers.org/wiki/Profiles .) Note that it is also
> > possible to use the non-compressed code in your page, useful for
> > debugging: just include lib/OpenLayers.js in your code directly.
> > 
> >   
> > > does that look helpful to you?  clean your stuff up, then maybe when we have
> > > bugs we can possibly help report where they might be coming from.
> > >     
> > 
> > It's impolite to attack the project without taking the time to
> > understand what's happening. I understand that our documentation is
> > weak, but we do have this covered relatively well, and I've never had
> > anyone ask this particular question before, so I'm not sure how we could
> > have made it easier for you. Where should we link this description from
> > so that you would have found it?
> > 
> > Regards,
> > -- Christopher Schmidt
> > MetaCarta
> >   
> _______________________________________________
> Users mailing list
> Users at openlayers.org
> http://openlayers.org/mailman/listinfo/users

The information transmitted is the property of Archetype, Inc. and is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Statements and opinions expressed in this e-mail may not represent those of the company.  Any review, retransmission, dissemination and other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, received late or incomplete, or could contain viruses. The sender therefore does not accept liability for any error or omission in the contents of this message, which arises as a result of e-mail transmission.