Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Jackie Ng
Hi All,

I've put up a new RFC for review:

http://trac.osgeo.org/mapguide/wiki/MapGuideRfc149

This RFC will be pretty disruptive for core MapGuide developers, but there's many benefits with this RFC so I'd really appreciate any comments and feedback.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Bruno Scott
Hi Jackie,
Pretty good idea.
We did something very similar just one month ago ;-)
+1
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Haris Kurtagic
Hi,
what I liked about MG and FDO is that you check out source code, run studio
and it successful builds and it even worked :)

It is very simple and it works. That was very much appreciated from me as
developer to start working with source code.

Right now, practically there is no development on MG source code in
community,  especially one that would require changes for building process.

I assume most developers working on source code are in Autodesk and I
wonder how this changes would effect them ?

Haris

On Wed, May 27, 2015 at 4:43 PM, Bruno Scott <[hidden email]> wrote:

> Hi Jackie,
> Pretty good idea.
> We did something very similar just one month ago ;-)
> +1
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Review-Discuss-MapGuide-RFC-149-Lightweight-MapGuide-Source-Tree-tp5207824p5207825.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Jackie Ng
The main motivation for this RFC is to make the MapGuide codebase more conductive to agile development, rapid iteration and continuous integration.

It's very hard to rapidly iterate on MapGuide when you have nearly 2GB of source code to check out and 2-3hrs build time for each build run.

So while yes, this does stunt the open-in-VS-and-compile experience for beginners, it's a small price to pay for faster build cycles.

I'd also argue that this new build process isn't much more different than what is currently in FDO. In FDO you had to init the build environment first with setenvironment.[bat|sh] before you could build from the command line or open up any FDO project in VS to build/debug. It wouldn't be that much different here.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Andy Zhang
Hi Jackie,

Fusion and CsMap are in Oem folder now. Will they be moved to the separate OEM folder too?
 
Best Regards
Andy

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Thursday, May 28, 2015 10:48 AM
To: [hidden email]
Subject: Re: [mapguide-internals] Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

The main motivation for this RFC is to make the MapGuide codebase more conductive to agile development, rapid iteration and continuous integration.

It's very hard to rapidly iterate on MapGuide when you have nearly 2GB of source code to check out and 2-3hrs build time for each build run.

So while yes, this does stunt the open-in-VS-and-compile experience for beginners, it's a small price to pay for faster build cycles.

I'd also argue that this new build process isn't much more different than what is currently in FDO. In FDO you had to init the build environment first with setenvironment.[bat|sh] before you could build from the command line or open up any FDO project in VS to build/debug. It wouldn't be that much different here.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Review-Discuss-MapGuide-RFC-149-Lightweight-MapGuide-Source-Tree-tp5207824p5207909.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Jackie Ng
Hi Andy,

These OEM directories will stay inside MgDev:

 - agg
 - fusion
 - fusionMG

Everything else is moved out.

AGG has its source code files referenced directly by the Renderers project on Windows, so moving that directory out is impractical

fusion isn't so much an "external library" but a framework built on top of MapGuide that just happens to sit in an external repository, so there isn't much sense moving that out either.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Andy Zhang
Hi Jackie,

Thanks for the reply.
I have another question, the Oem folder will be moved up on level. Will there be a folder like OemBranch corresponding to the MgDevBranch?

Thanks
Andy

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng
Sent: Friday, May 29, 2015 10:41 AM
To: [hidden email]
Subject: Re: [mapguide-internals] Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Hi Andy,

These OEM directories will stay inside MgDev:

 - agg
 - fusion
 - fusionMG

Everything else is moved out.

AGG has its source code files referenced directly by the Renderers project on Windows, so moving that directory out is impractical

fusion isn't so much an "external library" but a framework built on top of MapGuide that just happens to sit in an external repository, so there isn't much sense moving that out either.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Review-Discuss-MapGuide-RFC-149-Lightweight-MapGuide-Source-Tree-tp5207824p5208099.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Jackie Ng
Yes, you would branch Oem along with MgDev whenever you make a release branch.

So consider the hypothetical trunk under this RFC:

/trunk
   /MgDev
   /Oem

If you were to make a 3.1 branch, I suggest:

/3.1
   /MgDev -> branched from /trunk/MgDev
   /Oem -> branched from /trunk/Oem

And then make the necessary svn external URL adjustments for fusion and CS-Map as you do before.

- Jackie

Reply | Threaded
Open this post in threaded view
|

Re: Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Kevin Campbell
In reply to this post by Bruno Scott
This change will impact Autodesk development, but it's a good idea for all of us in the future.  Right now we're in the middle of upgrading our compiler to VS2015.  Once our compiler upgrade RFC is submitted and approved Autodesk can give this a +1.