Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open new entry in item list by default #6

Closed
JulianKniephoff opened this issue Mar 21, 2017 · 1 comment
Closed

Open new entry in item list by default #6

JulianKniephoff opened this issue Mar 21, 2017 · 1 comment

Comments

@JulianKniephoff
Copy link
Member

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)


When I create a new annotation (text or category label) the new entry in the item list should be open by default, so that data can be quickly accessed there.

Probably an item that was opened this way, should be closed as soon as a new item was added (keeping manually opened items open)


@JulianKniephoff
Copy link
Member Author

Original comment by Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf):


done with pr9

@JulianKniephoff JulianKniephoff added this to the 2. Category Management Improvements milestone Jan 10, 2018
mliradelc referenced this issue in mliradelc/annotation-tool Jun 24, 2019
# This is the 1st commit message:

Add HLS support

Update files from develop branch

Fixed German translation file syntax

Closes opencast#173.

Add Emacs configuration

`npm update && npm audit fix`

Changed `less` plugin for `grunt`

This switches from `assemble-less` to `grunt-contrib-less`
and updates the latter at least a bit,
all in order to get rid of a few security vulnerabilities.
Further updates pending mostly because of incompatibilities.

Updated `grunt-contrib-less` to the latest version

More package updates

# This is the commit message #2:

Removed unused grunt plugin

# This is the commit message #3:

Removed some unused dependencies

# This is the commit message #4:

Improved code quality

# This is the commit message #5:

Removed some dead code and obsolete comments

# This is the commit message #6:

Got rid of `box-sizing`-'polyfill"

Box sizing has good enough support now.
If we still want backwards compat,
I feel like a CSS postprocessor
would be a better approach.

# This is the commit message opencast#7:

Simplified some event handling code

# This is the commit message opencast#8:

Refactored comment model slightly

Comments should be creatable without text.
But I **do** see the problem this brings.
So why not make the empty string the default text? ;)

# This is the commit message opencast#9:

Refactored some view cleanup and deleted related dead code

# This is the commit message opencast#10:

Allowed editing multiple annotations simultaneously

# This is the commit message opencast#11:

Use `maven-enforcer-plugin` instead of `prerequisites`

Fixes opencast#187.

# This is the commit message opencast#12:

Pinned `maven-install-plugin`

Fixes opencast#185.

# This is the commit message opencast#13:

Added an `npm start` script
mliradelc referenced this issue in mliradelc/annotation-tool Jun 24, 2019
# This is the 1st commit message:

Add HLS support

Update files from develop branch

Fixed German translation file syntax

Closes opencast#173.

Add Emacs configuration

`npm update && npm audit fix`

Changed `less` plugin for `grunt`

This switches from `assemble-less` to `grunt-contrib-less`
and updates the latter at least a bit,
all in order to get rid of a few security vulnerabilities.
Further updates pending mostly because of incompatibilities.

Updated `grunt-contrib-less` to the latest version

More package updates

# This is the commit message #2:

Removed unused grunt plugin

# This is the commit message #3:

Removed some unused dependencies

# This is the commit message #4:

Improved code quality

# This is the commit message #5:

Removed some dead code and obsolete comments

# This is the commit message #6:

Got rid of `box-sizing`-'polyfill"

Box sizing has good enough support now.
If we still want backwards compat,
I feel like a CSS postprocessor
would be a better approach.

# This is the commit message opencast#7:

Simplified some event handling code

# This is the commit message opencast#8:

Refactored comment model slightly

Comments should be creatable without text.
But I **do** see the problem this brings.
So why not make the empty string the default text? ;)

# This is the commit message opencast#9:

Refactored some view cleanup and deleted related dead code

# This is the commit message opencast#10:

Allowed editing multiple annotations simultaneously

# This is the commit message opencast#11:

Use `maven-enforcer-plugin` instead of `prerequisites`

Fixes opencast#187.

# This is the commit message opencast#12:

Pinned `maven-install-plugin`

Fixes opencast#185.

# This is the commit message opencast#13:

Added an `npm start` script

# This is the commit message opencast#14:

Updated `grunt-cli`

# This is the commit message opencast#15:

Improved code quality
mliradelc referenced this issue in mliradelc/annotation-tool Jun 24, 2019
# This is the 1st commit message:

Add HLS support

Update files from develop branch

Fixed German translation file syntax

Closes opencast#173.

Add Emacs configuration

`npm update && npm audit fix`

Changed `less` plugin for `grunt`

This switches from `assemble-less` to `grunt-contrib-less`
and updates the latter at least a bit,
all in order to get rid of a few security vulnerabilities.
Further updates pending mostly because of incompatibilities.

Updated `grunt-contrib-less` to the latest version

More package updates

# This is the commit message #2:

Removed unused grunt plugin

# This is the commit message #3:

Removed some unused dependencies

# This is the commit message #4:

Improved code quality

# This is the commit message #5:

Removed some dead code and obsolete comments

# This is the commit message #6:

Got rid of `box-sizing`-'polyfill"

Box sizing has good enough support now.
If we still want backwards compat,
I feel like a CSS postprocessor
would be a better approach.

# This is the commit message opencast#7:

Simplified some event handling code

# This is the commit message opencast#8:

Refactored comment model slightly

Comments should be creatable without text.
But I **do** see the problem this brings.
So why not make the empty string the default text? ;)

# This is the commit message opencast#9:

Refactored some view cleanup and deleted related dead code

# This is the commit message opencast#10:

Allowed editing multiple annotations simultaneously

# This is the commit message opencast#11:

Use `maven-enforcer-plugin` instead of `prerequisites`

Fixes opencast#187.

# This is the commit message opencast#12:

Pinned `maven-install-plugin`

Fixes opencast#185.

# This is the commit message opencast#13:

Added an `npm start` script

# This is the commit message opencast#14:

Updated `grunt-cli`

# This is the commit message opencast#15:

Improved code quality

# This is the commit message opencast#16:

Revert back to a stable version of `grunt-cli`

Closes opencast#188.

# This is the commit message opencast#17:

Fix XACML parsing of rules

OAT filters for ACL rules with the wrong tag name "rules" instead of
"Rule".

# This is the commit message opencast#18:

Fix exception during export when no e-mail is set

# This is the commit message opencast#19:

Simplified some of the export functions a bit

# This is the commit message opencast#20:

Remove unused and vulnerable dependency

# This is the commit message opencast#21:

Updated demo link in the README

Changed the README to include a link to a working demo
# This is the commit message opencast#22:

Update README.md
# This is the commit message opencast#23:

Update checkstyle to fix a vulnerability

# This is the commit message opencast#24:

Improve the style of the checkstyle configuration

# This is the commit message opencast#25:

Update `grunt`
JulianKniephoff pushed a commit to JulianKniephoff/annotation-tool that referenced this issue Oct 29, 2021
…ed-to-series

Tell `Categories` collection when changing `id`-s in `Category#sync`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

1 participant