Mac/Windows Software

Basecamp Windows Sharing Basecamp Data

Sharing Basecamp Data

Former Member over 13 years ago

SWMBO and I often work on the same route files (obviously not at the same time). With Mapsource this is quite easy to achieve as we just save the individual files on a network share and both access them from there.

I can't see any way to do that in Basecamp short of exporting from one and importing in to the other. Is there a better way?

Thanks.

Kevin

0 Former Member over 13 years ago

I think exporting/importing would be the way to go.

In MapSource you had to open/save. In BaseCamp have you to import/export.

You could probably pull some shenanigans to make both your BaseCamp copies use the same database (make both %APPDATA%\BaseCamp folders point to a shared location using symbolic links), but I am not sure I can recommend that. Then you definitely would not want to use BaseCamp at the same time.

0 Former Member over 13 years ago

Thanks. I suspected that might be the case.

So to ensure we only ever have one copy the last person who worked on it does an export and delete from list, next person opens Basecamp, imports file, modifies, deletes from list to discard changes or exports, answers "Do you want to overwrite" question then deletes and so on.

Not exactly a step forward from double-click to open, modify, discard or save is it :(.

Kevin

0 Former Member over 13 years ago

I do agree, this is somewhat complicated for your use-case.

BaseCamp is a single database-app. Maybe we can add some sharing functionality in the (not too near) future.

0 Former Member over 13 years ago

BaseCamp is a single database-app.

And therein lies the rub. I don't want a single database application, I was quite happy using files in the same way as pretty much every other Windows programme does.

I realise you may argue your iTunes analogy but a) I don't use the library function within iTunes and b) iTunes doesn't enforce it in the way Basecamp does - I can have my music files wherever I like and they can be called whatever I like. Perhaps you can extend your 'iTunes functionality' to do similarly?

Maybe we can add some sharing functionality in the (not too near) future.

If I'm stuck with the database that would be nice but I'm guessing I shouldn't hold my breath... :)

Kevin

0 Former Member over 13 years ago

Is there any chance that in the future that you will make the interface work like millions of users are used to with the "open, save , Save as" or do we all have to change the way of the MAC?:mad:

0 kganshirt over 13 years ago

The way the Basecamp database is set up is fundamental to the entire Basecamp user interface. I would be astonished if the developers were allowed to make such a significant change.

By the way, that's not intended as a defense of it. The database model and the user interface have too many limitations and unintended consequences for my taste. I'm just taking the practical view so we can have realistic expectations about what the Basecamp developers might or might not do in the future.

Changing the database and the entire user interface is not something I would pin my hopes on. :eek:

In the meantime, there is always the option to use import and export of lists to do something sort of equivalent.

In my case, I have not switched permanently from Mapsource to Basecamp so I keep nothing in the Basecamp collection. If I want to do something in Basecamp that I cannot do in Mapsource, like convert a track to a route, I just import what I need, perform the operation, export the results to use in Mapsource and blow away the collection.

...ken...

0 Former Member over 13 years ago

In my case, I have not switched permanently from Mapsource to Basecamp so I keep nothing in the Basecamp collection. If I want to do something in Basecamp that I cannot do in Mapsource, like convert a track to a route, I just import what I need, perform the operation, export the results to use in Mapsource and blow away the collection.

...ken...

I'm sure I will be doing the same thing and in fact there is little in Basecamp to attract me away from Mapsource at the moment (if there is ever an 'optimise route' function that may change). OTOH I imagine that at some point Mapsource will not be compatible with a future version of the maps so we'll have no choice.

I'd sooner try to point out the inadequacies of the Basecamp model now rather than later. You never know, someone might be listening and be willing to do something about it.

Kevin

0 Killtimer_ over 13 years ago

We're (some of us anyway) fighting the same battle on the Mac front. The whole "Collection" concept makes any kind of collaboration cumbersome. Now if the developers would look to "Aperture" as their model instead of the limited iTunes we could have the best of both worlds. :)

0 Former Member over 13 years ago

The way the Basecamp database is set up is fundamental to the entire Basecamp user interface. I would be astonished if the developers were allowed to make such a significant change.

By the way, that's not intended as a defense of it. The database model and the user interface have too many limitations and unintended consequences for my taste. I'm just taking the practical view so we can have realistic expectations about what the Basecamp developers might or might not do in the future.

Changing the database and the entire user interface is not something I would pin my hopes on. :eek:

I agree why change something that has worked for millions of users, I don't want a database I want to make routes and save them as individual routes and to move them and save them where and when I want not when Garmin thinks I should. I guess I to will continue to use MS until it is not supported and then I will be buying a product that supports the Norm. Don't get me wrong but if I can't use it then i will have to look elsewhere, I have tried using BC to try to get used to it and if all the other things that are different "Good or Bad" that's fine but when I can't use my files the way I want and have been able to for many, many years. I'm not a novice i have been using computers since the 8088 days and there has always been a file system that you could save and file where you choose, I don't need things in a hidden database. If all the lemmings want to just go along , so be it, I won't be buying and more Garmin products and will surely be telling everyone that will listen that Garmin will not listen to its customers. I am on the Zumo forums as well and I have seen nothing but complaints about the product so far. I understand that it is a work in progress, I saw many times on here people asked about things and the response was , well thats the way it is so get used to it, or try this work around, Why not use a established program like MS and fix some miner flaws there. Basecamp was made for the MAC and then they are trying to just have one so lets make the millions of users do it like Itunes.

0 Former Member over 13 years ago

Basecamp was made for the MAC and then they are trying to just have one so lets make the millions of users do it like Itunes.

BaseCamp was not made for the Mac, and we also didn't invent the concept of database driven applications.

I understand you are not a fan, and you are of course free to use a different product.

However, I disagree that we do not listen to our customers. We cannot possibly listen to everyone, but I do believe these forums are proof that we do listen. Many of the changes made to our software are directly due to customer feedback.

We will continue to improve BaseCamp, and we are working hard trying to make sure that features people are missing from MapSource will make it into BaseCamp.

But why don't you just import and export files with BaseCamp? No one is forcing you to use the database. And of course you can keep using MapSource if it meets your needs better.