objectives niggles

[kohlhase]

• we need the e to edit in editor in the objectives dialogue
• it seems that the objective is put into the file after the % I would like it to be put directly after the \import/\usemodule.
• It would great if we could see what objectives are already present (I seem to have seen an ---A somewhere, but that does not seem to work everywhere
• Maybe only suggest the "new annotations" for objectives (the old ones presumably are already OK). No, that will now work for all the legacy files. This should be a user option. Ah, I know how we can handle this. We can use S to leave a snify comment that says "I am done with objectives for this subproblem". If there are no "new annotations in the subproblem", then it is automatically skipped for objectives.
• Somehow make clear (e.g. in the green header bar) which subproblem we are in. Also add the "setup text" in the text fragment.
• There should be a way to getting rid of objectives, e.g. 3du deletes the understand for 3.
• Sometimes the text fragment shown of the problem is not big enough. It would be very nice, if we could have an action > (more) that shows 50% more lines and < (less) that makes it smaller.
• sometimes the objectives are not related to a symbol reference, e.g. when the code listing has a while loop. For that it would be good to have the l interaction at the objectives level, so that we can just pick out the objectives we need (and tag them with the conitive dimension in some way (to be designed).
• [ ]

[jfschaefer]

I've fixed the first two points. I don't fully understand the other two points - let's discuss them a bit later when I'm in the office.

[kohlhase]

thanks, let's do it that way.