<div style="font-family: arial; font-size: 14px;"><div fr-original-style="" style="box-sizing: border-box;">Hi All,</div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" style="box-sizing: border-box;">  Examples/desktop</div><div fr-original-style="" style="box-sizing: border-box;">        mapbook.xml</div><div fr-original-style="" style="box-sizing: border-box;">        mapbook-editing-geoserver.xml (superset of mapbook.xml)</div><div fr-original-style="" style="box-sizing: border-box;">        mapbook-editing-tinyowx.xml (superset of mapbook.xml) </div><div fr-original-style="" style="box-sizing: border-box;">        mapbook-testing.xml (kitchen-sink of all possible map source types, might need its own app.js)</div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" style="box-sizing: border-box;">  Examples/mobile</div><div fr-original-style="" style="box-sizing: border-box;">        mapbook.xml</div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" style="box-sizing: border-box;">Thanks!</div><div fr-original-style="" style="box-sizing: border-box;">Brent</div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><hr id="previousmessagehr" fr-original-style="" style="box-sizing: border-box; clear: both; user-select: none;"><div fr-original-style="" style="box-sizing: border-box;"><span fr-original-style="" style="box-sizing: border-box;"><strong fr-original-style="" style="box-sizing: border-box; font-weight: 700;">From</strong>: Dan Little <theduckylittle@gmail.com><br fr-original-style="" style="box-sizing: border-box;"><strong fr-original-style="" style="box-sizing: border-box; font-weight: 700;">Sent</strong>: 5/22/21 9:36 AM<br fr-original-style="" style="box-sizing: border-box;"><strong fr-original-style="" style="box-sizing: border-box; font-weight: 700;">To</strong>: GeoMOOSE PSC <geomoose-psc@lists.osgeo.org><br fr-original-style="" style="box-sizing: border-box;"><strong fr-original-style="" style="box-sizing: border-box; font-weight: 700;">Subject</strong>: [geomoose-psc] Examples / Demos / Mulitple Mapbooks</span></div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div dir="ltr" fr-original-style="" style="box-sizing: border-box;"><div fr-original-style="" style="box-sizing: border-box;">I think we have hit a critical mass of needing *four* Desktop demos:</div><div fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;">  A. Based on GeoServer.</div><div fr-original-style="" style="box-sizing: border-box;">  B. Based on PostGIS.</div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;">3. "The testing mapbook":</div><div fr-original-style="" style="box-sizing: border-box;"> - This can have the same layers configured in different ways (WFS, WMS)</div><div fr-original-style="" style="box-sizing: border-box;"> - "Test grids" - So we can test scaling and printing issues.</div><div fr-original-style="" style="box-sizing: border-box;"> - Can include stuff that is intentionally broken to test error handling.</div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" style="box-sizing: border-box;">Does this seem like a lot? Sure. Maybe? Why I don't think it is:</div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;">2. The "Desktop demo" will be a subset of the functionality that starts in the testing mapbook.</div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" 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 fr-original-style="" style="box-sizing: border-box;"><br fr-original-style="" style="box-sizing: border-box;"></div><div fr-original-style="" style="box-sizing: border-box;">Thanks for reading!</div></div></div>