[Bf-taskforce25] Blender spring cleaning

Campbell Barton ideasman42 at gmail.com
Sat Jun 27 22:22:38 CEST 2009


There is a case for this however I dont think this relates to image
formats that can be dropped.

In cases where it is valid, Id still be careful where to allow access
to variables like this since it could make checking peoples reported
bugs more time consuming.
As well as generally complicating testing/checking other peoples files.

Having some way to know if the object/material/scene uses 'Advanced
Settings' would be useful.

On Fri, Jun 26, 2009 at 7:56 AM, Dalai Felinto<dfelinto at gmail.com> wrote:
>>2) if you wanted to save an amiga image format. you can't via the UI
>>(even though the code is there).
>
> On the other hand if we have it in the code, someone that really needs
> it can create his own gui to support it, doesn't it?
>
> Custom guis for advanced parameters can be very handy IMHO. I remember
> Erwin and Benoit saying that Bullet internally has a lot of parameters
> that could be set if we have a gui for them. So why not leave it to
> the users? Once we have the feature exposed, it's a matter of advanced
> users customize their Blender to have higher control.
>
> I'm also thinking about very specific features here. Those features
> harmless to the code but not for general use. (eg offline rendering
> dome or some nodes). It's not always good to keep things in branches
> (not for the developer at least). And if we have it implemented in the
> code we could distribute scripts exposing the gui for those features.
>
> * I'm not sure that applies for image types since I believe the types
> are embedded in the operator, but those are my 2 cents anyway.
>
> Cheers,
> Dalai
> 2009/6/25 Campbell Barton <ideasman42 at gmail.com>:
>> 1) nobody uses it, we can be 99.9% sure of this
>>
>> 2) if you wanted to save an amiga image format. you can't via the UI
>> (even though the code is there).
>>
>> 3) HamX on the other hand is available (in 2.4 anyway), really this is
>> a useless item in the list just adds that extra bit of confusion with
>> options.
>>
>> 4) it doesnt hurt anyone to remove the code.
>> Imbuf code is not the nicest to read/work with. removing unused cruft
>> makes updating or improving less work. also means theres a bit less
>> code to read when going over imbuf to update for new image formats for
>> eg - did this with jpeg2000.
>>
>> I was under the impression you only wanted to keep this temporarily
>> for convenience. but long term why NOT remove?
>>
>> On Sun, Jun 21, 2009 at 5:07 AM, Ton Roosendaal<ton at blender.org> wrote:
>>> Hi,
>>>
>>> All fine, with one amendment; leave the code for for Imbuf (amiga
>>> formats) just there. It works, it's harmless, and doesn't take
>>> maintenance really. If it becomes a burden we can drop it entirely.
>>>
>>> -Ton-
>>>
>>> ------------------------------------------------------------------------
>>> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
>>> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>>>
>>> On 8 Jun, 2009, at 19:39, bkurdali at freefactory.org wrote:
>>>
>>>> *2
>>>>> +1
>>>>>
>>>>> On Mon, Jun 8, 2009 at 2:05 AM, William Reynish<william at reynish.com>
>>>>> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> After a nice long thread about what features we should deprecate in
>>>>>> 2.5, I've compiled this list:
>>>>>>
>>>>>> http://www.reynish.com/files/blender25/springcleaning.html
>>>>>>
>>>>>> These are features we seem to agree makes no sense to port over to
>>>>>> Blender 2.5. Removing these things should make Blender cleaner, and
>>>>>> easier to maintain too.
>>>>>>
>>>>>> Comments?
>>>>>>
>>>>>> I can also bring this up next sunday at the meeting, where such
>>>>>> decisions can more officially be approved. Then we can actually flip
>>>>>> the switch.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> -William
>>>>>> _______________________________________________
>>>>>> Bf-taskforce25 mailing list
>>>>>> Bf-taskforce25 at blender.org
>>>>>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>>>>>
>>>>> _______________________________________________
>>>>> Bf-taskforce25 mailing list
>>>>> Bf-taskforce25 at blender.org
>>>>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Bf-taskforce25 mailing list
>>>> Bf-taskforce25 at blender.org
>>>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>>>
>>>
>>> _______________________________________________
>>> Bf-taskforce25 mailing list
>>> Bf-taskforce25 at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>>
>>
>>
>>
>> --
>> - Campbell
>> _______________________________________________
>> Bf-taskforce25 mailing list
>> Bf-taskforce25 at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>



-- 
- Campbell


More information about the Bf-taskforce25 mailing list