On Nov 23, 2011, at 10:14 PM, Sean P. DeNigris wrote: > MCWorkingCopyBrowser has #workingCopy:, which I thought would allow me to > programmatically select a working copy. Unfortunately, it doesn't update the > UI. > > Poking around, I found that there are two mechanisms to update the working > copy list selection - #workingCopySelection: and > #workingCopySelectionWrapper: - and they are not connected. So I ended up > with the really ugly: > > browser := MCWorkingCopyBrowser new. > wrapper := MCDependentsWrapper with: wc model: browser. > browser workingCopySelectionWrapper: wrapper.
wonderful isn't > So my question is: is it worth it to open an issue/work on this? Yes > Will Ring/RPackage/other-new-thing replace this tool anytime soon? Not at this level for now we will work on the layer below. Because MC uses FilePackage and other abstractions to collect and represent information. Stef > > Sean > > -- > View this message in context: > http://forum.world.st/Monticello-Browser-Model-tp4101637p4101637.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >
