2.0 Update Part 3

[Thantos]

Yes

[pulkit]

Regarding the theme change ...

For those who just HAVE TO upgrade the moment 2.0 is officially out, there's no advise, but for those who can wait, here's what I plan to do ...

Check out SMF 2.0 as a brand new install and also update my test site ... Throw out the mods I don't need and check out if the rest have been updated to work with 2.0. Then, I experiment with 2.0 and learn the inside out of 2.0 functionality while waiting for the perfect theme and set of mods to come along. Once they are here, redesign the entire site in accordance with the theme of my choice ... The whole process should be complete 3 months from the launch of 2.0 (which also gives me time to do small crucial updates like 1.1.1 > 1.1.2 > 1.1.3 which seem to come in with a new version) ...
How does that sound ??

[karlbenson]

I think it will be fine for 90% of mods.  I think it will be themes that will take a bit more time.

Edit: I think it will be fine for 90% of mods by the time SMF2.0 is released as already the necessary alterations/updating have been made to a good few. I think it will be themes that will take a bit more time.

[Gary]

A Correction to what Karl said, VERY few mods from 1.1 will work on 2.0 due to the new database systems the db_query for example is not defined anymore but is now $smfFunc['db_query'], so the actual chances of a mod working is probably less than 5%.

And unless you upgrade with a theme installed, themes wont be compatible. Period.

-ALM

[karlbenson]

oops, edited with that I was trying to say.

I realise that the mods as they stand are unlikely to work.  But that more and more are already being made compatible.

Although they may need updating/tweaking slightly again depending on beta 2, beta 3

[Deaks]

A Correction to what Karl said, VERY few mods from 1.1 will work on 2.0 due to the new database systems the db_query for example is not defined anymore but is now $smfFunc['db_query'], so the actual chances of a mod working is probably less than 5%.

And unless you upgrade with a theme installed, themes wont be compatible. Period.

-ALM

It is possible to manually update a theme though.  I have tried on 2 of my themes

[Dannii]

Who would want to use a 1.1 theme when we'll have fabulous semantical 2.0 themes?

[trocobob]

When this version can be released .. can you estimate the duration of this charter members ?
i cant wait it

[Tristan Perry]

When it's ready - timetables aren't given

[SleePy]

When this version can be released .. can you estimate the duration of this charter members ?
i cant wait it

If you can't wait you can get the Charter Membership and get the first 2.0 beta right now

[melroy888]

wow i cant wait to get my hands on 2.0....hmm still wondering whats this charter member?

[Aaron]

http://www.simplemachines.org/charter/

[Eleglin]

Who would want to use a 1.1 theme when we'll have fabulous semantical 2.0 themes?

someone who has customized a theme, for a better integration with his site.

[Nolt]

Great. Can't wait for 2.0 beta. Im very excited :D

[heavyccasey]

A Correction to what Karl said, VERY few mods from 1.1 will work on 2.0 due to the new database systems the db_query for example is not defined anymore but is now $smfFunc['db_query'], so the actual chances of a mod working is probably less than 5%.

And unless you upgrade with a theme installed, themes wont be compatible. Period.

-ALM

Are all the functions contained in that array? o_o

[codenaught]

Are all the functions contained in that array? o_o

$smfFunc? Not all functions have a reference in that array. I think most of the database functions do, in order to support database abstraction for multiple database support. Also the functions that used to be called with $func in 1.1, are now called with $smfFunc instead. Apart from that, many other functions are just called the regular way they were called in 1.1.

[metallica48423]

$smfFunc currently handles just the database abstraction and maybe another small thing or two, i believe.

[heavyccasey]

I don't understand, what's the point of $smfFunc? Couldn't you just make regular functions?

[SleePy]

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.

[Dannii]

Dynamic functions can be very useful! Just as values (numbers and strings etc) can be either unchanging (constants) or dynamic (variables), functions can also be dynamic. Just as you can write code to use a variable with any value (as long as it's the right type), you could use any dynamic function without caring about the code inside the function, as long as it has the expected interface.