-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, pertinent to the discussion yesterday about where the project is going Christoph again proposed to go for OpenLayers as the (only) viewing component to reduce the scope of development. One argument that I always bring up against this is that OpenLayers is way too fat. It invariably crams several 100k through the pipe and into the browser while all that is needed in many cases are just a few 10k. With 2.9 this has not become any better. Today I found this blog [1] that describes hwo to reduce the size of OpenLayers from a user perspective. If we go for OpenLayers could we work backwards by starting with as little OL code as possible and increasing as we add functionality? Then we could always trade off functionality for weight and balance both as best required by the corresponding project.
Best regards, Arnulf. [1] http://linfiniti.com/2010/05/slimming-down-openlayers/ - -- Arnulf Christl Exploring Space, Time and Mind http://arnulf.us -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvyUnYACgkQXmFKW+BJ1b3CowCfafEDWDNZatU7CJM0583iJSWz cqoAn1rlluTyK5NH7WxDDx/zhlGuUA/C =HJoM -----END PGP SIGNATURE----- _______________________________________________ Mapbender_dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapbender_dev
