Why does the World Menu cache it's menu builder? Is building a menu that labor intensive? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Caching-the-World-Menu-tp4693263.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Marcus Denker-4 wrote
It uses Pragmas and therefore has to iterate over all methods to be build.
I disabled the caching and it seems pretty fast... maybe on an old machine you would notice? Was the optimization done in reaction to a problem or preemptively? Also, does anyone need PasteUpMorph>>discoveredMenu? There are no senders. I'm implemented registration for window menus and during the refactoring to remove duplication with the world menu, it would be easier if I could nuke PasteUpMorph>>discoveredMenu ----- Cheers, Sean -- View this message in context: http://forum.world.st/Caching-the-World-Menu-tp4693263p4693265.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Sean P. DeNigris wrote
Also, does anyone need...
What about #discoveredWorldMenuAt: and #worldMenuAt:? Safe to remove? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Caching-the-World-Menu-tp4693263p4693266.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (2)
-
Marcus Denker -
Sean P. DeNigris