General design of knotes improvement
I have just finished my midterm exams, so I didn’t update blog for several days. But I am continue working on knotes in my spare time.
Now I have basicly completed the knotes code’s analyzing.
The improvement will effect following class at least:
I am planning to carry out the improvement in the following way:
1. Left click on the icon will generate a menu with sub menues(categories). In fact, one note can be displayed under different sub menues.
2. When right click on the icon, you can find a way to manage all categories, like rename. I don’t think the new and delete action is needed here. Because I preferred( so did my mentor ) Method B, which means if there is no note with this tag, the tag won’t exist. I don’t know if it is properly, and if it is can be accepted by most people. But I know the idea of tag is very popular with web2.0 like delicious. At least, I think this method has very good flexibility.
3. When you editing a note, you can setting its tags by right click on the title or something other. The exist tags will be provided to choose, you can also create a tag.
I have send a survey to mailinglist(kdepim-user and kde-linux). I want to know if tags-style can be accepted.
The other thing is about knotes in kontact. I skimmed the source code, and it is seems another story… I am planning to add something like QListWidget for users to choose categories.