|
I'm not following the example of a cached parse tree that a relaunched plugin (same Sigil instance) could reuse either. Just because the same instance of Sigil is open is no guarantee that the cached tree in the plugin is still going to match the current tree in Sigil. If it does still match (no subsequent Sigil edits were made before the plugin was relaunched) then why was the plugin closed in the first place?
Unless you're talking about a completely external tree that's being cached. But in that case, why would it matter if Sigil had been relaunched or not?
I understand this sort of thing might work well for your particular workflow, but it seems like a highly specialized thing that's not going to benefit very many people in the long run.
|