Actually no Roofoo. For instance, let’s look at video games for a second here. Now video games can’t obviously place all their models in each level, it isn’t practical and causes tons of slowdown. So there are loading screens that pull up certain files such as sound and models that the game requires to be playable, then leaves the rest in the disk. A disk is no more than a compact hard drive, so if there was a loading screen for blender, it could optimize itself as it went from mode to mode, which is probably contradictory to blender’s amazing ability to model quickly.
But the upside would be if one was working on a project that only requires one mode or if the person did not mind the constant load times, thus it could be more efficient with the faces.(come on blender I know you could render 12 million faces on my old windows machine!)or(yes! sculpting at 5 million faces and still as smooth as butter!) or even (HA! With graphic quality of my game with normal mapping, along with 2000 tris each object, and running at 120 fps it pwns even professional games!) "really unpractical in a sense,but still one could only dream.... :D"
~‘note most of this is pure speculation from a 14 year old, thus one must not get their hopes up or mad rage at any information misrepresented’
I’ve noticed that Blender 2.5 SVN starts slower than 2.49 on my system (a couple more seconds). As anyone else noticed the same thing?
Is it caused by the parsing of UI elements from the Python files?
Initially brecht and I planned to store all script data in 1 file and only load the classes as needed, but surprisingly loading every script isnt THAT slow.
Python compiles into bytecode and reuses this so after the first load its not too bad. I did some tests and on my 3-4 year old system it could load 500 or so of our interface scripts in under a second IIRC.
options are
cache class info and know which ones to load first.
write our own import function which does less file lookups then pythons
have scripts load in the background (can do some trick where buttons/ui scripts load first)
write a python to C converter that only needs to handle our simple UI scripts. (ok, this is just silly - but possible)
make users suffer and just accept slower loading times!
Basically if it becomes a problem we can work around it :), have no fear!
2.49 is so fast to start, (on my rig, it takes only 2 second before the whole interface is displayed), so, when Blender took 2 more seconds to display the interface in 2.5 I noticed it. That’s all.
A couple of seconds to start an application like Blender 2.5 is still an amazing performance!