Webhook parsing functionality

[GoogleCodeExporter]

Purpose of feature on this branch:
Heyu webhook will allow for better parsing of the config file which will allow:
1. The user to maintain a custom organized config file
2. Allow dL to parse ALIAS entries correctly in case of extra AUX type fields.
3. We may be able to organize units in the floorplan based on [sections] in
the config file.
4. Prevent commented config entries from being parsed.
5. Allow the user to edit the config file on a more sectional basis which
would allow for better interactive editing.

The infrastructure change brought on by the implementation of webhook will
allow for a more transparent integration with Heyu, a better end-user
experience, and open the doors for more feature support down the road.

Proposition for feature implementation:

Need to research. Please feel free to comment on this.

Original issue reported on code.google.com by brandtda...@gmail.com on 12 Apr 2010 at 6:59

[GoogleCodeExporter]

Looks great!

Comments:

Item 1 clarification: User will be able to maintain the custom config file 
within the
constructs of heyu config file specifications.

Item 3: With sections, we would only be able to categorize by one attribute, 
i.e.:
floorplan location or module type. There are 2 attributes used in the comments 
after
an alias for domus.Link which are type and floorplan location. We wouldn't be 
able to
do that with sections for identifying both attributes without a lot of parsing. 
I
would suggest we keep this information in a db file in domus.Link since it is
specific to domus itself. That way we can keep the heyu config files pure. I 
did this
for the sched files when I updated the sched file handling.

Original comment by bwsamuels@gmail.com on 13 Apr 2010 at 1:34

[GoogleCodeExporter]

Original comment by bwsamuels@gmail.com on 13 Apr 2010 at 1:54

• Changed state: Accepted

[GoogleCodeExporter]

1. I was thinking there are two types of users. There are those that have been 
heyu
users for a while, and already have their config file organized the way they 
want it.
Then there are those that are new to heyu and are starting from scratch with 
dL. It
the latter case dL should have full functionality for editing the config file 
giving
the user options with drop down menus or radio buttons, etc...

Original comment by brandtda...@gmail.com on 13 Apr 2010 at 2:07

[GoogleCodeExporter]

Original comment by bwsamuels@gmail.com on 18 Apr 2010 at 4:13

• Changed state: Started

[GoogleCodeExporter]

This issue was closed by revision r736.

Original comment by bwsamuels@gmail.com on 11 May 2010 at 1:25

• Changed state: Fixed