← All ideas
  • Published 26 Sep 2018

Addons Built in

It would be a good idea that some addons like F2, LoopTools, etc be internal tools ?

70%

Development Status: Open

Upvote 7 Downvote 3
salvador
26 Sep 2018

8 Comments

jason

It would be better to make a separate proposal for each add-on you think should be integrated into Blender's core behavior, why you think that, and whether you think it should be re-implemented in C or if the add-on should stay as Python and just be enabled by default.

1
salvador Author

@Jason van Gumster: It is not as such a proposal, that's why the sign?

The idea arises when testing the alpha, you can achieve several things in their current state, but in the modeling workflow you miss the F2 or a couple of tools in the LoopTools that looking at other programs, these are by default and in blender for being addons are not present as other basic modeling tools.

Of course, we also accept that it is an alpha and it is not advisable to use it for production

jason

@Salvador Garcia: Thing is, this site isn't for questions. It's for ideas and proposals.

salvador Author

@Jason van Gumster: blender artist? or post in general comunity?

jason

@Salvador Garcia: Yes, I think that blenderartists.org would be a good place for this kind of discussion.

MickHanks

I disagree, in fact, I would not include any add-ons. But in turn, there should be a better add-on repository because the existing ones are sad.

Dan_Blenderplayer

I just think most of the addons should be distributed with blender installer .msi or .zips, with a selection enabled by default and a kind of (SKIPABLE) setup routine to chose your settings, skin, and addons.

dpdpforlife

LoopTools for sure.