+1
Cheers
Andrea
Il 13 lug 2016 22:29, "Torben Barsballe" <[email protected]> ha
scritto:
> GSIP-149 <https://github.com/geoserver/geoserver/wiki/GSIP-149> has been
> updated based on this discussion. I have added several of the suggestions
> above to the document. I am happy with the state of it now, and have not
> recieved any additional feedback.
>
> Shall we move this to the voting stage?
>
> Torben
>
> On Tue, Jul 12, 2016 at 9:36 AM, Torben Barsballe <
> [email protected]> wrote:
>
>> Hi Jonathon
>>
>> I think this would require substantial changes to the geoserver wicket
>> interface to get working. All of geoserver has been designed with a fixed
>> screen-width in mind, so changing this behvior would likely require changes
>> to core ui components and styling.
>>
>> So I would say it is out of scope for now. It could be a good idea for
>> future work?
>>
>> Torben
>>
>>
>> On Tue, Jul 12, 2016 at 9:27 AM, Jonathan Moules <
>> [email protected]> wrote:
>>
>>> Hi Torben,
>>> On the issue of layout, this may be out of scope, but how about having
>>> the style box on one side of the screen for large-screens and the
>>> tabbed-stuff on the other? For less-wide screens have them stacked as they
>>> are now.
>>> I don't know how well wicket can handle that sort of thing, but it'd
>>> certainly make for excellent use of screen real-estate.
>>>
>>> Cheers,
>>> Jonathan
>>>
>>>
>>>
>>> ---- On Tue, 12 Jul 2016 16:54:14 +0100 *Torben
>>> Barsballe<[email protected] <[email protected]>>*
>>> wrote ----
>>>
>>> Hi Andrea,
>>>
>>> This is a functionality that I do want to retain, however I have not yet
>>> decided on the best place to put it.
>>> The CSS styling page has these controls to the right of the style box,
>>> however this reduces the amount of space available for styling, which can
>>> be usefull, especially for styles with complex filters or other functions.
>>>
>>> A seperate tab for Set preview layer / set as default style / associate
>>> style with layer may be a good idea. Alternatively, I could include these
>>> controls in the existing style admin tab.
>>>
>>> Other suggestions are welcome.
>>>
>>> Torben
>>>
>>> On Mon, Jul 11, 2016 at 10:40 PM, Andrea Aime <
>>> [email protected]> wrote:
>>>
>>> Hi Torben,
>>> Checking the proposal and screenshots from my phone, it's a bit hard to
>>> read and check (seaside vacation, no computers).
>>> I do not see a way to associate a style as primary or secondary style to
>>> a layer, which is available in the CSS one instead.
>>> If retaining that functionality is too much work please do not remove
>>> the existing CSS style editor
>>>
>>> Cheers
>>> Andrea
>>> Il 11 lug 2016 20:45, "Torben Barsballe" <[email protected]>
>>> ha scritto:
>>>
>>> I am currently putting together a GSIP proposing several improvements to
>>> the GeoServer Style page. This idea has been informally discussed before -
>>> this email is in part attended to gather up the ideas which were discussed.
>>> I expect there will also be new suggestions for what you would like to
>>> see in an improved style page, which will affect the content of the GSIP.
>>>
>>> The basic idea is to move some of the features from the CSS Styles page
>>> over to the main GeoServer styling page in order to improve the main page.
>>>
>>> Additionally, once the core styling page has incorporated these
>>> features, the CSS Styles page would be deleted from the CSS Styling
>>> extension
>>>
>>> The WIP GSIP is here: GSIP-149
>>> <https://github.com/geoserver/geoserver/wiki/GSIP-149>
>>> I will continue updating it with more details, and will add in any
>>> viable ideas discussed here.
>>>
>>>
>>> Torben
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
>>> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
>>> present their vision of the future. This family event has something for
>>> everyone, including kids. Get more information and register today.
>>> http://sdm.link/attshape
>>> _______________________________________________
>>> Geoserver-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>> traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>> are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning
>>> reports.
>>> http://sdm.link/zohodev2dev_______________________________________________
>>> Geoserver-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>>
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
