I wonder what is teh better strategy: create 1 template and ask on a subsequent page for the options or create 9 different tempales to be picked in the template editor one one by one?
Can it detect user-created custom profiles and add rules accordingly? Code: HKEY_CURRENT_USER\Software\Google\Chrome\PreferenceMACs HKEY_CURRENT_USER\Software\Microsoft\Edge\PreferenceMACs %AppData%\Mozilla\Firefox\profiles.ini
currently the rules target the folder containing all profiles: C:\Users\Me\AppData\Roaming\Waterfox\Profiles\* so if you have a very custom profile located someware else it wont work that said its a first draft, so what it cant do yet can be still be added you can grab the newest CI build from github and test it out, once its done building...
I vote for option number 1, 1 template and ask for the rest. More like it usually is with programs, first 1 main option, then one has to choose the sub alternatives.
Option 1 has a major draw back, how to change once mind later, you would always need to delete the old template and create a new one, or we would have to add a option to edit once created compatybility templates.
Possibility to edit sounds like something that usually exists, MrX. Why is it a MAJOR draw back? What is the draw back for the other option?
The draw back is the need to add a mechanism for editing, because its not trivial given how sandboxie handles options. As you can see in the attached template example (ignore the Tmpl.XXX lines) some of them have multiple OpenFilePath directives so 1 checkbox for example "Direkt Bookmark Access" needs to switch 2 lines "OpenFilePath=chrome.exe,%Tmpl.Chrome%\Bookmarks*" and "OpenFilePath=chrome.exe,%Tmpl.Chrome%\Favicons*" Which well ... switching is easy,... but later for the UI we want to display the current state for that we need to check booth lines, and if one of them would be missing or altered display some undetermined state indication. The way sandboxie tackled this in the past was to simply use a template in place of a bunch of individual options and then just switch the template on or off. Actually if we would want to go with a complex editing scheme, we could go with not using templates at all but applying the presets to a selected sandbox directly Using a intermediate editable tempalte mught also be an issue for the user, imagine you create a tempalte to force only and then in an otehr box you want to have also bookmark access if you edit the tempalte it would affect all your sandboxes using it, which may not be what you wanted. Having a bunch of simpler templates instead allows you to use the wizard once and then configure multiple boxes indifferent ways. For the current implementation I went yesterday with just creating end enabling a new set of templates, as its the most strait forward. Code: # # Google Chrome # [Template_Chrome_Force] Tmpl.Title=#4323,Google Chrome Tmpl.Class=WebBrowser ForceProcess=chrome.exe [Template_Chrome_Bookmarks_DirectAccess] Tmpl.Title=#4356,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Bookmarks* OpenFilePath=chrome.exe,%Tmpl.Chrome%\Favicons* [Template_Chrome_History_DirectAccess] Tmpl.Title=#4336,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Bookmarks* OpenFilePath=chrome.exe,%Tmpl.Chrome%\Favicons* OpenFilePath=chrome.exe,%Tmpl.Chrome%\*History* OpenFilePath=chrome.exe,%Tmpl.Chrome%\Current * OpenFilePath=chrome.exe,%Tmpl.Chrome%\Last * OpenFilePath=chrome.exe,%Tmpl.Chrome%\Visited Links* [Template_Chrome_Cookies_DirectAccess] Tmpl.Title=#4328,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Cookies* [Template_Chrome_Passwords_DirectAccess] Tmpl.Title=#4331,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Login Data* [Template_Chrome_Preferences_DirectAccess] Tmpl.Title=#4339,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Preferences* [Template_Chrome_Sync_DirectAccess] Tmpl.Title=#4324,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\Sync Data\* OpenFilePath=chrome.exe,%Tmpl.Chrome%\Sync Extension Settings\* [Template_Chrome_Phishing_DirectAccess] Tmpl.Title=#4337,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Local AppData%\Google\Chrome\User Data\Safe Browsing* OpenFilePath=chrome.exe,%Local AppData%\Google\Chrome\User Data\CertificateRevocation [Template_Chrome_Profile_DirectAccess] Tmpl.Title=#4338,Google Chrome Tmpl.Class=WebBrowser OpenFilePath=chrome.exe,%Tmpl.Chrome%\*
I do not understand all you wrote but, as i see it, that which makes it easiest for a user is the best. Easy for a user = more users = more money/income. So if you make your living by this, the best choice is obvious. But may not be the easiest way to do it. Anyway, really looking forward to the result!
