When searching for an answer, you find at least two quotes which tell
you that it is important:
[Quote=Fons]
3. Clearly defining the way an app should behave w.r.t. its
File menu entries (when managed). This is quite intrusive
to existing clients, but it is IMHO absolutley essential.
Kudos to the designer(s) for the having the courage to do
this instead of allowing application developers to take
the 'least effort' way (which would of course be better
marketing, but invite later misery).
[/Quote=Fons]
*Why* this is essential isn't elaborated by Fons though.
[quote=Liles]
Currently one of the strong points of NSM is that applications with
heavy state (e.g. large audio files) know *exactly* where to put the
state at the time they join the session. This eliminates the need for
undesirable hacks with just storing a link to the heavy state (as was
generally required with LASH). I felt like this was one of the primary
requirements of Non-DAW which was not addressed by other session managers.
[/quote=Liles]
(Assuming that this ^ is because of the strict opening and saving rules
of NSM).
Liles compares here with LASH, undesirable hacks are not needed anymore.
Why is this a primary requirement?
Moreover LASH isn't seen as a serious candidate anyway these days. I
would rather see a comparison with JackSession in this area. In other words:
How JackSession does this and why is it, or why it is not, a problem to
not have these strict rules for applications which are in a session.