[geomoose-psc] dist contents in Releases

[Brent Fraser]

Thanks for the info.  I was wondering if a common use-case would be a Linux 
admin wanting to just install GeoMoose and try the demo with no intent to 
debug etc.   Should we require them to install Node and do the  build?  Can 
we just include the geomoose.min.js in the dist dir?
  
 Thanks!
 Brent
  
  
  

----------------------------------------
 From: "Jim Klassen" <klassen.js at gmail.com>
Sent: July 17, 2020 9:58 AM
To: geomoose-psc at lists.osgeo.org
Subject: Re: [geomoose-psc] dist contents in Releases   

The /dist/ folder (and contents) is basically the sum total of the release. 
 The rest of the files are included basically for convenience sake (source 
code, examples/demos, documentation) but aren't needed (well examples is 
needed for the out of the box "demo" but people really shouldn't be using 
that for a production application, but should use them as starting points 
and make their own files in their own folders).  

The MS4W and Linux packages are structured differently to ease migration 
from GeoMoose 2.x.  I would say installing from the NPM package or git 
would be the preferred/modern option.  

The npm package has /package/dist  

The Linux package has /gm3-exmaples/htdocs/geomoose/dist  

The MS4W package has /ms4w/apps/gm3/htdocs/geomoose/dist  

   On 7/16/20 4:29 PM, Brent Fraser wrote:
   
 Hi All,
  
   Is there a reason why we don't include the "dist" directory and contents 
(specifically geomoose.min.js) in a Release package?
  
 Thanks!
 Brent
  
      

 _______________________________________________ geomoose-psc mailing list 
geomoose-psc at lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/geomoose-psc  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20200717/dce4c913/attachment.html>