<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 22, 2021 at 9:38 AM Brent Fraser <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div style="box-sizing:border-box">Hi All,</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box"> I agree with Dan's proposal below. Here's a structure to consider (in preparation for an RFC) to minimize the duplication of css etc:</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box"> Examples/desktop</div><div style="box-sizing:border-box"> mapbook.xml</div><div style="box-sizing:border-box"> mapbook-editing-geoserver.xml (superset of mapbook.xml)</div><div style="box-sizing:border-box"> mapbook-editing-tinyowx.xml (superset of mapbook.xml) </div><div style="box-sizing:border-box"> mapbook-testing.xml (kitchen-sink of all possible map source types, might need its own app.js)</div></div></blockquote><div><br></div><div>Would mapbook-testing.xml have editing? I would like to see editing in some testing/demo capacity beyond isolation. See my previous comments in this thread, <a href="https://github.com/geomoose/gm3/issues/631">https://github.com/geomoose/gm3/issues/631</a> </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box"> Examples/mobile</div><div style="box-sizing:border-box"> mapbook.xml</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">And I think we should tweak mapbook.xml and app.js to help new users adapt them in their journey in implementing GeoMoose.</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">Thanks!</div><div style="box-sizing:border-box">Brent</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><hr id="gmail-m_-740131844236726546previousmessagehr" style="box-sizing:border-box;clear:both"><div style="box-sizing:border-box"><span style="box-sizing:border-box"><b style="box-sizing:border-box;font-weight:700">From</b>: Dan Little <<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>><br style="box-sizing:border-box"><b style="box-sizing:border-box;font-weight:700">Sent</b>: 5/22/21 9:36 AM<br style="box-sizing:border-box"><b style="box-sizing:border-box;font-weight:700">To</b>: GeoMOOSE PSC <<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a>><br style="box-sizing:border-box"><b style="box-sizing:border-box;font-weight:700">Subject</b>: [geomoose-psc] Examples / Demos / Mulitple Mapbooks</span></div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div dir="ltr" style="box-sizing:border-box"><div style="box-sizing:border-box">I think we have hit a critical mass of needing *four* Desktop demos:</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">1. Editing - The two mapbooks below should be identical but for their target server. I am in favor of having these be a more limited workflow that shows how editing works in a practical way.</div></div></div></blockquote><div><br></div><div>Benefits and drawbacks with this approach, as noted in that issue thread. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div dir="ltr" style="box-sizing:border-box"><div style="box-sizing:border-box"> A. Based on GeoServer.</div><div style="box-sizing:border-box"> B. Based on PostGIS.</div></div></div></blockquote><div><br></div><div>I assume that "PostGIS"=TinyOWS? Would GeoServer be backed by PostGIS or spatialite, shapefile, or some other file based data source?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div dir="ltr" style="box-sizing:border-box"><div style="box-sizing:border-box">2. "The Desktop Demo" a la the status quo. The demo that people will "Copy Pasta" and turn into their deployed Website. Drop all the scary warning messages, ensure our comments are up to date, and that we remove the "Test code". We attempt to show a reasonable set of data types that people would find around in a "typical" County/City/Division website.</div><div style="box-sizing:border-box">3. "The testing mapbook":</div><div style="box-sizing:border-box"> - This can have the same layers configured in different ways (WFS, WMS)</div><div style="box-sizing:border-box"> - "Test grids" - So we can test scaling and printing issues.</div><div style="box-sizing:border-box"> - Can include stuff that is intentionally broken to test error handling.</div><div style="box-sizing:border-box"> - I feel we can add stuff with a <exp:> prefix to denote some experimental stuff we could point users to but not feel the need to adopt and support long term.</div></div></div></blockquote><div><br></div><div>Hopefully this would include editing and not so much experimental and intentionally broken things as to prevent useful testing. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div dir="ltr" style="box-sizing:border-box"><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">Does this seem like a lot? Sure. Maybe? Why I don't think it is:</div></div></div></blockquote><div><br></div><div>GeoMoose does a lot so this does not seem like a lot to me. I agree, it is not a lot. It is a little (for the footprint of functions that GeoMoose covers). <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:arial;font-size:14px"><div dir="ltr" style="box-sizing:border-box"><div style="box-sizing:border-box">1. The editing workflow is pretty dedicated and I feel Brent has put some real time into making sure it is well tested. I feel like that will continue and we have historically had good stakeholders for that functionality.</div><div style="box-sizing:border-box">2. The "Desktop demo" will be a subset of the functionality that starts in the testing mapbook.</div><div style="box-sizing:border-box">3. I find it harder to comment, uncomment, and generally futz around with the "Desktop demo" all the time to make sure it looks okay AND that we have all of the needed functionality ready to test. While, yes, additional unit-testing will help it is very hard to beat a real-world end-to-end test.</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">I may take an initial swipe at this when I do the multiple mapbooks support but drafting an official RFC may be prudent here.</div><div style="box-sizing:border-box"><br style="box-sizing:border-box"></div><div style="box-sizing:border-box">Thanks for reading!</div></div></div>
</blockquote><div><br></div><div>Sounds mostly great!</div><div><br></div><div>Cheers, Eli<br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div></div>