Andrea Aime wrote:
> Luca Morandini ha scritto:
>> So, my idea would be to first build the API, then (or concurrently) the
>> admin UI.
>
> This idea of making the UI a separate web application worries me.
> So far we've tried to be the champions of the "easy to use", at least
> for the first step, the getting started ones.
Point taken.
>> Of course, this may cause a different pace of development of services
>> code and UI code, but there would always be the option of using Ant (or
>> even wget) to use a newly-added service API in a CLI fashion.
>
> Which is exactly what I wish to avoid, a situation where you have to
> use non friendly tools because developers did not have time to develop
> a usable UI (which is already happening btw with sld and freemarker
> templates, I find both of them very painful to work with and a major
> shortcoming of the current GeoServer value proposition).
Well, in an ideal world, the same developer should:
1) Develop the service.
2) Build the UI for said service.
3) Write the documentation.
Since this rarely happen, it might be wise to allocate different people
to do these three things.
An SLD UI with rapid prototyping is my top wish for GeoServer, but since
it is hard to code I'm not expecting it soon... anyway, I'd rather have
SLD without an UI than not having it at all.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
