Re: [Gramps-devel] text reports, etc...

[Rob H. <rob...@gm...>]

Dear Benny and all:

I certainly expect the end user to be able to choose the stylesheet that
they want from within the list that NarrativeWeb/ WebCal has already.

I believe the idea behind using stylesheets as was the case in the WebCal
plugin, is to remove the style editor functionality!  We give people the
option of which stylesheet to use, but no editing is allowed.  We can do a
default stylesheet which is a very simple one that the plugin now outputs
now.  Which template should be used as a default one???

Sincerely Yours,
Rob G. Healey

On Mon, Apr 6, 2009 at 2:39 AM, Benny Malengier
<ben...@gm...>wrote:

>
>
> 2009/4/5 Rob Healey <rob...@gm...>
>
>> Greetings:
>>
>> As some of you may know already, but for those that do not!  There is a
>> huge change coming in a lot of the reports:
>>
>> Instead of using templates anymore, we are going after using just
>> stylesheets as WebCal and NarrativeWeb already do now!  Stylesheets are the
>> best way to control styling, fonts, and presentation!  Currently, in the
>> text reports, if your report has more than one page, and you want to change
>> the styling/ presentation?  You would need to personal edit all of the pages
>> or delete them amd run your report over again!
>>
>> With stylesheets, there is one maybe two stylesheets to make your edited
>> changes.  It is all in one place and easier to modify.
>>
>> One person so far thinks that there should be a one stylesheet for the
>> basic stuff and on more for styling and presentation away from the
>> stylesheets that we already have from Jason Simanek.
>>
>> I believe that can be done.  Which of the styling templates would you like
>> the style and font to be modelled after?  Anybody who wants to be included
>> here in a vote, which template style do you like the best in using the HTML
>> Options in the reports that this is allowed?
>>
>> Or I think is the biggest question of them all!  Since linux is all about
>> personal choice in a lot of things.  Do we give the actual user the right to
>> chose for themselves which stylesheet they want to use as in NarrativeWeb
>> and WebCal right now?  The existing sheets can be modified to include the
>> additional styling necessary for these reports~
>>
>> What do you think?
>>
>
> I would go for user selectable css.
>
> So if on a textreport the user selects Html, then the document options
> shows a combobox to select the css style as is possible for the narrative
> website.
> Note however that there is still a Style and a style editor present. For
> Html you need to map style settings to css, so do you still allow the user
> or more importantly the report writer to override it... It might be better
> to have defined css settings that do not allow the Style to be changed
> (apart from giving underline, bold, italic), and to have one setting 'Free
> style' that when chosen resembles most a pdf document, and allows the user
> to set a style with the style editor. When default style is chosen, the
> style of the report author is used.
>
> It might be interesting to add to BaseDoc the ability to write a header?
> Now headers are paragraph styles with bigger fonts and bold.
> Did not think much about this, html is not my expertise. I just mean that
> we can update basedoc to make things easier to achieve.
>
> Eg, I want to add word wrap around a picture to the cairo (pdf) backend,
> but as I don't know now when a new section/header begins in BaseDoc, this is
> not straithforward (picture should not be next to the content of another
> person).  So having the reports issue headers themself, and doing numbering
> in the basedoc, would not only benefit html output.
>
> Benny
>
>
>> Sincerely Yours,
>> Rob G. Healey
>>
>>
>>
>>
>> On Sat, Apr 4, 2009 at 2:28 PM, Duncan Lithgow <dun...@gm...>wrote:
>>
>>> 2009/4/5 Gerald Britton <ger...@gm...>:
>>> > I guess the bigger question would be should we use the same css file
>>> > for all purposes or perhaps break it out into a basic css and specific
>>> > for each type of report.  Not being a CSS expert, I'm not really sure
>>> > what the best practice is
>>>
>>> Typically the best practice would be to have one CSS file which
>>> controls layout (might be different for different reports) and one for
>>> visual styles like colors and fonts. That second style sheet should be
>>> the same for all html output.
>>>
>>> This is not as easy as all that though. For the website the
>>> stylesheet(s) are separate files, but for other single page reports I
>>> think we need to use inline style definitions. So that will need to be
>>> kept in mind when the html files are built.
>>>
>>> Duncan
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Gramps-devel mailing list
>>> Gra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Gramps-devel mailing list
>> Gra...@li...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>>
>