- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

First people should use it, second we should check if the code is overriding or not the code in the image (if this is the case we should see how the code in the kernel and in the builder should be changed to avoid overrides), .... Now you can load the package and use it. and this is the best move for pushing its adoption. I looked at the code long time ago and I should redo it. Stef On Jan 5, 2011, at 8:38 AM, Olivier Auverlot wrote: > uibuilder is a very impressive tool ! > > Pharo must have this type of tool for to be a credible solution in the development of desktop applications.I think that integrate uibuilder in the standard image will be a good idea :) > > this is planed ? > > Best regards > Olivier > www.auverlot.fr > >> Cool ! >> >> Laurent >> >> On Wed, Jan 5, 2011 at 2:18 AM, nullPointer <epicfan(a)gmail.com> wrote: >> >> Finally I implemented the posibility of create a custom windows in >> CLFramework. >> >> The final visual result fails in somethings, but seems the original: >> >> http://forum.world.st/file/n3174741/example.png >> >> http://www.youtube.com/watch?v=QAu6fPyz1b0 >> http://www.youtube.com/watch?v=Gb9NoWFdhXo >> http://www.youtube.com/watch?v=5CpUnIH9KVw >> -- >> View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3174741.… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > >

Jan. 5, 2011

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

> I donÂ´t know if I understand correctly the question... Yes > The design code is saved in a basic message #specmorph: > specMorph > > | cLStatusbar container cLPanel | > "container" > container := CLPanel new. > self containerSpec: container. > container visible: false. > container openInWorld. > > "cLPanel" > cLPanel := CLPanel new. > container addMorph: cLPanel. > self cLPanelSpec: cLPanel. > > "cLStatusbar" > cLStatusbar := CLStatusbar new. > cLPanel addMorph: cLStatusbar. > self cLStatusbarSpec: cLStatusbar. > > ^container > > and another spec method for define each control of view, in current example > be #cLPanelSpec:, #cLStatusbarSpec: and #containerSpec:, for example: > > cLPanelSpec: aTCLControl > > aTCLControl name: 'cLPanel'. > aTCLControl usePolymorphStyleMechanism: false. > aTCLControl balloonText: nil. > aTCLControl enabled: true. > aTCLControl location: 0@0. > aTCLControl extent: 530@377. > aTCLControl anchors: {true .true .true .true .}. > aTCLControl imageResource: nil. > aTCLControl style: {(BorderStyle width: 0 color: Color transparent) .(Color > r: 0.892 g: 0.887 b: 0.879) .(Color r: 0.503 g: 0.553 b: 0.662) .false .true > .}. > aTCLControl minWidth: 2. > aTCLControl minHeight: 2. > aTCLControl layout: {ProportionalLayout .#spaceFill .#spaceFill .0 .false > .false .false .0 .0 .1073741823 .#topToBottom .#none .#center .#topLeft > .#topLeft .#none .#none .}. ok this is better than to serialize the object. > I believe the definition of UI must be do with XUL, or XAML. Of that way > donÂ´t need a designer in Smalltalk, else could be use some of tools for > create XAML o XUL uis. Later, a "Reader" could parse the XML and build a > Morphic GUI or a Seaside GUI. As I told you before (read my previous emails) you do not need XML or XAML. You just need what is done in VW a spec They have done that and it works well. Here I did not formatted it well but you GET EXACTLY THE SAME EXPRESSION POWER THAN XML without the need for yet another parser. > cLPanelSpec: aTCLControl > > aTCLControl name: 'cLPanel'. > aTCLControl usePolymorphStyleMechanism: false. > aTCLControl balloonText: nil. > aTCLControl enabled: true. > aTCLControl location: 0@0. > aTCLControl extent: 530@377. > aTCLControl anchors: {true .true .true .true .}. > aTCLControl imageResource: nil. > aTCLControl style: {(BorderStyle width: 0 color: Color transparent) .(Color > r: 0.892 g: 0.887 b: 0.879) .(Color r: 0.503 g: 0.553 b: 0.662) .false .true > .}. > aTCLControl minWidth: 2. > aTCLControl minHeight: 2. > aTCLControl layout: {ProportionalLayout .#spaceFill .#spaceFill .0 .false > .false .false .0 .0 .1073741823 .#topToBottom .#none .#center .#topLeft > .#topLeft .#none .#none .}. can be turned into #(Spec name: 'cLPanel'; usePolymorphStyleMechanism: false; ... and...) this is strictly equivalent to XML. Now if you build an XML reader we will be able to reuse the interpretation (oh there is this reference in the XML then I should create an object of a specific class). Look at the example below for the changeList widget. I do not have the time to format it well. #(#{UI.FullSpec} #window: #(#{UI.WindowSpec} #label: #(#{Kernel.UserMessage} #key: #ChangeList #defaultString: 'Change List' #catalogID: #labels) #min: #(#{Core.Point} 300 400) #bounds: #(#{Graphics.Rectangle} 512 268 942 768) #menu: #menuBar #isEventDriven: true) #component: #(#{UI.SpecCollection} #collection: #(#(#{UI.SequenceViewSpec} #properties: #(#{UI.PropertyListDictionary} #dragOkSelector #wantToDrag: #dragEnterSelector #dragEnter: #dragOverSelector #dragOver: #dragStartSelector #doDrag: #dropSelector #drop: #dragExitSelector #dragLeave:) #layout: #(#{Graphics.LayoutFrame} 0 0 0 0 -100 1 150 0) #name: #listView #model: #selectionInList #callbacksSpec: #(#{UI.UIEventCallbackSubSpec} #doubleClickSelector: #toggleRemoveForListController: #requestValueChangeSelector: #changeRequest) #menu: #changeListMenuHolder) #(#{UI.CompositeSpecCollection} #collection: #(#(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 0) #model: #fileFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #file #defaultString: 'file' #catalogID: #labels)) #(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 25) #model: #changeTypeFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #type #defaultString: 'type' #catalogID: #labels)) #(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 50) #model: #classNameFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #class #defaultString: 'class' #catalogID: #labels)) #(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 75) #model: #protocolFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #protocol #defaultString: 'protocol' #catalogID: #labels)) #(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 100) #model: #selectorFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #selector #defaultString: 'selector' #catalogID: #labels)) #(#{UI.CheckBoxSpec} #layout: #(#{Core.Point} 4 125) #model: #valuesFilterAdaptor #label: #(#{Kernel.UserMessage} #key: #same #defaultString: 'same' #catalogID: #labels))) #compositeSpec: #(#{UI.CompositeSpec} #layout: #(#{Graphics.LayoutFrame} -100 1 0 0 0 1 150 0) #name: #filters #flags: 8)) #(#{UI.ResizingSplitterSpec} #layout: #(#{Graphics.LayoutFrame} 0 0 150 0 0 1 153 0) #name: #ResizingSplitter1 #horizontal: true #minAboveSize: 150 #minBelowSize: 25 #aboveWidgets: 'listView filters' #belowWidgets: 'textCanvas') #(#{UI.SubCanvasSpec} #layout: #(#{Graphics.LayoutFrame} 0 0 153 0 0 1 0 1) #name: #textCanvas #flags: 0 #minorKey: #standardText)))) The first view is what you get in the UIbuilder and the second view is the widget once it is open > > > Regards > > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3175227.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] Hudson Win setup build

by Marcus Denker

On Jan 5, 2011, at 11:11 AM, Torsten Bergmann wrote: > Would be nice if Hudson could also build > the Pharo windows setup automatically > in the future. Should be easy to setup. > > I know thats not the highest prio but > I wanted to check if it is possible anyway > (dont know what kind of machine the ci server > is currently runnning on). > right now we just have a linux slave builder. This is what IT Services was able to provide. > Since I think VM's are built in the future > via Hudson too there must be access to a > win32 machine anyway. Yes, we will look into setting up a Mac and a Windows slave soon. One idea is to use an older intel mac and install windows there as a virtual machine and use this machine for both windows and mac. Alternatively, Hudson can have Amazon E2C slaves... for windows, that would be an alternative (but an expensive one). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 5, 2011

Re: [Pharo-project] Best way for change a window style

by nullPointer

I donÂ´t know if I understand correctly the question... The design code is saved in a basic message #specmorph: specMorph | cLStatusbar container cLPanel | "container" container := CLPanel new. self containerSpec: container. container visible: false. container openInWorld. "cLPanel" cLPanel := CLPanel new. container addMorph: cLPanel. self cLPanelSpec: cLPanel. "cLStatusbar" cLStatusbar := CLStatusbar new. cLPanel addMorph: cLStatusbar. self cLStatusbarSpec: cLStatusbar. ^container and another spec method for define each control of view, in current example be #cLPanelSpec:, #cLStatusbarSpec: and #containerSpec:, for example: cLPanelSpec: aTCLControl aTCLControl name: 'cLPanel'. aTCLControl usePolymorphStyleMechanism: false. aTCLControl balloonText: nil. aTCLControl enabled: true. aTCLControl location: 0@0. aTCLControl extent: 530@377. aTCLControl anchors: {true .true .true .true .}. aTCLControl imageResource: nil. aTCLControl style: {(BorderStyle width: 0 color: Color transparent) .(Color r: 0.892 g: 0.887 b: 0.879) .(Color r: 0.503 g: 0.553 b: 0.662) .false .true .}. aTCLControl minWidth: 2. aTCLControl minHeight: 2. aTCLControl layout: {ProportionalLayout .#spaceFill .#spaceFill .0 .false .false .false .0 .0 .1073741823 .#topToBottom .#none .#center .#topLeft .#topLeft .#none .#none .}. I believe the definition of UI must be do with XUL, or XAML. Of that way donÂ´t need a designer in Smalltalk, else could be use some of tools for create XAML o XUL uis. Later, a "Reader" could parse the XML and build a Morphic GUI or a Seaside GUI. Regards -- View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3175227.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 5, 2011

[Pharo-project] Hudson Win setup build

by Torsten Bergmann

Would be nice if Hudson could also build the Pharo windows setup automatically in the future. Should be easy to setup. I know thats not the highest prio but I wanted to check if it is possible anyway (dont know what kind of machine the ci server is currently runnning on). Since I think VM's are built in the future via Hudson too there must be access to a win32 machine anyway. Thx T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Jan. 5, 2011

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

How do you save the ui once designed because I'm thinking that we could ask one of our guy here to help (implementing a kind of UIBuilder). Stef On Jan 5, 2011, at 2:18 AM, nullPointer wrote: > > Finally I implemented the posibility of create a custom windows in > CLFramework. > > The final visual result fails in somethings, but seems the original: > > http://forum.world.st/file/n3174741/example.png > > http://www.youtube.com/watch?v=QAu6fPyz1b0 > http://www.youtube.com/watch?v=Gb9NoWFdhXo > http://www.youtube.com/watch?v=5CpUnIH9KVw > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3174741.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

This is really good On Jan 5, 2011, at 2:18 AM, nullPointer wrote: > > Finally I implemented the posibility of create a custom windows in > CLFramework. > > The final visual result fails in somethings, but seems the original: > > http://forum.world.st/file/n3174741/example.png > > http://www.youtube.com/watch?v=QAu6fPyz1b0 > http://www.youtube.com/watch?v=Gb9NoWFdhXo > http://www.youtube.com/watch?v=5CpUnIH9KVw > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3174741.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] Generators for Pharo Xmax wish)

by StÃ©phane Ducasse

On Jan 5, 2011, at 8:55 AM, Noury Bouraqadi wrote: > Hi, > > Before integrating some code into Pharo the first step is to check that the licence is MIT. from Squeak it is since they publish in MIT. Having tests and class comments would be a good check. > > Noury > On 5 janv. 2011, at 00:22, Miguel CobÃ¡ wrote: > >> The easiest way to get this code into pharo core is to create a mcz >> package, put it on PharoInbox on squeaksource and create a ticket in >> code.google.com/p/pharo referencing it and taggint it Fixed, this way >> StÃ©phane or Markus can harvest it to the core image. >> If the mcz package is overkill, then a simple fileout of the package in >> squeak attached to the ticket will do. >> >> Maybe in the long term a project on squeaksource should be created (if >> not exists) and new changes to to it and from there pulled to squeak and >> pharo. >> >> Cheers >> >> El mar, 04-01-2011 a las 15:43 -0700, Ralph Boland escribiÃ³: >>> I earlier posted a Xmas wish that Pharo add generators >>> (steal the generators code from Squeak). >>> No one appeared to be familiar with them. >>> The generators code was added to Squeak by Andreas Raas. >>> The class Generator can be found in Squeak as a subclass >>> of Stream. It's about 140 lines of code and, as I said before, >>> is really useful and needed in order for me to port some of the >>> packages I am developing from Squeak to Pharo. >>> Class Generator is tested in class GeneratorTest which also serves >>> as examples of uses of Generators. >>> So please, someone go steal the code! >>> And stealing is easy. For example I stole the following comment on >>> class Generator directly from the class comment: >>> >>> " >>> A Generator transforms callback interfaces into stream interfaces. >>> >>> When a producer algorithm provide results as callbacks (blocks) and a >>> consumer algorithm expects streamable input, a Generator transforms >>> one into the other, for example: >>> >>> | generator | >>> generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g >>> yield: prime]]. >>> [generator atEnd] whileFalse:[Transcript show: generator next]. >>> " >>> >>> Regards, >>> >>> Ralph Boland >>> >> >> -- >> Miguel CobÃ¡ >> http://twitter.com/MiguelCobaMtz >> http://miguel.leugim.com.mx >> >> >> >> > >

Jan. 5, 2011

Re: [Pharo-project] Generators for Pharo Xmax wish)

by StÃ©phane Ducasse

On Jan 4, 2011, at 11:43 PM, Ralph Boland wrote: > I earlier posted a Xmas wish that Pharo add generators > (steal the generators code from Squeak). > No one appeared to be familiar with them. > The generators code was added to Squeak by Andreas Raas. > The class Generator can be found in Squeak as a subclass > of Stream. It's about 140 lines of code and, as I said before, > is really useful and needed in order for me to port some of the > packages I am developing from Squeak to Pharo. > Class Generator is tested in class GeneratorTest which also serves > as examples of uses of Generators. > So please, someone go steal the code! Ralph please package it, open ticket, so that we have tracability. > And stealing is easy. We are not stealing we are reusing. And Generator are probably coming from GNU Smalltalk. > For example I stole the following comment on > class Generator directly from the class comment: > > " > A Generator transforms callback interfaces into stream interfaces. > > When a producer algorithm provide results as callbacks (blocks) and a > consumer algorithm expects streamable input, a Generator transforms > one into the other, for example: > > | generator | > generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g > yield: prime]]. > [generator atEnd] whileFalse:[Transcript show: generator next]. > " > > Regards, > > Ralph Boland >

Jan. 5, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by StÃ©phane Ducasse

thanks sean! On Jan 4, 2011, at 11:44 PM, Sean P. DeNigris wrote: > > Fix in inbox > SLICE-Issue-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1 > > Added comments for TextMorph's #autoFit: and #wrapFlag: > -- > View this message in context: http://forum.world.st/Issue-3506-in-pharo-TextMorph-s-autoFit-and-wrapFlag-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011