Merge lp:~zubairassad89/sahana-eden/vms into lp:~sahana-eden-vms/sahana-eden/vms
| Status: | Merged |
|---|---|
| Approved by: | zubair assad on 2010-06-17 |
| Approved revision: | 770 |
| Merged at revision: | 770 |
| Proposed branch: | lp:~zubairassad89/sahana-eden/vms |
| Merge into: | lp:~sahana-eden-vms/sahana-eden/vms |
| Diff against target: |
512 lines (+398/-42) 6 files modified
controllers/vol.py (+10/-3) models/vol.py (+132/-0) views/vol/index.html (+1/-0) views/vol/person_skill_list_create.html (+21/-0) views/vol/person_skills_list_create.html (+0/-39) views/vol/skill.js (+234/-0) |
| To merge this branch: | bzr merge lp:~zubairassad89/sahana-eden/vms |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| zubair assad | Approve on 2010-06-17 | ||
| Pat Tressel | 2010-06-16 | Approve on 2010-06-17 | |
|
Review via email:
|
|||
Commit Message
Merge assad-dev-vms
Description of the Change
Merge assad-dev-vms
| zubair assad (zubairassad89) wrote : | # |
Nice idea, with all skills converging into a single table.
Ok, i will take out the subcategory and change the name of skillcust to skill_type.
> Eventually the skillcust table will have all the types of skills in it, even
> if the site starts out using a pre-defined set. So maybe we shouldn't call it
> skillcust. Would be nice if we could use something generic. Maybe
> skill_types?
>
> I recall you wanted to start out with just one level of category (easier to
> get something working, and maybe users don't want more than that). So how
> about taking out the subcategory?
| Pat Tressel (ptressel) wrote : | # |
I still see "skillcust" in a comment and in the name of an html file.
How about putting in CRUD strings for skill_types?
I wonder if you need a custom form if you have CRUD strings -- see what happens if you don't have an html page.
You'll need something like Add Skill Types in the top level menu, and take it out of the person menu -- it doesn't go with a specific person.
| zubair assad (zubairassad89) wrote : | # |
Sorry about that skillcust!
put the CRUD for skill_types
add skill types put in top menu
> I still see "skillcust" in a comment and in the name of an html file.
>
> How about putting in CRUD strings for skill_types?
>
> I wonder if you need a custom form if you have CRUD strings -- see what
> happens if you don't have an html page.
>
> You'll need something like Add Skill Types in the top level menu, and take it
> out of the person menu -- it doesn't go with a specific person.
| Pat Tressel (ptressel) wrote : | # |
Want to take out that alert foo from skill.js? Also there are some code lines commented out -- those can go away.
The skill_types table looks like it has some debug stuff -- the name and category fields are commented out, and there's an extra comment1 field (or do you want a "description" field in there)? The subcategory field is still there but commented out -- it can go away.
Some formatting cleanup needed:
Extra blank lines in menu, before the ) in add_component, in between code blocks (ok to have 2 blank lines between major sections, like different tables), in skill.js.
Line num_column=3 in models/vol.py looks like it's got a newline in front of it.
When you post a reply comment, set the "Review" to comment only. ;-)
| Pat Tressel (ptressel) wrote : | # |
At about line 149 in the current diff, the indent for the name Field isn't same as the other Field lines. Also put the args for that first Field on the same line.
How about using just category rather than skill_category? Or use skill_name instead of name -- just looks odd to have one say skill and the other not.
Search for SK -- some of the CRUD strings have uppercase K.
What about using a list_create form for skill types? There isn't a way to see a list right now. You can get this by just taking away the skill_types_
How about using just "Skill Types" on the main menu, to go along with using the list_create form (since it's not just adding)?
- 770. By zubair assad on 2010-06-17
-
Addition of Skill Type and Formatting of VMS files


Eventually the skillcust table will have all the types of skills in it, even if the site starts out using a pre-defined set. So maybe we shouldn't call it skillcust. Would be nice if we could use something generic. Maybe skill_types?
I recall you wanted to start out with just one level of category (easier to get something working, and maybe users don't want more than that). So how about taking out the subcategory?