<div dir="ltr">Good proposal Julian, I agree. Being a really big task we'll have to keep the discussion in control, so as to avoid too many <i>design by committee </i>problems.<div><br></div><div>Keeping the UI development mostly separate should help, but only to a certain extent. Let's just be sure not to hold up Bastien's progress with UI tasks :)</div><div><br></div><div>Julian, since it sounds like you've talked with Bastien a bit more than I have (not at all) on the asset project, could you handle creating the initial UI-related tasks and then we can go from there?</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Jonathan Williamson<div><a href="http://cgcookie.com" target="_blank">http://cgcookie.com</a></div></div></div></div>
<br><div class="gmail_quote">On Tue, Sep 8, 2015 at 2:44 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey all,<br>
<br>
Bastien just published this -> <a href="https://developer.blender.org/T46049" rel="noreferrer" target="_blank">https://developer.blender.org/T46049</a><br>
and I think we should already start some work on the UI side of this.<br>
This could prevent the project from being stuck because of pending UI<br>
questions, help Bastien with further work and I'm sure in the end,<br>
users will benefit from it.<br>
<br>
I propose we organize it like this:<br>
* Keep UI development a bit separate from technical development, but<br>
make sure to communicate well. This will allow Bastien to stay focused<br>
on technical stuff which is a big enough task on its own.<br>
* Create tasks on <a href="http://dev.blender.org" rel="noreferrer" target="_blank">dev.blender.org</a> for needed design discussions (tasks<br>
and sub-tasks).<br>
* Stay away from discussing details as long as possible. We should<br>
create a really rough base first, and step by step develop it further.<br>
We can't predict all the details of the interaction yet, so we need<br>
flexible approaches.<br>
<br>
Bastien already proposed basic workflows for asset interaction, we<br>
should review them and continue the work.<br>
<br>
Like written in the task, the fundamental asset interactions from<br>
within Blender are:<br>
* Browsing<br>
* Loading<br>
* Updating<br>
assets.<br>
I suggest we start by breaking these up into their possible sub-steps<br>
and define where the needed data for them will be displayed (roughly!<br>
Even more rough than this:<br>
<a href="http://wiki.blender.org/uploads/0/0b/Elubie_asset_browser_ui_v1.png" rel="noreferrer" target="_blank">http://wiki.blender.org/uploads/0/0b/Elubie_asset_browser_ui_v1.png</a>).<br>
Again, some of this was already written down by Bastien in the task.<br>
<br>
Curious on what you guys think and as always I hope we can get something done.<br>
<br>
Thanks,<br>
- Julian -<br>
_______________________________________________<br>
Bf-interface mailing list<br>
<a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-interface" rel="noreferrer" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
</blockquote></div><br></div>