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 overall vision of the styles; it's far from being a full alternative to Inspect Element.
It took me 50 hours and 17 minutes to develop. Inspired by @levelsio I recorded all the development and made a speed video. If you want to check it:
https://www.youtube.com/watch?v=OtsNNXpXcYs
Just had a chance to check it out on Chrome. Looks cool! Another feature that might be useful is to have links back to the related stylesheets via css source maps.
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!
I really enjoyed Angular 1.x, was not happy with the 2.0 version (other then they fixed some critical performance issues with scaling websites). It was perfect for making simple single page applications for internal use at an an eCommerce company. POS, Order Processing, RMA processing, Research, competition and price controls, inventory & warehouse management, etc. I use ReactJS for large applications these days.
I think it's due to its enterprise users and customer bases, and never underestimate the power of legacy code base inertia that often keep these types of things going.
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.
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?
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).
Hey! I have good news! Just updated the app. Now you can copy the selector name! If you use Chrome, the extension will update itself. On Firefox, I'll implement auto-update functionality tomorrow. More updates to come!
Looks super useful but I don't want to buy before I try. The landing page says "for the price you want", but the product page has a 1.99+ and I can't enter less than that.
This is really GREAT! The timing is perfect, I have to rewrite a whole bunch of CSS for a project and now I can easily pick and choose what I want to port over to the new layout.
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)
I've used a similar tool[1] before to convert all styles of an element to inline styles in order to copy it into a more isolated setting for testing, and it worked pretty well for me. There were a lot of manual steps for me to do this though, so CSS Scan seems like a pretty nice "one click" alternative.
This looks super useful! Is it also able to grab media queries and other styles that may not be applied at the current time (like style based on a parent class that gets added later to trigger an animation)?
This is great. I've been looking for a good way to be able to identify between active styles and legacy css that seems to build up over time, and this is a pretty neat way to do it.
HN has a pretty strong history of people posting their/other's projects, commercial or otherwise and getting feedback. So in a way, every Show HN is an advertisement. I don't believe this should be discouraged. I personally find the Show HN posts far more interesting and closer to HN roots than the typical tech/political news that dominates the front page these days.
I mean a synonym for "advertise" is literally "show". What I really have a problem with is when someone else hijacks someone's thread with their own agenda.
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 overall vision of the styles; it's far from being a full alternative to Inspect Element.
It took me 50 hours and 17 minutes to develop. Inspired by @levelsio I recorded all the development and made a speed video. If you want to check it: https://www.youtube.com/watch?v=OtsNNXpXcYs