Mantis Bugtracker
  

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0001702 [Squeak] Monticello minor N/A 08-18-05 00:23 03-27-06 19:51
Reporter mzimmerm View Status public  
Assigned To
Priority normal Resolution open  
Status new   Product Version
Summary 0001702: [MC][ENH] how do I remove a package from the list of required packages?
Description Stephane Ducasse <ducasse@iam.unibe.ch>:

"hi

- how do I remove a package from the list of required packages?
without clearing all the required packages. I tried to implement it but
I'm not sure that the logic is correct. Please check
and this can be improved to only propose the parents of the package
currently selected...

- I found some references to SARMCPackageDumper in the
MCWorkingCopyBrowser>>workingCopyTreeMenu: aMenu
where can I find this class?

- colin are you interested having some simple printing methods for the
MC objects because this could help and I'm ready to
spend some time to just improve the navigability in the
debugger/inspector? Or should I wait for MC2?

Stef"
Additional Information
Attached Files  MCremoverequiredpackage.1.cs [^] (3,102 bytes) 08-18-05 00:23

- Relationships

- Notes
(0002386 - 575 - 705 - 746 - 746 - 746 - 746)
mzimmerm
08-18-05 00:24

Colin Putney <cputney@wiresong.ca>:

"On Mar 19, 2005, at 3:28 PM, stéphane ducasse wrote:

> - colin are you interested having some simple printing methods for the
> MC objects because this could help and I'm ready to
> spend some time to just improve the navigability in the
> debugger/inspector? Or should I wait for MC2?

More informative printing would be great. Don't wait for MC2. It's
getting closer, but I don't think it will be read for production for a
while yet.

I'll have a look at your change set later tonight...

Thanks Stéphane,

Colin"
 
(0002387 - 548 - 839 - 881 - 881 - 881 - 881)
mzimmerm
08-18-05 00:25

Stephane Ducasse <ducasse@iam.unibe.ch>:

"Ok I will spend some times. I hope not to make mistakes.
Next week I hope that alex will release a new version of the
packageBrowser (now OOPSLA deadline is over).

I saw also that there are missing queries such as give the name
    Bot-Pica-sd
    from
    Bot-Pica

(Package named: 'Bot-Pica') fullName
        'Bot-Pica-sd'
(Package named: 'Bot-Pica') fullVersionName
        'Bot-Pica-sd.45'

Is it somewhere? May be I missed them
Now I use MCWorkingCopy allManagers .... but this is a bit ugly.

Stef"
 
(0002388 - 675 - 876 - 912 - 912 - 912 - 912)
mzimmerm
08-18-05 00:27

Bert Freudenberg <bert@impara.de>:

"Packages do not know about their version. Indeed, what is "the" version
of a package? There is often not only one version in your image. Like,
what if you modified it? What if you merged in someone else's version?
The closest you can get is looking at the ancestors of your working
copy:

    (MCWorkingCopy forPackage: (MCPackage named: 'Bot-Pica')) ancestors
        collect: [:each | each name]

Granted, only looking at the first ancestor will give you the right
answer most of the time. But there is a conceptual problem assuming
"the" version. Which is why these convenience accessors do not exist, I
think.

- Bert -"
 
(0002389 - 1458 - 1770 - 1812 - 1812 - 1812 - 1812)
mzimmerm
08-18-05 00:28

Stephane Ducasse <ducasse@iam.unibe.ch>:

"On 20 mars 05, at 13:53, Bert Freudenberg wrote:

> Packages do not know about their version. Indeed, what is "the"
> version of a package? There is often not only one version in your
> image. Like, what if you modified it? What if you merged in someone
> else's version?

I saw that.
Still been able to access some well named stuffs
>> (Package named: 'Bot-Pica') current/mostRecent fullName
>> 'Bot-Pica-sd'
>> (Package named: 'Bot-Pica') current/mostRecent fullVersionName
>> 'Bot-Pica-sd.45'
would help. So I will have a look. I was not willing to spend more time
on that since I was trying to do an automatic
sar creation from MC file but dived to deep. :)

Still the DumpSar functionality referred into the MC menu creation
method seems interesting (assuming that we could find where it is).

> The closest you can get is looking at the ancestors of your working
> copy:
>
> (MCWorkingCopy forPackage: (MCPackage named: 'Bot-Pica')) ancestors
> collect: [:each | each name]
>
> Granted, only looking at the first ancestor will give you the right
> answer most of the time. But there is a conceptual problem assuming
> "the" version. Which is why these convenience accessors do not exist,
> I think.

I think that the code of MC would deserve a bit more class comments and
two or three printOn:
and this would help a lot. I did a printOn: but it was wrong."
 
(0002390 - 293 - 384 - 424 - 424 - 424 - 424)
mzimmerm
08-18-05 00:29

Ned Konz <ned@squeakland.org>:

"On Saturday 19 March 2005 12:28 pm, stéphane ducasse wrote:
> - I found some references to SARMCPackageDumper in the
> MCWorkingCopyBrowser>>workingCopyTreeMenu: aMenu
> where can I find this class?

It is/was in my SARBuilder package.

--
Ned Konz"
 

- Issue History
Date Modified Username Field Change
08-18-05 00:23 mzimmerm New Issue
08-18-05 00:23 mzimmerm File Added: MCremoverequiredpackage.1.cs
08-18-05 00:24 mzimmerm Note Added: 0002386
08-18-05 00:25 mzimmerm Note Added: 0002387
08-18-05 00:27 mzimmerm Note Added: 0002388
08-18-05 00:28 mzimmerm Note Added: 0002389
08-18-05 00:29 mzimmerm Note Added: 0002390
03-27-06 19:51 KenCausey Project Squeak Packages => Squeak
06-03-07 20:46 asparagi Issue Monitored: asparagi


Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
54 total queries executed.
37 unique queries executed.
Powered by Mantis Bugtracker