Blender Is GPL
BartV writes with a low-key snippet from the new blender.org: ""Today, Sunday oct 13, 2002, we've launched the Blender sources as GNU GPL to the Internet. Blender has become Free Software forever!" This should be a case study for other companies with software no longer profitable as payware; read some of our previous postings about Blender to follow the story from idea to release.
I was reading through some of the previous articles b/c as we all know, the server is /.'ed.
I found a lot of complaints about the UI of the program (see one here)
Any of the hardcore Blender users planning on actually doing some development on the UI (and some features which other programs have, ie default lighting?)
I am really interested in doing some of my own editing soon and I would love to see an easy to use program that isn't referred to as " the vi of 3D modelling "
Just some thoughts until we can see the actual article.
While I was poking around on www.blender3d.com yesterday, I clicked through one of the Links/Sponsors and found some fairly cool things.
The site is http://www.quelsolaar.com/ with 2 projects based on blender (I think, but they might not be) at http://www.quelsolaar.com/loqairou/screens.html and http://www.quelsolaar.com/quelsolaar/screens.html (a 3rd project lacks screenshots, but is a new experimental interface for blender, it says)
Some really cool stuff, coming real soon.
fair.org counterpunch.com truthout.com indymedia.org salon.com
eff.org guerrilla.net debian.org gentoo.org
"Actually since this is such an anticipated release, I think the site was hammered before the article was finished submitting."
It was. I checked it this morning. Imagine, being slashdotted without assistance from slashdot.org ! The horrors! What [other] force in the universe is capable of such obliterative power?
fair.org counterpunch.com truthout.com indymedia.org salon.com
eff.org guerrilla.net debian.org gentoo.org
Bite your tongue! Those who would trade a little freedom for a program that works deserve neither freedom nor a program that works.
...is some open source drink recipies!
Heh, that's very funny. I remember I tried an iMac once. I can't do absolutely anything useful with it, and I've been using computers and Windows for years. I see lots of people talking about how intuitive is $GUI. That's a plain lie. Any GUI requires getting used to it. If a really intuitive one is ever made it will work by reading your mind.
"any GUI that needs people to "get used to it" is bad design"
Not if it lets people who KNOW HOW TO USE IT do what they need in a signifantly more efficient manner. As far as I care, all GUI's should be more difficult to use, people are too stupid as it is.
Just so you know, any GUI that needs people to "get used to it" is bad design and doesn't take into consideration human factors and usability.
Not really. It's only bad design if your goal is to make the program as easy to learn as possible. In the case of Blender, it means that it's a UI optimized so that those who know it can work as fast as possible. Those optimizations may be inconsistent with optimizations that allow somebody to learn it as fast as possible.
The ideal UI would do both. Given where Blender comes from, the "skilled user efficiency" optimizations were far more important. I suspect there will be a lot of resistance to decreasing the efficiency of the UI to skilled users in the name of improving it for newcomers. If the latter can be done without sacrificing the former, then that will be welcome.
-Rob
Then how do you explain the ui of every in house 3d tool in the industry?
They have been designed with only one goal in mind. Workflow speed.
Its better to design the ui of an app you use all day to be as fast as possible and then not to care about the learning curve.
This is becouse the time it takes you to learn the app is made up for in a matter of days when you actually use the app.
You cannot claim that people must understand the app when its about 3d software. This is becouse they are in themselfs very hard apps to use. So the people using them havto be very tech friendly. They should not have any problem learning the ui nomatter how hard it is.
The people that complain about the ui eather havent spent enough time learning it or quite simply doesnt have any buisness learning it in the first place.
If you are just using a 3d app to play with and create some cool graphics you might aswell use poser or bryce.
Blender is a tool designed for fast workflow, to be used in a team environment within a company.
Can you run complex real systems without any training? Could you drive a car intuitively? Play a saxophone intuitively?
Everything else in the world requires patience, practice and knowledge to operate. Why is it that people think extremely complex machines (computers) should/can be easy enough for any retard to use?
That being said I still hate the blender GUI. I tried in earnest for 3 or 4 hours to use it, didnt make any headway and said "Fuck this, im going back to rhino"
Religion is a gateway psychosis. -- Dave Foley
Huh? It's fast, it's efficient and it's easy on your fingers. How is that a bad thing? Just because you don't like it doesn't mean everyone has to agree.
"Steep learning curve" does not make the UI fast. It makes it slow.
It means the interface takes some time to learn. Of course, if you haven't learned it yet and have to check the docs everytime you want to do something it will be slow. If you use the program often enough that you don't forget everything between every usage, spending some time to learn the interface properly is a great investment.
If you only edit text files once or twice a week, MS notepad is all you need. If you spend hours every day editing text, you'll want something more powerful and won't mind spending some time to use it properly. Of course, it would be great if the interface was "intuitive" enough so you wouldn't need to learn it. But as we all know, the only intuitive interface is the nipple; after that it's all learned.
So, vi and Blender suck for the casual user but are perfect for anyone who uses them a lot.
Please alter my pants as fashion dictates.
w00t!
:-)
o ur ce-2.25b.tar.gz
Blessed are the sourcemakers.
ftp://dl.xs4all.nl/pub/mirror/blender/blender-s
fair.org counterpunch.com truthout.com indymedia.org salon.com
eff.org guerrilla.net debian.org gentoo.org
Comment removed based on user account deletion
Blender is an absolutely frosty 3D modeling/animation/rendering package.
Okay, that's about as much I can describe with words, and I'm not a poet so I can't describe it that way, either. It is slightly puzzling on the surface, but surprisingly amazing when you look at the renderings it spews out, and the time spent doing the picture.
I've been using Blender since 1.5 or something (can't remember) and it's become one of my Graphics Packages of Choice. (Linux may be slightly behind Windows on audio and video side, but on graphics side, The GIMP, ImageMagick and Blender clearly prove it isn't behind on that area. =)
It occurs to me, what with all the debate going on concerning the validity of open source as a business model, that we are missing the bigger lesson from the blender story.
While I know that those 100 k Euros probably did not really cover all the assets of NaN, all the same, it showed it is possible.
What would people say to programming teams picking up desired projects, and then 'holding them ransom' and waiting for some form of corporate sponsorship, perhaps?
Or just doing it the way blender did it, and accepting private donations? That way, the projects that people really deem worthy would be the ones that made it into the open source community. Survival of the most valuable?
Good idea? Bad idea? Comments?
Blearf. Blearf, I say.
I know it is always easier to just sit back and wait for others to do things. In this case make donations. I do not use Blender, I probably will not use it in the foreseeable future, but I might end up using free software that uses Blender. Anyways, thank you folks for the donations. Every one and all of them counted :-)
People who find the UI difficult to use remind me of people who can't read sheet music bitching about how hard it is to play the violin. Perhaps the reason you find blender difficult is you lack a foundation in 3d to base your knowledge upon.
The other camp that complains about the UI is the Lightwave and Max crowd who are comparing this relatively small program to a full featured suite.
Blender is a good tool. It is about to get better. I dig the fact that it will be part of Linux distros from now on.
I believe in Blender so much I gave my fifty and became a member. And yes, I'm very happy right now.
Your statement is true only if your primary concern is making the app easy for new users.
There is always a clear tradeoff between new users and experienced ones. Others have said below something along the lines of: "Just look at all the 3D apps out there now, each one of them focuses on the experienced user..." They are right. Once you understand the workflow, things are generally fast --which is the way all of these users want things to be anyway longer term.
Interestingly, the MCAD market (for Engineers, not entertaiment or styling) is making this mistake. All the major apps are converting their custom U.I. to one that works for new users. Each and every one of them loses their productivity as a result. Each of them are fighting with their user base. Blender will have the same problem.
One solution is to make *good* documentation with lots of use cases. The Blender folks have done a fair job of this.
The bottom line here is that complex tasks are complex. The software can only go so far to make performing the task easier. Any 3D app that has a very easy UI, also suffers from the inability to do the little complex things that make the app worth using anyway.
Why spend time building the perfect UI, when new feature creep from the fast evolving 3D market will slowly erode your interface anyway.
Personally, I feel the Blender UI is a little out there. It could be a little more standard, but that effort is probably not worth the time. Adding good things to Blender will likely motivate new users to make use of the package given its price and capability.
Blogging because I can...
What is so horrendous about ALT+LMB????
Because there are combinations that involve the middle one.
For example, if you have a middle button (MMB), then the command may be Shift+MMB. Translated through the translation you get:
Shift+Alt+LMB
Two meta-keys at the same time is BAD DESIGN, except for something rare, like rebooting (well, it should be rare in a decent OS).
Table-ized A.I.
As I understood it, the code can be used in two forms: 1) Use it under the terms of GPL, in which case if you distribute a modified version, code must be included, or 2) negotiate the license to distribute only the binaries with the Foundation, and pay them to fund the development (and I expect this payment is not that light!).
I fail to see how this "stifles a major part of the GPL". The Blender Foundation releases all of their code under this dual license - People donate them money to do their job and release code under these terms. This license does allow others to take this code and modify it, and choose to either pay up, or be a nice citizen and contribute the code.
And yes, this dual license thing was mentioned a couple of times in past. Loudly. Were you not listening?
Because it does rule. The open-source world doesn't really have had any good 3D modeler (and only a handful of even remotely tolerable renderers - no, PoV-Ray isn't open source, yet).
(And, people who say it's not intuitive and the interface sucks just don't get it. Trust me, it is a wonderful program to work with once you get hang of it. =)
(Okay, this paragraph is probably going out of hand, but within realms of argument...) What do you get if you buy something that's compatible with some obscure, undocumented Windows software? Uh, a server that is tailored to work together nicely with some proprietary API that was never meant to see the light of the day. This, as opposed to funding development of some standard server. Why pay for Exchange compatible calendar/mail server? Why not pay for development of vCalendar / SMTP server? Why not tell your boss that using a standard server would probably mean higher security and increased reliability? </offtopic>
Of course, the same argument could be said of Blender: it only took some open formats as input, processed a proprietary format, and spewed out a (somewhere) standardized file in one form or other. But it could also be argued that there are still not that good standards on this field (swapping a model file from one modeler to another is always a nice way to spend a weekend), and that Blender does support a few of currently known "open" formats (or at least provide some way of converting).
Was it "worth it"? I don't know the first thing about blender or very much about this buy-out. Was the source available prior to the buy-out so that it could be inspectad/evaluated?
:-P
If the code is anything like the UI, then "it is great after you get used to it in a few years."
Table-ized A.I.
Here's the timeline:
January 1 - Microsoft announces that they will open source Windows 3.1 and DOS 6.22 for the paltry sum of $50,000. Apparently, this is to make up for the money Bill Gates lost when he ran his wallet through the laundry.
February 12 - "The Freedows Project" (sounds like "Fritos") obtains the required $50,000 through generous donations by individuals and random muggings.
February 13 - Microsoft turns over the source code.
February 14 - The Freedows project sues Microsoft for violating the GPL by deliberately obscuring their code. Microsoft counters by explaining that, no, that's the code they really were using. They enter as evidence fifty pages of source code for IE 7.
March 22 - Freedows announces that they've overcome the first project hurdle: Separating out the integrated Solitare code from the rest of the OS.
March 25 - Freedows is forked, and a new project called XFreedows emerges.
March 27 - Freedows forks again after an SMP patch is rejected. The new project is called "Lindows."
March 28 - Lindows is sued by Lindows.
April 1 - Freedows announces that Freedows OS is now running on top of the Linux kernel. Nobody believes them.
April 2, 3, 4, and 5 - Freedows resends the press releases, publishes all sorts of screenshots and demos, bribes CmdrTaco to publish a, "No it wasn't an April Fools Joke" story. Freedows is slashdotted, detonating three servers and killing five. The project is set back a month.
May 15 - A seven day flame war erupts when someone on the Freedows mailing list suggests changing the UI to require "triple clicking" for some functions.
June 1 - XFreedows is integrated back into the Freedows main branch, adding native NVIDIA support, an OpenGL-based 3D GUI, 16-way SMP support, the XFAT file system (a relational database filesystem which supports file sizes up to 300 petabytes and transparent compression), full 32 bit, 64 bit, and 128 bit support, and DRM support that can be disabled with a couple of IFDEFs.
July 15 - IBM "donates" ten million dollars to the Freedows project in what can only be described as a corporate mugging.
August 5 - Solitare is re-integrated into the OS, improving performance 300-fold.
August 7 - Thanks to IBM's generous donation, Freedows can move its CVS server onto a ludicrously powerful server running the Freedows OS.
August 29th - 2:14 a.m. Freedows becomes self-aware.
You want the truthiness? You can't handle the truthiness!
Comment removed based on user account deletion
Actually, I've never seen a 3D modeling program that didn't expect a three-button mouse (I'm an engineer, not an artist BTW, although many 3D programs use the same engines). I don't think making some "shortcut" functions (zoom, rotate, pan, etc) work with the middle mouse button is bad design, it works very well for me; but even that were the case it's still an industry standard.
- Classical music alternates frequently between very long notes (sometimes held across eight or nine measures) and very quick notes (sixteenths very frequently, occasionally thirty-seconds or faster). Representing both of those notes in a human-readable form, without changing your scale every measure and thereby negating the whole point, would be very difficult. If you try to avoid that by defining the standard measure width by the most cramped measure, you're still in trouble because you'll end up with such long measures that you cannot easily guage the distance of your notes and therefore also negate the value of the system. In other words, you'll have to add other notations to your staff until you negate the benefit which you are proposing.
- Your solution works great for computer, but I want you to try to tell musicians who notate pieces (which would be any professional musician anywhere and any half-decent music student as well) that they should bring a ruler to practice to ensure their notes are the proper width. There is a major value to our current system, which is I can do it with an unsteady hand and a pencil on sheet music propped in front of me at 45 degrees. With your system I'd have to lay it flat, take out a ruler, figure out how wide the measures were, divide that width by the width of the note I wanted to draw, line that note up with the end of the previous note, and then draw the right length. I fail to see this catching on.
There are other problems with your system too--for example, what happened to rests?--but quite frankly I think the above two complaints are sufficient enough.