Property sheet - ideas wanted

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Property sheet - ideas wanted

Bob.Cowdery
Hi All

I have an application which is essentially a bunch of custom morphs
interacting together through connectors. Some of these talk to hardware
and plugin processes and need a fair amount of parameterization. The
parameters are strings, boolean, selections, numbers etc. All the usual
things you would expect in a conventional app. I need something akin to
a property sheet - not a million miles away from the eToys scripting
sheet. I played with this a bit but couldn't figure out how to add
methods and parameters. Is this
a fixed sheet - can it be changed easily - or is it a major code hack.
The other option I was toying with is Seaside but that would not be
ideal as I would have two completely different user interfaces. Is there
any other way to tackle this problem apart from biting the bullet and
coding up a whole load of dialogues from whatever useful morphs I can
find.

Thanks
Bob
*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else.  In such case, you should destroy this
message and are asked to notify the sender by reply email.

Reply | Threaded
Open this post in threaded view
|

Re: Property sheet - ideas wanted

Chris Muller-2
If you've already coded up a bunch of custom morphs,
one more (a property-sheet) shouldn't be too much
trouble should it?

  PropertySheetMorph
    LabelValuePairMorph
      StringMorph (label)
      PropertyValueMorph
        TextMorph (type it in)
        PropertyValueSelectorMorph (select it)

something like that..

Sounds like you're interested in a consistent UI for
the property-sheets, so you could code these to match
the existing style of your custom morphs..

> Message: 8
> Date: Thu, 9 Feb 2006 23:03:18 -0000
> From: "Cowdery, Bob [UK]"
> <[hidden email]>
> Subject: Property sheet - ideas wanted
> To: "The general-purpose Squeak developers list"
> <[hidden email]>
> Message-ID:
>
>
<[hidden email]>

>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All
>
> I have an application which is essentially a bunch
> of custom morphs
> interacting together through connectors. Some of
> these talk to hardware
> and plugin processes and need a fair amount of
> parameterization. The
> parameters are strings, boolean, selections, numbers
> etc. All the usual
> things you would expect in a conventional app. I
> need something akin to
> a property sheet - not a million miles away from the
> eToys scripting
> sheet. I played with this a bit but couldn't figure
> out how to add
> methods and parameters. Is this
> a fixed sheet - can it be changed easily - or is it
> a major code hack.
> The other option I was toying with is Seaside but
> that would not be
> ideal as I would have two completely different user
> interfaces. Is there
> any other way to tackle this problem apart from
> biting the bullet and
> coding up a whole load of dialogues from whatever
> useful morphs I can
> find.