Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions src/NewTools-Sindarin-Commands/SindarinCopyOsInfo.class.st
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
Class {
#name : 'SindarinCopyOsInfo',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really specific to Sindarin to copy some infos?

Seems like something more general than Sindarin

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we want to have it on all menus.
According to the issue we want to be able to report system info from a debugger window when an error is raised, to help documenting a new issue about it.

This way we avoid carrying an extra entry in the right click menu elsewhere where it isn't used as much as on a debugger.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with you Faouzi but what Cyril means is that it maybe should be at the "general debugger" level rather than on Sindarin.
That's another subject but in my opinion Sindarin should be removed from the system, and be an external, optional project. If that ever happens, should we still want to have the feature you propose available in the debugger?
If that is so, then it just means you have to rename and move your command class in the debugger packages with other commands ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah now i see what you mean, in this case i'll try to move the command into the debugger. Thanks for clearing this up for me :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Steven about sindarin, let us know. I liked the idea of being able to script the debugger.
What I can tell you is that with debug info we paid attention not to break it.
If it is out of Pharo, it will be probably difficult to maintain it. Now I think that for debug info we will not do more changes. so may be we could remove it when the debugger can use offlinedebuginfo like that it will be in a good shape for the future.

#superclass : 'SindarinCommand',
#category : 'NewTools-Sindarin-Commands',
#package : 'NewTools-Sindarin-Commands'
}

{ #category : 'default' }
SindarinCopyOsInfo class >> defaultDescription [

^ 'Copy to clipboard system information and Pharo image version'
]

{ #category : 'initialization' }
SindarinCopyOsInfo class >> defaultIconName [
^#smallCopy
]

{ #category : 'default' }
SindarinCopyOsInfo class >> defaultName [
<toolbarExtensionDebugCommand: 50>
<codeExtensionDebugCommand:1 >
^ 'Copy system information'
]

{ #category : 'executing' }
SindarinCopyOsInfo >> execute [

Clipboard clipboardText: self systemInfo.
]

{ #category : 'as yet unclassified' }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No as yet unclassified

SindarinCopyOsInfo >> systemInfo [

^ Smalltalk os platformName,
Smalltalk os version ,
Character space asString ,
Smalltalk os subtype ,
Character cr asString,
Smalltalk image lastUpdateString
]
Loading