QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Cobalt on July 26, 2020, 11:39:06 am

Title: Podcast topics? What would you guys want to hear about?
Post by: Cobalt on July 26, 2020, 11:39:06 am
Looking for suggestions on what our community would like to hear covered in the next few podcast?

Title: Re: Podcast topics? What would you guys want to hear about?
Post by: SMcNeill on July 26, 2020, 02:56:03 pm
I'd still love to hear about how to utilize _HARDWARE and _HARDWARE1.  http://www.qb64.org/wiki/DISPLAYORDER

How the heck do we make use of that second hardware layer??
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: johnno56 on July 26, 2020, 08:44:50 pm
As I cannot speak for, or on behalf of 'The Community', the suggestion I wish to place before you is totally selfish.

I lack two of the main abilities to create games (I enjoy games more than 'general' programs... lol). Imagination and creativity. Not totally but enough to cause a great deal of frustration.

For those of us (Ok. Me.) who have this 'creative block', perhaps a series on game design and or creation. Focusing on concept; storyboarding; tools; structure and efficiency.

Perhaps game creation is  too large a topic for one lesson? I think we (Ok. Me.) could benefit from a lesson on good program structure and efficiency.

Just a thought...
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: Dimster on July 27, 2020, 10:05:10 am
I would love to learn more on "Libraries" - What's out there? What steps to take to adapt them to my program? Do you need to be well versed in QB64 to understand them? Tricks and considerations on building my own libraries.

Title: Re: Podcast topics? What would you guys want to hear about?
Post by: FellippeHeitor on July 27, 2020, 10:20:11 am
I'd still love to hear about how to utilize _HARDWARE and _HARDWARE1.  http://www.qb64.org/wiki/DISPLAYORDER

How the heck do we make use of that second hardware layer??

We'll have to wait for @Galleon to guest star on the show for this one 😉.
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: FellippeHeitor on July 27, 2020, 10:20:47 am
@johnno56 @Dimster thank you for your suggestions, too.
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: johnno56 on July 27, 2020, 11:33:36 pm
Umm... I like Libraries too...
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: Pete on July 28, 2020, 12:16:42 am
SCREEN ZERO, because podcasting anything else is just a waste of my time. :D

Pete
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: Gets on July 28, 2020, 03:25:07 am
I'd still love to hear about how to utilize _HARDWARE and _HARDWARE1.  http://www.qb64.org/wiki/DISPLAYORDER

How the heck do we make use of that second hardware layer??

Most graphic/text commands have to be done on the software layer, so I think it's just there for when you need to sandwich those between hardware images
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: bplus on July 28, 2020, 12:32:30 pm
All these API things Spriggsy has been springing on us, maybe an interview with him?

Luke says they are of a kind, variations on a pattern, so what is that pattern?
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: SpriggsySpriggs on July 28, 2020, 12:48:20 pm
Luke says they are of a kind, variations on a pattern, so what is that pattern?
@bplus
The pattern is basically either URLmon or CURL and parsing the response. Usually either JSON or plain text. I might end up making a function that actually goes through and parses a JSON file properly by grabbing values based on key name rather than just using MID$ right in the function itself. I'll think about it.
Title: Re: Podcast topics? What would you guys want to hear about?
Post by: bplus on July 28, 2020, 02:02:02 pm
@bplus
The pattern is basically either URLmon or CURL and parsing the response. Usually either JSON or plain text. I might end up making a function that actually goes through and parses a JSON file properly by grabbing values based on key name rather than just using MID$ right in the function itself. I'll think about it.

Yeah see, you are writing about elements I am unfamiliar. It would be good to lay a foundation. Luke did nice job of that.