<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div>Hi Julian,<br><br>All in all the design doc looks very solid, many annoying or problematic UI/workflow issues were addressed (like area split by merging, or UI grid system).<br><br>I wonder if you have discussed popup messages? As an add-on developer in certain cases I have a need to notify user with important information, and popup messages are a best fit for this task. But currently popup messages will disappear if user moves mouse cursor away or use “ALT TAB” to switch windows back to Blender which might lead to user unintentionally skipping important message.</div><div>I like current behavior for popups in case of user driven actions (like create new object etc.) where user calls popups by himself, but in case of error or report it would be nice to have dialog messages which won't go away until user clicks “OK” or “Yes/No” buttons.</div><div><br></div><div>Design doc only mentions “Notification logs (log of last displayed warnings, errors and hints)”, but without visual and behavior example I can't say if this is a good solution to this issue.</div><div><br><div dir="ltr">--<br>Mikhail Rachinskiy<br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Dec 20, 2016 at 11:58 PM, Julian Eisel <span dir="ltr"><<a href="mailto:eiseljulian@gmail.com" target="_blank">eiseljulian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
So the write-up of the 2.8 UI workshop is published now [1], but that<br>
doesn't mean we are done! We have just started! We now have to create<br>
and finalize designs based on the doc, decide on and write down<br>
guidelines, work on prototypes and organize ourselves. For sure we'll<br>
also get feedback on the doc from the community which should be<br>
discussed and considered.<br>
<br>
I suggest we make extensive use of tasks on <a href="http://developer.blender.org" rel="noreferrer" target="_blank">developer.blender.org</a>. We<br>
can use columns to categorize tasks on the UI Workboard [2]. Columns<br>
relating to 2.8 should be marked specifically (e.g. "Blender 2.8:<br>
Custom Manipulators"). It's also possible to use parent and sub-tasks<br>
which can be incredible useful for structuring.<br>
We should still stick to the practice of only creating and keeping<br>
tasks that are actually being worked on. Others should be archived<br>
[3].<br>
I'll go ahead now and do some task cleanup, and I'll update the workboard a bit.<br>
<br>
Everybody is invited to help out and be a part of the process. We can<br>
use every helping hand!<br>
<br>
[1] <a href="https://wiki.blender.org/index.php/Dev:2.8/UI/Workshop_Writeup" rel="noreferrer" target="_blank">https://wiki.blender.org/<wbr>index.php/Dev:2.8/UI/Workshop_<wbr>Writeup</a><br>
[2] <a href="https://developer.blender.org/project/board/12/" rel="noreferrer" target="_blank">https://developer.blender.org/<wbr>project/board/12/</a><br>
[3] <a href="https://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#Archived_Design_Tasks" rel="noreferrer" target="_blank">https://wiki.blender.org/<wbr>index.php/Dev:Source/<wbr>Development/Todo/<wbr>UserInterface#Archived_Design_<wbr>Tasks</a><br>
<br>
Cheers,<br>
- Julian -<br>
______________________________<wbr>_________________<br>
Bf-interface mailing list<br>
<a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-interface" rel="noreferrer" target="_blank">https://lists.blender.org/<wbr>mailman/listinfo/bf-interface</a><br>
</blockquote></div><br></div></div>