regularly updated executables? Re: [Bf-funboard] Blender 2.29 GUI development, bf-fun GUI discussions

[Luke Wenke]

> 2.29 is just an internal name to describe the currently
> (in-heavy-development) blender CVS version that will be released as 2.3.

Ok....

> Yes, the screenshots in the UI doc were half mockups, half working. There
> has been an incredible amount of work down over the last few weeks to make
> the proposals in the document a reality.

I guess discussions about that (people actually implementing things) would
be happening elsewhere...

> The UI changes are following the proposal. That's why the opportunity has
> been here to offer improved proposals if necessary. 2.3 is aimed for
release
> at the conference at the end of October. This is all mentioned on the
site.

It would be good if people could have access to the latest compiled CVS (for
Windows in particular)..... it would save lots of people downloading all the
sourcecode just to recompile it, and it would mean that non-hardcore
programmers would be able to try the GUI out for themselves to give better
comments. I mean there could be multimedia students who don't know C++ or
how to use CVS's, etc, and give up.

So if there were regular (e.g. daily) compiles for Windows, etc, then the
non-programmers could comment on the GUI better. And the programmers who are
compiling it just to check out GUI (and not add code) would save time since
only one executable for each OS would need to be made (per day). There could
be a kind of history too (e.g. a 7 day history) so people can download
previous versions if the current one has a major bug in it.
(Personally, I've done a Bachelor of I.T. degree but have only done basic C
[not big applications] - I mostly did Java - so it would be fairly difficult
for me to compile a Windows version but I guess I could work it - and
install VC++ and do lots of reading, etc, on the other hand, others who know
a lot about GUI's, etc, mightn't know about C/C++)

- Luke.