Qbasicnews.com

22: "hi

is (insert name of basic unsuitable for game programming) suitable for Game programming and how good (if is he) is suport for opengl"

(insert emphatic "no!" here from programmers, followed with a "and probably never!")

SJ0: "Hi, I'm sort of an outsider who has been taking a look at the different open source basics. I've used FreeBASIC, found at http://www.freebasic.net/ to develop one game and I've ported two from other BASICs very quickly. It supports SDL and OpenGL, examples are included, and it runs under both windows and linux. There's also a pretty big community of indie game developers surrounding it. Considering that this seems to be an application basic, freebasic might be worth a look.

SJ Zero"

David Cuny: "Hrm... It could be a good language, but you wouldn't know it by the website. Hopefully they'll improve that a bit. icon_confused.gif"


I will admit since I was running around checking out the other open source basicis, and he's right, they all have very nice websites.

Of course, as languages, open source basics are almost universally horrible, almost of them being completely hard coded for the favourite lib of the author.

But don't let that stop you.

No, he is right, the site sucks, no contents, no good.

Jofers redesigned it, but i've a lot of crap to do right now on the compiler itself, so, so..

These people usually want to see a bunch of screenies, lets make it like the blitz3d site, loads of useless screen shots that at 64x64 resolution make any game look great.

It's no worse than kernel.org.

Hey, if you're going to have screens, could you include one of Quest for a King and Space Phalanx?

v!ctor: FB site should concentrate in releases, FAQs and bugfixes ( the only pending thing is the documentation).

Screenies and sources could be good for a "FB users site".. AAP's FB page has a lot of screenies

I guess, v1ctor should keep improving and debugging the compiler.

I'm suggesting something like database or wiki thread posting at documentation page for keyword syntaxes, usage and descriptions. registered member allow to add new and edit existing keyword description and examples. No duplication keyword names allows.

You could set-up different database for each category like fb native keywords, graphics (tinyptc, qbxl, sdl, ...) and directive. Probably mySQL would help to keep those database. And don't forget to back-up once a week or so.

This is the only way I think could helps open-source documentation completing it's requirements. A team-work efforts, if the community love this compiler.

alternative:

Add another forum category here just for articles and documentation. Then collect any new posted material from members to documentation project and compile them into a proper documentations.

If you want to do that set up another documenting project, though i am already 85% finished documenting all of the commands. I will be finished soon, and make it easy for anyone to edit and add commands / help topics.