[mwlib] Re: Suggestions... double Sided Printing... hyperlinkStyle...

[pg]

Hi Volker I summarize my suggestions: (1) have wider customization options (2) have customizables  values, format,... defined in property files - not in python code files. (3) have all important style(s) customizable (already true, but in a better way) (4) include the links in the list of customizable styles (The -> arrow is just one of many relevant options; other could be special fonts, special color and/or background highlighting) [for now, the TOC, the local user VARS and the double side printing are second level suggestions: I easily found turnaround for these ] Best regards, Philippe [ I'll check the pediapress offer when my writings will become les stupid... ] Volker Haas wrote: Hi Philippe, pg wrote: Hi Volker, *1* Regarding *the property issue*... Is there anything in the python language similar to the Property class available in java ? This is very simple to use (in java), and would do the job easily... Can you clarify that please. This thread/discussion has gotten rather long and confusing and I lost track what you are refering to. Is it related to the following point? Which is related to http://code.pediapress.com/wiki/ticket/400 . *2* Regarding the 3rd problem (the '*mediawiki vars*'). I had to introduce some code in magics.py (around line 225): # this file is part of /usr/lib/python2.5/site_packages/mwlib..../mwlib/rl/templ/magics.py # 8 lines inserted by PGE - see also LocalSettings.php @noarg def XMOD(self): return 'M3M' @noarg def XVER(self): return '0.9.1' @noarg def XDB(self): return 'Rescope' @noarg def XETAT(self): return 'Resom' # (240 lines after) I guess It would be possible - and better - to transfer this code in customconfig.py, isn't it ? And if it is possible, then it would also make sense to use some specific format in a property file. Hence my suggestion to have them called {{XMOD}}, {{XVER}},... in this same config file, as in the mediawiki edition This is related to the parser (mwlib) - therefore any configuration should probably be done there. I know that it is not exactly great to maintain multiple configurations - but currently I can't really offer a solution. As mentioned above your issue is described in http://code.pediapress.com/wiki/ticket/400 . Feel free to reopen this ticket and discuss details with the parser expert Ralf ;) *3* More suggestion. Since some people (like me) would like to take adavantage of *double sided printing*, it should be convenient to have additional vars defined in customconfig.py. For instance, I would like to write: oddLeftExtraMargin=0.8 * cm evenRightExtraMargin=0.8*cm And of course the PDF writing engine should use them... :-) I added a ticket for that. I am not sure if and how reportlab (the toolkit for generating PDFs) supports double side printing at all though. I'll check that later. http://code.pediapress.com/wiki/ticket/418 By the way: did you check out the books you can order at pediapress from your wiki. The PDFs are rendered with latex and they feature a double sided layout ;) *4* More suggestion. In pdfstyles.py and in customconfig.py, numerous writing styles are defined, but NOT a writing style for the internal references (mediawiki hyperlinks). I would like to customize that, because now they are not enough highlighted in the text. So I suggest to define one more style *hyperlinkStyle* in these files... :-) :-) How would you want to style the links? If you have any good suggestions please open a ticket at http://code.pediapress.com Best, Volker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to mwlib@googlegroups.com To unsubscribe from this group, send email to mwlib+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mwlib?hl=en -~----------~----~----~----~------~----~------~--~---