|
|
|
|
Customers
GenoPro version: 2.5.4.1
Last Login: Friday, September 23, 2022
Posts: 39,
Visits: 1,789
|
I'd like to announce my project of new skin for report generator.
It is based on current one, but has lot of modifications and changes.
Primary goals:
-Remove all frames
-Make it more css dependent, so it will be more customizable for any user
-Speed up opening pages, by loading content on left sidebar by using AJAX
You can check now, how it looks on http://familytrees.genopro.com/Quayle/dev
Config.xml is slightly modified, but not Dictionary.xml, so all the translations will be valid for it.
Any comments are welcome. 
Edit:
Changed dev-site address.
Tags:
Edited: Thursday, October 7, 2010 by
Quayle
|
|
|
|
|
Customers
Last Login: Friday, June 15, 2018
Posts: 28,
Visits: 231
|
The current abstraction layer just copies GenoPro's structure. Would it be unreasonable to just say "Use GenoPro as the abstraction layer"? We can obviously create a report on anything GenoPro can import, including GEDCOM, so why write new code to provide this translation? I still don't see the value of having this abstraction layer in the Skin.
|
|
|
|
|
Customers
GenoPro version: 2.5.4.1
Last Login: Friday, September 23, 2022
Posts: 39,
Visits: 1,789
|
Hurray! Finally, I managed to upload files on git.
edanite (9/22/2010)
The current abstraction layer just copies GenoPro's structure. Would it be unreasonable to just say "Use GenoPro as the abstraction layer"? We can obviously create a report on anything GenoPro can import, including GEDCOM, so why write new code to provide this translation? I still don't see the value of having this abstraction layer in the Skin.
Ok. I agree: "Person" doesn't do anything new for now. But if you want it to do something new in it... You can. And that's the point. Of course it's possible to write function which gets as an argument "Individual" object, and do the same thing, as the method inside class. But for me, code is more readable when I write: person.do_something(), than: do_something(person). Additionally you can change default appearence of methods like: e.g.: name_nick(), to do additional grammar, or other things which couldn't be achieved in Dictionary, NameDictionary etc... Whatever you can imagine. My native language has so much grammar rules exceptions... No matter how I try, my report when reading looks poor. I want to make something that let me achieve grammar more... Customizable? 
If I'll have any other ideas with using it I'll tell you. But if you still do not like my solution, why don't you start your own project to let your own idea grow? More us, more skins, more everything, the better. (I don't now if it's a correct sentence, but I hope it's understandable.. :/ ) It's always healthy if there are more options/alternatives. Isn't it?
Edited: Saturday, September 25, 2010 by
Quayle
|