How to build a GUI

> Now i´m adding new capabilities.
>
> -Radio buttons widget mechanism.A selection of one must disable the  
> others
> in the same container.
> -Styles editor. I want add the capabilitie of create and edit styles  
> for the
> widgets.And apply with a #applyStyle: method. and too from UIBuilder.
> -Add new properties for set in the UIBuilder, not only the basics  
> text,
> image or font.
> -I want build a tabControl of intuitive way, add, remove and fill  
> tabs from
> designer.
> -A good way for persist the morph mechanism is needed.Perhaps not  
> now but it
> will be necessary more ahead if something serious is wanted.

>
> On Aug 30, 2009, at 10:32 32PM, nullPointer wrote:
>
>> -Create a mechanism for link properties or accessors of a object
>> ( entitys )
>> at controls.I don´t like the MorphicModel mechanism,and dependences.
>> I want
>> events for all.That last is very important necessity.
> Having seen a...fair amount of how complex event handling can get in
> VisualWorks GUI's, I'd really appreciate it if you'd take a look into
> using Announcements :)
> Unless of course, events mean something entirely different in Squeak.
>> Now i´m adding new capabilities.
>>
>> -Radio buttons widget mechanism.A selection of one must disable the
>> others
>> in the same container.
>> -Styles editor. I want add the capabilitie of create and edit styles
>> for the
>> widgets.And apply with a #applyStyle: method. and too from UIBuilder.
>> -Add new properties for set in the UIBuilder, not only the basics
>> text,
>> image or font.
>> -I want build a tabControl of intuitive way, add, remove and fill
>> tabs from
>> designer.
>> -A good way for persist the morph mechanism is needed.Perhaps not
>> now but it
>> will be necessary more ahead if something serious is wanted.
> I love the sweet smell of feature creep in the morning!
> Just remember, shipping something is better than nothing, and it's not
> like anything existing seems to come even close to what you have made
> already.
>>
>> I prefer not to say when I will conclude my work, but It does not
>> have sense
>> to raise something incorrect or incomplete. I´m put much effort in
>> that work
>> and i want do it good.
>>
>> Regards :)
> Incorrect, I agree. Take a look at the Pharo bugtracker and note the
> amount of pure bugs not marked 1.0 if you feel 0 bugs is the limit for
> when something is in a releasable state though :)
> Incomplete... well, 20% gets used 80% of the time and all that.
>
> I have no idea of the structure of what you are doing, just thought
> I'd add one thing, which I've found immensely useful in the VW
> UIBuilder:
>  - Include hooks in the interface building process. (preBuildWith: ,
> postBuildWith:, preOpenWith: postOpenWith: ), so you can modify the
> spec at runtime.
> Not everything about how you want an interface to display can be known
> at design-time, adding such hooks provide the means to do pretty neat
> dynamic stuff based on the runtime environment.
> F.ex: - VisualWorks allows you to provide application-specified labels
> instead of hardcoding them in the design viewer.
> However, by default, only labels defined as methods on the class side
> of the ApplicationModel will be mapped to the builders list of labels.
> (as far as I know at least...).
> Using preBuildWith:, you can add instance-specific (say, taken from
> its model) labels to the Builders dictionary of available labels.
>
> Good luck with the further work, I look forward to seeing the results!
>
> Cheers,
> Henry
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project