> I'm sorry, I still don't like the appearance.
No problem Thats why I'm showing it to you.
> . Never nest labeled frames
>
> . Using labeled frames has made you make up useless names for things.
> What's the stiff at the bottom? Oh, it's "other options". What else
> would they be? Giraffes?
I could remove the frame text and just leave it as a box. Was thinking
it just groups similar items together. Maybe just one box around all
classicladder options and one around all others?
maybe none :)
>
> . Stick to a single column unles stuff doesn't fit
>
> . Show explanatory text to the left of the interactive control, using a
> colon to separate them. Left-justify explanatory text:
> Number of digital out pins: [ 15 ]
> Number of digital in pins: [ 15 ]
> Number of ... [ 15 ]
Yes I hadn't added your suggested changes yet.Just wanted your
thoughts on frames.
>
> . Don't put blank areas at the top, put it at the bottom. Unless
> things are "very close" to fitting in the default space, don't
> stretch the space between them, let the extra space all appear at the
> bottom.
Ok.
>
> . Use initial caps. Don't write
> [ ] include modbus master support
> write
> [ ] Include modbus master support
Yep Typo
> . Unless it's happening because of your gnome theme, don't bold text
> (group frame titles) or change colors (advaned configuration
> options). Never modify font or color defaults given to you by glade.
>
I send you a pic of the wrong page I experimented with colour
changes etc. The working one has standard colours.
> . How is "Create ladder program" going to work the second time through,
> when the user has possibly edited the ladder already? How is the
> "edit" button going to work--can the classicladder GUI run while emc
> is not running?
The second through time I have options.
-I can redirect ladder to load from the users config file.
That program should always be custom.clp.
- I can pop a window up telling people to manually
( through CL ) search for their file.
If someone edits with say the E-stop ladder program
clicked I will have to pop a window reminding them to save it
as custom.clp.
-Another more involved way would have stepconf copy a ladder
program to their folder (or a temp one) rename it custom.clp
then have CL load it. That way no matter what optional file
they load it will always end up as custom.clp in their conf
folder with out the user having to think much.
Yes CL's GUI will load without EMC. This edit feature I already
have working in my latest version of stepconf (although it always
loads a black file at the moment)
>
> . While we may not have a standard way of writing 'halui' in
> user-visible program text or documentation yet, Hal_UI probably isn't
> one I would have picked.
Yes that option I added because It is pretty much needed to
add real physical operator panels.
My thoughts on the and classicladder is if we can get the
components to load for the user, they have a better chance to
find the pins and connect them. It seems a common problem
is that they don't know where to put the load command.
Using stepconf to do it makes it consistent for us to help
debug and easy for them to get the pins to show.
I will work on my UI design and get back to you.
Cheers Chris Morley
_________________________________________________________________
Show them the way! Add maps and directions to your party invites.
http://www.microsoft.com/windows/windowslive/events.aspx
------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
