Hi Christian:
Justin pointed us in the direction of 1.7.x/2.5.x - did you have any
plans/schedule to port this work to trunk? Also if you had any
feedback on this technique for integration now would be an excellent
chance (before another team has a go at the problem).
Jody
On 25/06/2009,
Good Morning List:
I am having an excellent visit with Justin and Garbiel and the team
that has been working on application schema stuff. I hope we can bully
Ben into some kind of news post later in the day.
Today we are actually hitting the codebase and may have a few random
questions. Ch
Hi Christian,
Jody and I are about to look at your work on geoserver datastore registry used
for your pregeneralization info provider. I am looking to probably use your
existing code for my app-schema feature chaining work. Just giving you a heads
up, in case we need your help.
Cheers
Rini
--
Hello All,
I am using geoserver 1.7.4 .I installed it on my desktop it works fine but
when I installed it on server , i configured it on port 1979
then i am unable to access it from outside.I am using following url:
http://MyServerName:1979/geoserver/
Could you tell me which mis
Been chatting with Jody, Justin, Gabriel and a bunch of users - we had
an idea which might be relevant here...
Role-based wizards - this would address the concerns here in two ways:
1) you show the options most relevant to the role of the user -
service deployer vs system admin vs developer vs co
Namespaces omitted for some layers in wms capabilities
--
Key: GEOS-3192
URL: http://jira.codehaus.org/browse/GEOS-3192
Project: GeoServer
Issue Type: Bug
Components: WMS
Affe
Unable to prevent geoserver.log from being written to .\logs
Key: GEOS-3191
URL: http://jira.codehaus.org/browse/GEOS-3191
Project: GeoServer
Issue Type: Bug
Components:
alyssa wright ha scritto:
i would be into that.
just so you know, its hard for me to make hard and fast recommendations
for geoserver, as i'm still determining how people use it. (as i said
to mike yesterday, what's the heart of geoserver? or something like
that.) so these suggestions are
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/1281/changes
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/li
Allow Serializable instances in resource metadata
-
Key: GEOS-3190
URL: http://jira.codehaus.org/browse/GEOS-3190
Project: GeoServer
Issue Type: Bug
Components: Configuration
Affe
i would be into that.
just so you know, its hard for me to make hard and fast recommendations
for geoserver, as i'm still determining how people use it. (as i said
to mike yesterday, what's the heart of geoserver? or something like
that.) so these suggestions are coming from a beginner's per
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/1280/changes
Changes:
[aaime] Added tooltips to type icons
[aaime] Keep shapefiles around
[aaime] Improvements to the file browser
--
[...truncated 3204 lines...]
]]>
5.0 -1.0 5.0 2.
Andrea Aime wrote:
> alyssa wright ha scritto:
>> for me the rational in hiding them, is not about overwhelm. rather, its
>> about the hierarchy of options. the current hierarchy doesn't sync with
>> how i use geoserver. for me, data is the most active part of my
>> geoserver time, yet its
alyssa wright ha scritto:
> for me the rational in hiding them, is not about overwhelm. rather, its
> about the hierarchy of options. the current hierarchy doesn't sync with
> how i use geoserver. for me, data is the most active part of my
> geoserver time, yet its all the way on the bottom.
for me the rational in hiding them, is not about overwhelm. rather, its
about the hierarchy of options. the current hierarchy doesn't sync with
how i use geoserver. for me, data is the most active part of my
geoserver time, yet its all the way on the bottom. server details are
not things im
For historical reference, the reason we decided to make them all up
front is because the current 'hospital green' UI hide everything and
is very frustrating to newbies and power users alike. Most people
enter GeoServer with a specific task in mind—putting all the nav items
out there facilit
Mike Pumphrey ha scritto:
> I see what you mean, Andrea, but my response would be:
>
> "So I don't get confused/overwhelmed and so I can see only what I
> want to see"
>
> I'd be fine having it "remember" whether the menus are collapsed or
> not, so that fearless pros can expand them once (and th
17 matches
Mail list logo
