- User Since
- Jan 18 2016, 1:03 AM (170 w, 3 d)
Sun, Apr 21
this is quite similar to the interface/common_shortcuts maybe it can be merged or at least moved into the folder.
Wed, Apr 17
Sat, Apr 13
Sat, Apr 6
Mon, Apr 1
versions should work now the json is read-in by the py ext. (same as the js, the tag is then passed to the template via context)
Mar 24 2019
Mar 23 2019
Mar 22 2019
Mar 11 2019
I stumbled upon the magic solution: the <base> tag it defines the base url for relative links,
which makes the extension obsolete,
all links work now,
version is still dev, the baseURL is read-only so it can't be changed by the inline script.
Mar 5 2019
Reverted, thx. Yeah, the style can be improved there.
Mar 3 2019
Feb 14 2019
So, I wrote the extension: a fragile patchwork of ways making the links absolute. Split between the template, the extension, the inline script.
The version is set to 'dev': that's bad for the old versions (solution: server redirect number to 'dev' , has to be updated every release, so no)
home links (/index) are not fixed, solutions: inline script loop over all 'A's; slow, thus bad for mobile
or maybe it can be done in the extension I'll try it *later.
Feb 11 2019
Still running smoothly :D
Feb 7 2019
Feb 1 2019
Jan 28 2019
Jan 17 2019
Jan 10 2019
Dec 12 2018
Please remove the "contents_quicky" file and be more careful when committing.
I could add a comment to almost ever single line (Why are you: altering the meaning, remove examples/explanations, the reshuffling, removal of rules..)
You're turning it into a cheat sheet.
Yes, it improves the wording. I'm sorry but your not experienced enough (yet) to rewrite the guide.
Dec 11 2018
Yeah sure, except for "incrementally make changes" it's doesn't works and likely ends up in a mess.
We already have the Data System section for scences, etc.
Moving Grease Pencil is part of 2.8.
Dec 10 2018
No, I don't have a reference for that; other than other programs of similar type/scale *cough GIMP ;).
The problem where to end: all upper for editors, modifiers, constraints, but not for other UI's (menus, panels, nodes).
With all upper we would end up with all words uppercase in some sentences.
Dec 9 2018
But a script needs instructions, it's the planning that's costs precious time.
It would take 1 person 2 month full time to plan, test, apply this.
2.8 1 person 2 years full time at current speed 5 years (very vague).
Dec 8 2018
Yes, the current structure is mix of UI based (editors) and the production pipeline ("workspaces") - it's best of two worlds.
To be honest I have to reject this directly and even a more in-depth discussion:
We are too few people to handle such major restructurizations.
2.8 is enough a 'challenge' (euphemistically) on it's own.
But 3 words "numeric input fields" are too long. Especially when it's a specific one like 'the X rotation numeric input field'.
Does just 'numeric field' works in the English? That would also be consistent with 'text/ search field'.
Dec 5 2018
As Campbell already wrote in a comment in the Markup Style Guide: there are too many rules (capitalization, hyphenation, to the spelling of individual words: Internet, mip-map)
We can turn this in a fleshed out style guide with headlines or
keep it simple with: look what's there and copy it. i.e. the UI section defines the capitalization.
Dec 4 2018
Sorry for the late reply my PC was broken.
The 'Arranging' headline is consisted for all pages in [Windows System], but that can be fix/changed later.
Nov 26 2018
This should not be part of the online instructions. I explained why.
This is not a personal preference, it's common opensource knowledge; see under 2.
Ruth Holloway - "A 5-step plan for making sure new contributors have a positive experience"
Finding new contributors is vital for the project.
Nov 25 2018
Nov 24 2018
Please, move/merge this to /release.rst,
the reason why this shouldn't be there is:
a) long instructions a prevent people considering to contribute, because it seams to difficult to set things up.
b) it's not needed that often.
Nov 23 2018
Nov 22 2018
Nov 16 2018
Oct 31 2018
That's the wrong repository, translations repo. is this: https://developer.blender.org/diffusion/BMT/
the svn repo. is: https://svn.blender.org/svnroot/bf-manual-translations/trunk/blender_docs
Oct 1 2018
Sep 1 2018
Aug 17 2018
the JS works as intended, it's the JSON:
the version is extracted from the second column, because the theme var is a number (and not 'latest').
so there can't be '2.79' two times - it will take the first match.
Aug 15 2018
Aug 10 2018
Aug 3 2018
Thanks for reporting (those are almost impossible to spot), fixed in https://developer.blender.org/rBM4392
Jul 29 2018
Jul 28 2018
Jul 21 2018
Jul 18 2018
Jul 13 2018
Jul 6 2018
Jul 4 2018
Jun 29 2018
Jun 28 2018
Jun 23 2018
Jun 14 2018
Jun 11 2018
Jun 7 2018
Jun 5 2018
May 11 2018
switch cmd arg parser (discontinued -ups) and add it to other files.
change tool function execution and arguments.
natural: repeated words: change filtering to be applied below threshold.
wordcount: add difference function.
May 10 2018
some additions from my list (not confirmed, outdated):
- Proxy/override system
- Asset manager
- Outliner refactor
- Gsoc projects: Custom normal edit, new UV tools?
- Fluid/smoke - Mantaflow?
Apr 28 2018
Apr 21 2018
research.py: split some tools to natural.py language (grammar, style) not markup
listsearch.py: add ignore case