From: <bm...@ca...> - 2007-09-28 12:42:59
|
Quoting Brian Matherly <br...@gr...>: > Benny, > >>>> However, my Home page is already a long text, and I want to extend >>>> that. A text >>>> field in the website would be highly inadequate for so much text. >>> >>> How about a text box? It could be larger with a vertical scroll bar. >> >> My main gripe is I need two footers, two home pages, ... as I want >> to generate >> different websites. Working with the report options, means I would loose my >> previous edit, so I need a text file anyway in this case. > > I think we are making some great progress here. Here is what I am > learning about the header/footer options for the Narrative web site: > > 1) Users do not want to be forced to edit CSS, HTML or arbitrarily > saved text files on their computer outside of Gramps in order to > customize the site. > > 2) Users want to be able to configure customizations once and recall > those customizations in the future to generate the same report. > > Storing those report customizations as notes and saving them in the > Gramps database is one possible solution for these requirements. > Allow me to propose another. I propose that we make a narrative > webpage customization editor. It would work very similarly to the > Book Report Editor or the Styles editor. That is, the interface would > allow the user to customize each field separately, then, the user can > save those customizations with a unique name. Whenever the user wants > to generate a web report, they can choose one of their previous > customizations, or create a new one. The customization would be saved > in a settings file external to the database - but the user doesn't > care because it is always just "inside" gramps when they use it. > > I think this proposal might even be better than using notes. Here's > why: If we use notes, then in order for your to generate a web report > for your mother's side, and then your father's side, you have to > manually reselect the notes for the header, footer, intro, and home > separately. Using my scheme, you would simply generate a report and > select the "Mother" web customizations. Then you would generate > another report and select the "Father" web customizations. There s > only one selection to be made instead of 4 or 5. > > This is only a suggestion, but I'm starting to fall in love with it. > > What do you think? I like it. Some other complicated reports could use the same scheme. About the footer, home page, note that we could reuse (part of) the note editor for that (spell checking), but not save it in grdb, and store it as gramps xml. Just an idea. Let me suggest the following: 1/I remove internal note on media editor 2/i now just replace the code that uses internal note by the note selector (which is in svn). Should be only a couple of hours work. 3/we aim at a general solution with customizations as you suggest. If that is with notes in the gramps genealogy db, or with text in some other xml is not the point now. For 1/ and 2/ we have a programmer, me. For 3, somebody must think of a framework, a design, and an implementation. Would be nice to have 3/ in 3.0, but if it is 3.1, no problem. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |