Key Concerns

First off, Google's breaking apart. First Google Code was down for a couple of hours (a week-or-so ago), and now Blogger/Blogspot was down for a few hours.

But, back to the point:

I've done some tweaking with the code, correcting some typo-related bugs, and fixed some stuff previously done in plain stupid ways. This is a part of me postponing the start of any bigger feature. Just like I did miscellaneous smaller stuff before starting on the Model/Field pair, I fixed previous code before doing any foreign key -related logics, which will translate to ForeignKeyField and ManyToManyField.

Actually, I'm not sure if I like those names for the fields because they relate too much directly to relational theory, instead of being intuitive and reflect what they do/contain. Anyhow, the name is a minute detail, it's easy to change, as long as it's changed before wide-spread use.

But, I hit immediately to a snag. I haven't yet thought of a way to translate the id, stored inside the Model, to something that I can give to the Field, so that it can search for the matching referenced model. I would really hate to force the user to manually transfer the id to the field, which would go against the "maximum automation" mantra I adhere to.

Once I get the referencing fields working, I'm thinking LightFrame being ready for live testing... I could write user documentation while waiting for this to solve itself, but I'd rather not.

Update: Forget the above... Where do I need the model's key anyhow? Things are progressing just nicely.