User forums > Nightly builds
The 08 september 2006 build is out.
orefa:
--- Quote from: Alturin on September 08, 2006, 09:50:28 pm ---What would be like, superb, is a message underneath that "Latest official release", reading: "Latest nightly build"?
--- End quote ---
Yes, new wording would help! Technically savvy people are notoriously poor at communicating with the public at large, a normal hazard of the profession.
Along these lines I suggest not to use the term "build" when refering to the latest version. Just use "version". When I first read "nightly build" I wondered why developpers were reporting on their workouts. I have programmed for years but never used that term to refer to a version. Well, maybe that's just me. But also the term may not be clear to a number of visitors who just started programming in C++ and don't know what it refers to.
While we're on the subject, since RC2 turned out not to be a release candidate after all, why not take a small step back on nomenclature and a giant step forward in useability: publish a new Beta! Forget about the so-called RC2 from over a year ago. Release today's version as a new "Beta 20060908" for example. Then provide the same link to lead visitors to the nightly builds (as daily Beta versions). The world needs to know! :lol:
tiwag:
--- Quote from: killerbot on September 09, 2006, 12:36:25 am ---I can confirm this, probably you have some special characters in your file.
@Yiannis : in windows (Xp) : open up the Cb project and open the tinyxml sources --> tinystr.cpp will show some of those strange blocks
--- End quote ---
you can get around this when you do "Edit->File Encoding->ASCII" and confirm the reload dialog
then CB loads the file and shows correctly.
i had this issue since a long time, when i got source code files with swedish characters in it ...
with forced ascii encoding, some of them get probably mismatched, but it mostly doesn't harm
because they are all in comments (which i even can't read)
but you can save the file and work with it.
annoying is only, that you have to do this everytime when opening this file ...
maybe we could add a file encoding property to the *.layout file
when the user had choosen a specific encoding from the available encodings ?
brgds, tiwag
Kazade:
I don't know what changed last night, but now the save bug (where it crashes on CTRL+S) on linux is back! It was fixed in the previous build. :(
Poobah:
-File->New Project
-Pick any project
-Project->Properties
-Select "Targets" tab"
-Output filename reads "\test.exe" assuming that the project was called "test".
Shouldn't it default to ".\test.exe" in this case?
torikx:
--- Quote from: mandrav on September 08, 2006, 09:25:55 pm ---Many people seem to think so and I must say I 'm confused as to "why"...
Mind telling us why you thought the project had stalled?
--- End quote ---
If you dont mind me barging in, I'd like to comment as well:
I think the most prominent reason is the absence of a stable release for almost a year following something labeled as a Release Candidate.
It's my understanding that an RC is supposed to have no more features added, have no grave bugs to be fixed, have a life no longer than several months during which its developers focus solely on elimination of showstoppers and rough edges until final release.
It's also my understanding that a Nightly Build conveys a bleeding-edge, alpha state of software. I find the statement "pretty stable nightly builds" contradictory, it's like an oxymoron. If you think it's stable/usable, then take it out of that cage and release under a name that'll attract people (no other RCs, thank you).
Correct me if wrong, but it seems C::B is like trapped in a cycle of adding features, fixing bugs, adding more features, fixing more bugs... I think it's time to stop adding features, focus on bugs, drop features for now whose bugs need lots of effort to fix and prepare for a final release.
Please take no offense, just my 2c.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version