- still working on quickhull (2d)
 * not working yet but edging ever so closer
 * added redundant position removal on intial insert
 * moved the recursive processing to a seperate method
 * extracted a few utility methods
 * experimenting, learning, debugging
- modified the rectangle shape "size" param to behave correctly (now it is specifies the actual size of the edges correctly)
- more work on hull()
 * still not there yet : tried a different implementation (still quickhull) : while some result shows up on the screen ,it is badly broken
 * need to reorganise code for more clarity and other attempts
- quickhull works !! yay ! also:
* moved all the various quickhull implementations to the "extras" module for clarity
* refactored code base on yet another implementation variation: turns out the original try we had was close to the working version
* various small cleanups and import changes (csg.sugar2.coffee) to work with the changes above
- starting to get settings system working again, but modular this time
 * started cleanup of settings view
 * added request/response (reqres) as experimental system to request specific settingviews
 * modified/fixed modalRegion to auto generate div, and to re-enable the main settings modal
 * added event trigger to menuview to send message to display settings view
 * moved out most of the specific settings to their correct submodules, and added a "connectors" subfolder to store well...
connector (github, dropbox) related elements (just the few non working github settings for now)
 * small changes to code and visual editor to mach all the above changes
 * modified main app to be able to launch the settingsView
- more work done on settings (views mostly)
 * now each sub app registers its setting type with the main settings object : this is used for correct instanciating of sub classes on fetching the data
 * enhanced decoupling : when asking for the displaying of the settingsView, we use a marionnete request/response object to dynamically get the correct settingView from
the various sub apps: this way the main app is never aware of the details of the sub apps
 * various smaller fixes (renaming of visualEditor settings name / title attributes etc), and cleanups
 * this means that, at least visually the settingsView works again (the different settings don't yet have their event system correctly attached)
 * still need to correctly handle the order in which the settings get fetched from storage/ sent to the various subapps
- more cleanup work in settings and related views
 * settings now get correctly saved and reloaded from localstorage again
 * modified the settings' parse & initialization methods to match
 * moved the instanciation of sub app to beforeInit, and the fetching and dispatching of sub setting object to be done at sub app start
 * modified codeEditor settings (now extending from backbone.nestedmodel) & its view to correctly render the linting settings:
its far from perfect (object/nested model support in backbone forms is not perfect) but it will have to do for now
 * these nested settings are NOT correctly updating the various editors for now
- added package.json as suggested by KimGressens in issue #60 : this will make installing the dependencies for the cakefile easier to install
- updated readme with info about the cakefile/ build process etc
- worked on preliminary elements for dropbox integration:
 * moved connectors into core as they are essentially part of it (storage etc)
 * added  backbone.dropbox from repo
 * added menu item for dropbox login

- overall cleanup
 * removed a lot of debug console messages
 * small but many cleanups in different files (nothing functional, just cleaning up useless stuff)
- small amount of work done on better integration of exporters as modules/mini sub apps: not there yet!
- attempting to add the various exporters as "stubs" into the main menu : visually it works, but event binding is broken
- addendum to previous commit :
 * events (event vent.trigger) now work (almost) correctly thanks to delegateEvents()
 * still a bit buggy : why does the same event get fire for both exporter entries ?
- worked on exporters :
* both stl & bom exporter have been refined , and work as "seperate" sub apps
* stl exporter works again BUT it turns out the recent CSG refactoring introduced some unknown bug in the TJUNCTION system,
which makes the export either crash or fail with more complex objects : needs fixing asap
* bom exporter basics are now in place: all visual elements are there , export itself does not work yet , but all the views and the underlying system are ok
* started working on more refined part regiter to take into account the parameter variations : in the bom, two object instances with different params should not
be displayed on the same line
* related cleanups and small alterations in the menuView (dynamic generation of event entries for the various exports, from a list, are now generated correctly)
and in coffeeescad.app
- fixed a few issues in bom exporter:
 * variant counts are now updated correctly
 * better display of variants : variant names default to "default"
 * exporting to Json file (and auto download) actually works
 * refactored bom exporter view a bit : moved the creation of parts collection to bomExporter itself (even here it is not quite its place
but that is for another refac)
 * download url request now works correcly
 * cleaned up the main bomExporter view
- Added screenshot & basic change to readme to display it
image link fix
- a few changes and fixes to the bom exporter
 * changed "number" to "quantity"
 * a few minor template changes
 * added working modification of part numbers: now the quantity gets actually altered in the model, and thus the json export contains the correct quantities
as well
- started api breaking modification : no more "return CSGObject" but "project.add CSGObject"
* for now very bare bones: all the objects added to the "project" object are "unioned" together , so still one final object on export
* semi hackish implementation, but started modifying the csg.processor (the one in charge of compiling the code in the ui) for a much cleaner
way to do this , and to remove the need for csg globals (ie if this works, no more window.objectRegistry = , no more window.square = etc)
* for now only the project has an "add" method , but this will very likely be moved into the base csg class to be able to build object hiearchies (thus dealing with issue #36)
- important, project, visual editor, and csg processor changes:
* now multiple seperate "visual"(selectable) objects are generated based on all the object added with project.add
* modified the project and visualEditor class to enable this: now projects have a "compile" method (moved there from the visualEditor, which makes more sense (seperation of concerns)
* for now this is a bit broken as the previously generated objects (by a previous compiling) don't get deleted from the scene: fixes required in visualEditor
* the visual editor view now takes the Project as model, not an individual file
- worked on csg processor
* cleanup of old openjscad code
* making changes so async (web worker) processing can be enabled again (issue #52)
* most likely will replace the "project.add(object)" with "assembly.add(object)" as it makes more sense (assembly is the overall tree structure of parts)
- added a "bom" subcollection to the Project class:
* generation of the bom from the class registry now takes place in the "compile" method
* bom exporter modified to fit these changes
- fixes #64 (object selection issues)
 * turns out the selection bug only required this additional line to fix : mesh.geometry.computeCentroids()
 * cleaned up object selection code
- a bit of cleanup in project & csg processor, stl exporter etc regarding the root assembly object
* the project class now has a rootAssembly object that holds the tree of csg objects
* added "mergeAll" options to stl exporter , so the whole project (including the rootAssembly's sub objects) can be merged into a single csg for export