Live data from Hacker News

Show HN: CSS Scan – Instantly check or copy computed CSS from any element

guivr.github.io

41–50 of 52 posts

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#41
post #37

Can you share anything about how many sales you've made? I'm curious how willing developers are to pay for tools like this. I'm working on selling a Chrome extension as well so I'd be super interested in learning more.

Hey seanwilson, I actually made a lot more sales than I expected. $500 Revenue so far. 167 sales :) I'm also planning to write an article, I'll update stats on twitter (@gvrizzo)

By the way, how does the Gumroad integration and license checking work? You get the extension files to download on purchase?

I'm integrating Paddle for payments into my extension. It requires you to implement user accounts or license keys yourself though.

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#42
Isn't this literally getComputedStyle[1]? Chrome devtools already has a 'computed' section which shows the same thing. What additional functionality does this provide that I'm missing?

[1] https://developer.mozilla.org/en-US/docs/Web/API/Window/getC...

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#43
post #31

Earlier quoted context omitted.

I'd vote for web components over React, as some of us use Vue or Angular...

I still don’t understand why Angular hasn’t died out. It’s very hard to understand and the tutorials can’t simplify that because it’s just inherently very complex. It feels highly over engineered like classical Java. Instead of allowing you to opt into more complex features as needed like a good framework should do, it forces you to learn its steel curve up front!

It has improved quite a lot, it's a joy to code in in the newest versions. You do need to invest a bit of time to learn it but it's well worth it

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#44
post #2

Hello Hacker News! Creator here, happy to answer any questions! :) I decided to build CSS Scan to get computed styles with no hassle and in real-time. It's faster than using browsers' Developer Tools and give all of the styles in the shorthand way, this means no messy CSS or styles being overwritten. You can also copy to clipboard by just clicking on it. P.S.: Of course this is only for use cases you want to have an…

I want to know more about the bicycle tour this is paying for!

Glad you got off the sofa a few times during the code-a-thon, you could have spent all that time in front of a games console, so well done for completing the task.

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#45

Isn't this literally getComputedStyle[1]? Chrome devtools already has a 'computed' section which shows the same thing. What additional functionality does this provide that I'm missing? [1] https://developer.mozilla.org/en-US/docs/Web/API/Window/getC...

Not identical, just similar. getComputedStyle gets the default styling of the browser too, and also some properties that are used just for rendering.

Besides that, you'd have to use the console for each element you want. With CSS Scan you just have to hover it.

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#46
post #37

Earlier quoted context omitted.

Hey seanwilson, I actually made a lot more sales than I expected. $500 Revenue so far. 167 sales :) I'm also planning to write an article, I'll update stats on twitter (@gvrizzo)

By the way, how does the Gumroad integration and license checking work? You get the extension files to download on purchase? I'm integrating Paddle for payments into my extension. It requires you to implement user accounts or license keys yourself though.

What are you currently doing to handle licensing outside of Paddle? I'm guessing you're building an Electron app?

Re: Show HN: CSS Scan – Instantly check or copy computed CSS from any element

#50

Great tool! I'd like to see you keep going with this. Quick feedback: it would be useful to copy the entire ruleset, including the selector and brackets (as an option). Further if you can reach into source via document.stylesheets, grab the selectors from source (as another option).

It'd actually be great to see something like this absorbed into browser dev-tools.
Post reply on HN