Exactly

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On Mar 29, 2018, at 11:24 AM, Andrei Stebakov <lisper...@gmail.com> wrote:
> 
> Thanks, Alexandre
> Looks like RTResizeableViewContextInteraction has no effect for the tree that 
> goes beyond the page.
> On the other hand RTEmptyViewContextInteraction makes the tree that used to 
> be shrunk to fit in the page go beyond the page, as expected I guess.
> So the RTResizeableViewContextInteraction doesn't work as expected (since the 
> expectation is to fit in the page as I understand)
> 
> On Wed, Mar 28, 2018, 13:56 Alexandre Bergel <alexandre.ber...@me.com 
> <mailto:alexandre.ber...@me.com>> wrote:
>> I also stumbled upon RTHorizontalTreeLayout that works much better in terms 
>> of having more compact representation.
>> What I found out though is that when I inspect the view sometimes it 
>> displays all the ellipses with their specified sizes and sometimes it 
>> shrinks the view to fit in the viewable area. Can't put my finger on what 
>> triggers the view be rendered with normal sized (doesn't fit the page) vs 
>> zoomed out (fits the page)
> 
> Yes, you can have a look at Roassal2GT-Glamour-Roassal-Interaction
> 
> Here are some examples. The default behavior is obtained by:
> -=-=-=-=-=-=-=-=-=
> b := RTMondrian new.
> b nodes: (1 to: 100).
> b layout grid.
> b view @ RTResizeableViewContextInteraction.
> b
> -=-=-=-=-=-=-=-=-=
> 
> If you wish to not have any resize, then you can do:
> -=-=-=-=-=-=-=-=-=
> b := RTMondrian new.
> b nodes: (1 to: 100).
> b layout grid.
> b view @ RTEmptyViewContextInteraction.
> b
> -=-=-=-=-=-=-=-=-=
> 
> The code is not clean at all. This is due to the limitation of GTInspector. 
> Help is welcome on that front!
> 
> Alexandre
> 
>> 
>> On Tue, Mar 27, 2018, 23:21 Alexandre Bergel <alexandre.ber...@me.com 
>> <mailto:alexandre.ber...@me.com>> wrote:
>>> Alexandre, is there a way to display RTTreeLayout so that it would try to 
>>> fit elements in a more vertical fashion.
>>> Let's say even if the parent node has 8 children it would try to arrange 
>>> them not in one long horizontal line (which depending on the width of 
>>> elements can be really wide), 
>>> but spread them more vertically, so they would be viewable on one page.
>>> Or maybe I need to try another layout to reach that goal?
>> 
>> There is the horizontal tree layout that you may want to try.
>> 
>> -=-=-=-=-=-=-=-=
>> b := RTMondrian new.
>> b shape circle.
>> b nodes: Collection withAllSubclasses.
>> b edges connectFrom: #superclass.
>> b normalizer normalizeSize: #numberOfMethods; normalizeColor: 
>> #numberOfLinesOfCode.
>> b layout horizontalTree.
>> b
>> -=-=-=-=-=-=-=-=
>> 
>> 
>> 
>> Does it help?
>> 
>> Cheers,
>> Alexandre
>> 
>>> On Fri, Mar 23, 2018 at 8:15 PM, Alexandre Bergel <alexandre.ber...@me.com 
>>> <mailto:alexandre.ber...@me.com>> wrote:
>>> > Thanks, Alexandre, it works!
>>> > Also since I use RTView and RTEdgeBuilder I can use
>>> > view @ RTDraggableView to achieve the “draggability"
>>> 
>>> Yes! Glad to hear the problem is solved!
>>> 
>>> Alexandre
>>> 
>>> >
>>> > On Mar 22, 2018 14:01, "Alexandre Bergel" <alexandre.ber...@me.com 
>>> > <mailto:alexandre.ber...@me.com>> wrote:
>>> > I see.
>>> > Do you know you can drag and drop the background to scroll?
>>> >
>>> > You can also make the view zoomable, using the mouse wheel.
>>> >
>>> > Try this:
>>> > -=-=-=-=-=-=-=-=-=
>>> > b := RTMondrian new.
>>> > b nodes: (RTObject withAllSubclasses).
>>> > b edges connectFrom: #superclass.
>>> > b layout radial.
>>> > b build.
>>> >
>>> > b view @ RTZoomableView.
>>> > RTHTML5Exporter new
>>> >       directoryPathname: '/tmp';
>>> >       export: b view.
>>> >
>>> > b view
>>> > -=-=-=-=-=-=-=-=-=
>>> >
>>> > Alexandre
>>> > --
>>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> > Alexandre Bergel  http://www.bergel.eu <http://www.bergel.eu/>
>>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >
>>> >
>>> >
>>> >> On Mar 22, 2018, at 1:40 PM, Andrei Stebakov <lisper...@gmail.com 
>>> >> <mailto:lisper...@gmail.com>> wrote:
>>> >>
>>> >> Hi Alexandre
>>> >>
>>> >> I don't see how I can do without the scroll bars in HTML since the node 
>>> >> tree that I tender using RTTreeLayout has a big width and only 1/4 of it 
>>> >> fits in one page view.
>>> >> Since I am building a web service I rely on rendering and serving the 
>>> >> view in HTML and without the scroll bars there is no way for me to view 
>>> >> all elements of the model in Chrome.
>>> >>
>>> >> On Mar 22, 2018 11:50, "Alexandre Bergel" <alexandre.ber...@me.com 
>>> >> <mailto:alexandre.ber...@me.com>> wrote:
>>> >> Hi!
>>> >>
>>> >> Scroll bar are not exportable to HTML, as benefits in doing so are not 
>>> >> really apparent.
>>> >> What would be the ideal behavior? Will removing scrollbars when 
>>> >> exporting to HTML sufficient for your need?
>>> >>
>>> >> Cheers,
>>> >> Alexandre
>>> >> --
>>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> >> Alexandre Bergel  http://www.bergel.eu <http://www.bergel.eu/>
>>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >>
>>> >>
>>> >>
>>> >>> On Mar 22, 2018, at 11:20 AM, Andrei Stebakov <lisper...@gmail.com 
>>> >>> <mailto:lisper...@gmail.com>> wrote:
>>> >>>
>>> >>> When I do
>>> >>> v @ RTDoubleScrollBar.
>>> >>> and then export to HTML
>>> >>> the bars are rendered in the middle of HTML page and they don't 
>>> >>> actually scroll.
>>> >>> I checked in in Chrome and IE on windows. Could you guys take a look?
>>> >>
>>> >
>>> 
>>> 
>>> 
>> 
>> <Screenshot 2018-03-28 00.19.54.png>
> 

Reply via email to