Request: Named Colors
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- api
Research direction
Start by reviewing how Colors and Viewpoints are defined in the BCF-API specification, then compare the requested optional color names and color-schema name with the related Viewpoints should have names issue (#388). Done means the API request is resolved for both the BCF-API and BCF-XML concerns, with the intended naming scope documented.
Written by the indexing model from the issue text.
Description
Coloring in Viewpoints is usually not applied just for fancy looks, but as indicators. For example, walls may be colored by type, or by clash results. Rooms may be colored by purpose, or by renter, etc.
It is currently not possible to have this kind of semantic information in BCF. I think an optional Name property on Colors would be a valuable addition.
Additional to this, it would be nice to not only have names for each color, but also one for the entire color schema, to indicate the purpose of the coloring. This purpose would mostly be identical with the purpose of the Viewpoint, which is one more reason why Viewpoints should have names, too.
This request is obviously also for BCF-XML, but I wasn't sure if I should duplicate the issue.
- Dominant language
- No language data
- Stars
- 238
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from buildingSMART/BCF-API
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
buildingSMART/BCF-API#395 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
buildingSMART/BCF-API#394 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
buildingSMART/BCF-API#392 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
buildingSMART/BCF-API#390 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
buildingSMART/BCF-API#388 · 2 comments ·
All issues in buildingSMART/BCF-API
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
octobercms/october#6130 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·