[Geomoose-users] documentation ideas

[Dan Little]

I'd also really consider either:
a) Not including Dojo / OpenLayers as a part of the "intro to GeoMOOSE
structure" document. or...
b) Make the "GeoMOOSE Code" bubble larger and putting little bubbles in.
Users don't really need to know or care what we use to support the
application.



On Tue, Dec 22, 2015 at 10:18 AM, Brent Fraser <bfraser at geoanalytic.com>
wrote:

> bobb,
>
>   Not bad.  If the diagram is for first time users, I would highlight the
> objects that need to be edited, like:
>     - mapbook.xml
>     - .map files
>     - templates
>
> with some blobs showing the browser connecting to their server and
> 3rd-party WMS servers.
>
> Best Regards,
> Brent Fraser
>
> On 12/21/2015 12:08 PM, Basques, Bob (CI-StPaul) wrote:
>
> Brent,
>
> So, I I’m going to start with a simple Component list to start with.
> Everyone here can comment on how much detail to jump into as an additional
> phase of this.
>
> Here is a first stab at something
>
> .
>
> The Direct Links Bubble is alluding to the fact that GeoMOOSE can be set
> yup without MapFiles at all.  All WMS requests, etc.  Maybe that’s too much
> info up front.
>
> bobb
>
>
>
> On Dec 18, 2015, at 11:59 AM, Brent Fraser <bfraser at geoanalytic.com>
> wrote:
>
> bobb,
>
>   Good idea.  I did a diagram for mapserver 15 years ago that seemed to
> help understand the flow of browser - web server - cgi app - data.  I see
> they've got a much better one now
> http://mapserver.org/introduction.html#anatomy-of-a-mapserver-application
>
> The trick is to keep is simple but useful.
>
> Best Regards,
> Brent Fraser
>
> On 12/18/2015 10:30 AM, Basques, Bob (CI-StPaul) wrote:
>
> Brent,
>
> For item number 3, I’ve often thought about some sort of flowchart looking
> thing, that would show data flow through components used by GeoMOOSE, etc.
> There are many capabilities of GeoMOOSE that are hard to convey quickly
> that a diagram might help with, both for the new user as well as potential
> users in a sales capacity.
>
> I could put a graphic together for something like this.  It also seems
> like something that would be easy to keep up to date, as well as something
> that could be made to expose even more details at some point in the future.
>
> bobb
>
>
> On Dec 18, 2015, at 11:07 AM, Brent Fraser <bfraser at geoanalytic.com>
> wrote:
>
> Hi all,
>
>  I'm considering doing a little re-organization of the Geomoose doc and
> I'm looking for opinions.
>
> After several years of answering questions on the Geomoose email list,
> I've seen a pattern.  Most of the first-time users with questions:
>    - use (or at least start with) Windows and MS4W
>    - want to use their data (and start with shapefiles) after confirming
> the demo works
>    - have trouble understanding the architecture and syntax of Geomoose
> components
>
> While the current set of docs is a great start, I think we can improve by
> filling in a few holes and re-ordering some of the sections.  Basically I'd
> like to give those first-time users a document to follow along as they
> integrate their data.
>
>    And of course we still need doc for the power implementers and
> developers.
>
> If anyone has some suggestions please let me know.  Thanks!
>
> --
> Best Regards,
> Brent Fraser
>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
>
>
>
>
> _______________________________________________
> 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/20151222/a4105d63/attachment.html>