This project is archived and is in readonly mode.

#338 ✓invalid

Unnecessary separation of 'core' and 'more'

Reported by mark | August 27th, 2008 @ 05:38 AM | in 2.0 (closed)

With the addition of the "builder" feature on the website, the separation of mootools into 'core' and 'more' is unnecessary, and probably even problematic.

Most importantly, there is no way (that I've seen) to reliably determine which 'core' components are necessary for particular 'more' components. As a result one must do trial and error adding bits to the core until the desired 'more' feature works.

While less critical, the separation into two files seems to confuse new users as well.

It's my recommendation that the builder page include all mootools components with the prerequisites coded in appropriately. This would allow you, for example, to simply click "Fx.Slide" and automatically retrieve only the minimal required core components.

In short - completely get rid of the core/more distinction.

  • mark

Comments and changes to this ticket

  • alcohol

    alcohol August 27th, 2008 @ 09:00 PM

    I personally agree.

    more seems more of a plugin/addon section, which in such a case, could also list user contributed classes/extensions if you ask me. Should you choose to keep this separation, perhaps it would be nice to allow users to contribute in some manner. Specific notes on which parts of the core are required would be a pre though.

  • Valerio

    Valerio October 5th, 2008 @ 08:55 PM

    • State changed from “new” to “invalid”
    • Tag changed from builder, minor, website to builder, website

    More can be seen as the official "plugins" section, stuff that isnt always needed in a basic build, but that could be situationally useful, hence "more". Every "more" component officially needs all of the core components.

    If you want to filter out some core components, i'm afraid you're gonna do it by hand. However, for the next release, we plan to make some modifications to the scripts.json file for more, which will include all the dependancies (unlike now).

    The builds however will remain separate.

    In the future (for 1.3) we are even considering to completely get rid of "more", and just move those components to the forge.

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket