Squeak-dev January 2018

squeak-dev@lists.squeakfoundation.org

50 participants
171 discussions

Unicode display support in text morphs?
by Lawson English 27 Jan '18

27 Jan '18

I was going to start a project or two related to learning Japanese and I need to be able to input (and display) Japanese characters in squeak text morphs. This doesn't seem to be possible? I've got all sorts of Japanese fonts loaded on my Mac, but not a clue how to display such characters. I'm trying to do a bit of translation of juvenile books and want to track which words I've already dealt with so I don't have to recreate the wheel constantly. I can do it in TextEdit and other Mac text editing applications, but the ability to do it in Squeak would open up vast new worlds in this regard. BUT, I can't see how to get started. Thanks for any advice. For example, how do I display 「こんにちは」　or 「今日は」　surrounded by English text in a text morph? Is this even possible? Lawson

2 1

Did you VOTE?
by Ron Teitelbaum 26 Jan '18

26 Jan '18

Hi all, I know it seems like there is a lot of time left to vote but it goes fast and it becomes harder and harder to find your ballot if you wait much longer! Please take the time to find your ballot and vote for the Squeak Oversight Board 2018. Please let me know if you can't find your ballot. I am happy to resend it to you! For everyone that has voted so far THANK YOU! It's a great way to show your support for the board! All the best, Ron Teitelbaum

1 0

Transcript flush
by Eliot Miranda 26 Jan '18

26 Jan '18

Hi All, recently Transcript flush, in the context of the UI process, no longer causes the Transcript to display its contents immediately. This is a most serious regression and I ask that it be rectified as soon as possible. I would rather have a slower transcript than one that does not update immediately on being sent flush. One can always use show: if one does not require immediate update, but flush implies that one wants to see the update now. Yes, one can use the progress notification for update but it has its own issues with its complex structure. being able to write periods to the transcript occasionally is something I depend upon. To reproduce, the following should update the transcript periodically, but now no longer; no output appears until one interrupts the computation: 0 to: SmallInteger maxVal do: [:i| i \\ 10 = 0 ifTrue: [Transcript nextPut: $.; flush]. 10000 factorial] _,,,^..^,,,_ best, Eliot

2 2

Fwd: [Pharo-dev] Code Completion
by Eliot Miranda 26 Jan '18

26 Jan '18

From: "Torsten Bergmann" <astares(a)gmx.de> Date: January 25, 2018 at 11:51:17 PM PST To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Code Completion Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org> Hi Myroslava, some infos: Initially for Squeak there was "eCompletion" written by Ruben Bakker. According to the package "eCompletion is code completion inspired by eclipse", it required MCInstaller, Shout 4 and RoelTyper. http://uncomplex.net/ecompletion/ Back in Squeak "Shout" was used to have syntax highlighting as you type. RoelTyper is a fast type reconstructor for Smalltalk (name comes from its Author Roel Wuyts) https://roelwuyts.be/roeltyper/index.html https://www.youtube.com/watch?v=CvKTCSv7s8s Later oCompletion followed - "OCompletion builds on ECompletion and improves its accuracy." http://www.squeaksource.com/OCompletion/ http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf OCompletion uses (based on recent activity) considerably improves the accuracy of code completion. That is, the actual selector you want to insert is usually in the top 3 matches OCompletion proposes. https://news.squeak.org/tag/ocompletion/ A paper you should read is https://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf OCompletion is a re-working of the venerable eCompletion package, based on research done by Romain Robbes and Michele Lanza. OCompletion is in Pharo since Pharo 2.0 There already was a discussion about better completion back in 2015 https://www.mail-archive.com/pharo-users@lists.pharo.org/msg14835.html based on the need for pluggability (https://pharo.fogbugz.com/f/cases/13124/NECContext-needs-plugin-design) and basing it on AST instead of Shout https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… So NECController is the old code and NOCController (there was a setting to change from one to the other) ECompletion was just a list of matching classes/selectors. OCompletion added some candy like showing first last typed entries (with some other heuristic). http://www.jarober.com/blog/blogView?showComments=true&title=ST+4U+46%3A+Au… What I always liked in Eclipse compared to Pharo is that you can code complete an expression and the parameters are visualized with a rectangle and by "tabbing" you can fill each of them: https://www.youtube.com/watch?v=OMbVQcZ0gV8 Also one can do own code templates who are used in the completion then: https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2… Some other alternatives: CACHECA is a cache language model based code suggestion tool (https://github.com/christinef/CACHECA) for Eclipse which could be seen in https://www.youtube.com/watch?v=3INk0N3JNtc RubyMine code completion for Ruby https://www.jetbrains.com/help/ruby/auto-completing-code.html Thanks T. Gesendet: Donnerstag, 25. Januar 2018 um 22:52 Uhr Von: "Myroslava Romaniuk" <romaniuk(a)ucu.edu.ua> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff: [Pharo-dev] Code Completion Hi, I'm Myroslava Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any resources that would help me better understand how it works? I'd also like to know what's the difference between ecompletion and ocompletion, and what's NOC and NEC completion, as it doesn't seem very clear to me so far? If any of you worked on it and can help me get started, I would really appreciate it. Thanks

1 0

Programming Experience 2018 (PX/18) Workshop | Call for Papers
by Robert Hirschfeld 26 Jan '18

26 Jan '18

Programming Experience 2018 (PX/18) Workshop | Call for Papers ============================================================== April 10 (Tue), 2018 Co-located with <Programming> 2018 in Nice, France http://2018.programming-conference.org/track/px-2018-papers http://programming-experience.org/px18 Abstract -------- Imagine a software development task: some sort of requirements and specification including performance goals and perhaps a platform and programming language. A group of developers head into a vast workroom. In that room they design and code—and sometimes they discover they need to explore the domain and the nature of potential solutions. The Programming Experience (PX) Workshop is about what happens in that room when one or a couple of programmers sit down in front of computers and produce code. Do they create text that is transformed into running behavior (the old way), or do they operate on behavior directly (“liveness”); are they exploring the live domain to understand the true nature of the requirements; are they like authors creating new worlds; does visualization matter; is the experience immediate, immersive, vivid and continuous; do fluency, literacy, and learning matter; do they build tools, meta-tools; are they creating languages to express new concepts quickly and easily; and curiously, is joy relevant to the experience? Here is a list of topic areas to get you thinking: - creating programs - liveness - domain-specific languages - psychology of programming - user studies - visual, auditory, tactile, and other non-textual languages - text and more than text - program understanding - error tolerance - non-standard tools - experience of programming - exploratory programming The experience of programming and how to improve and evolve it are the focus of this workshop, and in this edition we would like to focus on exploratory programming. Submissions ----------- Submissions are solicited for Programming Experience 2018 (PX/18). The thrust of the workshop is to explore the human experience of programming—what it feels like to program, or more accurately, what it should feel like. The technical topics include exploratory programming, live programming, authoring, representation of active content, visualization, navigation, modularity mechanisms, immediacy, literacy, fluency, learning, tool building, and language engineering. Submissions by academics, professional programmers, and non-professional programmer are welcome. Submissions can be in any form and format, including but not limited to papers, presentations, demos, videos, panels, debates, essays, writers' workshops, and art. Presentation slots will be between 30 minutes and one hour, depending on quality, form, and relevance to the workshop. Submissions directed toward publication should be so marked, and the program committee will engage in peer review for all such papers. Video publication will be arranged. All artifacts are to be submitted via EasyChair (https://easychair.org/conferences/?conf=px18). Papers and essays must be written in English, provided as PDF documents, and follow the new ACM Conference 'acmart' Format with the 'sigconf' option using the Times New Roman font family with 10 point font size. If you are formatting your paper using LaTeX, you will need to set the '10pt' option in the '\documentclass' command. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission for review using the LaTeX command '\settopmatter{printfolios=true}' (see examples in template). Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. There is no page limit on submitted papers and essays. It is, however, the responsibility of the authors to keep the reviewers interested and motivated to read the paper. Reviewers are under no obligation to read all or even a substantial portion of a paper or essay if they do not find the initial part of it interesting. Review ------ Papers and essays labeled as publications will undergo standard peer review; other submissions will be reviewed for relevance and quality; shepherding will be available. Important dates --------------- - Submissions: February 10, 2018 (anywhere in the world) - Notifications: March 2, 2018 - Intermediate versions: March 17, 2018 - PX/18: April 10, 2018 - Final versions: April 28, 2018 - Publication Papers and essays accepted through peer review will be published as part of ACM's Digital Library; video publication on Vimeo or other streaming site; other publication on the PX workshop website. Workshop format --------------- Paper presentations, presentations without papers, live demonstrations, performances, videos, panel discussions, debates, writers' workshops, art galleries, dramatic readings. We will be following a variant of the writers' workshop format used in the software patterns community. This format works well when the goals include improving the form or presentation of the ideas as well as improving or understanding the ideas themselves. In the writers' workshop: - A moderator leads and directs the discussion. - We review the pieces and their ideas one at a time. - In general, the authors whose work is under review are silent. - When discussing form, the following kinds of questions will be asked: + What did you gather / understand from the piece? + What aspects of the piece worked well to present the ideas? + What aspects need improvement? (These comments must be in the form of suggestions, not criticisms.) - When discussing the ideas, the following kinds of questions will be asked: + What are the ideas? + Which ideas seem like good ones (and why)? + Which ideas need improvement or elimination? (Make positive suggestions when you can.) - At the end the authors ask questions of the group. This is the basic format, but we adjust the flow according to the needs of the group and the way the discussion is going. It is formal to ensure all the important points are covered. For more information about the workshop format, please have a look at Richard P. Gabriel's book "Writers' Workshops & the World of Making Things" (at dreamsongs.com). Organizers ---------- - Luke Church, University of Cambridge, United Kingdom - Richard P. Gabriel, Dreamsongs and Hasso Plattner Institute, California - Robert Hirschfeld, Hasso Plattner Institute, University of Potsdam, Germany - Hidehiko Masuhara, School of Computing, Tokyo Institute of Technology, Japan Program committee ----------------- - Titus Barik, Microsoft AI+Research, United States - Kerry Chang, IBM TJ Watson Research Center, United States - Parmit Chilana, Simon Fraser University, Canada - Ravi Chugh, University of Chicago, United States (LIVE 2018) - Jonathan Edwards, Y Combinator Research, United States (LIVE 2018) - Jun Kato, National Institute of Advanced Industrial Science and Technology, Japan - Stefan Marr, University of Kent, United Kingdom - Yoshiki Ohshima, Viewpoints Research Institute, United States - Stephen Oney, University of Michigan, United States - Roland Perera, University of Glasgow, United Kingdom (LIVE 2018) - Michael Perscheid, SAP Innovation Center, Germany - Guido Salvaneschi, Technische Universität Darmstadt, Germany - Marcel Taeumel, Hasso Plattner Institute, University of Potsdam, Germany - Steven L. Tanimoto, University of Washington, United States - Allen Wirfs-Brock, Wirfs-Brock Associates, United States We welcome the organizers of LIVE 2018 to our program committee to help us build a lively, programming experience community. PX editions ----------- - PX/18 at <Programming> 2018, April 9 or 10, 2018, Nice, France - PX/17.2 at SPLASH 2017, October 22, 2017, Vancouver, British Columbia, Canada - PX/17 at <Programming> 2017, April 3, 2017, Brussels, Belgium - PX/16 at ECOOP 2016, July 18, 2016, Rome, Italy -- Robert Hirschfeld hirschfeld(a)acm.org www.hirschfeld.org

2 2

The Trunk: Collections-mt.781.mcz
by commits＠source.squeak.org 26 Jan '18

26 Jan '18

Marcel Taeumel uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-mt.781.mcz ==================== Summary ==================== Name: Collections-mt.781 Author: mt Time: 26 January 2018, 7:41:59.694036 am UUID: c0e03e0a-31fe-384d-bc46-71aff7946d0f Ancestors: Collections-mt.780 For the ReleaseBuilder, adds setter for #characterLimit Transcript preference. =============== Diff against Collections-mt.780 =============== Item was added: + ----- Method: TranscriptStream class>>characterLimit: (in category 'preferences') ----- + characterLimit: anInteger + + CharacterLimit := anInteger.!

1 0

Removing of Universe classes
by H. Hirzel 26 Jan '18

26 Jan '18

On 11/25/15, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 24 November 2015 at 21:09, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> On 11/21/15, Chris Muller <asqueaker(a)gmail.com> wrote: >>> On Fri, Nov 20, 2015 at 12:40 PM, tim Rowledge <tim(a)rowledge.org> wrote: >>>> I suggest we should Universes. >>> +1. +1. +1 and, +1. .. > > I was under the impression that Universes _was removed_, like, back in > 4.4 or the beginning of the 4.5 cycle, when I was up to my eyeballs in > hairy dependencies... Certainly the build processes think so - > https://github.com/squeak-smalltalk/squeak-ci/blob/master/package-load-scri… > is the _load script_ for Universes (implying its _unloaded by default_ > state). > > frank > >> I think this has been discussed before the release of 4.6 and people >> agreed but at that time it was to late to do it. >> >> --Hannes >> > > Hi Frank Indeed I do not see a Universe browser in the app menu of Squeak 5.0. However there seem to be some classes left in the system, see screen shot. So there was removal but it seems it was not done completely.

9 14

Opening two debuggers in a single doit
by Eliot Miranda 26 Jan '18

26 Jan '18

Hi All, I'm comparing two close copies of a class in attempting a complex refactoring, comparing the original code with the close copy. In doing this I need to open up two debuggers to step through the two computations simultaneously. If I try it this way, where the two JITs break at a particular bytecode: [:m :opts| [StackToRegisterMappingCogit cog: m options: opts] fork. Processor yield. AltStackToRegisterMappingCogit cog: m options: opts] value: TabbedPalette class>>#unload value: #(ObjectMemory Spur64BitCoMemoryManager debugBytecodePointers #(59) compilationTrace 0). I get an emergency evaluator :-(, and if I type restart I only ever get one debugger. What's the right way to do this? To boil down the example I need this to work: [1 halt] fork. Processor yield. 2 halt i.e. I want to be able to get two debuggers, one open on 1 halt, and the other on 2 halt. _,,,^..^,,,_ best, Eliot

8 16

The Trunk: System-dtl.998.mcz
by commits＠source.squeak.org 26 Jan '18

26 Jan '18

David T. Lewis uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-dtl.998.mcz ==================== Summary ==================== Name: System-dtl.998 Author: dtl Time: 25 January 2018, 8:05:33.27544 pm UUID: d20b1282-caaa-4e4f-8025-a85608b6345e Ancestors: System-bf.997 Project>>dispatchTo:addPrefixAndSend:withArguments: no longer requires manual update of baseSelectors since System-bf.997. Update method comment accordingly. =============== Diff against System-bf.997 =============== Item was changed: ----- Method: Project>>dispatchTo:addPrefixAndSend:withArguments: (in category 'dispatching') ----- dispatchTo: requestor addPrefixAndSend: baseSelector withArguments: arguments "Sender wants to perform a method with dependencies on the type of project. Dispatch to an appropriate method for the current project. - If additional base selectors are added for dispatching, the list of base selectors - in Project class>>baseSelectors should be updated. - This method is a workaround for lack of proper ToolBuilder support in the sender, and should be eliminated when possible (dtl Feb 2010)" <hasLiteralTest: #isDispatchSelector:> | selector | selector := (self selectorPrefixForDispatch, baseSelector) asSymbol. ^ requestor perform: selector withArguments: arguments!

1 0

The Trunk: System-bf.997.mcz
by commits＠source.squeak.org 26 Jan '18

26 Jan '18

David T. Lewis uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-bf.997.mcz ==================== Summary ==================== Name: System-bf.997 Author: bf Time: 25 January 2018, 4:56:35.380251 pm UUID: 604954ca-0389-43c0-a5c7-4ddc8e613cc9 Ancestors: System-dtl.996 Simplify project dispatch selector detection. No hard-coded list. Almost as good. =============== Diff against System-dtl.996 =============== Item was removed: - ----- Method: Project class>>baseSelectors (in category 'dispatching') ----- - baseSelectors - "The list of known base selectors that may be dispatched to project specific - implementations. For example, #OpenLabel:in: will be dispatched to #mvcOpenLabel:in: - for its MVC specific implementation. Add new base selectors here if additional methods - are added as targets of the dispatchTo:addPrefixAndSend:withArguments: mechanism." - - ^ { - #StartUpLeftFlush . - #StartUpWithCaption:icon:at:allowKeyboard: . - #OpenLabel:in: . - #Open: . - #Open . - #OpenOn:context:label:contents:fullView: . - #ResumeProcess: . - #OpenContext:label:contents: - } - ! Item was removed: - ----- Method: Project class>>dispatchSelectors (in category 'dispatching') ----- - dispatchSelectors - "All known targets of the dispatch mechanism" - - "Project dispatchSelectors" - - | selectors dispatchPrefixes | - selectors := OrderedCollection new. - dispatchPrefixes := Set withAll: (Project allSubclasses collect: [ :e | e basicNew selectorPrefixForDispatch ]). - self baseSelectors do: [ :base | - dispatchPrefixes do: [ :prefix | - selectors add: (prefix, base) asSymbol ] ]. - ^ selectors - - ! Item was changed: ----- Method: Project class>>isDispatchSelector: (in category 'dispatching') ----- isDispatchSelector: aSelector "In support of package modularity, some method selectors are generated based on project type and dispatched to the appropriate implementation for that project. For methods with these selectors, let dispatchTo:addPrefixAndSend:withArguments: be found as a sender." + | dispatchPrefixes prefix otherSelector | + dispatchPrefixes := Project allSubclasses collect: + [:cls | cls basicNew selectorPrefixForDispatch]. + "If it doesn't start with a recognized prefix, it's not dispatchable" + prefix := dispatchPrefixes detect: [:each | aSelector beginsWith: each] + ifNone: [^false]. + "If a similar symbol exists for all other prefixes, it's likely dispatchable" + ^(dispatchPrefixes copyWithout: prefix) + allSatisfy: [:otherPrefix | + otherSelector := otherPrefix, (aSelector allButFirst: prefix size). + Symbol hasInterned: otherSelector ifTrue: [:s]] - - ^ self dispatchSelectors includes: aSelector. !

1 0

← Newer
1
2
3
4
5
6
7
8
...
18
Older →

Jump to page: