Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Css reference (work in progress)#4

Open
burodepeper wants to merge 2 commits into
atom:masterfrom
burodepeper:css
Open

Css reference (work in progress)#4
burodepeper wants to merge 2 commits into
atom:masterfrom
burodepeper:css

Conversation

@burodepeper
Copy link
Copy Markdown
Contributor

As a side project I've been looking into language-css and at some point I thought, heck, why don't I just create a reference file with pretty much every possible selector, attribute-name, and attribute-value.

I think it is more in the scope of language pack development, but I am thinking of distilling a substantial range of different selectors from all the stuff I gather. Perhaps a directory with full references might be nice in the future.

@simurai
Copy link
Copy Markdown
Contributor

simurai commented Sep 24, 2015

Wow.. that's huge.

Hmm.. it almost feels too much for this project. 😁 I was more thinking language-examples should only give a hint to theme authors how languages look and not "test" every possibility.

  1. A quick overview
  2. Some more common examples and maybe a few edge cases.

In your reference, if something looks wrong, it most likely would need to be fixed in language-css and not in themes. Maybe a PR to https://github.com/atom/language-css/tree/master/spec would be a better place?

Also, I don't think we could match the same completeness for all the other core languages. Well, at least not by me. 😉

@burodepeper
Copy link
Copy Markdown
Contributor Author

Haha, it is definitely too much, but I wanted to gauge your reaction.

I agree that language-examples should give a hint to theme authors, but I think it should try to cover as much as possible in as little as possible. When I'm done with this, you'll get a better idea of what I think the hint should be.

And yeah, I'm definitely going to PR it to language-css (scss/less) too. I've been rewriting language-css as an exercise to get myself familiar with languages packs (and language references), and I got in a little over my head. But, I've also exposed some errors along the way.

And don't worry about the completeness for other core languages. You'll see after I've 'completed' this PR what I think is a good set of hints. I've got ideas for html, javascript, php, markdown, as well. And there sure must be some nutbags like me who can do the same for the others.

@simurai
Copy link
Copy Markdown
Contributor

simurai commented Sep 24, 2015

Sounds good.

btw. this repo now has a new home on atom-community.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants