Page 4 of 5
Re: Reworking Tips and Tricks forum section
Posted: Mon Aug 19, 2013 10:20 pm
by skywalk
Yes, I think granting some users the ability to move or copy fixed and verified posts from Archived(pre-v5.2) into new v5.2+ Tips/Tricks would satisfy many problems.
Re: Reworking Tips and Tricks forum section
Posted: Mon Aug 19, 2013 10:32 pm
by falsam
skywalk wrote:Yes, I think granting some users the ability to move or copy fixed and verified posts from Archived(pre-v5.2) into new v5.2+ Tips/Tricks would satisfy many problems.
Fred is it possible you rename
Tricks 'n' Tips by
Tricks 'n' Tips [PB 5.20] to avoid confusion with
Tricks 'n' Tips (Archive) ?
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 6:18 am
by wilbert
What do we have to do with code that is already working in 5.20 ?
It seems as a waste of forum space to duplicate such a topic but leaving it in a forum section with the word (Archive) in it gives the impression the code is outdated.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 7:44 am
by BorisTheOld
wilbert wrote:What do we have to do with code that is already working in 5.20 ?
It seems as a waste of forum space to duplicate such a topic but leaving it in a forum section with the word (Archive) in it gives the impression the code is outdated.
And what happens in two or three years when there's a new and improved version of PB? Is another forum to be created and the archive forum and the 5.20 forum to be scanned for more stuff to "update"?
And then what happens when the next and the next and the next.....versions of PB are released?
In the fullness of time, more and more code will not be kept up to date. And because the latest T&T forum will not contain current examples of all previous code, it will still be necessary to scan the other T&T forums for code which may or may not work with the latest release of PB.
Things will be as they are now, except the code will be spread over more forums. That's why I believe this is a makework project which will not change the way things have always been in the T&T forum.
Thankfully, participation is optional.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 7:53 am
by Opcode
You could always format the forums the same way you plan on distributing the PureBasic package. Make Tips & Tricks sub forums for each LTS version starting with 5.20. So you still have the main section, but also sub sections dedicated to specific versions. It would probably save a lot of time moving and editing old posts. As you could leave all the current tips and tricks threads as they are. And let the non-LTS versions be posted in the same section. It's not the best idea, but would be a good way to jump ahead of the game at keeping current version specific guides in order. And you would only need a new sub forum each LTS release, which every 2 years or whatever isn't bad. Tho I personally don't see the need in updating old posts, they are still valuable pieces of information even if the code doesn't work on newer versions. Updating the posts is effectively destroying all the follow up posts full of ideas and methods to get around a specific problem. So even if the code itself isn't useful, the input fixes and follow up responses serve as learning material. I personally feel they should remain as is in the main Tips & Tricks section. And just keep 5.20 LTS and later versions organized. Tho that's just my opinion.
- Tips & Tricks
- 5.20 LTS
- 5.30 LTS
- 5.40 LTS
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 9:52 am
by Fred
The work is in progress (and doing well), we will merge the 2 forums backs once it's done. So don't duplicate your Tips in the 'new' forum, as it's not a new forum
.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 12:04 pm
by Fangbeast
Fred, I found some 20 (pages) of my tips and tricks posts that points to downloadable code from various servers that are gone and no source code locally due to a HDD crash in 2006.
Those sorts of posts need to be deleted from Tips and Tricks entirely as they don't do anything.
What do you think, do you want a list?
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 12:12 pm
by Fred
We will handle that.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 12:44 pm
by Fangbeast
Fred wrote:We will handle that.
Okay. It's a pity I lost so much. Looking back on some of my old posts, I have no idea how to recreate the code. Oh well.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 9:38 pm
by chris319
For clarity, to the Tricks 'n'Tips(Archive) section, please add a few words to the description line that say "Prior to v5.20", e.g.
Prior to v5.20. Share your advanced PureBasic knowledge/code with the community.
Re: Reworking Tips and Tricks forum section
Posted: Tue Aug 20, 2013 9:53 pm
by em_uk
I think it's a great idea. A good clean out and an easy way to gain more users.
Searching the forums usually leads to old code that doesn't work OOTB, and only a regular user can adapt it to work.
Re: Reworking Tips and Tricks forum section
Posted: Thu Aug 22, 2013 3:26 am
by Danilo
Would be much more useful to add sub-sections to Tips & Tricks for "Windows", "Mac OS X", "Linux", and "Cross-Platform / Platform independent".
Most of the Tips & Tricks use API calls. WinAPI tips for example, are useless if you are looking for Linux tips for example.
So splitting Tips & Tricks section into the 3 currently supported platforms, plus one sub-section for cross-platform / platform independent would be more helpful, in my opinion.
Other idea could be to add specific sections:
[ Windows ]
* Windows - Windows specific forum
* Bug Reports - Post bugreports for the Windows version here
* Tips & Tricks - Share your advanced API knowledge/code for Windows with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Windows
[ Linux ]
* Linux - Linux specific forum
* Bug Reports - Post bugreports for the Linux version here
* Tips & Tricks - Share your advanced API knowledge/code for Linux with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Linux
[ Mac OS ]
* Mac OS - Mac OS specific forum
* Bug Reports - Post bugreports for the Mac OS version here
* Tips & Tricks - Share your advanced API knowledge/code for Mac OS with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Mac OS
[ Platform Independent / Cross-Platform ]
* General - Platform Independent / Cross-Platform specific forum
* Bug Reports - Post Platform Independent / Cross-Platform bug-report here
* Tips & Tricks - Share your advanced cross-platform PureBasic knowledge/code with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for all platforms
3 bug report sections already exist, and we have Windows/Linux/Mac sections. Would just require small adjustments (move to new category),
plus add Tips & Tricks for every platform. I think this could be more future proof and makes it easier to use, instead throwing all Tips & Tricks
for all platforms into one section with thousands of mixed topics/codes.
Re: Reworking Tips and Tricks forum section
Posted: Thu Aug 22, 2013 4:17 am
by yrreti
Danilo, whether adopted or not. That is a very good idea.
Re: Reworking Tips and Tricks forum section
Posted: Thu Aug 22, 2013 11:54 am
by Olby
Danilo wrote:Would be much more useful to add sub-sections to Tips & Tricks for "Windows", "Mac OS X", "Linux", and "Cross-Platform / Platform independent".
Most of the Tips & Tricks use API calls. WinAPI tips for example, are useless if you are looking for Linux tips for example.
So splitting Tips & Tricks section into the 3 currently supported platforms, plus one sub-section for cross-platform / platform independent would be more helpful, in my opinion.
Other idea could be to add specific sections:
[ Windows ]
* Windows - Windows specific forum
* Bug Reports - Post bugreports for the Windows version here
* Tips & Tricks - Share your advanced API knowledge/code for Windows with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Windows
[ Linux ]
* Linux - Linux specific forum
* Bug Reports - Post bugreports for the Linux version here
* Tips & Tricks - Share your advanced API knowledge/code for Linux with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Linux
[ Mac OS ]
* Mac OS - Mac OS specific forum
* Bug Reports - Post bugreports for the Mac OS version here
* Tips & Tricks - Share your advanced API knowledge/code for Mac OS with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for Mac OS
[ Platform Independent / Cross-Platform ]
* General - Platform Independent / Cross-Platform specific forum
* Bug Reports - Post Platform Independent / Cross-Platform bug-report here
* Tips & Tricks - Share your advanced cross-platform PureBasic knowledge/code with the community.
* Applications - Feedback and Discussion - Applications, Games, Tools, User libs and useful stuff coded in PureBasic for all platforms
3 bug report sections already exist, and we have Windows/Linux/Mac sections. Would just require small adjustments (move to new category),
plus add Tips & Tricks for every platform. I think this could be more future proof and makes it easier to use, instead throwing all Tips & Tricks
for all platforms into one section with thousands of mixed topics/codes.
Sounds right! We should do this instead, clean and simple. +1
Re: Reworking Tips and Tricks forum section
Posted: Sun Aug 25, 2013 9:05 pm
by bamsagla
Hi everyone.
My opinion: I got so much help from code samples (not only on this forum) that I would of course help by transferring it to 5.20 LTS (as much as I can).
It's a clear point that (almost) everyone cannot recode everything. So the actual editor should be able to do some kind of "rejection".
Just my two cents.
Harry.