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

[Pharo-project] [update 2.0] #20339
by Marcus Denker Oct. 13, 2012

Oct. 13, 2012

20339 ----- Issue 6803: Activate the new Pango ST80 style http://code.google.com/p/pharo/issues/detail?id=6803 Issue 6802: remove ChangeSetBrowser http://code.google.com/p/pharo/issues/detail?id=6802 Issue 6794: CommandLine Configuration installer http://code.google.com/p/pharo/issues/detail?id=6794 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20338
by Marcus Denker Oct. 13, 2012

Oct. 13, 2012

20338 ----- Issue 6800: remove old ChangeSorter form menu http://code.google.com/p/pharo/issues/detail?id=6800 Issue 6799: remvove all references to ChangeSetBrowser outside of ChangeSorter http://code.google.com/p/pharo/issues/detail?id=6799 Issue 6795: Tango ST80 Syntax Coloring Scheme http://code.google.com/p/pharo/issues/detail?id=6795 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20337
by Marcus Denker Oct. 13, 2012

Oct. 13, 2012

20337 ----- Issue 6777: Improve ChangesBrowser default behavior http://code.google.com/p/pharo/issues/detail?id=6777 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)
by Pavel Krivanek Oct. 13, 2012

Oct. 13, 2012

Unfortunately it is not only about a layer between Morphic and Spec. Whole Spec design is greatly conforming to Morphic. Check out Spec definitions, they look almost like transcription of Morphic calls MethodToolbar class >> defaultSpec <spec> ^ { #Panel. #changeTableLayout. #listDirection:. #rightToLeft. #addMorph:. {#model. #browseModel.}. #addMorph:. {#model. #sendersModel.}. #addMorph:. {#model. #implementorsModel.}. #addMorph:. {#model. #versionModel. }. #addMorph:. {#model. #dropListModel.}. #hResizing:. #spaceFill. #vResizing:. #shrinkWrap. } Of course these methods are implemented only in Morphic classes. Whole layout management is directly taken from Morphic. And the Spec definitions are unclear and hard to read. They are composed almost solely from symbols so it is hard to work with and analyze them with our development tools. We have such beautiful metalanguage where to create DSL is so easy... In comparison with OmniBrowser the Spec is big step back. Sorry, I do not want to be ugly but I started this impression when I was working on Periscope and since that time it is deeper and deeper. Cheers, -- Pavel On Thu, Oct 11, 2012 at 10:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 11 October 2012 20:52, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> This method is actually the only one from ComposableModel with direct Morphic binding :) >> >> >> I am still trying to move that away, but I needed the rebuild to work >> > i think you can introduce own protocol (and put it as extension to > morphic, if you want to) > so, instead of saying > > widget removeAllMorphs > > you will use own extension method ,like: > > widget specRemoveAllChilds > > etc (spec here is namespacing prefix for a method, to indicate that it > belongs to spec package > and to indicate that it is a contract implied between spec and widget) > >> Ben >> >> On Oct 11, 2012, at 8:49 PM, Pavel Krivanek wrote: >> >>> Hi Ben, >>> >>> I really would like to write Spec binding for Phobos (Esteban will >>> want to do it for Mars etc.). But, how to say that, Spec was not >>> written with UI Independence in mind :-) Very basic example of that >>> fact: >>> >>> ComposableModel>>buildWithSpec: aSpec >>> "Build the widget using the spec name provided as argument" >>> | widget | >>> >>> (self spec notNil and: [ self needRebuild not ]) >>> ifTrue: [ | old | >>> self needRebuild: true. >>> old := self widget. >>> old removeAllMorphs. >>> self ensureExtentFor: old. >>> widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. >>> widget submorphs do:[ :e | old addMorphBack: e ]. >>> self spec instance: old. >>> ^ old ] >>> ifFalse: [ widget := SpecInterpreter buildMorphFor: self withSpec: aSpec. ]. >>> >>> self ensureExtentFor: widget. >>> >>> ^ widget >>> >>> Can you please do at least basic steps in the architecture of Spec to >>> make it more independent on Morphic? >>> >>> Cheers, >>> -- Pavel >>> >>> On Wed, Oct 10, 2012 at 12:10 AM, Benjamin >>> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>>> It was part of my battle plan to rule the world ;) >>>> >>>> We wanted with Nico to part it to Amber to get the Javascript part for free, then generate some XUL :) >>>> >>>> Anyway, really cool job, and impressive as well :) >>>> >>>> Ben >>>> >>>> On Oct 9, 2012, at 11:07 PM, StÃ©phane Ducasse wrote: >>>> >>>>> It looks really nice. >>>>> I imagine that Spec could generate XUL too. >>>>> >>>>> Stef >>>>> On Oct 9, 2012, at 9:48 PM, Pavel Krivanek wrote: >>>>> >>>>>> 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 >>>>>> <01.png> >>>>> >>>>> >>>> >>>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

6 13

[Pharo-project] Pharo on retina display
by Sean P. DeNigris Oct. 13, 2012

Oct. 13, 2012

Like all apps not upgraded for retina, Pharo looks pixelated and fuzzy on the new MBPs. Is there any workaround which at least makes the text less fuzzy? http://forum.world.st/file/n4642567/Screen_Shot_2012-08-01_at_3.48.23_PM.png -- View this message in context: http://forum.world.st/Pharo-on-retina-display-tp4642567.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

10 25

[Pharo-project] Fwd: Some progress on Athens
by StÃ©phane Ducasse Oct. 12, 2012

Oct. 12, 2012

Thanks guys! Stef Begin forwarded message: > From: Igor Stasenko <siguctua(a)gmail.com> > Subject: Some progress on Athens > Date: October 11, 2012 7:03:18 PM GMT+02:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Some fixes i did today, with some help of Camillo. > > > -- > Best regards, > Igor Stasenko. >

5 5

[Pharo-project] [update 2.0] #20336
by Esteban Lorenzano Oct. 12, 2012

Oct. 12, 2012

20336 ----- Issue 6684: Failing tests related to RPackage http://code.google.com/p/pharo/issues/detail?id=6684 Issue 6744: Failing Test: TraitTest>>#testTraitsUsersSanity http://code.google.com/p/pharo/issues/detail?id=6744 Issue 6733: Failing Test: RPackageSetTest.testPolymorphicWithPackageInfo http://code.google.com/p/pharo/issues/detail?id=6733 Issue 6792: restore ocompletion and smartchars enabling http://code.google.com/p/pharo/issues/detail?id=6792

1 0

Re: [Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)
by Stephan Eggermont Oct. 12, 2012

Oct. 12, 2012

Igor wrote: >Anyways, UI stuff is tend to be complex no matter how nicely you wrap >it.. because it is UI. I'd have to disagree there. Building UIs with Glamour is easy. I'd say Spec is simply at too low an abstraction level for most UI work. We might need a different abstraction for different kind of applications (non-browsers, something like hotdraw comes to mind), but Glamour provides a very good base for most of the tools in the Pharo image. Stephan

1 0

[Pharo-project] [update 2.0] #20335
by Marcus Denker Oct. 12, 2012

Oct. 12, 2012

20335 ----- Issue 6786: TextEditor loses selection interval on right-click http://code.google.com/p/pharo/issues/detail?id=6786 Issue 6789: Open MCRepository after adding it http://code.google.com/p/pharo/issues/detail?id=6789 Issue 6781: Freetype startup + some cleanup http://code.google.com/p/pharo/issues/detail?id=6781 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20334
by Marcus Denker Oct. 12, 2012

Oct. 12, 2012

20334 ----- Issue 6790: MC SaveDialog fork fix http://code.google.com/p/pharo/issues/detail?id=6790 Issue 6788: Improve Regex match/search/matchprefix methods comments http://code.google.com/p/pharo/issues/detail?id=6788 Issue 6787: Finder Cleanup 2 http://code.google.com/p/pharo/issues/detail?id=6787 Issue 6756: Type code in editor go crash and show red panel http://code.google.com/p/pharo/issues/detail?id=6756 -- Marcus Denker -- http://marcusdenker.de

1 0