organicmaps/organicmaps-tmp

Archived

Fork 1

[android] Give valuable names to bookmarks files #585

New issue

Open

opened 2021-06-14 19:08:37 +00:00 by ioctl-user · 10 comments

ioctl-user commented

2021-06-14 19:08:37 +00:00

(Migrated from github.com)

For now new and imported bookmark files has names like MapsMe.kml , MapsMe1.kml ...

It's confusing while trying backup which adb on rooted phone.

Is it possible to give them the same names as displayed in the app?
If so, the only problem can be by importing new bookmarks with the same name as existing file. But, it seems, this can be fixed by adding number or so on.

For now new and imported bookmark files has names like MapsMe.kml , MapsMe1.kml ... It's confusing while trying backup which adb on rooted phone. Is it possible to give them the same names as displayed in the app? If so, the only problem can be by importing new bookmarks with the same name as existing file. But, it seems, this can be fixed by adding number or so on.

👍 4

biodranik commented

2022-10-23 22:50:22 +00:00

(Migrated from github.com)

If you import some file.kml, does it change its name to something else now in Organic Maps?

If you import some `file.kml`, does it change its name to something else now in Organic Maps?

ioctl-user commented

2022-10-25 08:07:27 +00:00

(Migrated from github.com)

If you import some file.kml, does it change its name to something else now in Organic Maps?

I just checked. Filename itself in the data directory will be named "file.kml".

> If you import some `file.kml`, does it change its name to something else now in Organic Maps? I just checked. Filename itself in the data directory will be named "file.kml".

biodranik commented

2022-10-25 10:03:20 +00:00

(Migrated from github.com)

So what should be fixed then and why?

ioctl-user commented

2022-10-25 10:07:43 +00:00

(Migrated from github.com)

It would be nice, that imported files has the same names in the storage, as user see in the app.

This is useful for bundle backup on the rooted phones.

It would be nice, that imported files has the same names in the storage, as user see in the app. This is useful for bundle backup on the rooted phones.

biodranik commented

2022-10-25 10:11:35 +00:00

(Migrated from github.com)

Renaming imported files doesn't look like a good idea. Btw, can you please check:

What if you rename the imported bookmark list in the app? Will the file name change?
What if you create a new bookmark list with some custom name? What is the file name?

Renaming imported files doesn't look like a good idea. Btw, can you please check: 1. What if you rename the imported bookmark list in the app? Will the file name change? 2. What if you create a new bookmark list with some custom name? What is the file name?

ioctl-user commented

2022-10-29 11:56:19 +00:00

(Migrated from github.com)

No, it will be the same, like "MapsMe15.kml" . That's looks not good.
Yes. File name is list name + ".kml" .

1. No, it will be the same, like "MapsMe15.kml" . That's looks not good. 2. Yes. File name is list name + ".kml" .

biodranik commented

2022-10-29 12:44:41 +00:00

(Migrated from github.com)

What if you rename a newly created bookmark list? Will the file name change too?
Why do you think that the imported file name should be changed? Will users expect that?

3. What if you rename a newly created bookmark list? Will the file name change too? 4. Why do you think that the imported file name should be changed? Will users expect that?

ioctl-user commented

2022-10-31 07:22:51 +00:00

(Migrated from github.com)

No. This is unexpected also.
KML is a quite widespread format. A lot of programs can export it with unpredicted name, that can be different from the list name itself; some of them can use static name like "file.kml". I think user will expect see file in filesystem tree with the same name, as he see in the program. This approach also will solve problem of importing two or more files with identical names.

3. No. This is unexpected also. 4. KML is a quite widespread format. A lot of programs can export it with unpredicted name, that can be different from the list name itself; some of them can use static name like "file.kml". I think user will expect see file in filesystem tree with the same name, as he see in the program. This approach also will solve problem of importing two or more files with identical names.

biodranik commented

2022-10-31 18:12:20 +00:00

(Migrated from github.com)

You want a file with the same name as the list name, but call renaming unexpected? Doesn't it contradict each other?
On modern Androids, there is no access to the app's files to see them in a directory tree. Almost the same is on iOS. While it sounds reasonable, this change may be useful only for a limited amount of users/scenarios.

3. You want a file with the same name as the list name, but call renaming unexpected? Doesn't it contradict each other? 4. On modern Androids, there is no access to the app's files to see them in a directory tree. Almost the same is on iOS. While it sounds reasonable, this change may be useful only for a limited amount of users/scenarios.

ioctl-user commented

2022-11-05 10:40:54 +00:00

(Migrated from github.com)

Wait... It's not renamed, and this is unexpected.
Yes. This is actual only for rooted phones. Unfortunately, there is no bundle export function in the program, that makes a problem for users, who have tens of lists.

3. Wait... It's not renamed, and this is unexpected. 4. Yes. This is actual only for rooted phones. Unfortunately, there is no bundle export function in the program, that makes a problem for users, who have tens of lists.

This repo is archived. You cannot comment on issues.