2.0 Update Part 3

[_simon_]

Thank you for the quick reply. Motoko-chan.

[H]

I split some posts out of this topic. Please see:

http://www.simplemachines.org/community/index.php?topic=203612.0

[heavyccasey]

Its actually a time saver and allows for better integration.

   When you load SMF it does work to figure out what type of database you are using and then sets that up with those variables. If we used actual functions, that work would need to be done every time you call that function. Which is a lot of overhead that is not needed.
   Just think of doing the same work over and over and over again. Here at simplemachines.org, to load the post page took 10 queries (keep in mind we use caching to reduce some of these queries). So that would mean that the function would need to 10 times figure out what type of database we are using, and setup the appropriate function for one use. And this is just would be for db_query. Lets not forget our db_fetch_assoc, db_free_result, etc that we use as well. So this could quickly rise in great numbers to how much unneeded work is done.
   The variable has the function name stored in it, Allowing SMF to do the work once when it starts up to figure this all out and then set them in the variables. Once it is done it can use the functions easily and correctly without having to redefine everything, saving lots of time and reducing the possibility of overhead for adding multiple database support.

   This simplifies things and makes it so less work is done, keeping our overhead down as much as possible for multiple database support.

   But lets not forget integration, This lets SMF bridge with other applications more easily and reducing the fact that a function may already be defined. I am seeing more web software that is implanting hooks to integrate do this to allow their software to work with others without having those dreaded function redeclared issues because of this. So as other software changes to use this they start picking common names that SMF already is using, so using $smfFunc makes it sure that only SMF will actually be using that or setting it up reducing this possibility, along with the functions setup with it.

Why use a variable when you could use regular functions?

if ($settings['use_mysql']) {
function db_query() {...}
} ...

[metallica48423]

didn't you read the post?

When you load SMF it does work to figure out what type of database you are using and then sets that up with those variables. If we used actual functions, that work would need to be done every time you call that function. Which is a lot of overhead that is not needed.
   Just think of doing the same work over and over and over again. Here at simplemachines.org, to load the post page took 10 queries (keep in mind we use caching to reduce some of these queries). So that would mean that the function would need to 10 times figure out what type of database we are using, and setup the appropriate function for one use. And this is just would be for db_query. Lets not forget our db_fetch_assoc, db_free_result, etc that we use as well. So this could quickly rise in great numbers to how much unneeded work is done

[distortedice]

Lol, this topic cracked me up  What an idiot! http://www.simplemachines.org/community/index.php?topic=203612.0

Anyhows, back to the point of my post! What I'd like to say is "when will SMF2.0 be available as RC?", but of course I know the answer that I'm likely to be given having read all the previous comments on here

I'm in the process of updating my website and plan to have it ready by February. One of the most important parts of my website is my SMF forum, however I'm wary of updating my 1.1.4 forum when I'll probably want to upgrade it shortly afterwards, so I'm looking for a few opinions from the experts ...

should I ...

• (a) hold off on development and hope that the first SMF2.0 RC is released before mid January?
• (b) take the plunge and launch with SMF2.0 Beta
• (c) not rely on SMF2.0 RC being out on time and stick to 1.1.4 until later?
• (d) use VBulletin instead?

I'm not currently a CM, but my (potentially) new co-admin is.

cheers,

PS: option (d) was a joke ... just in case some thinks I'm actually that silly

[Dannii]

I'd stick to 1.1.4 unless you have a big website and could do with the 2.0 enhancements (newsletters etc), in which case I'd use the CM Beta. The RC won't be for a long time.

[青山 素子]

Anyhows, back to the point of my post! What I'd like to say is "when will SMF2.0 be available as RC?", but of course I know the answer that I'm likely to be given having read all the previous comments on here

Probably not within the month. There will likely be at least two more betas and I don't think beta 2 will be out until at least December, but of course I'm just guessing. It could be December 2008, even.

I'm in the process of updating my website and plan to have it ready by February. One of the most important parts of my website is my SMF forum, however I'm wary of updating my 1.1.4 forum when I'll probably want to upgrade it shortly afterwards, so I'm looking for a few opinions from the experts ...

should I ...

• (a) hold off on development and hope that the first SMF2.0 RC is released before mid January?
• (b) take the plunge and launch with SMF2.0 Beta
• (c) not rely on SMF2.0 RC being out on time and stick to 1.1.4 until later?
• (d) use VBulletin instead?

Option d!

A lot will depend on how much development time you are allocating and actually need. We won't be dropping support for 1.1. when 2.0 comes out. If a security bug is discovered, it will be fixed until such time as it becomes too resource-intensive or an unfixable fault is found that would require a massive rewrite. At least, that is the unofficial policy right now. If you can do everything you want with the 1.1. series right now, then you have a good option if you want to launch it quicker.

Also, note that if you are going to use a pre-release of SMF, you need to keep in mind that you will want to upgrade to the final release when it comes out, and there won't be a nice package for that like there are for 1.1.3 to 1.1.4 and such.

[distortedice]

Thanks very much for the advice.

I'll be sticking with trusty old 1.1.4 then

[heavyccasey]

didn't you read the post?

When you load SMF it does work to figure out what type of database you are using and then sets that up with those variables. If we used actual functions, that work would need to be done every time you call that function. Which is a lot of overhead that is not needed.
   Just think of doing the same work over and over and over again. Here at simplemachines.org, to load the post page took 10 queries (keep in mind we use caching to reduce some of these queries). So that would mean that the function would need to 10 times figure out what type of database we are using, and setup the appropriate function for one use. And this is just would be for db_query. Lets not forget our db_fetch_assoc, db_free_result, etc that we use as well. So this could quickly rise in great numbers to how much unneeded work is done

I did

I understand now! I thought you were using create_function() *headdesk* xD

[iyeru42]

Charter Membership is really expensive. >>; Well, at least it's not as expensive as a vBull liscense that's for sure.

[Dragooon]

Charter Membership is really expensive. >>; Well, at least it's not as expensive as a vBull liscense that's for sure.

Its as a donation for SMF To run. You are not buying the software here, you are donating them and in-return they give you the access to a Beta.

And SMF 2.0 Is still in Beta 1, So I am sure they cannot handle to give a big splash and make it public. If you think Charter Membership is expensive, wait for the public release then.

[Code Wrangler]

Also, note that if you are going to use a pre-release of SMF, you need to keep in mind that you will want to upgrade to the final release when it comes out, and there won't be a nice package for that like there are for 1.1.3 to 1.1.4 and such.

Pardon me, but I'm unclear on this.  Does this mean that there won't be a package to auto-upgrade from a pre-release version of 2.0 to the first RC version, and any upgrade along those lines will have to be done manually?  Also, when an RC version does come out, will there be an upgrade package available at that time to upgrade from 1.1.4?

[青山 素子]

There will be an upgrade path as always, but there will be no package manager package to do any upgrades between betas, RCs, or RC to release. You'll need to do the download, upload, upgrade.php thing for all that. (The only reason we did a 2.0 beta 1.1 package was because of a security issue.)

Once 2.0 is released, there will be handy one-click upgrades for within that series.

[Code Wrangler]

Thank you for the clarification.  I understand completely now.   

Have a good weekend!

[iyeru42]

There will be an upgrade path as always, but there will be no package manager package to do any upgrades between betas, RCs, or RC to release. You'll need to do the download, upload, upgrade.php thing for all that. (The only reason we did a 2.0 beta 1.1 package was because of a security issue.)

Once 2.0 is released, there will be handy one-click upgrades for within that series.

Wait, you just said "within" that series. So, we can't upgrade from the 1.1.x series to 2.0 series from the Manager?

[Dragooon]

No You cannot. Because the changes are way to many.

[Deaks]

Wait, you just said "within" that series. So, we can't upgrade from the 1.1.x series to 2.0 series from the Manager?

Thats correct you will need to upload the files overwroting the old one then using the upgrade/update.php to upgrade

[metallica48423]

with 2.0, we're talking nearly total change to the system. 

So much like 1.0 => 1.1, there will be only large upgrade packages.

Sub-branch upgrades will still be handled by package manager (ie 2.0.0 > 2.0.1 > 2.0.2 > etc.)

[Ol' Wombat]

Take your time, buddy, better late than never!

[Leipe Po]

ok maybe its me, but if you upgrade from 1.1 to 2.0, and those themes are converted, why not build a function that can convert them and do the entire theme site??! otherwise it just seems a waste of time to provide that sort of functionality, whit php and CRON it would be a easy task to do...

but again, maybe its me...