Issue 7190 in pharo: MC core model depends on UI !!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 7190 in pharo: MC core model depends on UI !!

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-Bug

New issue 7190 by [hidden email]: MC core model depends on UI !!
http://code.google.com/p/pharo/issues/detail?id=7190

MCPatchOperation>>annotations
        ^self annotations: CodeHolder annotationRequests


=> Solution we should introduce a class or move annotation Class or  
CompiledMethod

annotationRequests
        "Answer a list of symbol characterizing all the available kinds of  
annotations;
        Each symbol represents the info type:
                #timeStamp :
                        The time stamp of the last submission of the method.
                #firstComment:
                        The first comment in the method, if any.
                #masterComment:
                        The comment at the beginning of the supermost implementor
                        of the method if any.
                #documentation:
                        Comment at beginning of the method or, if it has none,
                        comment at the beginning of a superclass's implementation of the method.
                #messageCategory:
                        Which method category the method lies in.
                #sendersCount:
                        A report of how many senders there of the message.
                #implementorsCount:
                        A report of how many implementors there are of the message.
                #recentChangeSet :
                        The most recent change set bearing the method.
                #allChangeSets :
                        A list of all change sets bearing the method.
                #priorVersionsCount:
                        A report of how many previous versions there are of the method.
                #priorTimeStamp:
                        The time stamp of the penultimate submission of the method, if any.
                "
         ^ AnnotationRequests ifNil: [AnnotationRequests := self  
defaultAnnotationInfo]

defaultAnnotationInfo
        "see annotationRequests comment"
        ^ #(timeStamp messageCategory sendersCount implementorsCount allChangeSets)

Then Nautilus, MC and CodeHodler should use it.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7190 in pharo: MC core model depends on UI !!

pharo
Updates:
        Status: FixToInclude
        Labels: Milestone-2.0

Comment #1 on issue 7190 by [hidden email]: MC core model depends on  
UI !!
http://code.google.com/p/pharo/issues/detail?id=7190

I also added many class comments and method protocol.
The slice is in the inbox.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7190 in pharo: MC core model depends on UI !!

pharo
Updates:
        Status: Integrated

Comment #2 on issue 7190 by [hidden email]: MC core model depends on  
UI !!
http://code.google.com/p/pharo/issues/detail?id=7190

Integrated in 20463


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker