[Pharo-project] Monticello Browser Model
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. So my question is: is it worth it to open an issue/work on this? Will Ring/RPackage/other-new-thing replace this tool anytime soon? 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.
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.
Stéphane Ducasse wrote
So my question is: is it worth it to open an issue/work on this? Yes
Issue 5016: MCWorkingCopyBrowser Cleanup http://code.google.com/p/pharo/issues/detail?id=5016 -- View this message in context: http://forum.world.st/Monticello-Browser-Model-tp4101637p4101691.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Sean P. DeNigris wrote
So I ended up with the really ugly:
browser := MCWorkingCopyBrowser new. wrapper := MCDependentsWrapper with: wc model: browser. browser workingCopySelectionWrapper: wrapper.
which works if each statement is executed individually, but not all at once. Ha ha ha! Sean -- View this message in context: http://forum.world.st/Monticello-Browser-Model-tp4101637p4101657.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (2)
-
Sean P. DeNigris -
Stéphane Ducasse