Quote
JamesD
The import/export idea sounds good. Would be a great way to backup the groups and install into a new instance of KM. Just remember that there is no way to delete a record in an ini file. I have not tried to overwrite an existing ini file with a new one. I know it is dangerous, but I would really like the ability to delete a record in an ini file.
That I known, at this moment you only can created an ini file and add/modify his content. You can set a key value to empty "" or a blank space " " or change to some unused character like "¬" or "*" to check an empty or deleted key value.
Quote
JamesD
Import could be complicated. Would import replace existing or add to existing? Replace is pretty easy. First delperf all existing groups2 lines and then write lines based on the ini file info.
Adding to existing groups is much more complicated. First check to see how many groups exist and the re-number the groups coming from the ini file so they fit it after the original groups.
For really complicated, check the groups from the ini file to see they are not exactly the same as an existing group. That way we would not have any duplicates.
- Import proccess:
Groups with different name to existed groups names are added, groups with same name are replaced. I think this is the better solution to avoid duplicates and not complicate a lot of the macro code.
Quote
JamesD
Now would it not be very fancy to have the ability to sort the groups by name. I don't think we have a sort function in the macrolanguage.
It's not easy, but I can tried to do something to sort groups by name.
Quote
JamesD
The export to bookmarks will have to come from you. I use Favorites and do not understand bookmarks.
I was thinking possibilities to do Groups2 export to Bookmarks or Favorites, but this need the help of an external tool (AutoIt). Better for more future version because with this feature will needed to be distributed like a K-Meleon Extension.
At this moment I want Groups2 work only with macro code, without external helper tools.
Quote
JamesD
I did not mean to completely take over your project. Do you wish me to continue with import function?
No problem, this is I like it, a Workgroup project.
(You can remember Groups2 is a workgroup macro since the begining)
- Replys about Questions for users:
1) I think for the moment ask for target folder is enought, and use a standard file named Groups2.ini (for example). To add a new prompt for file name we will time when the rest of code work fine. (Avoid problems with file names; spaces, system reserved characters, and other language characters)
2) Backup is responsability of the users, if an user like a backup before an import, user must know to do an export like backup before. (This is the informatic education)
We are not the user's mammy to go after picking up his toys.
But if you like automate a backup you can add a checkeable option in Groups2 menu to make a backup in profile folder before exit K-Meleon (OnQuit event). But this can delayed the K-Meleon closed time.
@ JamesD:
Thank you for your macro code, now I need some time (a pair of days) to work with the macro code. I'll notice you my advances with the code.
K-Meleon in Spanish