![]() ![]() ![]() The resolution of images should be setted to ensure smart printings at least at 300 dpi printing resolution. Be aware of the need for styles for screen but also for printing. The existing styles shows very simple examples, and anybody aware of web-design and CSS could create new styles. All colors, images, background images, and even toolbox appearance could be styled. If somebody would like to contribute on Treeview styles : you should take a look at the file /treeview/css/treeview.css. And least, theme's designers could also totally change the appearance of the toolbox according to their theme's graphical rules. When the new Treeview module will be integrated, 2 icons will still lacks and require to be drawn for each theme : one for "no zoom", and one other for "compact/fixed boxes". For rev 8, I've re-used existing images according to their name, using for example "patriarch.gif" as the icon for the "centering on root person" button. At least, webtrees team should publish rules about themes, and avoid the biggests incoherences. There's a real and serious problem about the coherence between existing styles, and nobody could get a smart presentation from ugly and so differents buttons. And in some themes, some images are drawn with borders as buttons, and some other not. I've also worked on integration with existing styles (you'll see that in rev 8), particularly for the toolbox appearance, BUT that is generally ugly because of the current state of most of existing styles : for example, in the "colors" theme, ldarrow.gif and rdarrow.gif files aren't symetricals. I would be glad to receive the cooperation of designers upon this styles and new ones. The 3 styles embedded in "rev 7" are just some demos, and NOT definitive choices. And last, it's now possible to choose the appearance of the tree itself whatever theme you choose : that is mandatory to get corrct printings. My new module has a default style (which need improvements), and take in account the existing theme which overide the default look (but this will practically work only when existing styles will have fully integrated the new TreeView module). ![]() "Personally, I do not like the framing and background images, and would rather like to have it fit existing themes" : as a developper, I do not work a lot on design, but I work to offer to designers the best environment possible to express their talent. To fix this bug, just edit the /treeview/module.php file and replace the getTitle() function by these one : I've corrected that for me, but I'm not a committer, so I can't "commit" a bug fix at each problem, even if I work around that by frequent ne versions. This bug was introduced probably yesterday in webtrees with an extra treatment on the Module's name string. "there seem to be a bug in the heading (tab name)" : that's right. But I stay tuned to ear and take account of any ideas. I vote for putting the module in the "all partners" mode by default. Suppressing this feature ? It's possible because there's no more performances issues, but the possibility to have a simple or more complex representation of a tree remain an asset. But as it seems to be a bit confusing, that probably need something to be done. These feature were probably introduced both as a workaround for performances issues and as a way to sometimes clear up the drawing in the old module, and after brainstorming I have choosen to keep this feature. You can choose to display all spouses (and related children and parents), or only the last one and their descendants and ascendants. "for a person married twice, I only see the child from the first marriage" : it's not a bug, it's a feature ! -) In fact, that is exactly the same feature that exists in the old interactive tree. It was a need because the existing one does not work properly (buggy and far much too slow). Thank you for having took a look at this new TreeView Module. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |