Mootools 1.2

[contao]

Mootools 1.2

[leofeyer]

We have to wait until the calendar script is being updated or we have to find a replacement.

--- Originally created on August 19th, 2008, at 02:19pm

[aschempp]

Hier ein Kalender-Script, welches Mootools 1.2 verwendet.

http://dev.base86.com/solo/43/vlacalendar_v2_compatible_with_mootools_12b2.html

Zur Zeit besteht in meinen Javascripts noch ein Problem mit dem neuen CheckboxWizard, dort funktioniert die Sortierung nur mittels Page-Reload. Ausserdem gibt es bei den Sortier-Pfeilen (in allen Wizards) minimale CSS-Probleme.

--- Originally created on August 19th, 2008, at 06:09pm

[leofeyer]

See http://www.contao.org/board/message/40703.html

--- Originally created on September 4th, 2008, at 08:38pm

I have added two updated versions of the calendar script which may help. Maybe andreas might run a test in his "updated" enviroment and choose one of the files which is working fine in typolight and mootools 1.2.

--- Originally created by Sven on September 10th, 2008, at 06:55pm

[fbender]

Just to mention it, Slimbox is now version 1.64 (bugfix release).

--- Originally created on September 29th, 2008, at 06:55pm

[leofeyer]

I am very sorry to have to delay this request. It seems that the mootools update should not be part of a maintenance release, because it is likely that a lot of extensions will not work properly with version 1.2 (including two major commercial modules I have created). And as I wrote in the book, maintenance releases should never break the installation.

In the meantime, you can use mootools 1.2 by changing the template file.

--- Originally created on October 24th, 2008, at 11:18pm

Maybe we can add both mootool versions and choose the version from backend per domain-tree as long as the basic extensions of typolight are up to date for mootools 1.2. I think this will help users users who wan't to use version 1.2 and the developers of the extensions can change or extend their scripts to work with version 1.2. Unless 1.2 is not officially included in typolight, the developers have no reason the support version 1.2.

maintenance releases should never breal the installation:
The option to choose the version will be a failsafe option and a solution to bring the development of typolight and its extensions forward. It allows the users to do a soft migration and unless tl-release 2.7 it can be marked as experimently.

--- Originally created by Sven on October 25th, 2008, at 12:42pm

[leofeyer]

That does not make sense at all, because once the core supports mootools 1.2, it will not run under 1.1 anymore. If you need mootools 1.2, you can modify the template file.

--- Originally created on October 25th, 2008, at 01:44pm

Found a Bug in the typolight.js

The lines 640ff

getMousePosition: function(event)
  {
    Backend.xMousePosition = event.client.x;
    Backend.yMousePosition = event.client.y;
  },

sould be changed to

getMousePosition: function(event)
  {
    Backend.xMousePosition = event.clientX;
    Backend.yMousePosition = event.clientY;
  },

See the Thread

--- Originally created by Psi on October 30th, 2008, at 04:13pm

[aschempp]

Please also include a mootools_src.js (uncompressed) version as it is available for other scripts. This simplifies debugging.

--- Originally created on March 17th, 2009, at 01:24pm

[leofeyer]

Which components of MooTools 1.2 More do you think we need?

--- Originally created on March 17th, 2009, at 05:26pm

[aschempp]

There are two sides of this. One one side, I would love to see all of them. It was like that in 1.1, and I always loved that all mootools modules are included and you don't have to include on your own. Imagine if two extensions load the same "more"-feature... that would probably break it.

On the other side is the "speed"-problem. The more you include, the bigger the file gets. It is questionable if the browser really caches it (like we want it to).

Would'nt it be good to place modules inside /plugins/mootools/ and let them be loaded together with the core script? This way we could prevent extensions from harming each other (someone might not respect that, but thats their problem), and not need to load everything if not needed.

Example: My autolink module uses the Tips class. I suppose this is the only extension who does. If you place the tips extension inside the folder and my module loads it if needed, that would solve the speed problem.

--- Originally created on March 17th, 2009, at 06:24pm

[leofeyer]

--- Originally completed on March 18th, 2009, at 02:06pm