search

GarryMorrison / Feynman-knowledge-engine

a minimalist but extensible knowledge engine
Other
5 stars 5 forks source link

split code? #20

Open GarryMorrison opened 9 years ago

GarryMorrison commented 9 years ago

I'm wondering if I should split my code into smaller, more manageable pieces? eg, split code file into one class per file? Not sure how we would split the functions or parser file.

allthingsgo commented 9 years ago

why not adhere to coding paradigm as MVC ( module/View/Control ) on the server/parser/compiler side and on the client side the more the merrier? but conceptual guideline as what is best left as raw data, intermediate calculus dataset in BKO format .sw, superposition, recall(), ket, grammar design etc, would be nice... but again, readers CAN make their own interpretation/justification on their own branching or their own time. As far as this project, we could make two sub-domains for your earlier followers, one for procrasti and one for me ( I've only wetted my pants with client side slurp code blocks, mostly figuring out how to reverse-engineer K5 content to fit whatever future is in stored for fringing characters...

GarryMorrison commented 6 years ago

I tried this, but then had circular import bugs that I didn't know how to solve. Now it is merged into these files: code.py, sigmoids.py, functions.py, usage_tables.py code.py contains: kets/superpositions/sequences/context/context_list/parser/etc sigmoids.py contains: sigmoids functions.py contains: our operators and sequence functions. usage_tables.py contains: a bunch of usage info