kennyb / awake-in-tenerife Goto Github PK

some way to define default values for fields when they're not found in the object

ability to load up the panels from mongo instead of from the filesystem...

convert old ones to new model and delete the dummy function

more specifically, check for the various libraries, and if they don't exist, then build them automatically

something like:
make P=../myproject && ./core -config ../myproject/config

add / sub / mul / div / etc.

mostly just the bson to use slicing and native strings and remove all exceptions chungas... this can be done in phases..

in expressions, often times temporary variables are needed. make these possible

a necessary step for dynamic panel stuff

gain a little space / memory savings and perhaps slight inline performance increase cause of shitty linking between obj / llvm-bc...

low priority

debería estar en los dos idiomas... it is awake in tenerife jajaja

something that automates the populating/updating an object through the FUNC vars

pretty important to remove injection possibilities

it should be a simple process of making this work:

<%loop Obj {var: 1} && Obj2 {var2: 1} %>

ability to define indices in edb to ensure their existance

list everything that's available

do all logging to the mongo database (presumably this would be the mongo db that's the master repo

make an example that shows a hello world example.

it's impossible to inject if variables are always used, but it's possible to manipulate the BSON object perhaps and inject more fields perhaps... even still, I need to think of a way to prevent this... I could obviously replace all '\0' with ' ' or something... need to do some testing to see what's possible and create a prevention system... perhaps it could be easier to do when the BSON code is moved over to D.

there are some weird language related bugs with m32 mode. fix these and write unittests for them

make all of these utf-8 safe. just need to jump the stride

store images inside of GridFS - obviously, it'd need some sort of caching layer, and some sort of smart system to cluster the fotos for better cache hit ratios

automatically generate docs which explain the data model and function parameters and stuff for a quick guide to the programmer as she's programming