Zini wrote:1. Profiles
There has been a lot of confusion about profiles. Several times people had problems with understanding what they are. That makes me think that maybe I chose the name for this feature poorly. Should we consider renaming it? "Named content stack" maybe? Or just "content stack"? Not sure if these names are much better. Suggestions welcome.
So that's what those are. I never got that before.
Zini wrote:4c. Saving in the editor
We have a problem when we load legacy format files for editing. The editor can not write these formats. Therefore on save a name change occurs, e.g. SomeRandomPlugin.esp -> SomeRandomPlugin.omwaddon. We need to communicate that to the user (and make sure we don't overwrite anything accidentally).
The question here is, should we handle this on load or on save? On load would be cleaner, but you might not always want to save after loading (when loading just for viewing and not for editing) and in this case we would bother the user needlessly.
One way to do it would be to display a warning message in the load dialogue which says that OpenCS cannot save to that format if an .esm or .esp is selected. No popup, no intrusiveness, just simple clear text below the file selection that always reminds the user that there isn't backwards compatibility. New users would notice that it text has appeared, and experienced users would likely ignore it and know about it anyway. If the .esp and .esm file icons and the .omwgame and .omwaddon file icons are different enough, this will help reinforce that distinction.
Likewise, when saving the same warning can be displayed and the option to save as an .esm or .esp is unavailable. The user will again see there is no saving that way and the reason is clear without being intrusive.
I'm sure there are better ways though.