[kde-guidelines] Conventions in the HIG

Thomas Pfeiffer colomar at autistici.org
Wed Jun 19 21:41:23 UTC 2013


On 19.06.2013 17:15, Aurélien Gâteau wrote:
> On Tuesday 11 June 2013 21:29:17 Thomas Pfeiffer wrote:
>> On Monday 10 June 2013 17:17:17 Aurélien Gâteau wrote:
>> > I have been thinking about this a bit more. Applications based on kdelibs
>> > 4.x and early kde frameworks 5.x, will be mostly widget based, but in the
>> > long term we probably want to migrate applications to QML. Since we don't
>> > want the HIG to become obsolete too fast :) I suggest picking "Control",
>> > which sounds more generic to me. Opinions?
>> 
>> +1 for future-proof HIGs
> 
> OK. I am back on this. Where should this terminology go? I see there is 
> a link
> on the HIG start page to a not-created-yet "Terminology" page [1], but 
> I
> assume it is terminology for KDE applications not for the HIG itself.
> 
> Maybe a Contributing_to_the_HIG page would make sense?

Yes, definitely!

>> > > > +1. A consistent look helps a lot here.
>> > > > Another reason for storing the ui files used for the screenshots in a
>> > > > central repository: If the default style used by KDE changes in the
>> > > > future, we can simply make the screenshots again with the new one to
>> > > > keep up to date. That would still be quite some work, but it should be
>> > > > doable
>> >
>> > [snip]
>> >
>> > I am happy to redo existing screenshots with Designer if we agree on this.
>> > Hopefully the git repository can then also serve as good starting points
>> > to
>> > create more screenshots. Shall I proceed?
>> 
>> +1 from me. I don't see any downside to this.
>> Sketchy wireframes are preferred if you want to make clear that you're 
>> at an
>> early design stage where things can still be changed easily, but this 
>> is
>> not the case here. We want our HIGs to look finished, not sketchy.
> 
> I started on this: I redid all images in Tabs_Pages and 
> Form_Label_Alignment.
> 
> I also put together a script to upload images to the wiki from the 
> command
> line.
> 
> Source for all of this is in the kdehig repository.

Great, thanks a lot!



More information about the kde-guidelines mailing list