Closed ChasNelson1990 closed 2 years ago
@joshuajames-smith I labelled this "feature" and the robot added the "enhancement" label... which is a lie... any ideas why?
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-wave-0f4ddd903-759.westeurope.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-wave-0f4ddd903-759.westeurope.azurestaticapps.net
@joshuajames-smith I labelled this "feature" and the robot added the "enhancement" label... which is a lie... any ideas why?
Mmm.. im not too sure? The templates for issues pre-defines a label but the template for PRs doesn't.
Mmm.. im not too sure? The templates for issues pre-defines a label but the template for PRs doesn't.
I presume this is the culprit: https://github.com/gliff-ai/.github/blob/ce7d8428c06a5c1fe0dadd9464e2d743c3fdf810/.github/labeler.yml#L7 ?
I also wonder from a UX P.O.V. if this isn't a toggle but a separate tool from the brush tool?
I also wonder from a UX P.O.V. if this isn't a toggle but a separate tool from the brush tool?
But it's just a different shape brush?
Interestingly, the annotation doesn't visually appear on Safari?
Sorry, I'm not sure I understand this comment @joshuajames-smith?
If you also move the mouse to the left or right of the canvas, the annotation tool appears back on the canvas?
Yes, known bug - will create an issue for it.
Mmm.. im not too sure? The templates for issues pre-defines a label but the template for PRs doesn't.
I presume this is the culprit: https://github.com/gliff-ai/.github/blob/ce7d8428c06a5c1fe0dadd9464e2d743c3fdf810/.github/labeler.yml#L7 ?
Good catch! The commit history is just you, should i swap out the label to enhancement
or remove this apply label for feat:
all together?
Interestingly, the annotation doesn't visually appear on Safari?
Sorry, I'm not sure I understand this comment @joshuajames-smith?
So if I have the Super Marker active and click to annotate nothing appears - it shows on Google Chrome, but not on Safari.
Good catch! The commit history is just you, should i swap out the label to
enhancement
or remove this apply label forfeat:
all together?
That's because I copy and pasted this file into the .github repo but I think you created it originally so I am happy for you to do what you need.
Re: enhancement vs feature... I think conventional commits would say both are feat:
in the commit message, so maybe just use feature for PRs? And keep enhancement for issues?
So if I have the Super Marker active and click to annotate nothing appears - it shows on Google Chrome, but not on Safari.
Can you make a bug issue please?
I also wonder from a UX P.O.V. if this isn't a toggle but a separate tool from the brush tool?
But it's just a different shape brush?
I could see a justification for a circle vs square brush but it's function is slightly disconnected - while yes its a brush annotation, it's less manual drawing/annotating and more clicking on auto defined areas?
I can see a user case where upon they use the super marker tool to click upon several defined areas but switch to the brush or eraser tool to tidy up edges. An insitive UX would likely be to switch tools rather than turn a toggle off. This is possibly because the tool if called super marker, a toggle might work if renamed something like "turn on automatic selection" / "turn on area selection".
I could see a justification for a circle vs square brush but it's function is slightly disconnected - while yes its a brush annotation, it's less manual drawing/annotating and more clicking on auto defined areas?
But it is manual annotation? I don't see the difference between this and a circular paintbrush lol?
I can see a user case where upon they use the super marker tool to click upon several defined areas but switch to the brush or eraser tool to tidy up edges.
This is exactly the idea... the smart marker, just like the eraser, is a way of getting the manual paintbrush annotations that you need?
An insitive UX would likely be to switch tools rather than turn a toggle off. This is possibly because the tool if called super marker, a toggle might work if renamed something like "turn on automatic selection" / "turn on area selection".
"insitive"?... see above. In my mind this is 100% a paintbrush activity... both in terms of the backend but also in terms of the output - a manually created pixel-level labelling of an image that you can combine with non-smart brush strokes and eraser strokes completely interchangeably?
In my mind this is 100% a paintbrush activity... both in terms of the backend but also in terms of the output - a manually created pixel-level labelling of an image that you can combine with non-smart brush strokes and eraser strokes completely interchangeably?
Happy to go with the toggle for now and if not UX issues/comments arise then it's all good!
Tooltip to use the beta-status
icon (or alpha-status
icon in it's place) as above. This will provide some good user feedback!
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-wave-0f4ddd903-759.westeurope.azurestaticapps.net
Despite not having done a major version change for STYLE, STYLE seems to broken and I can no longer npm run serve
... @ChrisBaidoo @cooper667 we ideally need this fixed on Monday so that this feature can be prod deployed and the sales team can use it at the expo - any ideas what's gone wrong given there shouldn't have been any breaking changes?
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-wave-0f4ddd903-759.westeurope.azurestaticapps.net
Despite not having done a major version change for STYLE, STYLE seems to broken and I can no longer
npm run serve
... @ChrisBaidoo @cooper667 we ideally need this fixed on Monday so that this feature can be prod deployed and the sales team can use it at the expo - any ideas what's gone wrong given there shouldn't have been any breaking changes?
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-wave-0f4ddd903-759.westeurope.azurestaticapps.net
@joshuajames-smith needs a change in Style but think that can come in another PR?
Description
The idea here is that when we toggle the Super Marker on we calculate a super-pixel image (should have region approximately the size of the brush but instead of circles they should snap to intensity boundaries).
This should make annotating images quicker in many cases as the details kind of get "auto caught".
At the moment you can only add one superpixel at a time (i.e. click to add). I have some experimental code for being able to drag and fill a series of superpixels but it's mega slow (https://github.com/gliff-ai/annotate/blob/7654e743277dadd129a23e7db40265a436c89010/src/toolboxes/paintbrush/Canvas.tsx#L514).
There is a lint error caused by https://github.com/gliff-ai/annotate/blob/7654e743277dadd129a23e7db40265a436c89010/src/toolboxes/paintbrush/slic.ts#L365 and for some reason the disable isn't working? @cooper667 ?
I need an icon for the button @joshuajames-smith - maybe with an alpha symbol as discussed.
@philhallbio - this will need documenting before the Expo.
Testing
No tests added yet - what do people think would be useful to add? (Will make issues for them)
Documentation
Needed.
Checklist: