That’s okay. Anyhow the future way will be Web 2.0 when it’s really ready and with less bugs. So it will be uninteresting in a few years
Only issue with this is if people are looking up an issue and find an old post they might not understand its for web1.0 instead of 2.0 and then get more frustrated when the accepted solution doesn’t work. It seems that web2.0 is really a different target than web1.0
There’s not different targets for API1, API2, new framework etc because they aren’t different targets to compile for so having them as targets doesn’t make sense anyway.
We can have sub categories.
So have a Web category with Web 1.0 as sub category for older stuff.
And move all old Web postings there.
Nice idea it’s what I am asking for Christian
API 1.0 is still in the current version, optional. The New Framework is also optional, API 2.0 on Desktop is mostly optional. API 1.0 proyects can be opened and will run with the current Xojo version almost without modifications, so the 3 can be mixed.
That is not the case from web 1.0 to web 2.0 proyects nor with API 2.0 in Web 2.0. So, it is NOT the same logic.