SEARCH_COMMONS_R0

[Astea]

wiki page: SEARCH_COMMONS_R0 - effort: 1d

[mitex]

analysis finished

[gogov]

Here's a list of some stuff which isn't right:

• There's no need to paste the rough descriptions from the WBS in the Overview section
• Lots of stuff which you've included in the task Task requirements is actually for the Overview section. Task requirements should include concrete list of things the designer/implementor should complete.
• You use bullets, which is good, though you could use them even more: "Text is typed in the field at the top of the palette and Enter is hit. A list of all occurrences in text are provided in the palette; to go to one of them, it is clicked in the list. Clicking on a result displays the page of the book with the match. The caret is positioned at the beginning of the match. The match is highlighted." could be bulleted and it'd be much more readable.
• You could consider splitting the long sections like Task requirements in subsections if necessary to enforce a more structured view on things that need to be done.
• When requesting a concept, or design or strategy of a new feature to be developed it's OK to list diagrams, unit tests, further explanations as requirements and task results.

You're on a right track, though I guess paying more attention to PLATFORM_STANDARDS_ANALYSIS would help writing better analysis.

[mitex]

OK, I'll improve my analysis.

Actually, according to PLATFORM_STANDARDS_ANALYSIS:
"it is recommended to have a code block including the description of the task that is found in the /manage/sched/sophie2_wbs.py file."
Maybe this requirement hasn't been present in previous versions of this wiki page.

[mitex]

start an2

[meddle]

By menu in the requirements you probably mean dialog. This should be later moved to a palette. deyan

[meddle]

• You know my comments about the code :) For the implementation this will be important.
• The task was wrong.
• There is no need of creating search menu item (and dialog window). If you like to implement quick search functionality make this in a proper way by using the correct palette. However in 'How to' section from the analysis the demonstration for the highlight is with selection not with search.(dido)
• Remove the dialog boxes and menu item move this functionality inside the palette.(dido)
• Discuss that with me and dido :)

3.5p (70m)

[meddle]

Error with stickies

[meddle]

I'll fail it now, because there is a strange error (see the attachment) when inserting sticky. I tried that because Stickies also contain hot text, which can be selectable... I think it is connected to the highlights and the activation channels of the timelines.
And can you tell me how to test the quick search if there is such, because the field bellow the book for searching don't work.

2.5p (70m)

[diana]

The quick search works after you have typed word in the field below the book and selected the frame that you want to search the text in, position the cursor somewhere in the text and press one of the buttons(prev/next). I suppose you haven't selected the frame.
Can you tell me the steps (one by one) causing this error because I cannot reproduce it.

[meddle]

• Behavior problems:
  • The highlight doesn't work in reader and preview.
  • When you go ahead with the next button the highlight selects one word after the cursor, then on the second next another word, bu if in this moment you press the prev button it doesn't select the previously highlighted word, that was after the cursor....
• Problems with crashes:
  • The highlight code crashes the chaining. See the attachment chaining-highlight.txt for the exception.

2p (3h)

[meddle]

Merged at last...

• Hehe the highlight class :)
• And there is a small bug with the selection into the trunk, if you fix it I'll be happy :) But after all this time:

3.5p (100m)

[deyan]

Batch update from file query-obsoleted.csv