<div dir="ltr">I'd also really consider either:<div>a) Not including Dojo / OpenLayers as a part of the "intro to GeoMOOSE structure" document. or...</div><div>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.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 22, 2015 at 10:18 AM, Brent Fraser <span dir="ltr"><<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
bobb,<br>
<br>
Not bad. If the diagram is for first time users, I would
highlight the objects that need to be edited, like:<br>
- mapbook.xml<br>
- .map files<br>
- templates<br>
<br>
with some blobs showing the browser connecting to their server and
3rd-party WMS servers.<br>
<br>
<pre cols="72">Best Regards,
Brent Fraser</pre><div><div class="h5">
<div>On 12/21/2015 12:08 PM, Basques, Bob
(CI-StPaul) wrote:<br>
</div>
<blockquote type="cite">
Brent,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Here is a first stab at something</div>
<div><br>
</div>
<div>.<img height="373" width="588"></div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>bobb</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<blockquote type="cite">
<div>On Dec 18, 2015, at 11:59 AM, Brent Fraser
<<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>>
wrote:</div>
<br>
<div>
<div>bobb,<br>
<br>
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
<a href="http://mapserver.org/introduction.html#anatomy-of-a-mapserver-application" target="_blank">
http://mapserver.org/introduction.html#anatomy-of-a-mapserver-application</a><br>
<br>
The trick is to keep is simple but useful.<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 12/18/2015 10:30 AM, Basques, Bob (CI-StPaul) wrote:<br>
<blockquote type="cite">Brent,<br>
<br>
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.<br>
<br>
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.<br>
<br>
bobb<br>
<br>
<br>
<blockquote type="cite">On Dec 18, 2015, at
11:07 AM, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>>
wrote:<br>
<br>
Hi all,<br>
<br>
I'm considering doing a little re-organization of
the Geomoose doc and I'm looking for opinions.<br>
<br>
After several years of answering questions on the
Geomoose email list, I've seen a pattern. Most of
the first-time users with questions:<br>
- use (or at least start with) Windows and MS4W<br>
- want to use their data (and start with
shapefiles) after confirming the demo works<br>
- have trouble understanding the architecture and
syntax of Geomoose components<br>
<br>
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.<br>
<br>
And of course we still need doc for the power
implementers and developers.<br>
<br>
If anyone has some suggestions please let me know.
Thanks!<br>
<br>
-- <br>
Best Regards,<br>
Brent Fraser<br>
<br>
<br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</blockquote>
</blockquote>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br></blockquote></div><br></div>