[Geomoose-users] startup service

Brent Fraser bfraser at geoanalytic.com
Tue May 17 20:16:52 PDT 2016


  Seems to work. I'll test again tomorrow with the new fixes to the 
startup logic.

Best Regards,
Brent Fraser

On 5/17/2016 7:14 PM, Dan Little wrote:
> It may solve the problem but I can't promise that I've done a lot of
> testing with non-default settings. YMMV.
>
> On Sun, May 15, 2016 at 6:07 PM, Brent Fraser <bfraser at geoanalytic.com> wrote:
>> Dan,
>>
>>    Now that the startup_service specified in the mapbook or config.js works
>> (or at least it should; I'm still having problems getting any of the three
>> startup methods to work using yesterday's nightly build), I expect my
>> original problem would still exist: the toolbar will be disabled.
>>
>> I did notice this in the GeoMOOSE doc
>> (http://docs.geomoose.org/2.8/docs/configuration.html#configuration):
>>
>> services.disable_others
>>    Toggle whether tools and other tabs should be disabled when starting a
>> service.
>>
>> I wonder if this would solve my problem of having a startup service with no
>> user input needed?
>>
>> Best Regards,
>> Brent Fraser
>>
>> On 3/29/2016 2:10 PM, Dan Little wrote:
>>
>> The disabling of the toolbar is actually a new usability 'feature.'  One of
>> the big struggles that both Jim and Eli found in the UI was the order of
>> operations when multiple services were starting at the same time due to the
>> 'open' nature of the toolbar operation.  You can see this in operation in
>> the current demo when you click the "Search Parcels" tab.  The only way to
>> get the toolbar back is to click "cancel" which allows the service to clean
>> itself up properly.
>>
>> If you've got a specific tab that you want displayed all the time it may be
>> necessary to write it as a custom-tab extension.  Which in 2.9 is going to
>> get a bit easier.
>>
>> On Tue, Mar 22, 2016 at 3:49 PM, Brent Fraser <bfraser at geoanalytic.com>
>> wrote:
>>> Hi devs,
>>>
>>>    In my task to upgrade my digitizing app, I see a couple of things:
>>>
>>> 1.  That specifying a startup service in the URL  disables the tools in
>>> the toolbar
>>>
>>> 2.  Specifying a startup service in the mapbook or in config.js doesn't
>>> seem to work.  And I can't find any place in the code where startup_service
>>> is referenced.
>>>
>>> So I added a few lines to main.js (at line 73):
>>>
>>>          var params = GeoMOOSE.getUrlParameters();
>>>          if(GeoMOOSE.isDefined(params.call)) {
>>>              var service_name = params.call;
>>>              delete params.call;
>>>              GeoMOOSE.startService(service_name, params, true);
>>>          };
>>>
>>>          /*  --- new: --- */
>>>          if(GeoMOOSE.isDefined(CONFIGURATION['startup_service'])) {
>>>              var service_name = CONFIGURATION['startup_service'];
>>>              GeoMOOSE.startService(service_name, params, true);
>>>          }
>>>
>>> while it does start the service in the config.js, but it has the same
>>> effect on the toolbar as specifying "?call=myservice" in the URL (it is
>>> disabled).
>>>
>>>    Is there something special I need to set to enable the toolbar after a
>>> startup service?
>>>
>>> --
>>> Best Regards,
>>> Brent Fraser
>>>
>>>
>>> _______________________________________________
>>> Geomoose-users mailing list
>>> Geomoose-users at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>>
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20160517/7921f8cc/attachment.html>


More information about the Geomoose-users mailing list