Mitchell Tannenbaum

refactor classes loader

1

separate nested functions unbundle and weave. avoid tangles and knots.

style: run loader/thing/thing_loader.lua instead of base

2

base is ugly and unnecessary setup the table, require the modules, run the main function, and return it within the main thing loader function

refactor assign action to event submodule

1

instead of require_action, use * action_raw * action check if action disabling works action_arguments -> input parameters see also #24

factor out content module to separate project

1

foundpatterns/ContentDB.lua

refactor fs.lua to a separate project

1

foundpatterns/fs_ext.lua - split functions - unify with other apps' fs functions - replace them with torchbear's fs bindings

refactor every function to an individual file and add log trace

2

https://stackoverflow.com/questions/21416798/lua-global-variable-containing-path-to-current-file

refactor theme loader

1

//cc @LuisReyes98

merge with lighttouch

2

use two peru.yaml files. one for packages and themes, one for core/ afaict, this means lighttouch-base would be the primary code base, content/ would be factored out and imported with...