From: Doug B. <dou...@gm...> - 2009-03-21 12:17:18
|
2009/3/20 ger...@gm... <ger...@gm...> > I've shared a document with you called "Html class": > http://docs.google.com/Doc?id=d6p7rnz_503hrg6jxhh&invite=137756891 > > It's not an attachment -- it's stored online at Google Docs. To open this > document, just click the link above. > --- > > Dear Gramps Developers, > > Please have a look at the document refered to herein, that describes work > that Rob Healey and myself have been up to during the last few weeks, and a > new module -- html.py -- that came out of it. We invite questions, > suggestions, critique and, above all, experimentation! Gerald and Rob, There are some nice ideas in there! As you have discovered, anyone that writes Python code for the web usually writes some kind of utility functions for doing this kind of thing. There are a couple of issues to think about going forward: 1) As there are so many ways of structuring HTML output, which one do we want to use as we go forward? 2) As Benny mentioned, we need to support HTML in the style of the rest of GRAMPS, so that other reports can be written for the web. I am especially interested in #1 because I see my focus this year on making a live GRAMPS web application: multi-user, add, edit, delete, ... the whole 9 yards. But, I don't want to limit the way we write this new web code to be in the style of the rest of GRAMPS. But, we also want to share code between these two parts: static HTML output (the kind that GRAMPS produces now) and dynamic HTML (the kind that will access the database interactively). Thinking out loud, here is a proposal: We should write an HTML docgen interface that is (or can be) separate from a full-blown HTML library. This would be the static side of a bridge between the dynamic and static. Then, we need to decide how we will write more sophisticated HTML-only code. There are some issues here that I'm not sure that your code deals with. For example, we might want "templates" (HTML code skeletons) or even better, to use CSS styles. Changing CSS styles should be able to be accomplished dynamically (ie, not by re-running Python code). There are quite a few Python libraries for producing HTML. Should we write our own from scratch (starting with yout html.py) or should we use an existing open source project? What are the pros and cons? I think it is now time for a gramps-web mailing list. There, we can discuss the longterm design of the HTML, how gramps-gtk will share code with it, how the static and dynamic HTML can be integrated, issues with javascript/CSS, libhtml, HTML docgen, etc. Once we have thought-out API, then we can bounce it off the rest of the GRAMPS developers to make sure that it creates a smooth, consistent experience for developers and users, and provides a path for future development. What do you think? -Doug > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |