HTML has image maps. It's been there since longer than many of the people who might read this post have even been alive. You don't need SVG and JS for this.
What's the benefit of image maps vs SVG here?
Making my bookshelves clickable
21–30 of 30 posts
Re: Making my bookshelves clickable
#22Very nice project.
Seems like it would be the ideal kind of thing for AR/XR.
Re: Making my bookshelves clickable
#23HTML has image maps. It's been there since longer than many of the people who might read this post have even been alive. You don't need SVG and JS for this.
It is certainly odd that they didn't use them, especially since image maps are mentioned at the beginning of the article.
You'd still need something to outline clickable areas. Map areas do have a visible outline when focused, but I doubt that there is much else.
Re: Making my bookshelves clickable
#24Works great in Vision. But now I want to get a browsable spacial model when I tap any book in my field of view
Cool demos are so frustrating!
Re: Making my bookshelves clickable
#25I wish when people published things like this they would take the time to notice that their requirements.txt and READMEs don't actually work; e.g., try it out in a fresh VM or container divorced from their working environment. Not even their arguments match what's in the README.
Re: Making my bookshelves clickable
#26I wish when people published things like this they would take the time to notice that their requirements.txt and READMEs don't actually work; e.g., try it out in a fresh VM or container divorced from their working environment. Not even their arguments match what's in the README.
It blows my mind how much effort people, particularly python ml people, put into creating, training, blogging, promoting their github repo and then give so little thought to whether anybody will be able to use it. You're lucky if you get an incomplete and unversioned requirements.txt and no mention of what python version was used. If it requires conda, just give up. You might get an injunction to "install pytorch" and you're on your own.
Re: Making my bookshelves clickable
#27Looks interesting, but surely image maps (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ma...) would be more suitable? no need for `onclick` handlers either then.
(They are mentioned at the start as an option so maybe there was a reason they were disregarded)
Re: Making my bookshelves clickable
#28Earlier quoted context omitted.
It is certainly odd that they didn't use them, especially since image maps are mentioned at the beginning of the article.
You'd still need something to outline clickable areas. Map areas do have a visible outline when focused, but I doubt that there is much else.
> something to outline clickable areas
Any graphics editor will let you do that.
Re: Making my bookshelves clickable
#29I would really love a control-f for the real world. Imagine you have a list of wines you want to try, or used books you’re hoping to buy. In the store you open your phone and scan the shelves with your camera and if it finds any matches from your lists, it shows you them on the screen.
Same. I've imagined 'spines.com' for books, where the work of linking book spines to ISBN's, etc, has been crowdsourced and you can point your phone camera at a shelf and look up reviews, etc.
When I visit spines.com it does a redirect to a self-publishing tool called booxAI.com . I don't think that's what you were referring to, or did the spines tool sell their domain name?
Re: Making my bookshelves clickable
#30HTML has image maps. It's been there since longer than many of the people who might read this post have even been alive. You don't need SVG and JS for this.
What's the benefit of image maps vs SVG here?
Weird question, but let's give it a shot. Off the top of my head:
Standards, semantics, simplicity of implementation + time-to-implement, cost at runtime...
What's the impetus for re-implementing image maps with JS instead of just using the browser-native implementation?