22 Commits (74d2041ed629d4fc5e8ab328128c8d6a00fa8247)

Author	SHA1	Message	Date
Jens Ulferts	bae0bfdd0b	prevent empty values from being hidden while editing	9 years ago
Oliver Günther	e28ad041d2	Don't show new work package id in single view	9 years ago
manuschiller	d9a38f8b89	Adding attachments to work package descriptions by drag and drop ... https://community.openproject.org/work_packages/22511 This adds drag and drop functionality for wiki-textareas concerning wp-attachments (mainly the description field) in workpackages. based on the use of our new directives by @furinvader as proposed in https://github.com/opf/openproject/pull/4471 Features: handles drop events on description fields of work packages and can distinguish between: - local files: initiates file upload (single file or upload queue) - external urls: become inserted as default weblink - external image files: become inserted as inline image - attachments from current work package: become inserted as attachment link - attachments (imagefiles) from current work package: become inserted as inline image	9 years ago
Jens Ulferts	2e5dfc794b	add missing closing div tag	9 years ago
Roman Roelofsen	e0bf811f77	Reduced watchers count, needs review!	9 years ago
Markus Kahl	f64d06638c	hide hidden fields even if they have a value (#4408) ... * Make test/dev assets settings explit * description must not be customizable * updated feature help text * fields with default values can be hidden * fixed hide condition * fixed edit wp spec (required cf) for some reason factories initialize custom fields with '' (empty string) as default values. The API interprets this as a default value being present. In normal operation a custom field without a default value will return nil, not the empty string	9 years ago
Oliver Günther	159a7f0007	Restore custom schema displayAttr functionality ... I don't really like that displayAttr is exploited for displaying sums, despite the directive clearly targeted to work packages alone. This makes the distinction clearer with a 'customSchema' attribute when not the work package schema is to be used.	9 years ago
ulferts	2c47657de7	unified date field for milestone work packages (#4437) ... Work packages having a type that is a milestone receive a 'date' attribute in their API resource. Other work packages still have the 'startDate'/'dueDate' attributes. The schema behaves analogous so that such a change is visible to a client. In the cient we can now remove some of the custom behaviour for the date field. The code removal is limited to the new inplace edit implementation as the old implementation can hopefully be removed fully in the near future.	9 years ago
Oliver Günther	3cc850b783	Replace comment cuke with spec	9 years ago
Oliver Günther	e299283bcb	Move wp-edit-form up to list-details ... This requires the new work package resource in the details controller parallel to the old resource. It's ugly, but temporary.	9 years ago
Alex Dik	f2246e32c7	Use one time binding for date field placeholder	9 years ago
Alex Dik	a1ba434ad0	Add placeholders to date fields	9 years ago
Jens Ulferts	c4e5bab07b	style inline-edit textarea fields	9 years ago
Alex Dik	4c1e56e993	Fix date field group editing	9 years ago
Jens Ulferts	09810c897f	add styling to rest of inline edit fields	9 years ago
Jens Ulferts	23515190cb	restyle subject on the wp.show	9 years ago
Alex Dik	33bdb3e50c	Rename directive work-package-attachments to wp-attachments	9 years ago
Jens Ulferts	e5d874a966	Accessibility for wp-edit fields ... * Hidden label for all fields once they are activated * aria-labelledby for all fields when they are in read mode * turned visible attribute text on split/fullscreen to be clickable so that it behaves like a label	9 years ago
Alex Dik	4a80aee14d	Implement SingleViewWorkPackage service	9 years ago
Alex Dik	bcde447403	Fix WP single view directive ... Refactor the controller and prevent some errors related to a non existing schema.	9 years ago
Alex Dik	977e6529a5	Adapt WP edit form to WP edit sync	9 years ago