Rev 1405 | Rev 1426 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 1405 | Rev 1410 | ||
|---|---|---|---|
| Line 66... | Line 66... | ||
| 66 | Ideas by Simon T.: |
66 | Ideas by Simon T.: |
| 67 | - System status plugin: Check if file owners are mixed |
67 | - System status plugin: Check if file owners are mixed |
| 68 | - a possibility to upload & assign custom icons to objects (both in the tree & in the page) |
68 | - a possibility to upload & assign custom icons to objects (both in the tree & in the page) |
| 69 | - a possibility to move objects/nodes from one hierarchy level to another (for now, I have to reconstruct them) |
69 | - a possibility to move objects/nodes from one hierarchy level to another (for now, I have to reconstruct them) |
| 70 | - 2FA TOTP support (+backup codes) - good for public instances, like FreeOID (Yes, I'm that one person who always asks for true totp 2FA everywhere xD ) |
70 | - 2FA TOTP support (+backup codes) - good for public instances, like FreeOID (Yes, I'm that one person who always asks for true totp 2FA everywhere xD ) |
| 71 | - a setting for a permanent choice between 'Always switch to newly created object' / 'Never switch' / 'Ask user if they want to switch' |
- | |
| 72 | - a possibility to 'construct' my own object types in UI (1: specify list of their fields and 2: choose "oid-like/forward" com.example.api or "domain-like/reverse" api.example.com naming scheme), so they would appear as the whole new type |
71 | - a possibility to 'construct' my own object types in UI (1: specify list of their fields and 2: choose "oid-like/forward" com.example.api or "domain-like/reverse" api.example.com naming scheme), so they would appear as the whole new type |
| 73 | 72 | ||
| 74 | Recently added TODO entries: |
73 | Recently added TODO entries: |
| 75 | - should all country codes (even unused) in 1.2 and 2.16 be added to the wellknown list? |
74 | - should all country codes (even unused) in 1.2 and 2.16 be added to the wellknown list? |
| 76 | - "Decoding" section (tech info) at OID nodes, e.g. the AID decoder, should this be a scrolling <pre> block instead of a <code> block? (For mobile devices) |
75 | - "Decoding" section (tech info) at OID nodes, e.g. the AID decoder, should this be a scrolling <pre> block instead of a <code> block? (For mobile devices) |
| Line 361... | Line 360... | ||
| 361 | 360 | ||
| 362 | QUESTIONS |
361 | QUESTIONS |
| 363 | - should the collation be case sensitive or case insensitive? For Java package names, it should be case senstivie |
362 | - should the collation be case sensitive or case insensitive? For Java package names, it should be case senstivie |
| 364 | - use word "guid" or "uuid"? |
363 | - use word "guid" or "uuid"? |
| 365 | - should "OID updated" be split into two categories "updated by superior" (e.g. identifiers) and "updated by owner" (description etc)? |
364 | - should "OID updated" be split into two categories "updated by superior" (e.g. identifiers) and "updated by owner" (description etc)? |
| 366 | - Don't renew "updated" field if you just click "Update" but didn't change anything (e.g. because you just wanted to send an invitation again) |
365 | - Don't renew "updated" field if you just click "Update" but didn't change anything |
| 367 | - "Documents" section: Can base of URLs/images inside the HTML be changed automatically? |
366 | - "Documents" section: Can base of URLs/images inside the HTML be changed automatically? |
| 368 | 367 | ||
| 369 | PRIVACY |
368 | PRIVACY |
| 370 | - bring back "vendor/cookiecontent"? DM 28 May 2019: Removed CookieConsent temporarily, because it is placed at the beginning of the page and therefore ruins the Google index ... |
369 | - bring back "vendor/cookiecontent"? DM 28 May 2019: Removed CookieConsent temporarily, because it is placed at the beginning of the page and therefore ruins the Google index ... |
| 371 | => We might not need it, because cookies are only set during login, and at the login page itself, we already warn about cookies, in addition to the Privacy documentation |
370 | => We might not need it, because cookies are only set during login, and at the login page itself, we already warn about cookies, in addition to the Privacy documentation |