How can I enumerate the Packages I have loaded to increase my bug reporting abilities without having to type all the package versions I have? I tried
PackageInfo allPackages do: [:each | Transcript show: each packageName; cr].,
but that only gets me the base package name, not the one with versions which shows up in Monticello.
An instance of PackageInfo doesn't seem to have a version that I can find.
Thanks...I have tried figuring out how Monticello is doing it, but just can't seem to find it...
Rob
On 29.03.2008, at 20:42, Rob Rothwell wrote:
How can I enumerate the Packages I have loaded to increase my bug reporting abilities without having to type all the package versions I have?
Thanks...I have tried figuring out how Monticello is doing it, but just can't seem to find it...
MCWorkingCopy allManagers collect: [:each | each ancestry ancestorString]
- Bert -
On Sat, Mar 29, 2008 at 4:47 PM, Bert Freudenberg bert@freudenbergs.de wrote:
MCWorkingCopy allManagers collect: [:each | each ancestry ancestorString]
Thank you. I wish I could follow the thought process you used to figure that out! It would have taken me a long time to get to "MCWorkingCopy allManagers."
That seems to have NOTHING to do with "List the current system packages!"
I assume you were able to find this because you understand how Monticello thinks...
Rob
MCWorkingCopy allManagers collect: [:each | each ancestry ancestorString]
Thank you. I wish I could follow the thought process you used to figure that out! It would have taken me a long time to get to "MCWorkingCopy allManagers."
That seems to have NOTHING to do with "List the current system packages!"
I assume you were able to find this because you understand how Monticello thinks...
not really necessary...
I once find that by myself by exploring the morph model in an opened monticello browser... I center click to open halos on morph until plugableListMorphPlus is selected, then debug icon, then inspect model and it open an inspector on aMCWorkingCopy... Then I chose explore and look for the monticello version string (wich is called ancestorString).
Not easy but I start to get used to find such information... just need to be well awake ;)
Cédrick
On Sat, Mar 29, 2008 at 5:48 PM, cdrick cdrick65@gmail.com wrote:
not really necessary...
I once find that by myself by exploring the morph model in an opened monticello browser...
That makes sense...
I center click to open halos on morph until plugableListMorphPlus is
selected, then debug icon, then inspect model and it open an inspector on aMCWorkingCopy...
1. I center click twice until I have selected pluggableListMorphPlus 2. debug>inspect model 3. Which gives me a MCWorkingCopyBrowser 4. Ok...If I "explore" workingCopy...
Then I chose explore and look for the monticello version string (wich is called ancestorString).
Whereas I would have struggled to find allManagers and would have had a hard time getting past:
(workingCopy ancestors at: 1) name, which of course doesn't always work!
Not easy but I start to get used to find such information... just
need to be well awake ;)
Man. "Zen and the art of Smalltalk Programming... "
You guys are amazing!
Rob
beginners@lists.squeakfoundation.org
-
Bert Freudenberg -
cdrick -
Rob Rothwell