[mapguide-users] Alert about Mapguide 4 FDO version

[Jackie Ng]

Hi Bruno,

In response to the following:

> I’ve just took a look at the SVN repo and I see a lot of merge from you,
that’s great 😊

> Is the future trunk base FDO will support SqlServer 2022 as the Adsk do?


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.


> It would be confusing if Mapguide 4 have a FDO 4.2 version smaller that
the Autodesk one.


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.


> The actual FDO 4.1 is not compatible with AutoCAD Map 2024,
> 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…
> I didn’t try with a FDO Trunk, I will give a try and keep you in touch.

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.

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.

Either way, do keep us posted on this.


> We have submit many FDO fixes in the past , we still have some but I
don’t know how/where to submit them, anymore…


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).


- Jackie

On Fri, 2 Aug 2024 at 22:05, Bruno Scott <bruno.scott at 1spatial.com> wrote:

> Hi Jackie
>
> *You wrote : “I am already constantly merging to trunk fixes and
> improvements that are in adsk branch.”*
>
>
>
> I’ve just took a look at the SVN repo and I see a lot of merge from you,
> that’s great 😊
>
> Is the future trunk base FDO will support SqlServer 2022 as the Adsk do?
>
>
>
>
>
> You wrote : “*Regarding version number, I intend to keep the 4.2 number
> for MapGuide 4.0 release.*”
>
>
>
> It would be confusing if Mapguide 4 have a FDO 4.2 version smaller that
> the Autodesk one.
>
> The actual FDO 4.1 is not compatible with AutoCAD Map 2024,
>
> 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…
>
> I didn’t try with a FDO Trunk, I will give a try and keep you in touch.
>
>
>
> You wrote : “*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*”.
>
>
>
> I don’t have any problem with that 😊
>
>
>
> You wrote : “*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.*“
>
>
>
> We have submit many FDO fixes in the past , we still have some but I don’t
> know how/where to submit them, anymore…
>
>
>
> Best regards,
>
> Bruno Scott
>
>
>
> *De :* mapguide-users <mapguide-users-bounces at lists.osgeo.org> *De la
> part de* Jackie Ng via mapguide-users
> *Envoyé :* vendredi 2 août 2024 13:07
> *À :* MapGuide Users Mail List <mapguide-users at lists.osgeo.org>
> *Cc :* Jackie Ng <jumpinjackie at gmail.com>
> *Objet :* Re: [mapguide-users] Alert about Mapguide 4 FDO version
>
>
>
> Hi Bruno,
>
>
> 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.
>
>
>
> 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.
>
>
>
> 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.
>
>
>
> - Jackie
>
>
>
> You wrote:
>
> Hi Jackie
>
> 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)
>
> This will become very confusing as Autodesk has already release many FDO 4.2...
>
>                AutoCAD Map 2020-> FDO 4.2.36
>
>                AutoCAD Map 2024-> FDO 4.2.502
>
>                AutoCAD Map 2024-> FDO 4.2.1040
>
> At  least the community have to modify the name and/or version to remove confusion between these 2 FDO versions.
>
> It is not rare that we have a Mapguide and an AutoCAD Map on the same computer...
>
> But the best thing to do would be to merge the Autodesk Sandbox branche into the
>
> But the best thing to do would be to merge the Autodesk Sandbox branche into the trunk
>
> There is a lot a good fixes and improvement on the Autodesk Branches.
>
> It seems that there is a lack of governance  in the Fdo Community...
>
> What is your ideas about this?
>
> Best regards,
>
> Bruno Scott
>
> <http://www.1spatial.com>
>
>
>
>
>
> <http://www.youtube.com/user/1SpatialFR>
> <http://www.linkedin.com/company/1spatialfr>
> <http://www.twitter.com/1Spatialfr>
>
> ------------------------------
>
> 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.
>
>
> ------------------------------
>
> 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
>


-- 
http://themapguyde.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20240805/988ef0cb/attachment.htm>