[openbeos] plug-ins [was Re: ShowImage "Mirror" Operations]

> almost no matter how big the app is; the
> parts that aren't used in an application are only loaded on-demand,
> they never get loaded if the functionality is never used (same for
> libraries).

Because of virtual memory, mapping the executable and lazy loading? 
Interesting. Is it true that putting all the GUI creation code into one 
place in the executable helps application launch time then? By pure 
laziness, WonderBrush happens to have the GUI creation code for its main 
window in one object file. Is this actually good for performance then? Or 
is the linker optimizing stuff and shuffling things around according to 
execution path?

And another question: Does BeOS use lazy loading or is this a Haiku thing? 
I have noticed that on Haiku, when I use a tool in WonderBrush the first 
time, there can be a short delay and some disk activity. Is this the effect 
of lazy loading? I wouldn't mind if there was a process that kept loading 
the app in the background to fill the virtual mapping so the chances of 
seeing this delay become less likely.

> I think
> Refraction is just poorly designed, especially in BeOS with its 32 MB
> system wide add-on limit (but even without it).

At least it should be usable when all plugins are removed. "Non-optional 
plugin" defeats the purpose of "plugin". Plugins should be either for 
making it possible to extend the app by third parties, or for the user to 
be able to remove unused stuff (like from the interface).

Best regards,
-Stephan

Other related posts: