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@gmail.com <mailto:epicfan@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.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

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@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.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

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.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

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.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

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.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

On Jan 5, 2011, at 12:38 PM, nullPointer wrote:

Yeah, that is dicussed before, many times.

UIBuilder is dead, and I believe any type of classic designer like VW use. Try implement a classic designer for UIs is lost time. I have many time for lost :)

I do not think so but this is your right to think that

I believe the future is WPF, and the tools for generate XAML.

oh no. You mix the techno and the concept. Anyway when you will see that I'm right you will smile.

Too exists some tools for create XUL. Don´t is needed a UI designer in Smalltalk, only is needed a "Reader" for build the UI from a XML text.

Regards. -- View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3175319.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Looks neat. Last time I was told about UIBuilder it was closed, repository wiped out. Does it mean you changed your mind or something else conduct you to develop it? In curiosity. Hilaire Le 05/01/2011 02:18, nullPointer a écrit :

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

-- Education 0.2 -- http://blog.ofset.org/hilaire

WHich is the difference between CLFramework and UIBUilder? I thought it was the same.... gracias! mariano On Wed, Jan 5, 2011 at 6:19 PM, nullPointer <epicfan@gmail.com> wrote:

CLFramework continues in develop but don´t the subset UIBuilder. For the change of window styles I didn´t almost update UIBuilder.

Regards. -- View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3175983.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Pensé que inglés era tu idioma nativo. Y como nullpointer no es un nombre normal en ningún país conocido ;) no tenía manera de saber que hablabas español. ¿De dónde eres? El mié, 05-01-2011 a las 12:16 -0800, nullPointer escribió:

Mi inglés es penoso. Lo que quiero decir es que aunque haya un proyecto en SourceSafe llamado UIBuilder, que es exactamente igual al CLFramework, lo único que he modificado son clases que no tienen nada que ver con aquellas categorías relacionadas con el diseñador de UIs. El desarrollo del diseñador de interfaces esta cerrado desde hace tiempo y yo al menos no lo voy a continuar.

Google translation - My English is poor. What I mean is that even if a project called UIBuilder SourceSafe, which is exactly equal to CLFramework only thing I changed are classes that have nothing to do with those categories related to the designer of UIs. The development of the interface designer is closed for some time and I for one am not going to continue.

-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Le 05/01/2011 18:19, nullPointer a écrit :

CLFramework continues in develop but don´t the subset UIBuilder. For the change of window styles I didn´t almost update UIBuilder.

Regards.

I don't understand. Hilaire