Re: [MSEide-MSEgui-talk] object inspector problem

[Julio Jiménez]

2017-03-16 22:06 GMT+01:00 Krzysztof :

>
> Thanks a lot Julio! Finally understand it! What I did wrong is that I
> always added not enough panels so tabs for "source | mainform |" didn't
> work properly (they disappeared when tried add components palette at top or
> messages at bottom of dock panel). For this case, (each) component palette,
> source and messages must be in own container and then they can be merged
> into one so source editor container keep its tabs.
>
>
Thanks to Code dz for his video :)

-- 
Julio Jiménez Borreguero
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[Martin Schreiber]

On Thursday 16 March 2017 22:06:15 Krzysztof wrote:
> 2017-03-16 10:46 GMT+01:00 Julio Jiménez :
> > A picture is worth a thousand words.  ;)
>
> Thanks a lot Julio! Finally understand it! What I did wrong is that I
> always added not enough panels so tabs for "source | mainform |" didn't
> work properly (they disappeared when tried add components palette at top or
> messages at bottom of dock panel). For this case, (each) component palette,
> source and messages must be in own container and then they can be merged
> into one so source editor container keep its tabs.

Are you sure? There must be a tabbed container (C) for the 
source(F)/message(G) combination(D) and the design form(E). The component 
palette(B) above does not need an own container. A is the docking area or a 
floating panel.

A--+
|B+|
||Component Palette   ||
|C+|
||D Source,Messages|E main.mfm||
||D--+||
|||F+|||

   Source   

|||G+|||
   Messages 
|||++|||
||+--+||
|++|
+--+

> @Martin. You could put that video in git repo or somewhere in sourceforge
> wiki so we don't lose it, it is only 1.4MB and very helpfull for newbies in
> docking :) .

@code dz:
Do you like to push the video to MSEuniverse Wiki? Please register on Gitlab 
and send me your username.
https://gitlab.com/users/sign_in

Martin

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[Krzysztof]

2017-03-16 10:46 GMT+01:00 Julio Jiménez :
>
> A picture is worth a thousand words.  ;)
>

Thanks a lot Julio! Finally understand it! What I did wrong is that I
always added not enough panels so tabs for "source | mainform |" didn't
work properly (they disappeared when tried add components palette at top or
messages at bottom of dock panel). For this case, (each) component palette,
source and messages must be in own container and then they can be merged
into one so source editor container keep its tabs.
@Martin. You could put that video in git repo or somewhere in sourceforge
wiki so we don't lose it, it is only 1.4MB and very helpfull for newbies in
docking :) . Now I must try to port Lazarus code completion (missing global
vars / object methods hints in MSE IDE) and I'll be happy as never have
been :)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[Julio Jiménez]

2017-03-16 9:02 GMT+01:00 code dz :

> here you go : https://youtu.be/8W0uRA0qHTM
>
>
>
A picture is worth a thousand words.  ;)



-- 
Julio Jiménez Borreguero
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[Julio Jiménez]

2017-03-16 7:50 GMT+01:00 Martin Schreiber :

>
>
> It is easy! ;-)
>
>
Yes, it's easy once you know how it works ;) but I was talking about new
users. This docking system is not something common so new users expect
someting like Delphi, Lazarus, Netbeans...

I remember it took me some time to understand how it worked. It was years
ago.


-- 
Julio Jiménez Borreguero
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[code dz]

here you go : https://youtu.be/8W0uRA0qHTM

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] object inspector problem

[Martin Schreiber]

On Wednesday 15 March 2017 18:45:02 Krzysztof wrote:
> 2017-03-15 18:16 GMT+01:00 Julio Jiménez :
> > Would be interesting for new users, create a GIF (like in your example to
> > reproduce the issue) showing how to create it from the standard template.
>
> I agree. Tried few times some time ago make one window IDE (including form
> designer) but always failed. Always gave up when some dock panel overlap
> whole window and brake everything so I had to start from beginning :) . It
> would be nice to have buildin template which switch for one window IDE,
> something like View -> Layouts -> Docked IDE etc. Or at least gif how to
> make it

It is easy! ;-)

The principle is that dragged to container area windows are docked on the top 
level container. In order to dock to an embedded container drag to the grip 
of the container. In order to switch to tabbed layout drag the grip of a 
child to the center of the container, in order to change the split direction 
drag the grip of a child to the opposite container side.
If you start from scratch best is to first combine the embedded containers in 
floating mode.

I do not recommend to use the docking area of the main window for more than 
the debugger butttons. The "command central" should be small. I suggest to 
use different floating panels for different tasks, one for the debug windows 
(threads, stack, watches...), one for source editor and compiler messages and 
one for the forms, possibly with sub tabs for data modules and visible forms 
and possibly the object inspector.

Martin

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk