Archives week 26 of 2006
June 26, 2006 - July 2, 2006
UI stuff just feels more interesting (Simple little navigation widgets for a hierarchic schema...)
Written by
on
in
Snaking.
Finished off the day's work by working on some simple navigation widgets for the billing system. The entire system is built using directed acyclic graphs (of various types). Because of that you can readily construct generic views that let you see the parents and children of any node in the system. I'm still looking for ...
FormEncode is nice (Validators are so much nicer than coding everything oneself)
Written by
on
in
Snaking.
Dipping my toes in the waters of FormEncode today. Basically decided I needed a break from financial aspects, so spent some time roughing out a simple list and add view for Inventory objects (in this particular case, phone numbers/DIDs). Most of the work was:
Figuring out that All and Any values are applied in reverse ...!-->!-->
Bogging down a bit on the charge-setup subsystem (Uncharted areas for me to some degree...)
Written by
on
in
Knight Errant.
One of the major wish-list items for the new billing system is the ability to set up differential charging schemes using a tabular setup, so that admins can set up a default table of charges and then sets of overrides to those charges based on a rule match (e.g. you have a given token, or ...
Addresses and constrained addresses (Long-term wish-list items...)
Written by
on
in
Knight Errant.
When you run a cable company, it makes sense to have the ability to explicitly and exhaustively define the streets and street-ranges in the town so that you can never have an invalid address entered for service. I've just finished the basic implementation of that for the better billing project, along with the other major ...
These are the continuing voyages... (More work on BetterBilling...)
Written by
on
in
Knight Errant.
Continued work on BetterBilling this evening. Particularly started working on creating stand-ins for the eventual user-driven package-setup functions. Eventually a user should be able to compose a new package (billable thing) out of technical effects (services provided by the backend) and configurations (user choices that control the operation technical effects). For now I'm just manually ...
Test suites are fun! (Cancelled meetings and working on almost-spec...)
Written by
on
in
Knight Errant.
Other than a few hours on the (largely finished) old project (so far), I've been concentrating today on TurboGears and particularly moving the BetterBilling project ahead. I've been running into (minor) SQLObject bugs here and there, probably because inheritance isn't a commonly used feature and I'm using it extensively.
I've finally got to the point ...!-->!-->