The Inbox: Tools-LM.808.mcz
Locked
 
|
A new version of Tools was added to project The Inbox:
http://source.squeak.org/inbox/Tools-LM.808.mcz ==================== Summary ==================== Name: Tools-LM.808 Author: LM Time: 28 April 2018, 4:16:15.825505 pm UUID: 44402b15-5903-4ba6-87eb-544389e25886 Ancestors: Tools-cmm.807 Added the ability to copy a bug report to the clipboard by right clicking on the stack trace in the Debugger and selecting "bug report to clipboard". This feature is added as an alternative to the "mail out bug report" feature, in the case that the bug report is not meant to be sent as an email, but rather distributed in a different way (for example via Github issues). It should make it easier for users to report bugs in detail and for developers to diagnose the issue. =============== Diff against Tools-cmm.807 =============== Item was added: + ----- Method: Debugger>>copyBugReportToClipboard (in category 'context stack menu') ----- + copyBugReportToClipboard + + | messageStream | + messageStream := WriteStream on: (String new: 1500). + self interruptedContext errorReportOn: messageStream. + Clipboard clipboardText: messageStream contents.! Item was changed: ----- Method: Debugger>>mainContextStackMenu: (in category 'context stack menu') ----- mainContextStackMenu: aMenu "Set up the menu appropriately for the context-stack-list, unshifted" <contextStackMenuShifted: false> ^ aMenu addList: #( ('fullStack (f)' fullStack) ('restart (r)' restart) ('proceed (p)' proceed) ('step (t)' doStep) ('step through (T)' stepIntoBlock) ('send (e)' send) ('where (w)' where) ('peel to first like this' peelToFirst) - ('return entered value' returnValue) - ('toggle break on entry' toggleBreakOnEntry) ('senders of (n)' browseSendersOfMessages) ('implementors of (m)' browseMessages) ('inheritance (i)' methodHierarchy) - ('versions (v)' browseVersions) - ('references (r)' browseVariableReferences) ('assignments (a)' browseVariableAssignments) - ('class refs (N)' browseClassRefs) ('browse full (b)' browseMethodFull) ('file out ' fileOutMessage) - + ('mail out bug report' mailOutBugReport) + ('bug report to clipboard' copyBugReportToClipboard)); - ('mail out bug report' mailOutBugReport)); yourself ! |
Re: The Inbox: Tools-LM.808.mcz
|
|
The "mail out" option is cool but not useful for the vast majority,
and a bit out-of-place in the IDE; nowhere else makes use of email. We don't need two options on this menu to be so similar, I think we should have only one or the other, and my vote is for the new one, Clipboard. On Sat, Apr 28, 2018 at 9:16 AM, <[hidden email]> wrote: > A new version of Tools was added to project The Inbox: > http://source.squeak.org/inbox/Tools-LM.808.mcz > > ==================== Summary ==================== > > Name: Tools-LM.808 > Author: LM > Time: 28 April 2018, 4:16:15.825505 pm > UUID: 44402b15-5903-4ba6-87eb-544389e25886 > Ancestors: Tools-cmm.807 > > Added the ability to copy a bug report to the clipboard by right clicking on the stack trace in the Debugger and selecting "bug report to clipboard". > This feature is added as an alternative to the "mail out bug report" feature, in the case that the bug report is not meant to be sent as an email, but rather distributed in a different way (for example via Github issues). It should make it easier for users to report bugs in detail and for developers to diagnose the issue. > > =============== Diff against Tools-cmm.807 =============== > > Item was added: > + ----- Method: Debugger>>copyBugReportToClipboard (in category 'context stack menu') ----- > + copyBugReportToClipboard > + > + | messageStream | > + messageStream := WriteStream on: (String new: 1500). > + self interruptedContext errorReportOn: messageStream. > + Clipboard clipboardText: messageStream contents.! > > Item was changed: > ----- Method: Debugger>>mainContextStackMenu: (in category 'context stack menu') ----- > mainContextStackMenu: aMenu > "Set up the menu appropriately for the context-stack-list, unshifted" > <contextStackMenuShifted: false> > ^ aMenu addList: #( > ('fullStack (f)' fullStack) > ('restart (r)' restart) > ('proceed (p)' proceed) > ('step (t)' doStep) > ('step through (T)' stepIntoBlock) > ('send (e)' send) > ('where (w)' where) > ('peel to first like this' peelToFirst) > - > ('return entered value' returnValue) > - > ('toggle break on entry' toggleBreakOnEntry) > ('senders of (n)' browseSendersOfMessages) > ('implementors of (m)' browseMessages) > ('inheritance (i)' methodHierarchy) > - > ('versions (v)' browseVersions) > - > ('references (r)' browseVariableReferences) > ('assignments (a)' browseVariableAssignments) > - > ('class refs (N)' browseClassRefs) > ('browse full (b)' browseMethodFull) > ('file out ' fileOutMessage) > - > + ('mail out bug report' mailOutBugReport) > + ('bug report to clipboard' copyBugReportToClipboard)); > - ('mail out bug report' mailOutBugReport)); > yourself > ! > > |
Squeak email client? (was Re: The Inbox: Tools-LM.808.mcz)
|
|
> On 28-04-2018, at 12:35 PM, Chris Muller <[hidden email]> wrote: > > The "mail out" option is cool but not useful for the vast majority, > and a bit out-of-place in the IDE; nowhere else makes use of email. I agree - hardly anyone will have set up to use email within an image and I'm all for simplifying menus where possible. Copy to clipboard seems by far the more useful option here. Mind you, it would be nice if people *did* frequently use email in Squeak! Given how my email (Mac OS mail app) regularly seems to get worse, perhaps it's time to write a really good email client. Yes, I've looked at others and mostly concluded they're even worse. My ideal would be a single UI that composites emails, twitter-like stuff, skype & Messages traffic, and anything else in the field. You might even persuade me to use Slack if it was all in one. tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Strange OpCodes: DUL: Delete Utility Library |
Re: The Inbox: Tools-LM.808.mcz
|
|
In reply to this post by Chris Muller-3
+1 for clipboard
On 4/28/18, Chris Muller <[hidden email]> wrote: > The "mail out" option is cool but not useful for the vast majority, > and a bit out-of-place in the IDE; nowhere else makes use of email. > > We don't need two options on this menu to be so similar, I think we > should have only one or the other, and my vote is for the new one, > Clipboard. > > > On Sat, Apr 28, 2018 at 9:16 AM, <[hidden email]> wrote: >> A new version of Tools was added to project The Inbox: >> http://source.squeak.org/inbox/Tools-LM.808.mcz >> >> ==================== Summary ==================== >> >> Name: Tools-LM.808 >> Author: LM >> Time: 28 April 2018, 4:16:15.825505 pm >> UUID: 44402b15-5903-4ba6-87eb-544389e25886 >> Ancestors: Tools-cmm.807 >> >> Added the ability to copy a bug report to the clipboard by right clicking >> on the stack trace in the Debugger and selecting "bug report to >> clipboard". >> This feature is added as an alternative to the "mail out bug report" >> feature, in the case that the bug report is not meant to be sent as an >> email, but rather distributed in a different way (for example via Github >> issues). It should make it easier for users to report bugs in detail and >> for developers to diagnose the issue. >> >> =============== Diff against Tools-cmm.807 =============== >> >> Item was added: >> + ----- Method: Debugger>>copyBugReportToClipboard (in category 'context >> stack menu') ----- >> + copyBugReportToClipboard >> + >> + | messageStream | >> + messageStream := WriteStream on: (String new: 1500). >> + self interruptedContext errorReportOn: messageStream. >> + Clipboard clipboardText: messageStream contents.! >> >> Item was changed: >> ----- Method: Debugger>>mainContextStackMenu: (in category 'context >> stack menu') ----- >> mainContextStackMenu: aMenu >> "Set up the menu appropriately for the context-stack-list, >> unshifted" >> <contextStackMenuShifted: false> >> ^ aMenu addList: #( >> ('fullStack (f)' >> fullStack) >> ('restart (r)' restart) >> ('proceed (p)' proceed) >> ('step (t)' >> doStep) >> ('step through (T)' >> stepIntoBlock) >> ('send (e)' >> send) >> ('where (w)' where) >> ('peel to first like this' >> peelToFirst) >> - >> ('return entered value' >> returnValue) >> - >> ('toggle break on entry' >> toggleBreakOnEntry) >> ('senders of (n)' >> browseSendersOfMessages) >> ('implementors of (m)' browseMessages) >> ('inheritance (i)' >> methodHierarchy) >> - >> ('versions (v)' >> browseVersions) >> - >> ('references (r)' >> browseVariableReferences) >> ('assignments (a)' >> browseVariableAssignments) >> - >> ('class refs (N)' >> browseClassRefs) >> ('browse full (b)' >> browseMethodFull) >> ('file out ' >> fileOutMessage) >> - >> + ('mail out bug report' mailOutBugReport) >> + ('bug report to clipboard' >> copyBugReportToClipboard)); >> - ('mail out bug report' >> mailOutBugReport)); >> yourself >> ! >> >> > > |
Re: Squeak email client? (was Re: The Inbox: Tools-LM.808.mcz)
|
|
In reply to this post by timrowledge
Glad you brought that up Tim :) I am using email on a daily basis in Squeak. While there are still lots of things to fix, it works well enough to get most of my reading, writing and organizing of emails done. What I like most about having my emails in Squeak is how fast I can adapt things. For example, I have an extension for my email reader which checks the sender of an email and if the email comes from students it shows me the groups they are in. Building that extension took me about 10 minutes (mostly UI work).
From a technical perspective, I am using the email abstraction from the base system, a Python-based IMAP to maildir synchronization tool (https://github.com/OfflineIMAP/offlineimap), and a maildir reader (https://github.com/codeZeilen/SMailDir). This way I can have objects for every email in my image and at the same time quickly access the content of most emails. If anyone is interested in setting this up for themselves I am happy to help. I would love to change the synchronization process to a Squeak-based library at one point (some work is done by students at HPI https://github.com/hpi-swa-teaching/IMAPClient). Besides that: I also think copy to clipboard is the better option for the debugger. :) Bests Patrick > > >> On 28-04-2018, at 12:35 PM, Chris Muller <[hidden email]> wrote: >> >> The "mail out" option is cool but not useful for the vast majority, >> and a bit out-of-place in the IDE; nowhere else makes use of email. > >I agree - hardly anyone will have set up to use email within an image and I'm all for simplifying menus where possible. Copy to clipboard seems by far the more useful option here. > >Mind you, it would be nice if people *did* frequently use email in Squeak! Given how my email (Mac OS mail app) regularly seems to get worse, perhaps it's time to write a really good email client. Yes, I've looked at others and mostly concluded they're even worse. > >My ideal would be a single UI that composites emails, twitter-like stuff, skype & Messages traffic, and anything else in the field. You might even persuade me to use Slack if it was all in one. > > >tim >-- >tim Rowledge; [hidden email]; http://www.rowledge.org/tim >Strange OpCodes: DUL: Delete Utility Library > > > |
Re: Squeak email client? (was Re: The Inbox: Tools-LM.808.mcz)
|
|
> On 30-04-2018, at 2:07 AM, <[hidden email]> <[hidden email]> wrote: > > Glad you brought that up Tim :) I am using email on a daily basis in Squeak. This is very cool. I know Jecel uses Celeste and that's about it. > While there are still lots of things to fix, it works well enough to get most of my reading, writing and organizing of emails done. What I like most about having my emails in Squeak is how fast I can adapt things. For example, I have an extension for my email reader which checks the sender of an email and if the email comes from students it shows me the groups they are in. Building that extension took me about 10 minutes (mostly UI work). Neat; that sounds really useful for workgroups etc. Filtering in the 'normal' manner by address is ok but we could actually lookup the address in assorted registries dynamically. And the usual content parsing - though there are (or were? possibly expired by now) patents about that. > > From a technical perspective, I am using the email abstraction from the base system, a Python-based IMAP to maildir synchronization tool (https://github.com/OfflineIMAP/offlineimap), and a maildir reader (https://github.com/codeZeilen/SMailDir). This way I can have objects for every email in my image and at the same time quickly access the content of most emails. If anyone is interested in setting this up for themselves I am happy to help. > > I would love to change the synchronization process to a Squeak-based library at one point (some work is done by students at HPI https://github.com/hpi-swa-teaching/IMAPClient). All we need to do (™) is add fetchers for tweets, messages, skype stuff, whatsapp, and so on. Easy! IPO next week! tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Strange OpCodes: CSD: Charge Surreptitiously to DOE |
Re: Squeak email client? (was Re: The Inbox: Tools-LM.808.mcz)
|
|
Sounds like I should look into this. The best mail client I’ve ever used was Eudora. How I miss Eudora.
Encrypted email at [hidden email] Web: www.objectnets.net and www.objectnets.org
|
«
Return to Squeak - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |