On 22.08.2010 01:57, Hans-Peter Diettrich wrote:
>> If I know I need a form with A B and C and a Close button and I know
>> already exactly how it should be layed out
>
> Are you willing to share your thoughts about this layout?
Of course it depends on what A, B and C are, how they relate to eac
Bernd Kreuss schrieb:
This looks to me like you never *constructed* a GUI, or a similar
design. Instead you seem to prefer to get whatever seems useful, and
connect everything later, somehow.
How do you arrive at this conclusion?
From you text ;-)
If I know I need a form with A B and C an
On 8/21/2010 07:29, Bernd Kreuss wrote:
__
[1] I am writing this from the perspective of somebody who's intuition
is not contaminated by decades of Delphi usage.
that's also where i was coming from... i think you've stated it much better than
i ;)
As long as I have not
become too used t
On 8/21/2010 06:03, Hans-Peter Diettrich wrote:
waldo kitty schrieb:
1. set Align := alLeft for the first control,
2. set Align := alLeft for the splitter and move it after the first control
3. set Align := alClient for the second control
wow... that doesn't seem "intuitive" at all :?
That'
On 8/21/2010 04:28, Michael Van Canneyt wrote:
On Sat, 21 Aug 2010, waldo kitty wrote:
On 8/20/2010 22:00, Paul Ishenin wrote:
21.08.2010 9:17, Bernd Kreuss wrote:
How is the splitter supposed to be used? Can It be configured in the
form editor at all? And if so, what steps are needed to co
On 21.08.2010 23:40, Hans-Peter Diettrich wrote:
> This looks to me like you never *constructed* a GUI, or a similar
> design. Instead you seem to prefer to get whatever seems useful, and
> connect everything later, somehow.
How do you arrive at this conclusion?
If I know I need a form with A
Bernd Kreuss schrieb:
So why should it be intuitive to add an splitter first, and to add the
splitted components later - provided that you don't forget to do so?
No. It doesn't matter in what order you add them.
You add them all and then you connect them like components in a circuit
diagram.
On Sat, 21 Aug 2010 21:19:33 +0200 (CEST), Dimitri Smits
wrote:
> Warning: probably off-topic
>
> And a final note on those designers in java: you can and always had the
> ability to use a NULL-Layout to use absolute layouting. That is the
closest
> to the way Delphi does it.
There is
On 21/08/2010 20:40, Bernd Kreuss wrote:
Please write up your ideas about intuitive GUI layouts, and compare
these to the established layout management procedures, as implemented in
e.g. in the Java, gtk2 or other layout managers.
No need for that. Lazarus implemented them already the way I fin
On 21.08.2010 21:19, Dimitri Smits wrote:
> it seems you are comparing Java with the pascal world.
It was more about GUI design and layout managers in general. This is not
a Java thing. I only mentioned the layoutmanager that comes with
netbeans (it is not one of those that come with Swing out of
On 21.08.2010 20:59, Hans-Peter Diettrich wrote:
> So why should it be intuitive to add an splitter first, and to add the
> splitted components later - provided that you don't forget to do so?
No. It doesn't matter in what order you add them.
You add them all and then you connect them like comp
Warning: probably off-topic
- "Bernd Kreuss" schreef:
> I have seen a lot of approaches to GUI design and GUI designers with
> other toolkits, they all use either a set of sizers of varying
> complexity for certain purposes (box, grid, gridbag, etc) and you are
> supposed to study and learn
On 21.08.2010 20:42, Hans-Peter Diettrich wrote:
> The coordinates and sizes stay valid until the extent of the container
> control changes.
But this is of no interest for the one designing the layout. The
absolute coordinates have no meaning for the form design at this moment.
It should displa
On 21/08/2010 18:54, Bernd Kreuss wrote:
On 21.08.2010 18:56, Martin wrote
Anchors to me are same as (if not even more) confusing as the align method.
Can you remember what exactly it was that confused you?
I didn't mean to say I was confused. I meant to say that if align is
confusing (in the
Bernd Kreuss schrieb:
wow... that doesn't seem "intuitive" at all :?
That's exactly how splitters are used in Delphi.
This doesn't make it a single bit more intuitive, you just don't notice
it anymore. This is a common problem in software development.
Right, but it is as splitters (of that
Bernd Kreuss schrieb:
Interestingly the TSplitter actually *has* already the ability to be
used with anchor docking in the way I (and many others) would have
expected it from the beginning on. The only thing that is wrong in my
eyes is the default still being set to the old delphi behavior inste
Bernd Kreuss schrieb:
The splitter is *expected* to be positioned freely in the *middle* of
the form *between* other controls. This is intuitive. Gluing it
unmovable to one of the form borders by default until the user finds out
how to make it movable (or how the alternative strange old Delphi u
Bernd Kreuss schrieb:
UI clearly communicating to the user
Here is an example: There are hints in the form editor that show amongst
other information the positioning coordinates of a control in the form.
Position: 123, 456
Size: 23 x 42
When a control is set to anything else than alNone
I didn't want to push any priority, I simply wanted to write it before I
forget it again. Probably some clearly written and easily accessible
documentation could prevented this in the future and I am glad that I
can use the anchors and free positioning even with splitters and am not
forced to use t
On 21/08/2010 15:14, Bernd Kreuss wrote:
On 21.08.2010 15:52, Richard Saunders wrote:
that's
the way it started and always has been and I think its too late to
change now.
Interestingly the TSplitter actually *has* already the ability to be
used with anchor docking in the way I (and many othe
On 21.08.2010 15:52, Richard Saunders wrote:
> that's
> the way it started and always has been and I think its too late to
> change now.
Interestingly the TSplitter actually *has* already the ability to be
used with anchor docking in the way I (and many others) would have
expected it from the b
Bernd-
There are often different interpretations of "intuitive" so it is far
from the universal, objective attribute you seem to view it as.
The original designers of TSplitter found it more useful, and possibly
more intuitive from the beginning, to have splitters always aligned to
somethin
On 21.08.2010 14:31, Mattias Gaertner wrote:
> Several controls set the Align property by default. For example
> TStatusBar, TSplitter, TButtonPanel, TPage.
These are intuitively supposed to be positioned where the align property
suggests and not moved to somewhere into the middle of a form
> TS
On Sat, 21 Aug 2010 13:29:02 +0200
Bernd Kreuss wrote:
> On 21.08.2010 04:00, Paul Ishenin wrote:
> > 1. set Align := alLeft for the first control,
> > 2. set Align := alLeft for the splitter and move it after the first control
> > 3. set Align := alClient for the second control
>
>
> Two quest
On Saturday 21 August 2010 15:08:21 Bernd Kreuss wrote:
> When a control is set to anything else than alNone then some or all of
> these coordinates become meaningless. This should be communicated to the
> user. The movable coordinates that are now not longer movable but
> calculated should be repl
On 21.08.2010 13:43, Bernd Kreuss wrote:
> UI clearly communicating to the user
Here is an example: There are hints in the form editor that show amongst
other information the positioning coordinates of a control in the form.
Position: 123, 456
Size: 23 x 42
When a control is set to anything
On 21.08.2010 12:03, Hans-Peter Diettrich wrote:
>> wow... that doesn't seem "intuitive" at all :?
>
> That's exactly how splitters are used in Delphi.
This doesn't make it a single bit more intuitive, you just don't notice
it anymore. This is a common problem in software development.
I am a re
On 21.08.2010 04:00, Paul Ishenin wrote:
> 1. set Align := alLeft for the first control,
> 2. set Align := alLeft for the splitter and move it after the first control
> 3. set Align := alClient for the second control
Two questions:
a) How can I then make the splitter always be in a fixed relativ
waldo kitty schrieb:
1. set Align := alLeft for the first control,
2. set Align := alLeft for the splitter and move it after the first
control
3. set Align := alClient for the second control
wow... that doesn't seem "intuitive" at all :?
That's exactly how splitters are used in Delphi.
Do
On Sat, 21 Aug 2010, waldo kitty wrote:
On 8/20/2010 22:00, Paul Ishenin wrote:
21.08.2010 9:17, Bernd Kreuss wrote:
How is the splitter supposed to be used? Can It be configured in the
form editor at all? And if so, what steps are needed to configure a
vertical splitter between two controls
On 8/20/2010 22:00, Paul Ishenin wrote:
21.08.2010 9:17, Bernd Kreuss wrote:
How is the splitter supposed to be used? Can It be configured in the
form editor at all? And if so, what steps are needed to configure a
vertical splitter between two controls in the form editor?
1. set Align := alLeft
21.08.2010 9:17, Bernd Kreuss wrote:
How is the splitter supposed to be used? Can It be configured in the
form editor at all? And if so, what steps are needed to configure a
vertical splitter between two controls in the form editor?
1. set Align := alLeft for the first control,
2. set Align :=
On 21.08.2010 03:17, Bernd Kreuss wrote:
> How is the splitter supposed to be used?
Found it: If I make any change to the property ResizeAnchor (switch it
to something else and then switch it back to what it was) the anchor
editor is no longer locked and I can remove the left anchor and move it
t
Hi,
I have now tried for more than 30 minutes clicking around in the form
editor trying to find out how the TSplitter is supposed to be used but
it simply wont work (for me). Or is it simply not completely implemented
yet?
I have tried giving it sub-panels but it doesn't seem to want anything
con
34 matches
Mail list logo
