Hi Brad, You're tapping into the frequently occuring discussion about having a full fledged COM model in Pro, just like several unnamed competitors. As far as I understand, this COM model's on it's way, but it involves porting Pro to the same code base MapX is derived from, and that task seems to be postponed by every new version. So far Pro is built as a monolithic application with just the basic COM interface that hasn't changed since 4.1
However, Pro comes in different flavours, some of which are the non-UI versions you requested - usually referred to as "runtimes". They have the full Pro (more or less) under the hood, and are very useful for building integrated mapping solutions. However, they're still priced at 3-4 times the price of MapX, so the incentive to replace MapX with runtimes are fairly limited, from an economic standpoint. >From a purely technical standpoint, I would like to see Pro with a full fledged COM model - asap - to be used BOTH for desktop AND web applications. Best regards / Med venlig hilsen Lars Nielsen ********************************************************** Lars Nielsen [EMAIL PROTECTED] Sr. Developer, MapInfo and WebMapping Specialist Kampsax/MapInfo, Odense http://www.kampsax-gis.dk Authorized MapInfo Distributor in Denmark & Norway Address: Rugaardsvej 55, DK-5000 Odense C Telephone: +45 6313-5000 Facsimile +45 6313-5090 ********************************************************** "Klik ind p� http://www.kortal.dk og se det hele lidt fra oven!" "Visit http://www.kortal.dk and see Denmark from above!" ----- Videresendt af Lars Nielsen/Kampsax - 17-05-02 10:04 ----- Brad Mathews <Brad@cypresssolu Til: [EMAIL PROTECTED] tions.com> cc: Vedr.: MI-L Discussion: Should a version of Integrated Mapping 17-05-02 01:49 replace MapX? List, While answering a question on the list, I remembered a thought I had when I first tried MapX. I would like to hear other people's opinions on the subject. I have done a lot of Integrated Mapping with VB 4 through 6. I love it! You get all of the benefits of MapBasic (which is a strong language with a few flaws) plus all of the benefits of Visual Basic - full IDE, debugging, strong language, etc. I even write map processing tools and utilities in VB using Integrated Mapping instead of MB. It's faster and easier and i can create more powerful and user friendly applications. When Mapinfo came out with MapX, I was ecstatic. Until I actually tried to use it that is. It is about as intuitive as quantum mechanics, the object model appears to be designed by 1000 monkeys at 1000 typewriters and it was missing a lot of key functionality that MapBasic had for years (like spatial SQL). Why didn't Mapinfo just take MapInfo Pro, strip out the user interface, keep the MapBasic scripting engine, add some key functionality (such as a Printer DC interface) and turn it into an OCX? I realize it would have taken a little bit of work, but it would have had the following key advantages: - A single code base for both products which would save MapInfo a lot of money. - When features were added to Mapinfo Pro, they would be quickly available in the new tool. - An already established developer base in MapBasic developers. When MapX was developed, COM was the "Sexy" thing to do whether it was the right thing or not. I can't blame Mapinfo too much as I found myself in this trap a couple times as well. Is it too late for Mapinfo to switch gears and do this? They would sell more copies of the new tool as there are many more MB developers than there are MapX developers. What do you think? Brad Mathews CTO, Cypress Technology Solutions, Inc. www.CypressSolutions.com --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
