[Bf-interface] The UI side of the asset project

[Julian Eisel]

*I just read https://developer.blender.org/T46049, ... :P

On 10 September 2015 at 00:05, Julian Eisel <eiseljulian at gmail.com> wrote:
> Created https://developer.blender.org/T46059.
>
> (And no, I didn't talk much with Bastien about it, I just read which
> has lots of information ;) )
>
> On 9 September 2015 at 16:04, Jonathan Williamson <jonathan at cgcookie.com> wrote:
>> 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 design by committee
>> problems.
>>
>> 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 :)
>>
>> 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?
>>
>> Jonathan Williamson
>> http://cgcookie.com
>>
>> On Tue, Sep 8, 2015 at 2:44 PM, Julian Eisel <eiseljulian at gmail.com> wrote:
>>>
>>> Hey all,
>>>
>>> Bastien just published this -> https://developer.blender.org/T46049
>>> and I think we should already start some work on the UI side of this.
>>> This could prevent the project from being stuck because of pending UI
>>> questions, help Bastien with further work and I'm sure in the end,
>>> users will benefit from it.
>>>
>>> I propose we organize it like this:
>>> * Keep UI development a bit separate from technical development, but
>>> make sure to communicate well. This will allow Bastien to stay focused
>>> on technical stuff which is a big enough task on its own.
>>> * Create tasks on dev.blender.org for needed design discussions (tasks
>>> and sub-tasks).
>>> * Stay away from discussing details as long as possible. We should
>>> create a really rough base first, and step by step develop it further.
>>> We can't predict all the details of the interaction yet, so we need
>>> flexible approaches.
>>>
>>> Bastien already proposed basic workflows for asset interaction, we
>>> should review them and continue the work.
>>>
>>> Like written in the task, the fundamental asset interactions from
>>> within Blender are:
>>> * Browsing
>>> * Loading
>>> * Updating
>>> assets.
>>> I suggest we start by breaking these up into their possible sub-steps
>>> and define where the needed data for them will be displayed (roughly!
>>> Even more rough than this:
>>> http://wiki.blender.org/uploads/0/0b/Elubie_asset_browser_ui_v1.png).
>>> Again, some of this was already written down by Bastien in the task.
>>>
>>> Curious on what you guys think and as always I hope we can get something
>>> done.
>>>
>>> Thanks,
>>> - Julian -
>>> _______________________________________________
>>> Bf-interface mailing list
>>> Bf-interface at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-interface
>>
>>
>>
>> _______________________________________________
>> Bf-interface mailing list
>> Bf-interface at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-interface
>>