<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.3">
</HEAD>
<BODY>
I don't know if it's the right time to throw these ideas but here they go.<BR>
<BR>
I've been thinking about the way I use Blender right now and the things that really interfere with my workflow or that I find inconsistent or simply what I wish for =).<BR>
<BR>
1 - I'd like to have Sequences and Composite independent of scenes. I understand that I can do it right now by building an empty scene just for the composite noodle, but I find it inconsistent and confusing.<BR>
<BR>
1a - I'd really like to be capable of using a noodle or sequence output as the input of an image Texture, a strip in a sequence or as the input for a composite, just like a render layer. It would be even greater if we could have more than one active camera in a scene and use the camera as an input texture for a monitor, for instance - I know that would require much more work, but since the interface is going to be rethought anyway...<BR>
<BR>
2 - When I change workspace, it changes the scene to the last scene that was edited in that workspace. I find that totally inconsistent and, in fact, has created some problems for me. I believe the change of workspace should be tied to the changing of the scene and not the other way around, so, when I change scene I get the workspace I was working in that scene.<BR>
<BR>
3 - I find the current method of selecting fonts for the text object to be suboptimal. It take a long time to change the font. The fact that the user needs to know the font filename doesn't help. We should have a font browser, with font names to choose from. That is in fact one of the point raised against blender at work: browsing the filesystem to find a font file just sucks - same for the way plugins are selected right now.<BR>
<BR>
Just suggestions that I think would improve usability a bit.<BR>
<BR>
Flávio.
</BODY>
</HTML>