March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Random refactoring on UITheme or what?

by Ben Coman

Hilaire Fernandes wrote: > I will propose a simple hierarchy for the theme: > > UITheme > +-UIPharoTheme > +-UIVistaryTheme > +-UIWateryTheme > > I will propose to delete all the other themes as they should belong to > other package. > > Hilaire > Just curious to learn... I saw mentioned somewhere that it was bad to subclass themes. What is inherently wrong with that? For example Pharo3Theme was inheriting from UIWateryTheme ? If I wanted my own theme, the same as UIThemeWatery but a different baseColor, should I do... UITheme subclass: MyTheme and copy all methods from UIThemeWatery then modify MyTheme class >> baseColor or do... UIThemeWatery subclass: MyTheme and add MyTheme class >> baseColor cheers -ben

March 26, 2014

Re: [Pharo-dev] Font problem is still there

by Alexandre Bergel

> I didn't tried to debug it, i can't bet it would be easy (need to build a debug version of cairo first) > but it worth trying. > Meanwhile i will put workaround back. Thanks Igor. Let us know! Alexandre > > > Hi! > > > >> there's some kind of caching interference either in cairo or between cairo and freetype, > >> when using identity transformation matrix and integral (integer) font sizes. > >> and there is a simple workaround: > >> > >> canvas pathTransform restoreAfter: [ > >> canvas pathTransform scaleBy: 1.00001. > >> "draw text here" > >> > >> ] > >> > >> this workaround was in font-rendering code, but then i removed it, because i thought problem was solved. > > > > Can we add this back please? > > This font problem is quite serious. It makes people laugh at Pharo... > > > > > -- > Best regards, > Igor Stasenko. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 26, 2014

Re: [Pharo-dev] When change on class with trait freeze

by Ben Coman

Hilaire Fernandes wrote: > https://pharo.fogbugz.com/f/cases/13133/When-change-on-class-with-trait-fre… > > I've somewhat isolated the problem, as reported on the case. Its related to... TEasilyThemed methods size "--> 164" and the sources being updated individually for each method. That is as far as I can take it on my own. cheers -ben

March 26, 2014

Re: [Pharo-dev] Nicer scrollbars [was RE: Fixing inconsistent buttons look in PharoUI]

by Esteban A. Maringolo

2014-03-26 10:55 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > On Wed, Mar 26, 2014 at 2:38 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> wrote: > >> 2014-03-26 10:27 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>:> >> Windows Explorer has others (which have cool arrows) and these (<-) (->) (^) >> > > things that we should put into nautilus in addition to the history >> dropdown. >> >> What are the (<-) (->) (^) you mention? :) >> >> >> > These: > > [image: Inline image 1] > > Doable for the methods history. And maybe the workspace previous contents > since we now have little toolbars in Spec. > > > That'd be nice. I miss the navigation history from Dolphin Browsers: http://www.object-arts.com/downloads/docs/system_browser.htm http://www.object-arts.com/downloads/docs/class_browser.htm Regards!

March 26, 2014

Re: [Pharo-dev] threading in Pharo

by Igor Stasenko

On 26 March 2014 15:04, Ben Coman <btc(a)openinworld.com> wrote: > Eliot Miranda wrote: > > > > > On Tue, Mar 25, 2014 at 10:21 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > >> Hi Igor, >> >> >> you have a point but I disagree. The scheduler is defined in the >> implementation section of the blue book. It could be more explicit, but >> the blue book scheduler is a known and simple system. In my threading work >> I've made sure to preserve its semantics (cooperative within priorities, >> preemptive across priorities, thread switch at activation of non-primitive >> sends and backward branches). The only serious bug I know of (that >> preempting sends a process to the back of its run-queue) was addressed in >> Cog and the VW VM. We can and should write up the semantics, but they're >> not undefined, they're simple and they do work. >> > > Oops. I lie. There is a serious bug with Semaphore>>critical: and the > like. There's a suspension point after signal and before block evaluation > that can result in deadlock if a higher priority process signals the > semaphore. Since the higher priority process is running the lower priority > process never makes progress to run the ensure block or cvlear the flag or > whatever it needs to do, and hence the system deadlocks. This requires > thought ;-) So I do know of one outstanding bug. > > My grasp of concurrency controls hasn't been tested in 20 years, so > naively I would say: If a lower priority process "L" holds** a semaphore > when the higher priority process "H" signals the semaphore, temporarily > raise the priority of the "L", or temporarily lower the priority of "H". > Is there something simple that I missing? > > It really depends what you put into "priority" thing. In preemptive scheduling policy it means: threads with higher priority always preempt ones with lower one. That means that any low-priority task has no chances to advance, if there even single higher priority task that never stops. In shared-time scheduling that means: threads with higher priority has higher % of computing resources allocated (the exact amount/ratio can depend on policy). But shared-time scheduling good in another aspect: all tasks has chance to advance, if observed over some finite time frame, regardless of their priority. The semaphores and other synchronizing primitives is not really related to scheduling. They are orthogonal, as they just giving a control over yielding execution of task (basically halting it) until some condition met. > cheers -ben > > -- Best regards, Igor Stasenko.

March 26, 2014

Re: [Pharo-dev] threading in Pharo

by Ben Coman

March 26, 2014

Re: [Pharo-dev] Access to voyage repository

by Norbert Hartl

Am 26.03.2014 um 14:53 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > done > thanks, Norbert > On 26 Mar 2014, at 10:48, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Can anybody add me to voyage repo on smalltalkhub? >> >> thanks, >> >> Norbert >> > >

March 26, 2014

Re: [Pharo-dev] Nicer scrollbars [was RE: Fixing inconsistent buttons look in PharoUI]

by phil＠highoctane.be

On Wed, Mar 26, 2014 at 2:38 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > 2014-03-26 10:27 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > On Wed, Mar 26, 2014 at 2:09 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> > > >> Like in Chrome... and almost everywhere else. The scrolling metaphor > >> is so ingrained that in some cases even the bar isn't displayed until > >> the scroll intent is initiated. > > > FWIW, Office 2013 has nice scrollbars with arrows. Along with supersmooth > > animations. > > Microsoft is very conservative in that regard. They aim at the broader > range of END USERS, from the noviceto the computer literate one. > > I payed particular attention to this "scrollbar" UX in the past, and > my personal research (watching people) shows that most of them use the > mousewheel or simply drag the bar in mouse based UIs, and/or swipe > up/down in touch based. > > I love supersmooth animations, but they're part of a whole transitions > engine. > Yes, true. But I am not doing any .NET and WPF anytime soon. Nor MFC. > > > Windows Explorer has others (which have cool arrows) and these (<-) (->) > (^) > > things that we should put into nautilus in addition to the history > dropdown. > > What are the (<-) (->) (^) you mention? :) > > > These: [image: Inline image 1] Doable for the methods history. And maybe the workspace previous contents since we now have little toolbars in Spec. Phil > Regards! > >

March 26, 2014

Fwd: CFP - IWST 2014

by jannik laval

[Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST14 -- International Workshop on Smalltalk Technologies Cambridge, England; August 19, 2014 http://www.esug.org/Conferences/2014/IWST14 ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- Submission deadline: June 15, 2014 Notification deadline: July 15, 2014 Workshop : August 19, 2014 All accepted papers will be published in ACM DL (To be confirmed) ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: Aspect-oriented programming, Design patterns, Experience reports, Frameworks, Implementation, new dialects or languages implemented in Smalltalk, Interaction with other languages, Meta-programming and Meta-modeling, Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank Lam Research Corporation for its financial contribution that makes it possible a price for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://www.easychair.org/conferences/?conf=iwst2014 ------------------- Program chairs ------------------- Alain Plantec (UMR 6265 Lab-STICC, University of Brest, France) Jannik Laval (Ecole des Mines de Douai, France) -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/ -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

March 26, 2014

Re: [Pharo-dev] Access to voyage repository

by Esteban Lorenzano

done On 26 Mar 2014, at 10:48, Norbert Hartl <norbert(a)hartl.name> wrote: > Can anybody add me to voyage repo on smalltalkhub? > > thanks, > > Norbert >

March 26, 2014