<div><div><span style>(resending, forgot to reply all)</span></div><span style><div><br></div>That's a larger problem: OpenLayers, the website, and the docs, doesn't talk about its modularity and what you do when when you don't have a component, or how you check to see if you have a component. That docs issue needs to be fixed, not avoided.</span><div style>
<br></div><div style>Enough with the filesize comparisons to WMS tiles or whatever; OpenLayers is a behemoth compared to other Javascript libraries - it's several times the size of jQuery, Backbone, Leaflet, and whatever else users have tried out, and for reasons that totally don't matter to 90% of users. OpenLayers is 177kb gzipped - that's 6x jQuery.</div>
</div><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 1:00 PM, Andreas Hocevar <span dir="ltr"><<a href="mailto:ahocevar@opengeo.org">ahocevar@opengeo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I can already smell the questions on the mailing list and elsewhere<br>
from people finding something not working when they go beyond the<br>
"light" use case...<br>
<br>
Still -1. What's so bad about a cacheable script of less than 1MB<br>
gzipped, compared to a single non cacheable set of WMS tiles for a<br>
fullscreen map with several MB?<br>
<span class="HOEnZb"><font color="#888888"><br>
Andreas.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Feb 22, 2012 at 6:48 PM, Tom MacWright <<a href="mailto:tom@macwright.org">tom@macwright.org</a>> wrote:<br>
> There's no need for the current light build to be the one that ships: it'd<br>
> be simple to expand and specialize it a bit more to align with what's needed<br>
> by the Leaflet/Google Maps usecase.<br>
><br>
> Tom<br>
><br>
> On Wed, Feb 22, 2012 at 12:46 PM, Andreas Hocevar <<a href="mailto:ahocevar@opengeo.org">ahocevar@opengeo.org</a>><br>
> wrote:<br>
>><br>
>> The light build with the current lite configuration would be useless<br>
>> for most users. As Tom says, many people won't be able to use the<br>
>> python based build tool, and what then happens is much worse than<br>
>> people using a full build: they'll be using the debug loader or the<br>
>> hosted version from <a href="http://openlayers.org" target="_blank">openlayers.org</a>.<br>
>><br>
>> So I'm -1 on shipping a light build.<br>
>><br>
>> Andreas.<br>
>><br>
>> On Wed, Feb 22, 2012 at 5:11 PM, Tom MacWright <<a href="mailto:tom@macwright.org">tom@macwright.org</a>> wrote:<br>
>> > Absolutely. If OpenLayers doesn't provide a jQuery-UI like build creator<br>
>> > (something that I tried to do with OpenLayerer, but that build-tool<br>
>> > refactoring was never accepted), then there should be a light build<br>
>> > distributed by default. The expectations of the user to run the Python<br>
>> > scripts are way too great for the use-case of just downloading and<br>
>> > running<br>
>> > the thing, even if they seems simple for developers. Like, some guy<br>
>> > making<br>
>> > an HTML website on a Windows machine would have to install Python from<br>
>> > scratch: it isn't going to happen.<br>
>> ><br>
>> > Tom<br>
>> ><br>
>> > On Wed, Feb 22, 2012 at 11:06 AM, Bart van den Eijnden<br>
>> > <<a href="mailto:bartvde@opengeo.org">bartvde@opengeo.org</a>><br>
>> > wrote:<br>
>> >><br>
>> >> As suggested by Antoine on Twitter, and I agree. Clearly a lot of<br>
>> >> people<br>
>> >> are still using a full build, even if we tell people not to.<br>
>> >><br>
>> >> So what about only shipping a minimal build for 2.12?<br>
>> >><br>
>> >> <a href="https://twitter.com/#!/bartvdeijnden/status/172328188704333825" target="_blank">https://twitter.com/#!/bartvdeijnden/status/172328188704333825</a><br>
>> >> <a href="https://twitter.com/#!/brankgnol/status/172345191670358016" target="_blank">https://twitter.com/#!/brankgnol/status/172345191670358016</a><br>
>> >><br>
>> >> Best regards,<br>
>> >> Bart<br>
>> >><br>
>> >> --<br>
>> >> Bart van den Eijnden<br>
>> >> OpenGeo - <a href="http://opengeo.org" target="_blank">http://opengeo.org</a><br>
>> >> Expert service straight from the developers.<br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Dev mailing list<br>
>> >> <a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
>> >> <a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Dev mailing list<br>
>> > <a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
>> > <a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Andreas Hocevar<br>
>> OpenGeo - <a href="http://opengeo.org/" target="_blank">http://opengeo.org/</a><br>
>> Expert service straight from the developers.<br>
><br>
><br>
<br>
<br>
<br>
--<br>
Andreas Hocevar<br>
OpenGeo - <a href="http://opengeo.org/" target="_blank">http://opengeo.org/</a><br>
Expert service straight from the developers.<br>
</div></div></blockquote></div><br>