Script Kiddy (bd361a02) at 28 Mar 02:39
GIT_SILENT Sync po/docbooks with svn
I think this kind of information is better suited for living in the components' own documentation; that way everything implementation-wise about them lives in one place and developers don't have to switch between the HIG and the component docs to get all the implementation info they need.
Marking the thread as resolved now, but feel free to re-open it if you have more to say though.
Ok, so this thread is just about whether to split it into multiple pages, right?
No response; assuming my explanation was sufficient and marking the thread as resolved now. Feel free to re-open it if you have more to say though.
No response; assuming my explanation was sufficient and marking the thread as resolved now. Feel free to re-open it if you have more to say though.
Done.
Nate Graham (8e3cef9a) at 27 Mar 21:14
If someone merged this commit, they didn't read stuff
Sounds good, I'll do that.
Assuming from the lack of response that what I've written does indeed roughly conform to that structure, so let's make this thread about whether or not the HIG should include icon design.
This one is done now.
Nate Graham (3aa6fbcd) at 27 Mar 21:01
If someone merged this commit, they didn't read stuff
... and 7 more commits
Ah, good source of information. I'll see about adhering to those guidelines for anything else relevant too.
Thiago Sueto (1ea0eea0) at 27 Mar 13:24
This MR:
This MR does not:
This MR:
This MR does not:
Jonah Brüchert (91c2e095) at 27 Mar 13:19
Carl Schwan (91c2e095) at 27 Mar 13:19
Kirigami: Shorten C++ model code a bit