Hi,
I have a few questions about TP's use of Mootools in general, not for any specific theme. I'm using SMF 1.1.9 and TP v1.0 Beta 4.
As well as TP I am planning to implement a few other modifications that require mootools. So far one of them works with Blocs supplied Mootools, but not with Slimbox (http://www.digitalia.be/software/slimbox).
It's obvious in a way that I can't have three or more versions of mootools being loaded with every page. So the solution is to make one package that will be loaded by TP at the outset and by no other script at all.
Ok so that's the solution, but what I need to know is what build of mootools Bloc is using; is it a basic core version or is it custom built ?
So my last question is what modules would I need to include in my custom mootools build so that it is compatible with TP ?
Edit : One further question - the only downloads for mootools I can find are for version 1.2.3 and I noticed TP ships with v1.2 as well, so would that mean this version could be used instead of the v1.1 that TP is using?
Can't believe how many times I can fit the word 'mootools' into one post :uglystupid2:
I don't think anyone here knows exactly what components Bloc selected when he did the Mootools build that he uses for TP 1.0 beta 4, except, of course, Bloc himself. Even if he comes in here and tells you what components are in that build, that doesn't mean that he won't change the build for the next version of TP so that he can make use of other features of Mootools.
However, I will mention this on the Team Board so that Bloc will see it, and, if he chooses to do so, he will likely come to this topic and let you know what components he is using. This may take awhile depending on how soon Bloc can get in here to answer your question.
ZarPrime
BAh... sorry I'll edit since I didn't answer the proper question. Have you tried just exchanging the mootools file with the updated one to see if things still work?
Hi guys, thanks for the replies.
@ZarPrime,
Well as long as I can keep my version of Mootools up to date with whatever Bloc uses it should be fine. I don't anticipate my other modifications to change that much. What would be cool is just a sticky topic somewhere with the details of the Mootools build that is being used. This would help with compatibility issues with other modifications.
Thanks for bringing it to the attention of the Team Board :)
@IchBin,
You mean try the v1.2 Mootools that came packed with TP ? I will give that a go. I would try experimenting with different Mootools builds, but there are so many different options it makes it very difficult to make my own ones and test them or I would. That's why I thought I would just try asking first.
Until (if) Blog answers, I was wondering if either of you knew which elements of TP uses Mootools. Maybe from that I could work it out. The only thing I can think of is possibly the Shout box (scrolling) but I am not sure - I wouldn't be using that anyway. It's the only thing that I can think of with special effects.
Once again thanks for the replies :)
As far as i know it's only the shoutbox so far that uses the mootools script.
Should be simple to figure out if you open the mootools file and check what it calls for ???
ATM its only the shoutbox. Though I am probably will change this over the next betas, as its presents a problem when also themes call its own Mootools core+plugins. If the themes were FOR TP then its no problem, but most are for SMF primarily - which doesn't load Mootools to itself. I also haven't found a good way to make TP check(it can't as themes are loaded after TP) if other things load Mootools.
So then its down to the themes to check that - or make TP not rely on Mootools. I am leaning towards the latter.
Thanks Bloc. I am guessing you used the core mootools, then for the shoutbox scrolling you used the qscroller script to go with it ?
I think I can just build my own custom core mootools build with everything I want in it and then just use qscroller for the shoutbox if I use it.
The other javascript solution I was looking at was JQuery (http://jquery.com/) as I can do some of the things I want with that too. That might stop some compatibility issues maybe.
Anyway's it's all food for thought.