January 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] New Cog VMs available...
by Eliot Miranda Jan. 9, 2013

Jan. 9, 2013

...at http://www.mirandabanda.org/files/Cog/VM/VM.r2662/. CogVM binaries as per VMMaker.oscog-eem.251/r2662 Give primitiveRemLargeIntegers primitive # 20. Add yet another libc line to the linux launch script(s), and try and make the script suggest users extend it themselves. you can lead a horse to water... Fix (old) bug in ssAllocateRequiredRegMask:upThrough: that would flush entire stack if allocating any register. Implement absent receiver sends in the Newspeak Cogit. On Mac turn off inlining when compiling the Cogit. The Cogit's runtime is negligible and we prefer to save space. With the recent changes (better shift code??) the VM appears faster anyway. Integrate directed shift changes from cog issue 111 that affect the CoInterpreter and Cogit. Make the translated primitive plugins include info from their primitive supplying classes. Integrate changes from VMMaker-dtl.293 which use >> & << shifts in place of slower bitShift: code in plugins. Add width failure cases to BMPReadWriterPlugin read & write 24Bmp prims. Integrate issue 115. Fix FFIPlugin/ThreadedFFIPlugin unsignedShortAt:. -- Happy New Year everyone, Eliot

1 1

[Pharo-project] UI blocked
by Janko MivÅ¡ek Jan. 8, 2013

Jan. 8, 2013

Hi guys, My 1.3 #13299 image is blocked again, but just UI not responding to any input events, while Aida web app server is running smoothly in backrgound. >From Transcript I can see that last action was a new image backup procedure, which is done simply by : OSProcess waitForCommand: 'cp some.image some-bck.image'. This procedure is called from a background process and report to Transcript its start and end. Is there something wrong with that? Or is some interference with OSProcess semaphores? (I saw such suspicious thing once before). In any case, is there a way to unblock image now? Ctrl or Alt . doesn't help. Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

5 7

Re: [Pharo-project] Is there a simple example of how to create a GUI form in Pharo or Squeak?
by Fernando Olivero Jan. 8, 2013

Jan. 8, 2013

Hi, two good sources of information on GUI building are http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html?utm_source=… http://book.pharo-project.org/book/LanguageAndLibraries/GUI/?_s=yllsSvKBo5c… They're not that hard to find (if you are aware of the Collab book and the pharocasts). You might want to check out Glamour also, http://www.themoosebook.org/book/internals/glamour Fernando On Mon, Dec 24, 2012 at 11:22 AM, Frank Church <vfclists(a)gmail.com> wrote: > Is there a simple example of how to create a GUI form in Pharo or Squeak? > > I want to accomplish a simple task with a form: > > 1. Create a form with a button and edit control and 2 text areas. > > 2. Enter a value into the edit control. > > 3. Run a database query using the value in the edit control as a parameter > and return the results in text area 1 > > 4. Run a shell script using the value in the edit control as a parameter > and return the results in text area 2 > > I have OpenDBX running successfully and I don't think using OSProcess and > CommandShell will be that difficult. > > Creating the form is the part I don't know how to accomplish. > > I have done some searching and there seems to be a surprising dearth of > info on how to create a simple GUI from scratch using Pharo or Squeak. > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com >

2 1

[Pharo-project] Spec news
by Pavel Krivanek Jan. 8, 2013

Jan. 8, 2013

Hi Ben, trying to run Periscope on the latest Pharo image, I see that everything is broken again. Please, start to write some documentation about Spec development, what have you changed, what do you plan to change, what are the new prefered ways to write UI specification and how to migrate old code. At least write some short mails here. I know, it is a lot of work but we cannot write tools and bindings to other user interface if the basic UI framework is undocumented and changing silently. Cheers, -- Pavel

5 12

Re: [Pharo-project] About morph layout
by Fernando Olivero Jan. 8, 2013

Jan. 8, 2013

Hi, a couple of years ago, i tried to port Small Morphic from CUIS to Pharo1.2. After a couple of weeks i gave up, because there are to many relations between the UI framework and the underlying system, which made it not just a matter of UI porting, but a complete system diff. Morphic relies on some kernel graphics which slightly differ in both systems (Form, Canvas, etc..), and on the base object model infrastructure, and some IDE related objects such as SystemNavigation , UIManager, etc.. I prefer the approach taken by Stef and other community members, clean the current system one step at a time. Maybe, there will be some overlapping with Juan's great work on CUIS, but on the bright side you wont get burned trying to port, manage, and plug a new Morphic into Pharo. Fernando pd: It was so hard, i decided to start a new UI framework from the ground up. On Wed, Jan 2, 2013 at 7:52 PM, Chris Muller <asqueaker(a)gmail.com> wrote: > Craig's NAIAD stands for "Name And Identity Are Distinct". Just > thinking aloud -- because Morphic is so entrenched.. Could NAIAD or > Colin's Environments allow Juan's Morphic (or, Morphic3) to co-exist > with original Morphic, so that it would allow working on the port > without depending on it for the tools? Once the port was complete, a > sane migration could more easily occur.. > > > On Wed, Jan 2, 2013 at 7:00 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 2 January 2013 12:55, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >> Hello again Igor > >> and Happy and Successful New "Pharo" Year 2013 > >> > > > > Thanks Hannes :) > > Wish best to you in New Year too :) > > > > > >> --Hannes > >> > >> my notes are inserted below. > >> > >> > >> On 12/24/12, Igor Stasenko <siguctua(a)gmail.com> wrote: > >>> On 24 December 2012 09:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >>>> Hello Igor > >>>> > >>>> Thank you for this interesting mail. An issue over 11 years old, see > >>>> below. > >>>> > >>>> On 12/24/12, Igor Stasenko <siguctua(a)gmail.com> wrote: > >>>>> Hi, > >>>>> > >>>>> just wanna share some ideas about how we can cleanup morph a bit. > >>>> > >>>> A bit? > >>>> It will be a lot of effort. > >>>> > >>> We can do it in small steps. > >>> > >>>> Squeak 4.4-12234 (current) > >>>> > >>>> Morph selectors size 1183 > >>>> > >>>> > >>>> Pharo 2.0 (Beta) > >>>> > >>>> Morph selectors size 865 > >>>> > >>>> > >>>> Cuis 4.1 (18th Dec 2012) > >>>> > >>>> Morph selectors size 343 > >>>> > >>>> > >>>> This was an issue in 2001 > >>>> > >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2001-June.txt > >>>> > >>>> see > >>>> > >>> I am not first day here, of course i am aware of this :) > >> > >> Did you start working with Squeak already in 2001? > >> > > no. But i know this is a long standing issue :) > > > >>>>> Layout.. bizarre. > >>>> > >>>> Yes, see humorous contribution from June 2001 > >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2001-June.txt > >>>> > >>>> search for > >>>> > >>>> the Morph class has 924 methods > >>>> > >>>> in that mails > >>>> > >>>> There was an effort > >>>> Morphic Cleanup Project > >>>> > >>>> http://wiki.squeak.org/squeak/3005 > >>>> > >>>> lead by > >>>> > >>>> Diego Gomez Deck > >>>> > >>>> It produced some results. But they did not reach far enough. > >>>> > >>> yes yes.. i know. > >>> > >>>> However Juan Vuletic was successful in coming up with a simpler > Morphic in > >>>> Cuis. > >>>> > >>>> http://www.jvuletich.org/Cuis/Index.html > >>>> > >>> search this mailing list for Small Morphic. > >>> It was an attempt to use Juan's work, which didn't fly. > >> > >> Of course I am aware of SmallMorphic. If a first attempt at > >> integrating SimpleMorphic into Pharo was not successful it does not > >> necessarily mean that a second one has to be a failure again. > >> > >> Time spent on an analysis why it didn't fly is surely not a waste. > >> > >> For example another approach could be instead of copying code from > >> Cuis and implanting it into Pharo "blob style" you could follow Juan > >> Vuletich's refactoring steps incrementally and copy smaller chunks of > >> code. Cuis had many releases until it reached version 4.1. > >> > >> In terms of factoring out classes from the class Morph you seem to > >> want to do that anyway. > >> > >> See for example > >> > >> http://www.jvuletich.org/Cuis/CuisReleaseNotes.html > >> New in Cuis 2.7 (released September 3, 2010) > >> > >> * Morphic. New LayoutSpec mechanism. Simpler and nicer. > >> * Morphic Simplification: Layout, Extensions, etc > >> > > > > Well, one thing is that Juan doing quite radical changes to code. > > He is not concerned about backwards compatibility (but unlike from > Pharo, nobody > > raising it as an issue over and over again ;) ). > > Yes, i checked new Cuis code. > > I see a lot of simplifications. But also i see reduced functionality. > > For instance, i did not found things like 'fill style', and themes. > > Also, i see some protocols is renamed, in preparation for something > > bigger (morphic 3 i guess ;) > > > > So, i agree we should not copy/paste the code. Because it won't fly. > > We should gradually analyze it and improve ours step by step. > > > > Layout code in Cuis is somewhat similar to what i proposing. > > But my proposal is essentially about approach, which you can apply to > > anything.. not just layouts in Morphics. > > > >>>>> There are so many methods dedicated to laying out morphs that it easy > >>>>> to get lost. > >>>> > >>>> Cuis has a new layout system. > >>>> > >>>> Worth to check out. > >>>> > >>> Sure. > >> > >> Fine. > >> > >>> > >>>>> For me the main mystery and source of confusion is that there > actually > >>>>> two different groups: > >>>>> > >>>>> - methods to control morph's own layout (in respect to its parent) > >>>>> - methods to control morph's children layout (something called > >>>>> layoutPolicy) > >>>>> > >>>>> the problem is that both APIs are found in single class, > >>>> > >>>> which one? > >>>> > >>> Morph > >>> > >>>> and most of > >>>>> them contain 'layout' word in it, > >>>>> so it is really hard to determine which one to use and when.. > >>>>> > >>>>> Over a years, i seen that people learned how to use existing > >>>>> functionality, without delving deep into > >>>>> implementation detail. > >>>> > >>>> Yes. > >>>> > >>>>> But if you try to extend/change behavior (in your subclass), you will > >>>>> quite soon find out that it is really > >>>>> hard to tell with 100% certainty that the methods you override is the > >>>>> right place for your customization. > >>>> > >>>> Yes, this actually has made development very difficult. In such a way > >>>> that most people have abandoned it. Very few GUIs are actually built > >>>> with it. > >>>> > >>>> > >>>>> Also, an important detail is extremely polluted protocol(s), making > >>>>> Morph a GOD class, > >> > >> Morph is at the root of a large subclasses tree. The question is: what > >> can be pushed down or factored out. An analysis in terms of number of > >> method candidates to move out would surely be a good thing to know. > >> > > > > > > > > -- > > Best regards, > > Igor Stasenko. > > > >

3 2

[Pharo-project] PluggableMultiColumnListMorph example?
by J. P. L. MartÃn Jan. 8, 2013

Jan. 8, 2013

Someone could give me a little example on PluggableMultiColumnListMorph? Does it work with OrderedCollections? Thanks in advance!

2 8

Re: [Pharo-project] FOSDEM 2013 Smalltalk devroom
by Stephan Eggermont Jan. 7, 2013

Jan. 7, 2013

Rafael wrote: >I've noticed that FOSDEM 2013 will host an Smalltalk devroom like the >previous year. Any idea about the scheduled sessions? > >I'd like to see tutorials related with Pharo, Seaside, Amber, Moose, etc. I'm working on finalizing the schedule now. We'll have presentation of the current state of Squeak & Pharo, experience report and getting started with Amber, the active filesystem, a workshop to get started with Smalltalk development, might have BabyMock/GOOS, Oak, Altitude & EtoilÃ©,and some more time to talk than last year. I would welcome someone showing Moose. Need to finalize the schedule soon though. Cheers, Stephan Eggermont

2 1

[Pharo-project] zero conf scripts location
by Camillo Bruni Jan. 6, 2013

Jan. 6, 2013

I plan to move the ci-zero conf scripts to a new subdirectory http://pharo.gforge.inria.fr/ci/script/* instead of http://pharo.gforge.inria.fr/ci/* is anyone besides our ci servers using theses scripts? best cami

2 2

[Pharo-project] [ANN] NBOpenGL update
by Igor Stasenko Jan. 6, 2013

Jan. 6, 2013

Hi there, for those, who interested, i updated a NBOpenGL configuration. Changes are: - updated GL API to most recent available (taken directly from opengl specs). Now there is about 300 more methods to explore :) - finally dealt with win32 support code and made it working again - fixed the GLX function prefix , which should be 'glX' not 'glx' To load it in 1.4 use: Gofer new squeaksource: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. and then (ConfigurationOfNBOpenGL project version: '1.0.2') load I did not tested the update thoroughly.. so i would appreciate if people will try it out and tell how it goes. -- Best regards, Igor Stasenko.

7 13

[Pharo-project] Slides for a talk on "Why I Still Use Smalltalk" for comments
by Stephen Travis Pope Jan. 6, 2013

Jan. 6, 2013

Hello all, I've put together a set of slides for a 90-minute lecture/demo on "Why I Still Use Smalltalk" to be given to a colloquium of graduate media arts and technology students at UCSB (where I taught from 1996-2010). I up-loaded the slides for your comments; there's a 19-page PDF file (6 slides per page) at, http://HeavenEverywhere.com/STP_ST80_Talk_Slides.pdf Your comments/questions are welcome... (The demo at the start will be using VisualWorks to build the canonical up/down counter.) (Slide 12 is me and the head of the composition department at UCSB, both in 1984, for context.) stp -- Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com Begin forwarded message: > From: Stephen Travis Pope <stephen(a)heaveneverywhere.com> > Date: October 26, 2012 12:47:55 PM PDT > To: vwnc <vwnc(a)cs.uiuc.edu> > Cc: Stephen Travis Pope <stephen(a)heaveneverywhere.com> > Subject: Outline of a talk on "Why I Still Use Smalltalk" for comments > > > Hello all, > > I'm planning to give a colloquium called "Why I Still Use Smalltalk" for the graduate students at UCSB, and wanted to solicit your comments on the outline. > > stp > > -------------------- > > Why I Still Use Smalltalk > > Graduate Colloquium > UCSB Graduate Program in Media Arts and Technology > November, 2012 > Stephen Travis Pope, stephen(a)FASTLabInc.com > > -------------------- > > Proposal > > Title: Why I Still Use Smalltalk > > Abstract > > The Smalltalk-80 programming system is celebrating its 30th birthday this year (Smalltalk-80 version 2 was released and documented in a series of books in 1982). The system was the first popular software development tool that incorporated a number of features we take for granted today, including an object-oriented programming language, a comprehensive open-source class library, an integrated window-based development environment, and a cross-platform virtual-machine-based delivery system. Nevertheless, Smalltalk has nowhere near the installed base or the mindshare of lesser peers such as C++ or Java, or more modern descendants such as Python or Ruby. This talk will introduce the Smalltalk system's language, libraries and tools, outline its history, and discuss the reasons why it is not more widely used. Several aspects of the Smalltalk system make it especially good for developing multimedia applications, and these will be introduced with examples from the last 30 years. The presenter was among the very first to use Smalltalk for real-world applications, and worked on the Smalltalk team at Xerox PARC and their spin-off ParcPlace Systems from 1986-94. He still uses Smalltalk (now available in both commercial and free versions) for his day-to-day work. > > Presenter > > Stephen Travis Pope is a software engineer and composer based in Santa Barbara. He taught at UCSB (in the departments of Music and Computer Science, and the Graduate Program in Media Arts and Technology) from 1996-2010, and is now known as FASTLabInc.com (for multimedia software) and HeavenEverywhere.com (for music and film). > > ---------------------------- > > Outline > Introduction > Demo > What Is Smalltalk? > The Language > The Libraries > The Environment > A Brief History > Smalltalk Leaves PARC > C++, ObjectiveC and Java > Smalltalk Today > Why I Still Use Smalltalk > > Introduction > Overview > My background in 1981 > > Demo > Counter Example with GUI > > What Is Smalltalk? > Language > Libraries > Tools, IDE > Methodology > Note: "OO is not Enough!" > > The Language > Terse, expressive, readable > Everything is an Object (really, everything) > All activity is message-passing > Trivial syntax, no reserved words > true, false, nil, self, super, thisContext > Control structures written in Smalltalk > Messages to Booleans, Blocks, etc. > Means they're extensible (!) > aCollection do: [ :item | Transcript show: item printString] > Keyword syntax - messages with > 1 argument alternate keyword/argumentâ¦ > anArray at: 1 (getter) > anArray at: 1 put: 'hello' (setter) > r := Rectangle top: 1 left: 1 width: 10 height: 10 > Fully Reflective > (isKindOf:, understands:, â¦) > Compiles to a virtual machine language (normally) > > The Libraries > Everything is an Object > Polymorphism (heavily used) > E.g., many implementations of at:put: or + > OO Design Patterns > Composite, Adaptor, Singleton, MVC, Visitor, â¦ > Magnitudes, Collections and Streams > Graphics and Windows > All classes are extensible (!) > Example: aString asPath: sepChar > Try this in C++ or ObjC... > > The Methodology > OO A/D Methods (OBA) > OO Design Patterns > Domain-specific Languages > > The Tools > Window-based GUI and Tools > Multi-desktop (Projects) > Browsers, Inspectors and Editors > Rules of Reuse (Programmer as Reader project) > Pluggable look-and-feel > Code-sharing tools: change-lists, Envy > Open-source Tools (!!) > > Tool Demo > Browsers > Code in DB package, class, category, method > Compile 1 method at a time > "Programmer as Reader" facilities > Senders, implementors, class/variable references > Flavors of browsers: protocol, hierarchy, namespace, etc. > Debugger > Just like the browser(!!!) > Fix and continue > CASE Tools > Change lists, packages, projects > > The Environment > VI/VM Architecture > VI like APL workspaces, LISP core files > Snapshot/restart (relation to BOSS files) > VM - "cheat but don't get caught" > Thinks it's an operating system > "The OS is only there for all the things you forgot to put in the language" > Scheduler, file system, network drivers, etc. in Smalltalk > Light-weight processes and scheduler in Smalltalk > Simple VM: Byte-code interpreter > High-performance VM: JIT Optimizing > Native code caches > Polymorphic inline caches > > Other Novel Aspects > Other languages in Smalltalk (Lisp, Prolog, etc.) > Compiler frameworks > Smalltalk-as-OS (running on naked hardware) > OOP and AI > Frames/objects, rules, logic, etc. > Early "block diagram compilers" > > Smalltalk and Multimedia > Early Computer Graphics > BitBLT pixel graphics > SPIM and graphics contexts > Music with Smalltalk > Real-time FM on the Alto > Real-time scheduling for MIDI > Music notations in Smalltalk > > Early (1980s) Applications > ThingLab > ThinkerToy > Graphical programming > Analyst > AI, Multimedia, Graphical Programming > Chinese Temple Design ToolKit > Models of process > MOBY, DoubleTalk > Petri Nets > ObjectWorks/C++ > ST-like IDE for C++ > > Early (1980s) Music Applications > HyperScore ToolKit/MODE > Music composition and notations > SoundKit > Music signal processing > Kyma > Cross-compilation for a DSP > Harmonic Analysis Tool > Chord/Harmony analysis expert system > Smoke > Flexible music representation language > > The Risks > Breaking the system (really easy) > Also easy to recover > VI Bloat > Strippers, Whittlers > Incompatible changes > Tools for merging packages > > A Brief History > Flex and Smalltalk-72 > Simula, Sketchpad, Augment and other precursors > PARC Learning Research Group > Smalltalk-76 and the Xerox Alto > Mostly ASCII > Personal Dynamic Media Paper in "Computer" 3/1977 > Smalltalk-78 > Browser, NoteTaker project > Smalltalk-80 V1 > 3rd complete rewrite before they had an installed user base > LRG now Systems Concepts Lab > 1981 Byte Magazine Special Issue > Context: Xerox Alto, MIT LISP Machines > Smalltalk-80 V2 > Incorporated feedback from first-round users > MVC used for all GUIs > Late-80s changes > Exceptions and I/O > Host window system interface > DLLCC > Compiler Framework > Namespaces, Packages > ANSI Smalltalk (1993-98) > > Smalltalk Leaves PARC > Getting Smalltalk to Users > (Porting to non-Xerox hardware) > Early licensees: Apple, H-P, Tektronix > Tex 44404 demo - http://www.youtube.com/watch?v=8yxCJfayW-8 > Berkeley SOAR and SPARC design > XSIS and the Analyst > ParcPlace Systems (spun off in 1988) > Digitalk's Smalltalk/V on early PCs (1984) > These merge in 1995 > GNU Smalltalk (free) > > C++, ObjectiveC and Java > C with Classes - hybrid language; class is like a struct > ObjectiveC - C + Smalltalk in 1 program > Java ("what a shame they didn't copy everything.") > > Why it failed (in the 1990s) > Price (relative to what?) > Perception of compute demands (requires graphics and mouse, lots of RAM, â¦) > Performance Issues > VM performance and optimization > GC overhead and generation scavenging > Performance much better on Xerox machines > VM in microcode > Tagged architecture > Not upward compatible with anything > "Everything you know is wrong" > C hybrids appeared to get you most of the way thereâ¦ > > Smalltalk Implementations > Cincom Smalltalk (commercial) > ObjectStudio (commercial) > Squeak (free, based on Apple V1) > Pharo (stripped Squeak) > > Coral (for scripting) > Amber (runs on JavaScript VM) > Bistro (runs on JavaScript VM) > S# (runs with .NET) > > Smalltalk/X > VisualAge > Dolphin > > Smalltalk Today > DLLCC and Slang > Seaside (for web apps) > Gemstone (scalable OODB) > > STIC/ESUG > Smalltalk.org > Squeak community > > Relatives/Derivatives > ObjectiveC > Self (no classes, VM advances) > Lively (JavaScript libraries and tools) > F-Script > Strongtalk > SuperCollider > > Reasons Why I Still Use Smalltalk > 3 top reasons: Productivity, productivity and productivity > Language features > Simplicity, scalability, stability > Keyword syntax (!!) > Library features > Comprehensive, consistent, stable, extensible (!!) > All source close at hand > Pluggable L&F > Development Environment > Open tools (!!!) > Integrated, cross-platform > Fix/restart in debugger (!!!) > VI/VM architecture > Code lives in DB, easy change management, publication, crash recovery, etc. (!) > > Why I complain about other languages > "Object-Oriented is not Enough" (Goldberg & Pope 1989 article) > âThe Computer Revolution Hasnât Happened Yetâ (A Kay quote) > Issues center on libraries and tools rather than the languages themselves > Lively for JavaScript > ?? for Python > > What I do use (other than Smalltalk) > C++ > Standard, fast > XCode > Python > Hybrid language > Good libraries (inconsistent, non-OO) > Poor tools > Good integration with C/C++ via ctypes > Curse of version 3 > Octave/MATLAB > Terse, good matrix support > Extensive code base > > -- > > Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com > >

1 0