Catalog backup and management

[michel038]

I suggest redesigning the "File's categories" menu in the categories panel :

export2.png

1) Rename this entry "Catalog"
2) Specify "Export as xml"
3) Specify "Erase and import xml"
4) If possible, add "Import and merge xml"
5) Add a "Save as..." action which will simply offer to save a copy of xnview.db in a classic save dialog.

This package should also be accessible via the "File" menu :
File > Catalog > Export as xml
File > Catalog > Erase and import xml
File > Catalog > Import and merge xml
File > Catalog > Save as ...

Other less important suggestions:
6) Add "Import photos" , which will work in the same way as the "Add folder" button in settings,catalog (in my opinion, it's not a setting, but an action).
7) Add "Erase currentDB, and Import Xnview classic db" ( instead of Settings>Catalog>Tools tab )

Another audacious suggestion :
8 ) Offer the possibility of working on different catalogs :
- Switch from catalog A to catalog B = save XnView.db into catalog A.db and copy catalog B.db into XnView.db (+restart ?) seems easy to implement ?

[xnview]

1) Rename this entry "Catalog"

Ok

2) Specify "Export as xml"
3) Specify "Erase and import xml"

json can be selected too

4) If possible, add "Import and merge xml"

ok

5) Add a "Save as..." action which will simply offer to save a copy of xnview.db in a classic save dialog.

I think that it's better to copy the file from folder....

This package should also be accessible via the "File" menu :
File > Catalog > Export as xml
File > Catalog > Erase and import xml
File > Catalog > Import and merge xml
File > Catalog > Save as ...

Better than in 'categories' panel? so i can remove it from this panel?

8 ) Offer the possibility of working on different catalogs :
- Switch from catalog A to catalog B = save XnView.db into catalog A.db and copy catalog B.db into XnView.db (+restart ?) seems easy to implement ?

yes can be implemented, but need some work...

[michel038]

1) Rename this entry "Catalog"
Ok

Thanks

2) Specify "Export as xml or json"
3) Specify "Erase and import xml "

json can be selected too

4) If possible, add "Import and merge xml"

ok

5) Add a "Save as..." action which will simply offer to save a copy of xnview.db in a classic save dialog.

I think that it's better to copy the file from folder....

Do you mean :
-Close XnViewMP
-Open Windows explorer
-Open C:\Proram files \...\Xnviewmp folder
-Copy Xnview.db to another place
?
Several users come to the forum calling for help, for not having thought of this ...
Providing a "File > Catalog > Save as ..." menu would help.

This package should also be accessible via the "File" menu :
File > Catalog > Export as xml or json
File > Catalog > Erase and import
File > Catalog > Import and merge
File > Catalog > Save as ...

Better than in 'categories' panel? so i can remove it from this panel?

I don't know if it's relevant to remove it now. pehaps better to wait some further versions, and keep both places for some months.

8 ) Offer the possibility of working on different catalogs :
- Switch from catalog A to catalog B = save XnView.db into catalog A.db and copy catalog B.db into XnView.db (+restart ?) seems easy to implement ?
File > Catalog > Switch ...

yes can be implemented, but need some work...

[user0]

This package should also be accessible via the "File" menu :
File > Catalog > Export as xml
File > Catalog > Erase and import xml
File > Catalog > Import and merge xml
File > Catalog > Save as ...

Better than in 'categories' panel? so i can remove it from this panel?

yeah, just remove it from Categories - parent elements should not be in child menu

However, I think potentially there are too many items to be grouped under one Catalog menu, some of them need to be flattened out.
So I thought of a separate menu group to make it clearer, but "File" would work too (more or less) since most apps use it that way.

5) Add a "Save as..." action which will simply offer to save a copy of xnview.db in a classic save dialog.

I think that it's better to copy the file from folder....

+1
moreover, I think "Save as" functionality shall shift focus to the new file which is not the case here.
if bother at all, making copy of db can be inside "Export..." as .db among .xml, .json options.