PureBasic Forums - English

Fred wrote:... There is more than 3000 topics, so we can't do it alone, may be some of you want to join us to do the refactoring ? ... What do you think ? Does it worth it ?

I think it is an admirable idea but ONLY if the work is done exclusively by volunteers and not Fred and Freak ...
I would much rather have their valuable time spent working on PB itself!

Thanks for your input. I will go on with the original idea, as some of you seems interested, and we will see what will happen .

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?

Fred wrote:"Updated for 5.20+"

Considering that most users would be using the latest versions of PureBasic anyway, it's undoubtedly a good idea to keep the forum examples relevant. Hope I could be of help too.

I just thought of another reason against it totally unrelated with the "worthiness" I mentioned in my first post.

If you give the permission to edit the original post, and if its contents are replaced by the new, updated code, one thing that can happen is the person upgrading the code can screw it.
With many trivial codes the problem is probably not existent, with more complex code it's certainly a possibility. A new data type replacing an old one, a voluntary side effect in the original code not happening anymore "by default", etc. It's easy to miss it.

That's why I think the original code should never be touched unless you wrote it (it's already possible to do so thanks to the edit function), and that's why posting the code updated with a link to it from the original thread as already possible it's the best thing.

I agree with luis.

It's better to see the original code and ask : "how to convert it to the current version ?"

p.s.: I can see a deamon now, that will write in every topic : "how to convert it to the current version ?"

Reworking section is a good idea.

2 problems I could see are:
* Lots of topics
* Many codes in a lonely topic

A sweeter method should consist in:
* Just add one or more new post in a topic including a key expression within this topic (ex: "2V520")
* Every week or every month, a bot is executed to search these key expression "2V520". For each expression found, a request is then executed to modify the title of the topic. Ex: Add "(5.20)" in the head of the title.

Original writers and updaters stay then visible.

sec wrote:it's great, i want join this project!

@ LuCiFeR[SD]

Nice Link satanicdreams.site90.com Comodo pulls it as a Known phishing/malware/virus site and blocks it

Zebuddi.

luis wrote:If you give the permission to edit the original post, and if its contents are replaced by the new, updated code, one thing that can happen is the person upgrading the code can screw it.
With many trivial codes the problem is probably not existent, with more complex code it's certainly a possibility. A new data type replacing an old one, a voluntary side effect in the original code not happening anymore "by default", etc. It's easy to miss it.

Yes, the risk is not unlikely, and this will certainly happen. Frankly speaking, I wouldn't like that my code is edited by someone who hasn't been personally authorised by me to do so.

luis wrote:That's why I think the original code should never be touched unless you wrote it (it's already possible to do so thanks to the edit function), and that's why posting the code updated with a link to it from the original thread as already possible it's the best thing.

Agreed. However, that might "blow up" the Tips & Tricks section. And say somebody writes an updated version of some old code of mine, and later I update the code myself by editing the original post. Then I'll have to add a note that the other update is not up-to-date anymore. That might cause some confusion.

So it'll be better just to create a new sub-forum for 5.20 compatible code, and let each contributer post updated versions of their own code to it, as already has been suggested.

Zebuddi123 wrote:

sec wrote:it's great, i want join this project!

@ LuCiFeR[SD]

Nice Link satanicdreams.site90.com Comodo pulls it as a Known phishing/malware/virus site and blocks it

Zebuddi.

good grief! let my get my comodo proof tinfoil hat out

google safebrowsing
VirusTotal

How is this proposal better than just posting a reply to the original tip/trick?
This way, the original and updated code are there for all to see.
The new LTS model demands that legacy versions of PB tips/tricks remain intact.
I am also against editing someone else's post.

The whole point is to find code easily, so it has to be on the first post, or it can be burried in the topic if someone post something else right after. We don't plan to do that at every release, it's mostly a one time shot and we will be OK for the next 10 years . Let's give it a try and will see how it goes along.

Fred wrote:Let's give it a try and will see how it goes along.

If a plan has too many obvious problems and there are better alternatives at the same time, then there is no point in trying that plan.

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)




This should be the best of both worlds.
The selected mods will move things to the 5.20 subforum after making sure it works.
The stuff that works on the latest versions of PureBasic is moved to Current.
While the majority of todays Tip's and tricks ends up in the Archive.


***************************************************


The alternative is to add a PHPBB plugin to provide a tagging feature.
That way when folks code or edit threads can select the tag.
And what should the tag be?
How about the version of PureBasic?
Each time a new release of PureBasic is out Fred or freak adds a new tag.

This should make things easier in the Bugs forum too as one could search/sort by the tags.

Little John wrote:There are two classical nonsense "arguments".

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

The other is:

BorisTheOld wrote: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.