Reworking Tips and Tricks forum section

[Little John]

There are two classical nonsense "arguments".

One is: "You have done this in the past, so keep doing it now."

The other is:

You haven't done this in the past, so why do it now?

And there's one way of making vacuous comments -- quoting out of context.

That "argument" is plain nonsense, with or without context.

[fsw]

It could work like that:

- We give you the right to edit the topic content
- There will be an hidden forum section to synchronize the work between contributing users
- After editing to have a 5.20 compliant code, put a small note at top in green: "Updated for 5.20+" or "Updated for 5.20+. Note: the built-in command xxxx() now provide this functionnality".

This doesn't have to be done immediately, you can work on one post every week or even less, the goal is to have an update section in about one year.

What do you think ? Does it worth it ?

Fred

I think it's a good idea.

However, there are some things to consider:
1) it only makes sense to work backwards as newer code can be easier to port than old code
2) not needed to port all tips as many are workarounds or their functionality is now implemented
3) crossfunctionality is key, mention if it's not

There are sure more things to consider.

Count me in to help

[J. Baker]

I don't mind updating any code that I have posted. Glad to see LTS!

[Kuron]

1. The licensing on posted code is unclear. Do people even have the right to modify the code and repost it?

2. Updating outdated code only breaks the code for other users using the existing code or older versions of PB, which many of us still do.

[TassyJim]

As a new user of PB, I regularly search through the Tips and Tricks section.
If the code is short, I can usually workout how to update it and the exercise helps me understand the language.

I do find that the conversations that follow a 'Tip' are very informative and often have alternative methods to explore.

For me, I would like a note added to the original post, pointing to a new post with the updated code.
The new code should also refer to the original post rather than updating the original.

Coming to PureBasic while a major update is happening has been exciting.

Jim

[Fangbeast]

For me, I would like a note added to the original post, pointing to a new post with the updated code. The new code should also refer to the original post rather than updating the original.
Jim

I prefer this method too. I went through all my old tips and tricks and pulled up something from 2006. Nothing worked of course, except on the compiler version it was written on and the two procedures used were totally replaceable by native PB gadgets!!

If I update that post 'in place', nobody running that version of the compiler or several revisions after (until the native PB gadgets were introduced to replace the functionality) would be able to use it or work it out.

And yes, I have heard of people running older versions of PB because they didn't need to update, didn't want to etc.

/me wanders off to see what can be done with all his old crap.

[Little John]

If I update that post 'in place', nobody running that version of the compiler or several revisions after (until the native PB gadgets were introduced to replace the functionality) would be able to use it or work it out.

Maybe you could use

Code: Select all

CompilerIf #PB_Compiler_Version < xxx
   <code for self-written gadgets>
CompilerEndIf

[lakomet]

My suggestion is this:

Turn Tip's and Tricks into just a forum, section/category.

Under that make sure there is at least 3 sub forums called something along the lines of:

* Tips & Tricks *

*** PureBasic 5.20 LTS *** (Tested/works on 5.20 LTS)

*** Current *** (The latest Development versions)

*** Archive *** (v5.11 and older)

+100500

[jack]

the few of my tip's & tricks posts can be discarded, except maybe the one on using Xnumbers.dll but it would not hurt my feelings if it's discarded as well.
btw that code still works with PB 5.20

[applePi]

the importance of Tips and Tricks are for its algorithms and strategies used. so the availability of the archived version of this forum are important

[netmaestro]

I would like to help!

[heartbone]

I was going to vote for a new Tips 'n' Tricks forum section, leaving the existing posts intact as they are,
but i see that it is too late.

How about renaming the new section Clever Code Solutions

[Guimauve]

As far as I know, all of the source code I have put in the Tricks'N'Tips forum work as is in PB 5.20.
In fact many of my code I have created in PB 4.20 still work as is in 5.20.

The only exceptions are codes using screen and sprites. Most of them don't work anymore and unfortunately I don't have time to rework them until many months. So if someone can upgrade them :

go for it man, got for it !!!

Best regards
Guimauve

[Mohawk70]

I would be interested in helping.
In addition to editing the first posting to include a notice regarding the updated status of the code, would the goal be to simply edit and replace the previously posted code in each thread or to make a new post with the updated code?

Some of the old code posted depends on using non-open sourced LIBs / DLLs that haven't been updated & features

changed in newer versions of PB ( for instance IIRC Memory /Packing Unpacking ). Is it too much to ask for the

old code to be left untouched and an updated version (appropriately tagged of course ) and linked to in the first post

be added to the thread ... especially since the older versions are still available for download ?

[falsam]

Creating Tricks 'n' Tips (Archive) and Tricks 'n' Tips is a good solution.