- Pharo-dev - lists.pharo.org

[Pharo-project] How to write a help in a geeky way :)
by Igor Stasenko Dec. 5, 2012

Dec. 5, 2012

MyHelp class>>topicAboutWritingHelpTopicInGeekyWay ^ self topicTitle: 'How to write help in geeky way' contents: 'There''s nothing special, since help system expects string to be returned, which is then converted to text and shown to user.. And who said that this method should contain the same text which you displaying? Sometimes, when you have some list of rules, which sits in a single class (like list of default options with short description for each of them, you can, of course copy and paste the list, format it more appropriate for reader and voila.. you got your page.. But downside of copying is that you will have to maintain two copies of same thing and have to sync them for the rest of your life. So, here a geeky way to avoid duplication effort: ' , self extractCommentsFromCode: ( MyClass >> #myMethodWhereIPutOptions ) , ' and of course, i can continue here putting some more text, if needed.. but i think i made it clear already how you can make your help system to stay more up to date when you updating the code ;)' ------ This is Spar... err smalltalk! :) -- Best regards, Igor Stasenko.

2 1

[Pharo-project] snapshot methods
by Camillo Bruni Dec. 5, 2012

Dec. 5, 2012

I am always confused about the snapshot behavior. Yes, it returns true when we are in the new image, but this is far from obvious :/. How about a more explicit method for snapshotting and continue with different code in the new / old image: self stuffInCurrentImage. Smalltalk snapshotIfNew: [ self stuffInNewImage ] IfCurrent: [ self stuffInCurrentImage ] self stuffInCurrentAndNewImage.

2 2

[Pharo-project] [[ false ] whileFalse: [ ]] in workspace
by Guillermo Polito Dec. 4, 2012

Dec. 4, 2012

Hi! I was surprised by trying to evaluate the following expression in a workspace: [[ false ] whileFalse: [ ]] and getting an error SubscriptOutOfBounds: 1... The strange thing is that compiling that expression inside a block works, but not in the workspace... Any idea? Guille

7 16

[Pharo-project] Gforge downtime 11 Dec
by Marcus Denker Dec. 4, 2012

Dec. 4, 2012

Due to sheduled maintenance on network appliances, the INRIA Forge will be unavailable from 2 pm to 4 pm on Tuesday, December 11th 2012. Marcus

1 0

[Pharo-project] [update 2.0] #20427
by Marcus Denker Dec. 4, 2012

Dec. 4, 2012

20427 ----- Issue 7093: DynamicVariable>>#value:during: should return the value of evaluating its second block argument http://code.google.com/p/pharo/issues/detail?id=7093 Issue 7092: MultiByteFileStream>>#readInto:startingAt:count: currently bypasses decoding http://code.google.com/p/pharo/issues/detail?id=7092 Diff information: http://ss3.gemstone.com/ss/Pharo20/Multilingual-Tests-MarcusDenker.23.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-MarcusDenker.456.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1261.diff http://ss3.gemstone.com/ss/Pharo20/Files-MarcusDenker.ducasse.285.diff

1 0

[Pharo-project] ECOOP'13/ECMFA'13/ECSA'13: Call for workshop proposals
by Damien Cassou Dec. 4, 2012

Dec. 4, 2012

Call for Workshops ================== In 2013, the European Conference on Object-Oriented Programming (ECOOP), European Conference on Modelling Foundations and Applications (ECMFA) and the European Conference on Software Architecture (ECSA) will be collocated in Montpellier, France. The 3 conferences will host an exciting array of workshops that address a variety of topics in object-oriented technology, Model-Driven Engineering and software architecture. A workshop is a forum for exchanging ideas and theories that are still in an evolutionary stage. Typically, a workshop will either address a focused topic in depth or explore connections between one of the three conferences' domains and other areas of interest. ECOOP 2013, ECMFA 2013 and ECSA 2013 thus invite proposals for workshops lasting half a day, one day or two days. The workshops will be held Monday and Tuesday 1-2 July 2013. Proposals ========= A workshop proposal must be submitted as one PDF file. It must include the following information, in this order: * Name of the workshop (first page) * Table of contents for the proposal (with page numbers) * Duration of the workshop (half-day, full day, 2 days) * Abstract: 150-200 words describing the workshop, suitable for the conferences Web site * Keywords and addressed domains. * References to previous editions of the workshop (if any), including name of host conference and number of participants to the workshop each year * Summary of the workshop format: e.g., refereed papers, and/or short papers, and/or invited talks, and/or problem solving, and/or brainstorming sessions. How will papers or other submissions be reviewed? * Description of how the workshop papers and results will be published or otherwise disseminated (see the "Dissemination of Workshop Results" section below) * Preliminary Call For Workshop Papers describing the workshop's focus, its main topics and its deadlines * A (draft) list of the workshop PC members * A list of the workshop organizers * For each organizer of the workshop: - name, - affiliation - contact information - a brief biography (up to 200 words), focusing on the organizer's expertise in the field and (if applicable) experience as a workshop organizer * Primary contact: identify one organizer as the primary contact * Any special requirements that the workshop may have Workshop Schedule Constraints ============================= Each workshop will have to pay attention to the following timing constraints : * the program must be made public before the early registration deadline of the conferences; we thus expect you to make it available around mid-may; * the workshop must be able to consider submissions of papers rejected by the conferences, and have these enter its reviewing process; we thus expect you to make your submission deadline around mid-april; * the workshop must send its Call For Papers at least one month before submission deadline; we thus expect you to send your CFP around mid-march; Proposal Submission and Review ============================== Workshop proposals should be submitted by email to the workshop chairs, at ws-chairs-ec-montpellier-2013(a)inria.fr Proposals will be reviewed by the workshop chairs. Proposals will be selected based on their relevance to the conferences aims, beneficiaries, and timely advances in their respective topics. In particular, proposals will be evaluated according to the following criteria: - The potential to advance the state of research and practice - The organizers' commitment to stimulate discussion at the workshop - The organizersâ commitment to arrange for sensible digital and permanent post-meeting proceedings - The organizers' experience and ability to lead a successful workshop - Timeliness and expected interest in the workshop topics - The balance and synergy between the proposed workshops. - The continuity of previous years workshops *Workshop proposal deadline: January 10th* *Workshop proposal notification: January 16th* Workshop proposals may still be submitted after January 10th, till February 15th, and will be evaluated with the same criteria. But in addition these "late" proposals may only be accepted if their themes do not interfere with those of already accepted workshops. We thus strongly advise you to submit your workshop proposal as soon as possible, and *before* January 10th. Dissemination of Workshop Results ================================= A proposal should clearly state how the results of the workshop, that is the papers and other outcomes, will be made available to participants and others, both before and after the workshop event. ACM DL publications are encouraged. Contact ======= For additional information about this Call for Workshops, please contact the workshop chairs at ws-chairs-ec-montpellier-2013(a)inria.fr. An up-to-date version of this call for workshops may be found at: http://info-web.lirmm.fr/ec-montpellier-2013/index.php/satelliteevents?id=1… Workshop Chairs =============== Olivier Zendra, INRIA Nancy - France Reda Bendraou, UniversitÃ© Pierre et Marie Curie - France Damien Cassou, UniversitÃ© Lille 1 - France StÃ©phane Ducasse, INRIA Lille - France

1 0

[Pharo-project] pharo-2.0-tests Â» win - Build # 496 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Dec. 3, 2012

Dec. 3, 2012

1 1

[Pharo-project] DynamicVariable>>value:during:
by Sebastian Sastre Dec. 3, 2012

Dec. 3, 2012

Hey guys, would not make much much more sense if we return the result of evaluating the block when we use dynamic variables? Here is the patch I'm using these days: DynamicVariable>>value: anObject during: aBlock | p oldValue result | p := Processor activeProcess. oldValue := (p psValueAt: index) ifNil: [self default]. [ p psValueAt: index put: anObject. result := aBlock value. ] ensure: [ p psValueAt: index put: oldValue ]. ^ result

2 2

[Pharo-project] [update 2.0] #20426
by Marcus Denker Dec. 3, 2012

Dec. 3, 2012

20426 ----- Issue 7091: TestRunner needs to register itself in ToolSet http://code.google.com/p/pharo/issues/detail?id=7091 Issue 7019: Move MIMEType from Network to FileSystem http://code.google.com/p/pharo/issues/detail?id=7019 Diff information: http://ss3.gemstone.com/ss/Pharo20/SUnit-UI-MarcusDenker.51.diff http://ss3.gemstone.com/ss/Pharo20/Network-MIME-MarcusDenker.52.diff http://ss3.gemstone.com/ss/Pharo20/FileSystem-Core-MarcusDenker.63.diff

1 0

Re: [Pharo-project] [squeak-dev] New Cog VMs available
by Eliot Miranda Dec. 3, 2012

Dec. 3, 2012

Hi Blake, On Mon, Dec 3, 2012 at 7:10 AM, Blake McBride <blake(a)mcbride.name> wrote: > Greetings, > > I tried to integrate Squeak to a C based application more than six years > ago. The project failed because we were not able to have our application > call Squeak, then have Squeak call the application, and then the > application call Squeak again recursively. An analysis of the Squeak VM > revealed a kernel design consisting of a lot of global variables - quite > unnecessarily. The unnecessary use of global variables over a localized > structure for example unnecessarily prevented the use of Squeak as an > extension language (unless you had no recursion). I spent several days > trying to re-structure the Squeak kernel but I kept running into problems > and just ran out of time. > > As a side note, that company I was with ended up making a lot of > investment in Scheme because we were easily able to integrate that language > with our application. Now, not only is Scheme used heavily within that > company but many of their clients use it too to customize their application. > > This brings me to my question, is COG reentrant? > Yes it is. It supports call-outs and call-ins. But currently there is no support for Cog to be packaged as a DLL. You have to start by calling C from Squeak. > If not, as the author of COG, I would think it relatively easy to > restructure it to be so. Such a design capability can make a huge > difference to COG's acceptance to many. It may even be the reason to > switch to COG. > Yes indeed. The issue is of course funding to spend the time to make the necessary changes. > Just sharing some thoughts. Thanks. > > Blake McBride > > On Sun, Dec 2, 2012 at 7:55 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > >> ...in http://www.mirandabanda.org/files/Cog/VM/VM.r2628. >> >> These fix a bug with pc mapping that could cause the Vm to crash on >> simple loops containing arithmetic on constants (e.g. 1 to: 20 do: [:i| >> 1=1]). They also cause the instantiation primitives to pop all their >> arguments rather than assume their argument count is 0 or 1. More change >> info available in the directory. >> -- >> best, >> Eliot >> >> >> >> >> > > > > -- best, Eliot

1 0