- User Since
- Aug 22 2009, 11:37 AM (485 w, 5 d)
Tue, Dec 11
Mon, Dec 10
Hi Tuomo. First off, great work with the wiki baking. Thank you for your help with this!
Sun, Dec 9
Fri, Dec 7
Thu, Dec 6
You copy paste content from the existing wiki. Let's not derail this topic further, if you have any specific question feel free to reach out directly :)
Wed, Dec 5
Hi Aditia, I started documenting our MediaWiki setup. I don't think there is much development to be done at this moment, but if you were able to check out my setup instructions and provide feedback that would be nice.
Tue, Dec 4
Thanks for the suggestions! I addressed them and deployed them.
Thanks. I addressed all the suggestions, except for the logo. I already placed an updated version of the logo on the server, but it breaks with the default skin (too high res). I'll replace it as soon as we switch. The next steps for me are:
Mon, Dec 3
Here is a proposal for the new design of the wiki, which is already available on wiki.blender.org (not enabled by default).
Thu, Nov 29
Wed, Nov 28
Tue, Nov 27
Mon, Nov 26
Thu, Nov 22
@Brecht Van Lommel (brecht) the issue discussed today is still open here. Maybe you could have a look if Bastien is too busy?
Fri, Nov 16
Thu, Nov 15
Wed, Nov 14
Update done and buildbot restarted.
Nov 9 2018
Nov 8 2018
Nov 5 2018
Thank you Campbell, this is definitely an improvement.
Nov 4 2018
Hey there @Tobias Johansson (mutze) - I think you actually fixed this issue. Could you confirm?
Nov 2 2018
- Permanently allow execution of scripts
If it's annoying, then it's secure, right? :)
On a more serious note, you don't want to accidentally allow execution of any future script by clicking on the wrong button. In one mockup I though of adding a text that hints where to change the setting, but that would make the message too verbose.
I don't want to be repetitive, but there were two more topics in my initial post (typography and proportions).
Do you have time to look into this, or can it be placed on the task list?
Nov 1 2018
Fantastic. Thank you!
I'm on a non-hiDPI monitor here, and it still shows the issue. Do you agree with the other 2 points of the issue?
What is the protocol to handle this kind of feedback? Should the task be set as open again?
I would like to point out a couple of minor issues with the current implementation:
Oct 31 2018
This has been an open issue since auto-run prevention was introduced (thinking about the implications at the time would have been ideal). I think that a blocking warning is the best solution. This is a losing-work situation, like quitting Blender with an unsaved file.
Oct 25 2018
Thanks for deleting the pages Brecht. I took some actions on the offending account. Will investigate this further.
Oct 24 2018
Oct 21 2018
This is now partially implemented (when viewing a result, we can compare with the average).