Web UI configuration system

Hi folks

Our procedure for handling administrator configurable values
in the  
web ui has been a minor problem for a few months. Pre-custom
dojo  
build we simply stored these values in
src/main/webapp/js/cosmo/ui/ 
conf.js, but the build process packs and compresses this
file like  
all the other javascript, making it useless to
administrators.

To fix this I've added src/main/webapp/webui.conf. This file
contains  
a JSON mapping of configuration keys to values. When
cosmo.ui.conf is  
loaded we fetch this file and mix the values defined there
into  
cosmo.ui.conf.

cosmo/ui/conf.js still contains the old configuration
system, which  
is used in quite a bit of code. We might want to think about
ways to  
phase this out after preview, but they are peacefully
coexisting for  
now!

-Travis
  
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Won't it still be packed up inside the war? If so, it's
equally  
useless to administrators.

I believe Jared was doing some work on a system that pulled
in props.  
stuff from the $SNARF_DIST/etc/cosmo.properties and made it
available  
to javascript somehow.

bobby
On Jun 27, 2007, at 9:05 PM, Travis Vachon wrote:

> Hi folks
>
> Our procedure for handling administrator configurable
values in the  
> web ui has been a minor problem for a few months.
Pre-custom dojo  
> build we simply stored these values in
src/main/webapp/js/cosmo/ui/ 
> conf.js, but the build process packs and compresses
this file like  
> all the other javascript, making it useless to
administrators.
>
> To fix this I've added src/main/webapp/webui.conf. This
file  
> contains a JSON mapping of configuration keys to
values. When  
> cosmo.ui.conf is loaded we fetch this file and mix the
values  
> defined there into cosmo.ui.conf.
>
> cosmo/ui/conf.js still contains the old configuration
system, which  
> is used in quite a bit of code. We might want to think
about ways  
> to phase this out after preview, but they are
peacefully coexisting  
> for now!
>
> -Travis
> _______________________________________________
> cosmo-dev mailing list
> cosmo-devlists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 6/27/07, Bobby Rullo <brosafoundation.org>
wrote:
> Won't it still be packed up inside the war? If so, it's
equally
> useless to administrators.
>
> I believe Jared was doing some work on a system that
pulled in props.
> stuff from the $SNARF_DIST/etc/cosmo.properties and
made it available
> to javascript somehow.

agree. all app configuration should be done in
cosmo.properties, not
in a file included within the war.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Sounds correct to me as well.

What's the status of the work Bobby is describing?

-Travis

On Jun 27, 2007, at 9:46 PM, Brian Moseley wrote:

> On 6/27/07, Bobby Rullo <brosafoundation.org>
wrote:
>> Won't it still be packed up inside the war? If so,
it's equally
>> useless to administrators.
>>
>> I believe Jared was doing some work on a system
that pulled in props.
>> stuff from the $SNARF_DIST/etc/cosmo.properties and
made it available
>> to javascript somehow.
>
> agree. all app configuration should be done in
cosmo.properties, not
> in a file included within the war.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-devlists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Travis Vachon wrote:
> What's the status of the work Bobby is describing?

Experimental and not ready for integration.  If you need to
commit 
something to accomplish the same thing, go ahead.

Bug is #9148.

-- Jared

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev