Community
Participate
Working Groups
Since Eclipe 3.2 RC2 whenever I start Eclipse and go to the Team Perspective, the Synchronize View always contains the text message: "This view is not populated on startup. You can choose to populate CVS (Workspace) without contacting the server or to synchronize with the server." If I choose "Populate" or "Synchronize", then the next time I quit and launch Eclipse I'm back to the same message whatever I do. This is intended behavior according to Michael Valenta who says in the newsgroup: "It is intended behavior. Populating the synchronize view can take a fair number of cycles and we found that doing it on startup had a considerable performance hit in some cases." I for one prefer the old behavior, because whenever I display the Synchronize View I like to see immediatley what changes need to be committed to CVS. Can we have the old behavior back as a preference? Cheers, Phil
The old behavior had several flaws. For one it didn't populate on startup unless the synchronize view was visible. Otherwise, it populated when the sync view was actibvated. Secondly, all synchronizations populated when the sync view was made visible. So the question is what should the proper behavior be? Do you want the page to populate on startup (regardless of whether the sync view is visible) or when the view is activated (as with the old-style sync)? One possibility is to add an option to synchronize shortly after startup. Synchronizing will populate the page. This has the added advantage that it will also show you any new remote changes.
I think I would like the "Populate on startup" option. In Eclipse 3.1 I liked to see immediately what local files had changed. I got used to using the CVS view as a kind of a quick "show me only the dirty local files" view.
I agree that the current behavior is annoying, since every time Ecipse starts up I click "Populate" (sometimes Synch, but I don't mind having to click a toolbar button for that). It feels to me like it goes against Eclipse's consistency in restoring the state of the workbench on restart. Regarding comment#1, part of me feels like it should follow the lazy loading we're accustomed to and not populate unless the view is visible. However, once the Package/Project Explorer loads it could be argued that the user/UI is 'requesting' a lazy load of synchronization info (e.g. expects the CVS decorators to be correct). So while I think either would be an improvement over the current thing, running the synch on resource view or team decorator synchronization could be better (and avoid needing to have an earlyStartup). Regarding setting the preference, an easy way might be to add an "Always synch on startup..." type checkbox to the Populate/Synchronize prompt when it comes up blank.
Fixed released to HEAD. There is a preference tab in the Preferences available from the view dropdown in the sync view and a checkbox on the Synchronize/Populate page. A scenario has been added to the manual test cases.
Thank-you for doing this. Is the new preference for Synch, Populate or either? PB
If you meant Synch, Populate or neither then the answer is yes. I'm not sure what either would do (perhaps randomly choose one ;-)
:-)
