Re: [Gramps-users] Reports->WebPage enhancements

[Tom W. <to...@ad...>]

Just an idea - If you are concerned about a tree taking up too much space on 
your page maybe you could make it link to a popup window.  The window could 
popup to show the tree then if a link on it is clicked it would disappear and 
change the view of the main window.

Tom Weichmann

On Friday 05 March 2004 02:14 pm, Alex Roitman wrote:
> On 03/05/2004 12:37:43 PM, Leonid Mamtchenkov wrote:
> > I understand.  Sometimes though the tree with hyperlinks can simplify
> > the navigation.  (Going through index to specific people might be
> > difficult to names being non-unique.)
>
> Sure.
>
> > > So, the two questions to you are:
> > > 1. Would you be happy with scrolling?
> >
> > Yes.  Scrolling is not a problem as long as I can get to the point in
> > the tree with just a couple of clicks.  Currently, it's not so easy.
> >
> > Additionally, maybe the whole tree thing needs to be reorganized into
> > a table-kind of structure to avoid fixed-length fonts?
>
> Yeah, it's possible. The history is that somebody contributed that code
> and it just worked. The author calles it "dirty hack", but to "clean it
> up" we need to look at that... If you want to do it, that's great!
>
> > > 2. Does the depth need to be adjustable?
> >
> > I prefer the adjustable depth.  Adjusting should happen report-wise
> > (all individual pages have the same maximum tree depth).  I even
> > managed to work this way a bit.
> >
> > I have added another text area on the dialog.  Then I pass the
> > specified value as the 'depth' parameter to the MiniTree class.  My
> > thinking is as follows:
> >
> > 1. With depth equal to D there is maximum of D**2 nodes at the depth
> > of D in the tree.  So, there is a need to define an array along the
> > lines of:
> >
> >     self.lines = [ "" for i in range(depth) ]
> > 	for i in range(len(depth)):
> > 		self.lines[i] = [ "" for j in range(i**2) ]
> >
> > Sorry for my Python. :)  This is more like a pseudocode.
> >
> > So, each element of self.lines will hold a list of nodes of
> > particular depth in the tree.
>
> No problem. A simpler way of doing the same would be
>     self.lines = [ [""] * 2**n for n in range(depth)]
>
> > 2. In order to construct a tree, there is a need for a recursive
> > function, that will propagate through nodes.
> >
> > 3. There is a relationship between the current depth and the position
> > of the node relative to the center of the tree (balanced tree with
> > maximum of 2 nodes parent/child), which is based described as
> > 2**current_depth/2.
> >
> > I think that I am pretty close to the patch, but Python is so strict
> > after Perl.  Even with "use warnings" and "use strict". :)
>
> Well, compared to C it's very relaxed :-)
>
> > Here is an illustration: http://www.leonid.maks.net/family/I0004.html  .
> > In the gallery, the diffience in size between first thumbnail and
> > second  thumbnail is huge.  But the difference in size of original
> > images is  not  that big.  I would really like some way of having
> > thumbnails be as  close  in size to each other, as possible.
>
> I see. You weren't taking about user interface gallery. Sorry, my
> mistake. The ones on the web page are rescaled in a strange manner.
> I'll look at that. You can click on the small gallery pictures to
> display full size photos, though.
>
> > As far as I can figure it out, picWidth from const.py is used to
> > generate thumbnails to images that are added to the database.  But
> > when a WebSite report is generated, new thumbnails are made for the
> > website, which are incorrect.
>
> That's right, I misunderstood your question :-)
>
> > Either code that generates web thumbnails should be fixed to use
> > proper sizes, or it should be fixed to use thumbnails
> > from the database.
>
> Sounds good. Eventually, the gallery pictures on the web page are added
> by add_photo() function in the src/docgen/HtmlDoc.py file. Right now it
> has following:
>         size = int(max(x,y) * float(150.0/2.54))
> which is strange, since x and y are the desired width in cm (hard-coded
> to 1.5 cm in src/plugins/WebPage.py). The plan is to have thumbnails
> with 1.5 cm maximum size. The above works only if you have 150 px/in
> resolution. I think we can add "size=1.5 cm" tag when adding photo.
>
> > I will look into the code more during the weekend, maybe I'll manage
> > to fix it at the end of the day.  Thanks for the pointer to picWidth. :)
>
> No problem, although it was absolutely useless as you weren't talking
> about UI galleries :-)
>
> Alex