Posts: 2,171
Threads: 222
Joined: Apr 2022
Reputation:
103
I loved SDL. I tried pretty hard, but just couldn't get Rob to finish it as an official QBasic replacement release. Instead, Rob wanted to move forward to GL. It was Steve who did a nice job on finishing off the SDL project. He even made one stripped of all QB64 underscore commands. At the time, PowerBasic had achieved the same idea. They had a DOS version that was fairly close to QBasic. There more advanced PowerBasic for Windows was much less BASIC in feel, more Win API like. Before QB64 came along, I had a couple of programs converted to PowerBasic for DOS. They ran well, but I definitely preferred switching to QB64.
As far as all that corporate crap talked about goes, I agree. I'm sorry I didn't have a heads up when it was happening. I took time off from everything computer related the first of the year, but just the few messages I read made me shake my head in total disbelief. That guy wanted to be known as the CEO, really? I think he meant COE, as in it sure looks like he crapped on everybody. So now between dot net and Qb64.rip, we've lost about 14 years of history.
Pete
Posts: 301
Threads: 16
Joined: Apr 2022
Reputation:
51
(04-20-2022, 01:50 AM)Pete Wrote: As far as all that corporate crap talked about goes, I agree. I'm sorry I didn't have a heads up when it was happening. I took time off from everything computer related the first of the year, but just the few messages I read made me shake my head in total disbelief.
I'd take it as far back as the day "the QB64 team" made a twitter account. What happened just recently might be a blunder but it was no accident.
Posts: 2,171
Threads: 222
Joined: Apr 2022
Reputation:
103
(04-21-2022, 11:24 PM)vince Wrote: (04-20-2022, 01:50 AM)Pete Wrote: As far as all that corporate crap talked about goes, I agree. I'm sorry I didn't have a heads up when it was happening. I took time off from everything computer related the first of the year, but just the few messages I read made me shake my head in total disbelief.
I'd take it as far back as the day "the QB64 team" made a twitter account. What happened just recently might be a blunder but it was no accident.
I'll have to take your word for it. Twitter (in general), never joined, never will. Same goes with FaceBook. Both too politically biased for me.
Thanks,
Pete
Posts: 276
Threads: 14
Joined: Apr 2022
Reputation:
27
Well, like a bad penny, I keep turning up. 
I don't hang around Discord so I had no idea what had happened. My only clue was having a "bad feeling" about something going on when I saw Luke post his farewell message. I tried logging on over the last few days and got zip.
It wasn't until I did a search for "tapatalk qb64" that I got my first eye full of what had transpired and found out where to go. In retrospect, it doesn't come as such a big surprise.
Simply amazing...
DO: LOOP: DO: LOOP
sha_na_na_na_na_na_na_na_na_na:
Posts: 3,968
Threads: 177
Joined: Apr 2022
Reputation:
219
@OldMoses glad you found us! 
Posts: 597
Threads: 110
Joined: Apr 2022
Reputation:
34
04-23-2022, 04:59 PM
(This post was last modified: 04-24-2022, 03:00 PM by CharlieJV.)
(04-22-2022, 08:31 PM)OldMoses Wrote: Well, like a bad penny, I keep turning up.
I don't hang around Discord so I had no idea what had happened. My only clue was having a "bad feeling" about something going on when I saw Luke post his farewell message. I tried logging on over the last few days and got zip.
It wasn't until I did a search for "tapatalk qb64" that I got my first eye full of what had transpired and found out where to go. In retrospect, it doesn't come as such a big surprise.
Simply amazing...
Kind of a goofy way for me to say "hi, pleasure to meet you" and introduce myself, but what the heck ...
"like a bad penny, I keep turning up."
My old sponge works in mysterious ways. My insta-thought/image: a penny getting flung into a wish fountain, with the scream of an "aaaaahhhhh, not again, I'll be baaaaaaaack" before the splash.
Streaming services ain't got nothin' on the television o' my mind...
Posts: 135
Threads: 25
Joined: Apr 2022
Reputation:
39
Hi ! I’ve been so bitter for days that a well-used forum doesn’t work.
This new interface is a bit unusual, but I'm so glad I found you, everyone!
Posts: 2,696
Threads: 327
Joined: Apr 2022
Reputation:
217
(04-24-2022, 06:36 AM)MasterGy Wrote: Hi ! I’ve been so bitter for days that a well-used forum doesn’t work.
This new interface is a bit unusual, but I'm so glad I found you, everyone!
Welcome home. You've been missed, like many others.
Posts: 135
Threads: 25
Joined: Apr 2022
Reputation:
39
Thanks SMcNeill !
I read the history of QB64, it's amazing! I now have a better understanding of Galleon, Fellippe's work. In fact, everyone else who has been actively doing it for 10-15 years! It's a great initiative to bring basic to life. On the one hand, technical development! The other is to bring together and forge a handful of people from all over the world, because despite the great development environment, it is the collective knowledge, the community, that enriches the knowledge. I owe a lot to the community too! I am very angry when someone destroys such a castle, for how much time, how much people, and how much work there is in what built this "castle."
Well-known names, ideas, posts are missing! I hope everyone finds it back!
I trust that the community and the collective knowledge will not fall apart!
Posts: 60
Threads: 11
Joined: Apr 2022
Reputation:
7
04-24-2022, 02:36 PM
(This post was last modified: 04-24-2022, 04:16 PM by dano.)
Thanks for the update, I really appreciate knowing more on why. I have to say that I was genuinely worried quite a bit about the future of QB64.
QB64 is key to my business...let me explain:
In 1997 I was using a DOS based POS system in my company. While this POS was great for invoicing and inventory control, it lacked pretty much everything else. So I set out to create the missing items via a wrapper (of sorts) for the POS. One great thing about this POS that allowed me to do this was that upon finalizing a transaction, it gave me the ability to write that transaction data to a file and then run an external .EXE. Voila! This was my ticket to making any external accessories functional - I would read this data and then the .EXE written in QB45 would take over . I worked and worked to integrate email into the POS (keep in mind this was late 1990's). I also generated a LOT of automation for this POS that ran tasks like bank and credit statement reconciliation, statements, invoice copy regeneration (the POS did not store these for some reason), and a bunch of other stuff.
There was so much integration of QB45 programs into this POS that I could not run the company without it (at least not as efficiently). When the company that wrote the POS came out with a Windows version, I could not justify having to rewrite all the code...so I stayed with the DOS POS for many, many years. Eventually all good things must come to an end and so it did. I started reaching the limits of the DOS software and it's indexing capabilities. Giving huge credit to the programmers of that DOS POS, it warned me that the limits of the indices were approaching their limits and actually game me a maximum number of transactions left. With the help of tech support they got that reset for me which gave me a year or so, but they warned me that it will be back.
I discovered QB64 and my life changed. Seeing as the new POS Windows version was 64 bit, the existing QB45 code will not run (no more 16 bit in 64 bit Windows). I would move to the new Windows version of the POS and continue where I left off, so to speak, with adapting the current code base that had been written over the years...yay!!!
I purchased the upgrade to the Windows version of the POS and started the massive task of adapting and rewriting the code to work around the new POS. Keep in mind that with 16 bit code and QB45 you were very, VERY limited to the amount of memory that you could use. I was stuck to the amount of memory that the POS software took along with the requirements of the QB45 code because of the way that the software shelled to the command line to allow me to execute my code. There were features that I could not implement because I did not have enough memory space to do so (way less than 640K).
I come to the realization that the sky is the limit when it comes to memory requirements for me to implement additional features. And did I implement soooo much more. About a year and a half later we went live with the new Windows based POS along with the new QB64 code to supplement it. QB64 has given me the ability to do way more with my POS software, and do it in less time with more accuracy. An example: Clients email an order and I used to have to type these orders into the POS by hand, replicating all of the many comments required by the client. I set up an Excel spreadsheet to track my time and an average order took around 10 minutes to enter. I wrote an import routine in QB64 for automating that entry process and it takes less than 30 seconds...and since there is no human interaction to make errors - the order is input exactly as the client requested so if there is an error it is on the client's side.
I am just so happy to see that QB64 is still with us and has not gone away. Once the donation links are up again I will definitely contribute...
Thanks to ALL that make this project a reality for those of us that want to continue using basic...
Dano
|
