<div dir="ltr"><div>Hi Bruno,</div><div><br></div><div>In response to the following:</div><div dir="ltr"><br></div><div dir="ltr">> <span lang="EN-US">I’ve just took a look at the SVN repo and I see a lot of merge from you, that’s great </span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">😊</span></div><p class="MsoNormal"><span lang="EN-US">> Is the future trunk base FDO will support SqlServer 2022 as the Adsk do?</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">I can spin up a 2022 docker container to verify, but I'm pretty sure the SQL Server provider is always highly compatible with any version since 2008. Their actual geospatial functionality set has not really changed since its introduction in the 2008 release. The only divergence between trunk and adsk versions of this provider is adsk's requirement of a newer ODBC driver and some internal limits (around binary content IIRC) raised as a result of switching to this newer driver.</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">> It would be confusing if Mapguide 4 have a FDO 4.2 version smaller that the Autodesk one.</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">Based on the example 4.2 version numbers you have provided, I don't think this will be a problem. I always use major.minor.patch.SVN_REVISION as the versioning scheme and right now SVN head is at 8261. It's clear adsk are not using this versioning scheme based on the version numbers given. It will be a very long time before adsk would catch up to this number based on the current version number trajectory.</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">> </span>The actual FDO 4.1 is not compatible with AutoCAD Map 2024,</p>> We sell a AutoCAD Map plugin that uses FDO and If we load our plugin with the FDO 4.1, some of the AutoCAD Map functionality (the one that uses FDO) stop working…<div>> I didn’t try with a FDO Trunk, I will give a try and keep you in touch.</div><div><br></div><div>An easy objective test is to WinMerge-diff FDO trunk's public header set against the FDO header set provided by their Map-vertical ObjectARX SDK and see if there are methods added/changed/removed.</div><div><br></div><div>That is of course a big decade-long assumption that adsk still ships vertical-specific SDKs with their yearly AutoCAD (and vertical) releases. I have not touched a commercial adsk product in over a decade so I do not know if this is still the case.</div><div><br></div><div>Either way, do keep us posted on this.<br></div><div><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">> We have submit many FDO fixes in the past , we still have some but I don’t know how/where to submit them, anymore…</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">If you post to mapguide-internals (even if the patches are FDO-related) or attach patches to any FDO tickets you open on the trac instance, there'll be at least someone who can look at it (me).</span></p><p class="MsoNormal"><span lang="EN-US"><br></span></p><p class="MsoNormal"><span lang="EN-US">- Jackie</span></p><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 2 Aug 2024 at 22:05, Bruno Scott <<a href="mailto:bruno.scott@1spatial.com">bruno.scott@1spatial.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 class="msg-2672368333524500486">
<div lang="FR" style="overflow-wrap: break-word;">
<div class="m_-2672368333524500486WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">Hi Jackie<u></u><u></u></span></p>
<p class="MsoNormal"><i><span lang="EN-US">You wrote : “I am already constantly merging to trunk fixes and improvements that are in adsk branch.”<u></u><u></u></span></i></p>
<p class="MsoNormal"><i><span lang="EN-US"><u></u> <u></u></span></i></p>
<p class="MsoNormal"><span lang="EN-US">I’ve just took a look at the SVN repo and I see a lot of merge from you, that’s great
</span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">😊</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Is the future trunk base FDO will support SqlServer 2022 as the Adsk do?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">You wrote : “<i>Regarding version number, I intend to keep the 4.2 number for MapGuide 4.0 release.</i>”<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">It would be confusing if Mapguide 4 have a FDO 4.2 version smaller that the Autodesk one.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">The actual FDO 4.1 is not compatible with AutoCAD Map 2024,
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">We sell a AutoCAD Map plugin that uses FDO and If we load our plugin with the FDO 4.1, some of the AutoCAD Map functionality (the one that uses FDO) stop working…<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">I didn’t try with a FDO Trunk, I will give a try and keep you in touch.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">You wrote : “</span><i><span lang="EN-US">Regarding lack of FDO governance, I don't see FDO being anything bigger than a sub-project of MapGuide and right now would
rather handle any FDO project affairs under the umbrella of the MapGuide Project PSC</span></i><span lang="EN-US">”.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I don’t have any problem with that </span>
<span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">😊</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">You wrote : “</span><i><span lang="EN-US">Mailing list activity can attest to this. There is near zero activity on FDO's mailing list, while we still get activity here
and any FDO questions/discussion we have is almost always done here anyways.</span></i><span lang="EN-US" style="font-size:11pt">“<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">We have submit many FDO fixes in the past , we still have some but I don’t know how/where to submit them, anymore…<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt">Bruno Scott</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11pt"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">De :</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"> mapguide-users <<a href="mailto:mapguide-users-bounces@lists.osgeo.org" target="_blank">mapguide-users-bounces@lists.osgeo.org</a>>
<b>De la part de</b> Jackie Ng via mapguide-users<br>
<b>Envoyé :</b> vendredi 2 août 2024 13:07<br>
<b>À :</b> MapGuide Users Mail List <<a href="mailto:mapguide-users@lists.osgeo.org" target="_blank">mapguide-users@lists.osgeo.org</a>><br>
<b>Cc :</b> Jackie Ng <<a href="mailto:jumpinjackie@gmail.com" target="_blank">jumpinjackie@gmail.com</a>><br>
<b>Objet :</b> Re: [mapguide-users] Alert about Mapguide 4 FDO version<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal">Hi Bruno,<u></u><u></u></p>
<div>
<p class="MsoNormal"><br>
I am already constantly merging to trunk fixes and improvements that are in adsk branch. The only bits I haven't been actively merging are changes around the SQLite provider and some bits of the SQL Server provider. I'll give these providers more attention
after I put out Beta 2.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regarding version number, I intend to keep the 4.2 number for MapGuide 4.0 release. Is your concern mainly around being able to reuse FDO providers between MapGuide and AutoCAD Map? I haven't concerned myself about that for a very long
time since I don't have access to any Autodesk commercial GIS products to test and verify.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regarding lack of FDO governance, I don't see FDO being anything bigger than a sub-project of MapGuide and right now would rather handle any FDO project affairs under the umbrella of the MapGuide Project PSC. Mailing list activity can attest
to this. There is near zero activity on FDO's mailing list, while we still get activity here and any FDO questions/discussion we have is almost always done here anyways.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">- Jackie<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">You wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-left:30pt;margin-right:0cm">
<div>
<pre><span style="color:black">Hi Jackie<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">The next Mapguide 4 will have a new FDO version based on the trunk ( I guess) and this version will be versioned as 4.2 (guessing again)<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">This will become very confusing as Autodesk has already release many FDO 4.2...<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black"> AutoCAD Map 2020-> FDO 4.2.36<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black"> AutoCAD Map 2024-> FDO 4.2.502<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black"> AutoCAD Map 2024-> FDO 4.2.1040<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">At least the community have to modify the name and/or version to remove confusion between these 2 FDO versions.<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">It is not rare that we have a Mapguide and an AutoCAD Map on the same computer...<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">But the best thing to do would be to merge the Autodesk Sandbox branche into the <u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">But the best thing to do would be to merge the Autodesk Sandbox branche into the trunk<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">There is a lot a good fixes and improvement on the Autodesk Branches.<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">It seems that there is a lack of governance in the Fdo Community...<u></u><u></u></span></pre>
</div>
</blockquote>
<blockquote style="margin-left:30pt;margin-right:0cm">
<div>
<pre><span style="color:black">What is your ideas about this?<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">Best regards,<u></u><u></u></span></pre>
</div>
<div>
<pre><span style="color:black">Bruno Scott<u></u><u></u></span></pre>
</div>
</blockquote>
</div>
</div>
<a href="http://www.1spatial.com" target="_blank"><img src="https://www.1spatial.com/signatures/1SpatialLogo_Small.jpg" align="RIGHT" border="0"></a>
<br>
<br>
<br>
<br>
<br>
<br>
<a href="http://www.youtube.com/user/1SpatialFR" target="_blank"><img src="https://1spatial.com/media/ahplm152/icons8-youtube-48.png" align="RIGHT"></a>
<a href="http://www.linkedin.com/company/1spatialfr" target="_blank"><img src="https://1spatial.com/media/dm4hkm3z/icons8-linkedin-48.png" align="RIGHT"></a>
<a href="http://www.twitter.com/1Spatialfr" target="_blank"><img src="https://1spatial.com/media/uvln1clv/icons8-twitter-48.png" align="RIGHT"></a>
<br>
<br>
<hr>
<p style="font-family:arial;font-size:100%"></p>
<p style="font-family:arial;font-size:75%">Les informations contenues dans cet e-mail sont confidentielles et uniquement adressées au destinataire. Les opinions qui y sont exprimées peuvent être celles de l'auteur et ne représentent pas nécessairement celles
du Groupe 1Spatial. Cet e-mail a été scanné et est garanti sans aucun virus. </p>
<br>
<br>
<hr>
<p style="font-family:arial;font-size:75%">The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. Any views or opinions expressed in this
e-mail may be solely those of the author and are not necessarily those of 1Spatial Plc. This email has been scanned for viruses and message content. 1Spatial Group Limited is a company registered in England and Wales No.4785688. Registered Office: Tennyson
House, Cambridge Business Park, Cambridge CB4 0WZ</p>
</div>
</div></blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><a href="http://themapguyde.blogspot.com" target="_blank">http://themapguyde.blogspot.com</a></div></div></div></div></div></div>