APP_RESOURCE_PREVIEW_DISPLAY_R0

[Astea]

wiki page: APP_RESOURCE_PREVIEW_DISPLAY_R0 - effort: 0.5d

[kyli]

3.5p. Seems ok, just the requirement "implement this after APP_RESOURCE_LIST_DISPLAY_R0" should be put - you cannot preview a resource you cannot select, after all.

[boyan]

regrouping tasks

[boyan]

updating status of a grouped task

[deyan]

Batch update from file import.csv

[todor]

taken for analysis

[deyan]

You could cover the case when nothing is selected.

[tanya]

The analysis is incorrect. For pdf resource - the user should be able to navigate through the whole document. Scrollbar for rtf could be a good idea (this should be discussed). Navigation between different pages of a book could be a good idea.

[dido]

Only fixing minor things.
analysis (30m)

[deyan]

When the image is deselected, the preview should go away. Also it seems that requirements are too few.

[pap]

• Fill in the custom fields (design_owners)
• You should've mentioned in the wiki page that you will have to change the SystemTestBase. Designing a task does include refactorings of other things that you plan to make.
• I understand that people prefer to have something implemented and working before they submit their design but this does not mean that you should commit everything at once. Please separate the commits of design related code and implementation one.
• I personally don't like the way visual elements are used but this is not of my competence.

[meddle]

The implementation seems OK, we had some problems but we resolved all of them without this with the PDFResourcePreview to be BaseVisualElement.
That's my comment:

	 TODO:
	 @since 03.06.2009 : Maybe this should be a {@link BaseVisualElement}
	 		     but there is a strange bug when it becomes one.
	                     Try to fix it in the future. --meddle

3.5p (100m)

[deyan]

Batch update from file query-obsoleted.csv