Gtk3

Robert Fewell 14ubobit at gmail.com
Sun Jul 9 12:32:40 EDT 2017


I have just issued a pull request for the changes that I made after Geert
had copied my branch and most of the changes he pointed out on his review.
The main ones being the missed alt key combination on some buttons, migrate
the dialog-import.glade to gtk3 again which stops a crash if you go to
preferences and a the some miss added style context classes.

I will try and look at the other points raised this week.

Bob

On 8 July 2017 at 19:54, Robert Fewell <14ubobit at gmail.com> wrote:

> I will have a think about this after I complete all the other required
> changes.
>
> Bob
>
> On 8 July 2017 at 17:46, Geert Janssens <geert.gnucash at kobaltwit.be>
> wrote:
>
>> On zaterdag 8 juli 2017 17:25:19 CEST Robert Fewell wrote:
>>
>> > The file name can be as you stated, I was thinking about the widget
>> style
>>
>> > contexts, maybe along the lines of GncDenseCal_font_size
>>
>> >
>>
>> > Bob
>>
>>
>>
>> Right. I actually have no idea what is common. The whole css thing is
>> pretty new to me. Did you find any examples in other applications ?
>>
>>
>>
>> I believe though there should be a combination of two things: a widget
>> type specifier (like gncdensecal) and style properties for that widget.
>>
>>
>>
>> So a widget of type gncdensecal can have a property called "font-size"
>> (note dashes are usually used in css rather than underscores).
>>
>>
>>
>> With that you could write css like:
>>
>> gncdensecal
>>
>> {
>>
>> font-size: 10pt;
>>
>> }
>>
>>
>>
>> If you want to alter a property of one particular Dense Calendar, you
>> could use the style context name you have set in your code, something like
>> this
>>
>> #DensCalX
>>
>> {
>>
>> font-size: 10pt;
>>
>> }
>>
>>
>>
>> That's only highlevel code, not fully verified :) More details
>> explanations and examples can be found here:
>>
>> https://developer.gnome.org/gtk3/unstable/chap-css-overview.html
>>
>>
>>
>> For default gtk widgets this is all available by default. And usually
>> we'd want to use the second form (altering css properties of one particular
>> widget instead of a complete widget class).
>>
>> For our custom widgets we'd have to define these widget types and style
>> properties ourselves.
>>
>>
>>
>> Geert
>>
>
>


More information about the gnucash-devel mailing list