October 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: Sujet stage Pharo
by StÃ©phane Ducasse Oct. 12, 2012

Oct. 12, 2012

Please distribute widely :) From: LE PORS Eric <eric.lepors(a)fr.thalesgroup.com> Subject: Sujet stage Pharo Date: October 11, 2012 10:01:27 AM GMT+02:00 To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Cc: Pierre LABORDE <pierre.laborde(a)fr.thalesgroup.com> A diffuser aux Ã©tudiants motivÃ©s : (Sujet de Stage THALES SYSTEMES AEROPORTES BREST, non diffusÃ© officiellement) Titre : Maquettage Innovant avec Pharo (Logiciel). DurÃ©e : 6 mois, dÃ©but en fÃ©vrier ou mars (stage de fin d'Ã©tude) Description (Contexte technique, objectifs et dÃ©finition prÃ©cise du travail) : Notre entitÃ© dÃ©veloppe rÃ©guliÃ¨rement des maquettes dâinterfaces homme-machine innovantes. Lâinnovation se situe autant au niveau de lâergonomie quâau niveau du design graphique visuel ou des Ã©lÃ©ments dâinteraction. Le maquettage est souvent utilisÃ© en sÃ©ance avec les opÃ©rationnels, dâoÃ¹ lâemploi dâun langage dynamique comme Smalltalk permettant la modification rapide (et en sÃ©ance) du code et des Ã©lÃ©ments dâinteraction. Le maquettage/prototypage des interfaces Homme-Machine est donc actuellement rÃ©alisÃ© sous SMOCK, un framework de maquettage dÃ©veloppÃ© en Smalltalk Visualworks (Commercial). De nombreux Smalltalk existent sur le marchÃ©, cependant une communautÃ© parmi les autres semble de plus en plus active et moderne, Ã la fois en terme de langage et dâaspects interfaces homme machine : la communautÃ© Smalltalk Pharo (OpenSource). Nous souhaitons expÃ©rimenter les apports de Pharo en terme dâinterfaces homme-machine innovantes. Pour ce faire nous proposons au candidat dâeffectuer un portage de notre framework de maquettage composÃ© de SCM (modÃ¨le en composant) et de CADE (Framework orientÃ© dessin et animations). Un exemple dâihm utilisant les Ã©lÃ©ments portÃ©s validera le travail effectuÃ©. CONNAISSANCES SOUHAITEES : Le stagiaire devra avoir une connaissance du Smalltalk ou Ãªtre motivÃ© par lâapprentissage de celui-ci. Il devra ensuite Ãªtre motivÃ© par la conception dâinterface homme machine de nouvelles gÃ©nÃ©rations et novatrices.

1 0

[Pharo-project] [ANN] Phobos
by Pavel Krivanek Oct. 11, 2012

Oct. 11, 2012

Hi all, I would like to introduce you Phobos - the XULRunner based Smalltalk framework for development of native GUI with standard look&feel for Linux, Mac OS X and Windows. It is based on Zinc, WebSockets and Seaside continuations. For more information including more screenshots see the project page: http://code.google.com/p/phobos-framework/ You should pay attentions to FAQ too: http://code.google.com/p/phobos-framework/wiki/FAQ Phobos has Seaside-like components and rendering style, can combine XUL with HTML or SVG, supports printing etc. Cheers, -- Pavel

10 29

[Pharo-project] Phobos and OmniBrowser
by Pavel Krivanek Oct. 11, 2012

Oct. 11, 2012

Hi, for Phobos [1] I created a very basic support for CodeMirror (HTML code editor) and OmniBrowser (on Pharo 1.4) so I can share some cool screenshot with you again ;-) [1] http://code.google.com/p/phobos-framework/ Cheers, -- Pavel

6 6

[Pharo-project] pharo-2.0-tests Â» linux - Build # 398 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Oct. 10, 2012

Oct. 10, 2012

1 0

[Pharo-project] [update 2.0] #20333
by Marcus Denker Oct. 10, 2012

Oct. 10, 2012

20333 ----- Issue 6784: Finder Cleanup http://code.google.com/p/pharo/issues/detail?id=6784 Issue 6783: TextEditorDialog + Theme improvements http://code.google.com/p/pharo/issues/detail?id=6783 Issue 6782: Gofer Metacello Extension: initialization and load fixes http://code.google.com/p/pharo/issues/detail?id=6782 -- Marcus Denker -- http://marcusdenker.de

1 0

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

Oct. 10, 2012

1 1

Re: [Pharo-project] Global session object?
by Fernando Olivero Oct. 9, 2012

Oct. 9, 2012

Yes, session management is cross-cutting concern, so it makes sense to have it in the system, and not just as a NB feature. Object new, is a cool workaround for the unique ID! Fernando On Mon, Oct 8, 2012 at 8:33 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > Yes, this sounds good. > > Marcus > > On Oct 8, 2012, at 5:11 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> I wanna have this: >> >> SmalltalkImage>>snapshot: save andQuit: quit >> ... >> resuming ifTrue: [ session := self newSession ]. >> ... >> >> (where session is additional instance variable of SmalltalkImage). >> >> SmalltalkImage>>newSession >> "Just answer unique object, which never can be identical to any >> previous session object, >> this is all what we need for detecting session change. >> A session object don't needs to carry any state (we have plenty of >> other objects in image which can do this for us). it just needs to be >> unique" >> >> ^ Object new. >> >> SmalltalkImage>>session >> ^ session >> >> then, i can write in own code: >> >> Smalltalk session == mySession ifFalse: [ self initForNewSession. >> mySession := Smalltalk session ] >> >> So, basically, this little addition allows you to detect whether >> session changed or not between >> two different calls to your code (given that you remembered the >> previous session somewhere). >> Currently we don't have such feature, and looking how some existing >> code deals with session management, >> i see how it can be simplified. >> If you want to do something similar today, you will need to register >> in startup list.. which IMO stinks ;) >> >> i don't like using startup lists, since you never know , what is the >> right order of resource initialization, >> and what inter-dependencies they may form, and changing dependencies >> over time will require changing startup order, again and again. Not >> fun. >> This technique allows you to lazily re-initialize any of your >> object(s) due to session change, once the control flow hits your code, >> but not before. >> (so you don't have to do all accounting at image startup time, you >> doing it only when it required/requested, which means shorter image >> startup time). >> >> The notion of session is highly important for external resource management. >> >> I using it in NativeBoost from very beginning, and wanna propose to >> use it globally. >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- > Marcus Denker -- http://marcusdenker.de > >

5 16

[Pharo-project] [update 2.0] #20332
by Marcus Denker Oct. 9, 2012

Oct. 9, 2012

20332 ----- Issue 6780: Nautilus Issue creation Menu is confusing http://code.google.com/p/pharo/issues/detail?id=6780 Issue 6779: MCSmalltalkhubRepository sends wrong instance creation message http://code.google.com/p/pharo/issues/detail?id=6779 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20330
by Marcus Denker Oct. 9, 2012

Oct. 9, 2012

20330 ----- Issue 6778: [Enh] Session object http://code.google.com/p/pharo/issues/detail?id=6778 (some packages are now dirty, this will be be fixed later) -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20329
by Marcus Denker Oct. 9, 2012

Oct. 9, 2012

20329 ----- Issue 5874: [ENH]: Notify progress with Announcements instead of Exceptions http://code.google.com/p/pharo/issues/detail?id=5874 (some packages are now dirty, this will be be fixed later) -- Marcus Denker -- http://marcusdenker.de

1 0