If you filed it out/in rather than using MC to save/load then that's what
I'd expect...
Regards, Gary.
- Original Message -
From: "Igor Stasenko" <[EMAIL PROTECTED]>
To: "Pharo Development"
Sent: Wednesday, November 19, 2008 2:56 PM
Subject: [Pha
wser.
Could you check if this is the case in your image?
Cheers,
David
- Original Message - From: "Igor Stasenko" <[EMAIL PROTECTED]>
To: "Pharo Development"
Sent: Wednesday, November 19, 2008 2:56 PM
Subject: [Pharo-project] OB package browser don't detec
gt; - Original Message - From: "Igor Stasenko" <[EMAIL PROTECTED]>
>> To: "Pharo Development"
>> Sent: Wednesday, November 19, 2008 2:56 PM
>> Subject: [Pharo-project] OB package browser don't detects
>> newpackages/updates a package list
&
,
>> David
>>
>>> - Original Message - From: "Igor Stasenko" <[EMAIL PROTECTED]>
>>> To: "Pharo Development"
>>> Sent: Wednesday, November 19, 2008 2:56 PM
>>> Subject: [Pharo-project] OB package browser don't detec
You need to have your package defined as a Monticello package. Otherwise
it's just a class cat, which is visible it the 'unpackaged' package of the
package browser.
Could you check if this is the case in your image?
That's the problem, its not visible anywhere, even in 'unpackaged' package!
2008/11/22 David Röthlisberger <[EMAIL PROTECTED]>:
>
>>> You need to have your package defined as a Monticello package. Otherwise
>>> it's just a class cat, which is visible it the 'unpackaged' package of
>>> the
>>> package browser.
>>> Could you check if this is the case in your image?
>>>
>>
>>
2008/11/26 David Röthlisberger <[EMAIL PROTECTED]>:
>
>> Just download a latest pharo-dev image. Then file-in (not through MC)
>> a .st file which having a package not-yet existing in your image.
>> And then try to find this package in package browser , or one of the
>> classes in it.
>> System br
Of course we could always update whenever there is a change in the system,
but this would lead to a huge performance penalty, particular when loading
or fileing in code, so I didn't change that.
I think that is fairly simple:
SystemChangeNotifier uniqueInstance
notify: self "browser"
o
Just download a latest pharo-dev image. Then file-in (not through MC)
a .st file which having a package not-yet existing in your image.
And then try to find this package in package browser , or one of the
classes in it.
System browser sees it, package browser don't.
ok, I could reproduce this
2008/11/26 David Röthlisberger <[EMAIL PROTECTED]>:
>
>>> Of course we could always update whenever there is a change in the
>>> system,
>>> but this would lead to a huge performance penalty, particular when
>>> loading
>>> or fileing in code, so I didn't change that.
>>>
>>
>> I think that is fair
10 matches
Mail list logo
