September 2010 - Pharo-users

Re: [Pharo-users] Support for SCIM on Linux

by StÃ©phane Ducasse

On Sep 26, 2010, at 10:58 AM, DavidWilson wrote: > > Hi Mario > > Thanks for the answers, I'm sorry to take so long to answer, I'm only online > very occasionally at the moment. > > 1. there is no problem displaying the unicode characters, once the > appropriate fonts are loaded (I simple use the update font option from the > preferences and set the appropriate font in the text morphs). I haven't > checked with a 1.0 image, but I don't remember any problem displaying these > characters in 1.0, I didn't try entering them! > > 2. the problem is inputting using SCIM. Alternative keyboards e.g. > Bhutan/Dzongkha) work ok, but the input methods supported by SCIM are how > most of the world enters Tibetan characters. > > 3. How do I open a ticket? Where? http://code.google.com/p/pharo/issues/entry > > Greetings from Kalymnos > > David > > > -- > View this message in context: http://forum.world.st/Support-for-SCIM-on-Linux-tp2544095p2714179.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

Sept. 26, 2010

Re: [Pharo-users] Support for SCIM on Linux

by DavidWilson

Hi Mario Thanks for the answers, I'm sorry to take so long to answer, I'm only online very occasionally at the moment. 1. there is no problem displaying the unicode characters, once the appropriate fonts are loaded (I simple use the update font option from the preferences and set the appropriate font in the text morphs). I haven't checked with a 1.0 image, but I don't remember any problem displaying these characters in 1.0, I didn't try entering them! 2. the problem is inputting using SCIM. Alternative keyboards e.g. Bhutan/Dzongkha) work ok, but the input methods supported by SCIM are how most of the world enters Tibetan characters. 3. How do I open a ticket? Where? Greetings from Kalymnos David -- View this message in context: http://forum.world.st/Support-for-SCIM-on-Linux-tp2544095p2714179.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 26, 2010

Re: [Pharo-users] [Pharo-project] [ANN] Pharo 1.1.1 OneClickCogVm

by Mariano Martinez Peck

On Sat, Sep 25, 2010 at 7:09 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Mariano, > > This is a good and needed step. > > Now, just a problem: 1.1.1dev image does not work with the regular VM. This > is probably because you saved it again after you opened it with the Cog VM. > It would be great if the released dev image would work with both. > Excellent suggestion :) Thanks doru. > > Cheers, > Doru > > > > On 25 Sep 2010, at 17:56, Mariano Martinez Peck wrote: > > > Hi. This is not an official release. I didn't do all the formal procedure > for releasing a Pharo image. My idea is try to push CogVM and try to get as > much as testers as possible. Try to report issues and help Eliot. For that > purpose, I think having a one click image is worth it. > > > > So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has some > fixes over 1.1 and the CogVM necessary changes). I build the image with > exactly the same versions of the external packages than Pharo 1.1. > > > > If you want to download that this Pharo1.1.1 dev image that works with > Cog here is the link: > > > > > https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip > > > > In addition, and thanks to Lukas, we could generate OneClicks with CogVM. > Here you can have a OneClick using the above image: > > > > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > > > Notice that this is not an official release and that there are > failing/errors tests. I've already sent emails for them and hopefully > someone may fix them. The only thing is not supported is the TestCoverage > (since it uses objects as methods, with is not yet supported in CogVM). > > > > Cheers > > > > Mariano > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 25, 2010

Re: [Pharo-users] [ANN] Pharo 1.1.1 OneClickCogVm

by Tudor Girba

Hi Mariano, This is a good and needed step. Now, just a problem: 1.1.1dev image does not work with the regular VM. This is probably because you saved it again after you opened it with the Cog VM. It would be great if the released dev image would work with both. Cheers, Doru On 25 Sep 2010, at 17:56, Mariano Martinez Peck wrote: > Hi. This is not an official release. I didn't do all the formal procedure for releasing a Pharo image. My idea is try to push CogVM and try to get as much as testers as possible. Try to report issues and help Eliot. For that purpose, I think having a one click image is worth it. > > So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has some fixes over 1.1 and the CogVM necessary changes). I build the image with exactly the same versions of the external packages than Pharo 1.1. > > If you want to download that this Pharo1.1.1 dev image that works with Cog here is the link: > > https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip > > In addition, and thanks to Lukas, we could generate OneClicks with CogVM. Here you can have a OneClick using the above image: > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > Notice that this is not an official release and that there are failing/errors tests. I've already sent emails for them and hopefully someone may fix them. The only thing is not supported is the TestCoverage (since it uses objects as methods, with is not yet supported in CogVM). > > Cheers > > Mariano > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

Sept. 25, 2010

[ANN] Pharo 1.1.1 OneClickCogVm

by Mariano Martinez Peck

Hi. This is not an official release. I didn't do all the formal procedure for releasing a Pharo image. My idea is try to push CogVM and try to get as much as testers as possible. Try to report issues and help Eliot. For that purpose, I think having a one click image is worth it. So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has some fixes over 1.1 and the CogVM necessary changes). I build the image with exactly the same versions of the external packages than Pharo 1.1. If you want to download that this Pharo1.1.1 dev image that works with Cog here is the link: https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip In addition, and thanks to Lukas, we could generate OneClicks with CogVM. Here you can have a OneClick using the above image: https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip Notice that this is not an official release and that there are failing/errors tests. I've already sent emails for them and hopefully someone may fix them. The only thing is not supported is the TestCoverage (since it uses objects as methods, with is not yet supported in CogVM). Cheers Mariano

Sept. 25, 2010

Re: [Pharo-users] Hello and Mac OS X question

by Sean P. DeNigris

Marc Hanisch wrote: > > although I'm a > die-hard vim-user ;-))... > I am also (vim rocks!!!). There are three things I found out: 1. because Smalltalk methods are ( supposed to be ;-) ) very short i.e. 10 lines or less, vi bindings are still incredible time/attention savers, but the gap isn't nearly as wide as with a traditional text file. 2. there is the SVI project, which I ported to the current version of Squeak, and could probably be ported to Pharo pretty easily, which gives you vi bindings for the tools. 3. Smalltalk systems are totally customizable, so if you decide to make Pharo your home, you could come up with vim-esque bindings appropriate for a Smalltalk image that cause a productivity leap similar to what vim does in text files. HTH, Sean -- View this message in context: http://forum.world.st/Hello-and-Mac-OS-X-question-tp2542106p2572954.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 24, 2010

Fwd: [Esug-list] Position Vacancy: New Mexico Highlands University

by Mariano Martinez Peck

---------- Forwarded message ---------- From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Date: Fri, Sep 24, 2010 at 5:18 PM Subject: [Esug-list] Position Vacancy: New Mexico Highlands University To: ESUG Mailing list <esug-list(a)lists.esug.org> Position Vacancy (Subject to funding and program approval) New Mexico Highlands University plans to offer both an undergraduate (BS) and graduate (MS) degree in Software-driven Systems Design. The undergraduate program is in place and State of New Mexico approval of the graduate program is in its final stages. Final approval during the legislative session in February 2011 is hoped for but is not guaranteed. If approval is forthcoming the position will be open as early as summer term (May 2011) and definitely by fall term (August 2011). If approval is not obtained (the legislature will be concentrating on economic issues this session), the dates will slip to May or August 2012. The position: Visiting Professor, School of Business Administration. Contract is renewable annually for up to five years. Compensation: $50,000 - $60,000, depending on qualifications, plus standard fringe benefits (health, retirement, dental). Additional compensation, from project work, is possible. Expected Start Date: May 20th, 2011 or August 15th, 2011. Qualifications: â¢ Masters degree in Computer Science (software engineering specialization), MIS, Informatics or similar degree focused on software development and systems design. â¢ Extensive knowledge of Squeak (ideally Pharo), its extensions (e.g. Seaside), and libraries (CMS, version control, morphic, etc.) plus several years experience using Squeak to develop commercial or research applications. â¢ Demonstrated multi-disciplinary / cross-disciplinary commitment; e.g. multiple degrees, publications or teaching experience across disciplinary boundaries, multi-disciplinary honors teaching. â¢ Demonstrated ability to use a hybrid approach to instruction and mentoring, combining the use of on-line and in-class resources and techniques. â¢ The position does not required full-time residency in New Mexico, but will require at least 26 weeks of residency (in two to four week blocks), annually. Full-time residency is highly desirable, but not an absolute essential. Expectations: This position is unlike any other academic position, because of the unique nature of the program it supports. Faculty are expected to spend up to forty hours a week, while in residence, in the Studio working with students at all levels, and delivering academic content âon-demandâ and in a highly modular and accelerated fashion. Faculty are expected to define (and seek grant funding for) research projects and involve students in both the conduct of the research and co-authoring of publications arising from the research. Faculty may take on project management responsibilities (receiving appropriate additional compensation) for commercial projects underway in the Studio. The program emphasizes the ability to think and to employ multiple perspectives (systems, object, design, agile, and computational thinking) and faculty are expected to help students develop this kind of thinking capability â far more challenging than simply preparing them to pass a final exam. Program: This program is unique: in focus, in structure, and in terms of the demands placed on faculty. The stated goal of the program is to graduate students as full-participating members of a professional community dedicated to and capable of using computing and software technology to analyze and solve the âwickedâ problems confronting business enterprises, communities, and global societies. Graduates will be âmodern polymathsâ masters not of all extant knowledge but who have learned and integrated knowledge from multiple disciplines and domains. The program is experience-based. All students will spend significant amounts of time (up to thirty-two hours a week) in a Studio â simultaneously working on real-world projects for paying customers and learning new subject matter. Students will work side-by-side- with professionals (acting as project managers and guarantors of successful delivery) who will provide tacit knowledge and mentoring. [Faculty members are eligible, and encouraged, to assume this kind of professional role â for additional compensation.] The University works with one or more private sector entities, the latter responsible for contracting and managing projects, generating sufficient revenues to pay for professionals, student apprenticeship wages, and program expenses (e.g. travel to conferences). The program is competency-based (approximately 100 currently defined) and not course-based. All competencies are defined at seven different levels (from âunderstands concepts as evidenced by objective testâ to âmakes an original contribution to the communityâ) and student progress (and graduation) is based on number of competencies demonstrated at level. Curricular subject matter is presented in highly modular form (think in term of one-credit, 16 face-time hours) and utilizes a combination of on-line and self-paced study, broadcast (e.g. webinar format), and in-class workshops. Students define iterative and incremental âindividual education plansâ every eight weeks and those plans, collectively, defined the curricular material to be delivered. Knowledge integration and motivation for learning is provided by the project and studio context in which all instruction is delivered. The Studio is a âone-room classroomâ â all students, faculty, and professionals occupy the same room at the same time (much like the ideal Agile work room or the botegga where Leonardo was an apprentice and later a Master). Multiple projects are underway, with different groups working on different projects. The rhythm of the Studio is defined with iterative cycles, each beginning with a planning session and ending with a retrospective. Within the cycles are defined, repetitive, periods for special activities like reader and writer workshops, social activities, and learning âspikes.â We would like to provide the students with a comprehensive development tool and environment â Smalltalk/Squeak â as a foundation for all of their technical software development learning and activities. The use of a uniform environment will make it easier to focus on the thinking behind the technology and the analysis of problems and design of solutions. When marketplace and technical demands indicate, students will learn prevailing technologies (ranging from HTML to Java â to relational database) and new technologies (e.g. non-relational and document databases) as alternatives to the Smalltalk base. Students will leave with the same level of expertise and understanding of current mainstream tools and technologies as graduates of any other CS / MIS program; but they will also have the underlying foundation made possible with the common tool and environment. If this kind of radically different program and alternative academic appointment is of interest, please contact: (Vita is OK, but would prefer a simple letter explaining why this is of interest to you and a description of your qualifications.) Dr. David West dmwest(a)nmhu.edu profwest(a)fastmail.fm 1-505-231-7233 School of Business Administration, New Mexico Highlands University Las Vegas, New Mexico, 87701 _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

Sept. 24, 2010

Fwd: Smalltalks 2010 --- Registration and invitation

by Mariano Martinez Peck

---------- Forwarded message ---------- From: Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> Date: 2010/9/24 Subject: Smalltalks 2010 --- Registration and invitation To: "pbe-spanish-group(a)googlegroups.com" <pbe-spanish-group(a)googlegroups.com > ======== INGLES The FundaciÃ³n Argentina de Smalltalk (FAST) invites you to the 4th Smalltalk Conference of Argentina, to be held on November 11, 12 and 13, 2010 at the ConcepciÃ³n del Uruguay site of the Universidad TecnolÃ³gica Nacional. Everyone, including teachers, students, researchers, developers and entrepreneurs, are welcome as speakers or attendees. Registration is free and now open athttp://www.fast.org.ar. The goal of the conference is to strengthen the Argentine and international Smalltalk community through the exchange of works, experiences and anecdotes connected with this technology or related matters. Renowned members of the international Smalltalk community will visit the conference. Moreover, this edition of the conference will have a Research Session with publications reviewed by an international committee, as well as an Industry Track for those preferring a more relaxed environment. We look forward to see your submissions. You can propose papers or talks know through our website, or by sending an email toinfo(a)fast.org.ar. See you there! ======== SPANISH La FundaciÃ³n Argentina de Smalltalk (FAST) los invita a la 4ta Conferencia de Smalltalk de Argentina, a realizarse desde el 11 al 13 de Noviembre del 2010 en la sede de ConcepciÃ³n del Uruguay de la Universidad TecnolÃ³gica Nacional. Esperamos verlos a todos entre la audiencia o como oradores, ya sean profesores, estudiantes, investigadores, desarrolladores o empresarios. La registraciÃ³n es gratis y estÃ¡ disponible enhttp://www.fast.org.ar. El objetivo de la conferencia es afianzar los vÃnculos entre las comunidades Smalltalk de Argentina y del mundo, a travÃ©s del intercambio de trabajos, experiencias y vivencias conectadas con esta tecnologÃa. De hecho, este aÃ±o nos visitarÃ¡n personalidades de renombre de la comunidad internacional. AdemÃ¡s, en esta ediciÃ³n de la conferencia tendremos un track de investigaciÃ³n formal con publicaciones y referato de un comitÃ© internacional. TambiÃ©n tendremos un track de industria para aquellos que prefieran un ambiente mÃ¡s informal. Pueden enviarnos sus propuestas de charlas o papers mediante nuestra pÃ¡gina web, o enviÃ¡ndonos un mail ainfo(a)fast.org.ar. Nos vemos en la conferencia!

Sept. 24, 2010

Re: [Pharo-users] ifTrue not acting as a polymorphic message?

by Marcus Denker

On Sep 24, 2010, at 10:17 AM, Marcus Denker wrote: > > > So the solution takes was to make some selectors special. ifTrue: is *always* compiled to a jump bytecode. > This in turn means that it can not be used for any other purpose. If you implement it in your own class, it will never > be called. (I alwasy wanted to look into the question if the vm could not just re-send ifTrue: instead of giving the > useless error message...) Which of course would be tricky as there is no block for the parameter... it has been optimized away. The solution to all these things is of course late-binding optimization to the point when all information is available. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 24, 2010

Re: [Pharo-users] ifTrue not acting as a polymorphic message?

by Marcus Denker

Hello, > > While I was thinking on an exercise to give to the students I though about developing a three-valued logic, creating the TTrue, TFalse, and TUnknown, whos instances understood some methods such as #ifTrue: #ifFalse: and so on. > > My surprise came when I discovered that the ifTrue: method only work for the True and False instances of Smalltalk, being unable to define a method named ifTrue: > > For what I saw the problem is that, on non boolean receivers, the method is not even evaluated to see if the receiver can understand it, but it automatically triggers the message #mustBeBoolean > > So my question is, why does it do this? Is there a way to use ifTrue: really as a method? > Is there a way that I can make ifTrue: to work with any Class and not just Booleans? > The reason is that ifTrue: is compiled by the smalltalk-to-bytecode compiler to a test-and-jump bytecode. So ^1 + 2 ifTrue: ['true'] is compiled to: 17 <76> pushConstant: 1 18 <77> pushConstant: 2 19 <B0> send: + 20 <99> jumpFalse: 23 21 <20> pushConstant: 'true' 22 <90> jumpTo: 24 23 <73> pushConstant: nil 24 <7C> returnTop In smalltalk, we do not know at compile time the type of any expression. So we can not build a compiler that does the jump for the case that the expression is a boolean and send the message else. We know the class of the result of an expression only at runtime, not at compile time. So the solution takes was to make some selectors special. ifTrue: is *always* compiled to a jump bytecode. This in turn means that it can not be used for any other purpose. If you implement it in your own class, it will never be called. (I alwasy wanted to look into the question if the vm could not just re-send ifTrue: instead of giving the useless error message...) One possible way around this (for experiments) is to change the compiler to always send ifTrue: and never do the jump bytecode. The image gets slow, though (but it can be done). Another, more practical solution is to just do the change for the classes you are experimenting with and use a hacked second compiler for those (we did this with the NewCompiler in the past when experimenting with different things). Or you could change the inlining logic of the compiler to not inline ifTrue just for your package, or depending on a pragma in the method. In Opal (the new compiler, sadly not yet a drop-in replacement, but soon), the place to do that is quickly found. There is a visitor that translates AST to bytecode. It has a method acceptMessageNode: aMessageNode aMessageNode isInlineIf ifTrue: [^ self emitIfNode: aMessageNode]. aMessageNode isInlineIfNil ifTrue: [^ self emitIfNilNode: aMessageNode]. aMessageNode isInlineAndOr ifTrue: [^ self emitAndOrNode: aMessageNode]. aMessageNode isInlineWhile ifTrue: [^ self emitWhileNode: aMessageNode]. aMessageNode isInlineToDo ifTrue: [^ self emitToDoNode: aMessageNode]. aMessageNode isInlineCase ifTrue: [^ self emitCaseNode: aMessageNode]. ^ self emitMessageNode: aMessageNode Easy. The old smalltalk compiler, I always get headaches looking at it. I guess #transformIfNil: would be the starting point to look at. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 24, 2010