Updating of sheetnode and 2.x release

Hi All,

I (willhallonline) have recently joined as a co-maintainer for the module and thought that I should update you on a number of ideas/plans for the moving forward of Sheetnode as a module. There are a few issues with regards to formatting of the code that I am looking to execute over the next few weeks and such like which I have outlined below.

SocialCalc Library

https://github.com/infojunkie/socialcalc

• Write gulp script to build and compress into socialcalc.min.js and socialcalc.min.css
• Update so that SocialCalc is responsive
• Restructure files and directories to make them more understandable
• Use better image handling (or fonts) to load the images

7.x-1.x

• Reformatting code to fix and coding standard errors (where possible) - this will probably be done in a few separate commits. For example - https://www.drupal.org/node/2632612
• Moving of CSS/JS to separate directories - https://www.drupal.org/node/2631622
• Move includes to separate directory
• Replace require_once() with module_load_include() for includes - https://www.drupal.org/node/2631668

With regards to the recently committed patch https://www.drupal.org/node/1906282. I feel that possibly this should be included in the 2.x release as it has changes that are not able to be done only within the module (moving of socialcalc to sites/all/libraries and installation of Libraries API). I will be looking at removing that at the moment for the 1.x release.

7.x-2.x

To fit in with the current way that most are running Drupal projects, and how Drupal 8 are going to be splitting modules apart, it makes sense to start to move towards an accepted way of adding some parts. This will, however, mean that we will be looking at moving away from the upgrade path for the 1.x release as there are some parts that cannot be moved inside the module. I will look at improving the 1.x release to a point and then focussing future development on the 2.x release. Possibly some parts will be able to be backported into the 1.x branch, but I am not sure at the moment.

Moving of libraries to sites/all/libraries (integration of Libraries API)
All libraries should be inside sites/all/libraries and managed by the Libraries API and therefore we will look to moving all the appropriate libraries into there

Sheetnode CKEditor
I will be looking at integrating Sheetnode CKEditor with the CKEditor module. Especially as that is in core for Drupal 8 and therefore has good usage across Drupal 7.

Sheetnode Templates
At the moment there is no way to manage Sheetnode templates (and in fact you can overwrite them by naming the same template). This is not particularly stable and not manageble for anyone. I am planning that we could look at whether a sheetnode template could become an entity and therefore leverage Entity API. - https://www.drupal.org/node/724814

What to do

I am particularly interested to hear from anyone who has an opinion on this. I want to push Sheetnode forward to a more manageable state as I think it is a great module, especially for business applications.