AW: [Mapbender-dev] Reminder: Code Conventions

[Christoph Baudson (WhereGroup)]

Hi Arnulf,

if there is a project you have in mind and if you rate the compression 
issue as high priority let me know and we can work something out.

Christoph

Arnulf Christl schrieb:
> Christoph Baudson wrote:
>> Hello devs,
>>
>>> I am a little bit confused about the discussion on compressed JS Code.
>>> If I understand it correctly, this would mean there is a "source" or
>>> raw JS code following the conventions of the packing routine (with
>>> comments inline, correct semi-colons) that lives e.g. in the
>>> repository, but a released version would use the compressed JS  (or
>>> the JS is compressed on the fly). Is that the case?
>>
>> This is not intended to be a standard way of distributing Mapbender, but
>> might be interesting for special applications where speed is essential
>> (and you may not be interested in changing the sources frequently). I was
>> thinking f.e. about the Mapbender installation at www.mapbender.org
>> (column on the right). It is just a basic demo and should load as fast as
>> possible. I guess that compression is an interesting idea worth 
>> keeping in
>> mind.
>>
>> Cheers,
>>
>> Christoph
> 
> Hi,
> Uli and me have discussed this years ago but did not have a tool to do 
> that automagically. I am the first to plusone this, we are wasting loads 
> of bandwidth with "wfs_featuretype_element" which could also be "x3" 
> which is 92.7% smaller. This code should only be used on productive 
> portal sites, development will always be done with full names 
> "wfs_featuretype_element".
> 
> Regards, Arnulf. _______________________________________________
> Mapbender_dev mailing list
> Mapbender_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapbender_dev