Yes something like that.
Use a system that we can hack and modify (have a look at the VW  
windowspec)

this way your builder to build morphic but also something else too.

windowSpec
        "UIPainter new openOnClass: self andSelector: #windowSpec"

        <resource: #canvas>
        ^#(#{UI.FullSpec}
                #window:
                #(#{UI.WindowSpec}
                        #properties: #(#{UI.PropertyListDictionary} #sizeType  
#specifiedSize #positionType #screenCenter #openType #advanced )
                        #label: #(#{Kernel.UserMessage} #key: #aboutVisualWorks 
 
#defaultString: 'About Visual Works' #catalogID: #labels)
                        #min: #(#{Core.Point} 20 20 )
                        #max: #(#{Core.Point} 1024 768 )
                        #bounds: #(#{Graphics.Rectangle} 512 384 992 704 ) )
                #component:
                #(#{UI.SpecCollection}
                        #collection: #(
                                #(#{UI.TabControlSpec}
                                        #layout: #(#{Graphics.LayoutFrame} 10 0 
10 0 -10 1 -40 1 )
                                        #name: #tabs
                                        #model: #tabListHolder
                                        #labels: #() )
                                #(#{UI.ActionButtonSpec}
                                        #layout: #(#{Graphics.LayoutFrame} -90 
1 -35 1 -10 1 -10 1 )
                                        #name: #ok
                                        #model: #accept
                                        #label: #(#{Kernel.UserMessage} #key: 
#OK #defaultString: 'OK'  
#catalogID: #labels)
                                        #isDefault: true
                                        #defaultable: true ) ) ) )

Stef


On Jul 21, 2009, at 2:58 AM, Mariano Martinez Peck wrote:

>
>
> On Mon, Jul 20, 2009 at 7:15 PM, nullPointer <[email protected]>  
> wrote:
>
> Excuse me for my poor english.
>
> I´m developing a GUI Builder for Pharo ->
> http://www.youtube.com/watch?v=CHbc1t83fEI
>
> One of my problems is the way of persist a morph.Now i use the same  
> way for
> create a Morph than message #saveOnFile  but not saving in a  
> external file
> else in array of bytes returned for a #spec message.
>
> I would know if morphic allow or exists another way of persistence  
> more
> readable and fast. A complex morph serialized of that way is too  
> slow in
> load.
>
> Perhaps you can use another serializer. Here a some: 
> http://www.seaside.st/documentation/persistence
>
> For example, http://www.seaside.st/documentation/persistence#230290016
> or http://www.seaside.st/documentation/persistence#40827471
>
> Your project seems very interesting, tough.
>
> Best,
>
> Mariano
>
>
>
>
> Regards.
> --
> View this message in context: 
> http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3292117.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to