Differences
This shows you the differences between two versions of the page.
|
development:nautilus-probs [2010/06/21 08:36] jason created |
development:nautilus-probs [2010/06/21 09:26] (current) jason |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| - Nautilus re-requests the menu **for every single open window!** What. The. What. | - Nautilus re-requests the menu **for every single open window!** What. The. What. | ||
| - | So this means we need to keep the information for **every single directory opened by Nautilus for the current session!** | + | So this means we need to keep the information for **every single directory opened by Nautilus for the current session!** Just for when we update the menu for ONE of them! |
| + | |||
| + | There's just no real cohesion between the methods. If we want to asynchronously update file information, we need to cache weird item objects and call an invalidation method on them. If we want to asynchronously update parent dir information, we need to keep a similarly weird provider instance (that, incidentally, never changes) and call a method on **that**. Which updates everything at once. The first is per node, the second is per extension. | ||
All text and image content on rabbitvcs.org, unless otherwise specified, is licensed under a Creative Commons Attribution-Share Alike 3.0 License. This does not include the RabbitVCS name, logo or icon. More...
