Open skopp opened 11 years ago
Hi Rashaad. Thanks for the feedback.
The main purpose of the project is to extract CSS from HTML document. I had no intention of showing where these classes or IDs are extracted when I started to the project. It might be useful to remove inline styles from the HTML, but I don't see any point to highlight the places of extraction.
Ah, ok. Thanks for clarifying. Do you think something like that could be possible (not neccessarily with/using this project specifically), if not existent already? And if possible, any idea how it could be done?
Sorry to bombard you with questions, but why do you say you "don't see any point to highlight the places of extraction."? I can think of a plethora of reasons.
Of course, it could be implemented. However, as I said before, the main purpose is to extract CSS from HTML document. I said "I don't see any point to highlight the places of extraction." because I can't think of any connection between extracting CSS -purpose of the tool- and seeing the place where they're extracted. Can you please explain why do you want to see the places of extraction?
This is an amazing project, but I feel there are a few things needed to make it truly essential for devs.
I'll mention them as I conceptualize them, and/or get the chance - I can't quite put my finger on it all just yet. But will start off with the following:
I tried using it with a chunk of code - oldschool HTML code with both linked and embedded style rules. Got an output of classes, id's, parents and children... but the problem is that I couldn't see any way of telling where they were pulled from other than manually sifting throught the original code (which defeats the purpose of this app).
Or am I doing it wrong?