Perhaps I missed a post or don't know where to look, but I have been looking around to see what the current 1.05 release has over the 1.00 release. I haven't bought Max yet, but have downloaded the 1.00 demo version. I am have thought about buying the current version, but without knowing what has been been addressed since the initial release, I am hesitant to do so. Does this info exist such that non-owners can see it?
Release notes for non Max owners?
BlitzMax Forums/BlitzMax Beginners Area/Release notes for non Max owners? Apparently not.
I suggest using the contact button and selecting Sales in the drop down.
I suggest using the contact button and selecting Sales in the drop down.
Here's a dump of the latest versions.txt, hopefully some info regarding the latest modules and additions will be available soon.
------------------------------- Core Version 1.05 : 07 Mar 2005 ------------------------------- ***** Changes to MacIDE ***** + Moved MacOS .app dir creation from IDE to BMK. + Added Build GUI App menu item. + Now saves locked build filename if reopen files at startup is selected. + Added character encoding to preferences. This is the 'save' encoding - load encoding is determined automatically. ***** Changes to BMK ***** + Fixed file leak in bbdoc. + C compiler now emits warnings. + Fixed BMK recognizing rem'd out Imports. + Fixed MacOS Tiger issue - should work OK on Tiger now. + Moved MacOS .app dir creation from IDE to BMK. + Added -t (app type) option, eg: "-t console", or "-t gui" ***** Changes to BCC ***** + Added utf8/utf16 source file support. Source files must start with correct byte 'markers' to be detected: $ef,$bb,$ff for UTF8; $fe,$ff for UTF16 big endian and $ff,$fe for UTF16 little endian. + Stricter import filetype checking: import source file type must be one of bmx,c,m,s,asm,cpp,cxx,o,a,lib and source file must exist. + RestoreData labels back in strict mode. Strict mode labels must now appear before a For/While/Repeat/DefData statement. ------------------------------- Core Version 1.04 : 14 Feb 2005 ------------------------------- ***** Changes to BCC ***** + Added labelled loops (strict mode only). Labels must be preceded by a '#' and must appear immediately before a For, While or Repeat loop. The label can then be used with Exit/Continue, eg: Strict #outer_loop For Local k=1 To 10 #inner_loop For Local j=1 To 10 Print "k="+k+", j="+j If k=5 And j=5 Exit outer_loop Next Next Exit/Continue without a label just exits/continues the nearest surrounding loop, as per usual. + Fixed non-const Global initializer code re-executing everytime global statement visited. + Fixed debug stm info hardcoded to build blitzmax dir ***** Changes to Mac IDE ***** + Fixed 'Replace All' confusing line numbering. ***** Changes to BMK ***** + Now uses bin/bbdoc instead of internal doccer. ---------------------------- Modules Update : 07 Feb 2005 ---------------------------- ***** Changes to BRL.System (1.03) ***** + Docs + Added GetChar() and WaitChar() ------------------------------- Core Version 1.03 : 01 Feb 2005 ------------------------------- ***** Changes to BMK ***** + Fixed bad doc links ***** Changes to BRL.Max2D (1.04) ***** + Fixed auto_midhandle causing crash if image didn't load ***** Changes to BRL.System (1.02) ***** + Fixed Win32 MoveMouse in Windowed mode ------------------------------- Core Version 1.02 : 27 Jan 2005 ------------------------------- ***** Changes to Mac IDE ***** + Added proxy options to syncmods requester. + Changed open/save string encoding to Latin1. ***** Changes to Windows/Linux IDE ***** + new debugger support + convert win32 clipboard to plain text before paste operations + specify openfile from commandline + hides main window till all files open + checks window bounds against desktop size + added deferred capitalizing cludge + fixed rem/endrem updating problem + fixed highlight/redraw noise + drag&drop file support added + dropdown menu in code and output windows added + run with commandline arguments + block indent/outdent + fixed drag&drop text crash + added escape handler to output window to replace auto hide ***** Changes to BMK ***** + Tweaked GCC args for better x86 FPU code generation. + Added http escaping for syncmods user and pass. + Added -y proxy_host:proxy_port option for proxies. + Added better checking for unsupported file types which were previously being silently ignored. ***** Changes To BCC ***** * 'Power of' now always used doubles. * Fixed uninitialized 'resolved' field of 'ClassType'. + Fixed const global byte/short initializer bug on little endian machines. + Changed 'Release' so it only takes an int variable parameter. + Fixed missing Long Min/Max. + Fixed debug info being generated for Type functions. + Changed default Extern Global munging from "bb_" prefix to none. + Fixed arithmetic type balancing so 2 float32 operands mean a float32 result as per spec. + Fixed unusued Long return vals hanging compiler. + Fixed arithmetic operators not checking for non-numeric type bug. ***** Changes to BRL.Blitz (1.02) ***** + Beefed up operator ^. + Fixed 64 bit Linux compile problem. ***** Changes to BRL.AppStub (1.01) ***** + Fixed functions in expressions confusing current statement in debugger. + Cleaned up appstub.win32.c a bit. Removed _control87 setup and FPE handling. ***** Changes to BRL.Math (1.01) ***** + Recompiled for faster math ops. ***** Changes to BRL.Stream (1.01) ***** + Moved '\' to '/' kludge from OpenStream to CStream which should fix '\' in Incbins failing and will have absolutely no other side effects whatsoever. ***** Changes to BRL.Pixmap (1.01) ***** + Fixed RBGA/BGRA docs having same description. + fixed 'bddoc:' doc error hiding PixmapWidth/PixmapHeight docs. ***** Changes to BRL.Random (1.01) ***** + Fixed Rand doc error. ***** Changes to BRL.System (1.01) ***** + Fixed 64 bit Linux compile problem. + Fixed / extended extensions$ handling in RequestFile ***** Changes to BRL.BlitzGL (1.02) ***** + Fixed 64 bit Linux compile problem. + Fixed Win32 windowed mode window size. This should fix a bunch of problems such as 'slightly off' MouseX/Mousey, GrabImage grabbing the title bar and probably more. + Fixed Win32 restore from fullscreen mode munting other window positions ***** Changes to BRL.Max2D (1.03) ***** + Added 'draw_last_pixel' to DrawLine (defaults to True). + Applied AutoMidHandle to images created with CreateImage. + Added ImagesCollide and ImagesCollide2 functions. ***** Changes to BRL.GLMax2D (1.02) ***** + Fixed Graphics() not resetting internal state, which was upsetting code with multiple Graphics/EndGraphics calls. ***** Changes to BRL.TGALoader (1.01) ***** + Fixed endian issues for MacOS users. ***** Changes to BRL.Audio (1.01) ***** + TSound and TChannel now used as default nullaudio device driver in the event of mute host ***** Changes to PUB.FreeAudio (1.01) ***** + Enlarged buffer for win32 mixer for SBLive users. + Increase fragment count from 2 to 3 for lowperformance Linux environments. + Fixed dynamic rate bug. ***** Changes to Pub.StdC (1.01) ***** + Rewrote Win32 system_ to use spawn() instead of system(). system() seems to have problems with multiple quoted args, which plays havoc with 'spaced' filenames. Note: spawn() requires an 'extended' app name, eg: 'myapp.exe' not just 'myapp'. May fudge this at a later date. ***** New modules Pub.Lua (1.11) and Pub.LuaScript (1.11) ***** + Thanks to Thomas Mayer for providing these modules. ------------------------------- Core Version 1.01 : 17 Dec 2004 ------------------------------- ***** General ***** + Fixed demo timeout problem when demo not installed by admin. ***** Changes to BMK ***** + Fixed spaces in BlitzMax path problem. ***** Changes to BCC ***** + Fixed unchecked negative array indices. + Fixed Null as string initializer crash bug. ***** Changes to MacIDE ***** + Added font panel. + Added a simple developer tools check (just looks for '/Developer' dir). + Fixed 'Hide NewApplication' menu item. + Fixed 'remblah' triggering rem block. ***** Changes to BRL.Blitz (1.01) ***** + Tweaked StringFindLast. ***** Changes to BRL.AudioSample (1.02) ***** + Added Try/Catch around sample loaders to catch stream exceptions. ***** Changes to BRL.WavLoader (1.01) ***** + Fixed 'data' chunk not found if it didn't come first. Added check for compressed samples (not yet supported). ***** Changes to BRL.BMPLoader (1.01) ****** + Fixed loader not skipping 256 color palette correctly bug. ***** Changes to BRL.BlitzGL (1.01) ***** + Added better check for fullscreen creation failure. Note: Mac's which only support soft GL can only do windowed mode. ***** Changes to BRL.Max2D (1.02) ***** + Fixed CollideImages ignoring endianness bug. ***** Changes to BRL.GLMax2D (1.01) ***** + Tweaked DrawOval for nicer results. ------------------------------- Core version 1.00 : 10 Dec 2004 ------------------------------- Initial Release!
IMO I feel as though all this hush-hush blitzmax crap is a bit annoying. Ooooo look, its the "secret hush-hush club", I wonder what they're up to.
As a dedicated blitz owner (Blitz3d, Blitzplus, etc) I feel as though I have been left out in the cold. I refuse to buy a product I can't test regardless of where my loyalties are. And thus far, all this silience has shown me that my hesitation to buy is probably the right thing to do. No demos, no exes, no videos, no nothing. Nothing to show that blitzmax is nothing more then an over-rated calc.exe. No insight to the language (other then a mac demo that I have no way of running unless I go out and spend a grand on a mac).
Oh good, core release 1.05 is out, whats soo cool about this, now if I visit the beta forum, oh wait, i cant... No wait, I can! All I have to do is spend 100 bucks and I can find out whats going on.. Will it do what I need it to? probably not, not at this point anyhow. But 100 bucks buys my way into finding out.. Sad...
It's a great marketing strategy though. It almost makes me want to stand out on the corner of my street with my hands cupped together. As poeple walk by, I will peek into my hands.. When they look over, and ask what is in my hands I will request $50 before allowing them to see.. After they hand me 50, I will issue them a membership card and let them have a peek. -Briliant!-
As a dedicated blitz owner (Blitz3d, Blitzplus, etc) I feel as though I have been left out in the cold. I refuse to buy a product I can't test regardless of where my loyalties are. And thus far, all this silience has shown me that my hesitation to buy is probably the right thing to do. No demos, no exes, no videos, no nothing. Nothing to show that blitzmax is nothing more then an over-rated calc.exe. No insight to the language (other then a mac demo that I have no way of running unless I go out and spend a grand on a mac).
Oh good, core release 1.05 is out, whats soo cool about this, now if I visit the beta forum, oh wait, i cant... No wait, I can! All I have to do is spend 100 bucks and I can find out whats going on.. Will it do what I need it to? probably not, not at this point anyhow. But 100 bucks buys my way into finding out.. Sad...
It's a great marketing strategy though. It almost makes me want to stand out on the corner of my street with my hands cupped together. As poeple walk by, I will peek into my hands.. When they look over, and ask what is in my hands I will request $50 before allowing them to see.. After they hand me 50, I will issue them a membership card and let them have a peek. -Briliant!-
The windows version still has issues, but they're not that severe at this point it seems. they're mostly related to the IDE. The language itself is pretty solid. After playing with it more and getting the hang of it i'm coming around.
So basicaly it comes down to this, 'Its still in beta'. As in not ready for release. But its close and its plenty usable now.
So basicaly it comes down to this, 'Its still in beta'. As in not ready for release. But its close and its plenty usable now.
I refuse to buy a product I can't test regardless of where my loyalties are.
Then wait until the product ships, and you can try out a demo. Nobody is asking you to buy it. No demos, no exes, no videos, no nothing.
You must mean apart from James' little shooter game. All I have to do is spend 100 bucks and I can find out whats going on.
Actually it's 80. But 100 bucks buys my way into finding out.
No it doesn't. 80 bucks buys you a license to all three versions of BlitzMAX. Currently only the Mac version is offered for sale, but Blitz Research decided that there was no point in not offering the Linux/Windows Beta to already paying customers so they could determine whether BlitzMAX really did deliver on that whole cross-platform development thing.I know a lot of Windows owners are pissed off that BRL decided to not primarily focus development on the Windows version, but it makes sense, when you're doing something innovative to developer for the better technology platform first, so you won't have to deal with (amoungst other things) that whole 1970's mindset that 4 CPU registers should be enough for everyone. The fact is that with the inferior technological platform on which Windows is executed, development simply takes longer. If you want to blame someone, blame Intel for not getting with the program, and blame Microsoft for being to reactive (as opposed to proactive, which we are fortunately seeing a shift towards).
Don't blame Blitz Research - it's out of their hands anyway.
Don't blame Blitz Research - it's out of their hands anyway.
Bull. It's a matter of priorities, and BR decided upon Mac. And 'better platform' is not appropriate here, it's the 'most used platform' whether you like it or not...
It was a good choice to release it for the Mac first...
Seeing how much bug-reporting (and complaining) there is allready with the win32 and linux betas, I can't even imagine how things would have been if they had released it on all platforms at once..
Seeing how much bug-reporting (and complaining) there is allready with the win32 and linux betas, I can't even imagine how things would have been if they had released it on all platforms at once..
I've only become involved with the Blitz products with the release of BlitzMax for OS X. Glad they did it that way because I just love it. It has put fun back into recreational programming again.
For my part I think they put out a great product for the Mac. Can it be improved? Certainly the language is and will continue to evolve. The actual IDE can be improved too but I have found it to be emminently useful. My biggest request in the OS X version would be a drop down procedure list in the source editor.
I am surprised they released a Mac version first. From what I can tell they have a history of Windows only products. What do the authors say about why they went with Mac first? Were they developing all version simulataneously and the Mac was done first?
For my part I think they put out a great product for the Mac. Can it be improved? Certainly the language is and will continue to evolve. The actual IDE can be improved too but I have found it to be emminently useful. My biggest request in the OS X version would be a drop down procedure list in the source editor.
I am surprised they released a Mac version first. From what I can tell they have a history of Windows only products. What do the authors say about why they went with Mac first? Were they developing all version simulataneously and the Mac was done first?
It's a matter of priorities, and BR decided upon Mac. And 'better platform' is not appropriate here
So what you're saying is that if platform "A" is more developer friendly than platform "B" then developing applications for both platforms takes a constant ammount of time? it's the 'most used platform' whether you like it or not.
I never argued that it wasn't. You'll notice however, that when developing software, the number of end users has no effect on development time.Developing software for the less developerfriendly, more convoluted API will take larger ammounts of time regardsless of whether it has a thousand users or a million users.
I am surprised they released a Mac version first.
It was finished first. I don't think that Mac is more dev friendly.
It just has less glitches and not 1% of the possible hardware configs which is for sure one of the main sources for bugs.
So for making the core stable, the OS with the lowest number of possible system configurations is the best choice ( would do the same for alpha tests of an app. On windows most bugs are due to users that don't keep their system up to date )
It just has less glitches and not 1% of the possible hardware configs which is for sure one of the main sources for bugs.
So for making the core stable, the OS with the lowest number of possible system configurations is the best choice ( would do the same for alpha tests of an app. On windows most bugs are due to users that don't keep their system up to date )
Simon,
Many thanks for the versions.txt listing. It was very helpful. If this file could be posted after version updates, I think it would help us non-owners see what had actually been addressed since release and should increase sales.
Now that I see what has been done since the 1.00 release, I have decided to start saving towards buying Max very soon.
Also, I wasn't intending to start another thread that prompted any kind of flame war, etc. I just wanted some info to help me on my future purchasing decisions.
Many thanks for the versions.txt listing. It was very helpful. If this file could be posted after version updates, I think it would help us non-owners see what had actually been addressed since release and should increase sales.
Now that I see what has been done since the 1.00 release, I have decided to start saving towards buying Max very soon.
Also, I wasn't intending to start another thread that prompted any kind of flame war, etc. I just wanted some info to help me on my future purchasing decisions.
I don't think that Mac is more dev friendly.
Well that would largely be a matter of personal preference, ofcourse.Some API's will be more appealing to people of a certain "school of thought", while others would be less so.
Don't blame Blitz Research - it's out of their hands anyway.
Of course I dont. I blame myself for being a stable enough of a pesonality to NOT buy something just to find out what it's about. Call it a weakness I guess.
So many users just baught Blitzmax because it was blitzmax, they even stated they didn't have a mac, they just wanted to have it... Oddly enough, the win32 beta came out.. Now everyone is showing screen shots for 3d work in blitzmax here and there... "I can't show you anything else until it comes out of beta, cant tell you anything about the language, no win32 demos or open beta tests to existing BLTIZ owners!"....
I am not trying to continue this flame war, I just feel betrayed as a blitz owner... I don't need to argue about how I feel.