Give the stars for each lib?

[Greedquest]

You can add little badges to show how many stars each repo has on Github. This is a quick way to assess popularity/quality.

If you can face it I think you can also link the badge to the github in the markdown:

• stdVBA - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

• - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

• - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

• - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

• - A framework by Japanese author RelaxTools. Contains numerous classes, interfaces and forms.

lots more nice options here https://shields.io/badges/git-hub-repo-stars . Personal favourite is the one with the github logo, so you know what you're clicking out to, and so it's more obvious why some resources don't get the badge.

 [![GitHub Repo stars](https://img.shields.io/github/stars/sancarn/stdVBA?label=stdVBA)](http://github.com/sancarn/stdVBA)

[DecimalTurn]

Could be nice indeed.
An alternative would be to keep the text label and just display the number of stars. This way the name of the ressource is still searchable (Ctrl+F) and if there is a problem with the image, we don't lose the label. Also, it creates less disparities between ressources available on GitHub vs outside of GitHub.

Eg.:

stdVBA - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

stdVBA - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.

[Greedquest]

100% Agree for Ctrl F.

Couple more styles (I think having 2 yellow stars is a bit confusing, maybe there is a white version?)

• stdVBA - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.
• stdVBA - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.
• Rubberduck - An open-source COM add-in project that integrates with the Visual Basic Editor to add modern-day features to the familiar IDE. Works in VBA6, VBA7.x (x86/x64), and yes, in VB6 too!

You can do the same thing with the tooltip (see 3rd entry)

* [![p_win]](#-) [![a_all]](#-) [stdVBA](http://github.com/sancarn/stdVBA) ![GitHub Repo stars](https://img.shields.io/github/stars/sancarn/stdVBA?style=flat&logo=github&label=&color=5C5C5C) - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.
* [![p_win]](#-) [![a_all]](#-) [stdVBA](http://github.com/sancarn/stdVBA) ![GitHub Repo stars](https://img.shields.io/github/stars/sancarn/stdVBA?style=flat&logo=github&label=) - A framework containing numerous classes for automation and utility. Focuses on code compactness and long-term maintainability.
* [![GitHub Repo stars](https://img.shields.io/github/stars/rubberduck-vba/Rubberduck?style=flat&logo=github&label= "GitHub Repo Stars")](https://github.com/rubberduck-vba/Rubberduck) [![p_win]](#-) [![a_all]](#-) [![o_inst]](#-) [Rubberduck](https://rubberduckvba.com/) - An open-source COM add-in project that integrates with the Visual Basic Editor to add modern-day features to the familiar IDE. Works in VBA6, VBA7.x (x86/x64), and yes, in VB6 too!

Shame everything has this weird dip in it

[sancarn]

This is an interesting idea. Playing devil's advocate, I do wonder what the relevance is... For the sake of argument let's say we included both:

• Cristian's fast dictionary
• Tim's dictionary

In my mind Cristian's is orders of magnitude more awesome despite it having 10% of the star count. So what exactly is the star count meant to represent here?

From my perspective if it's in this list, we all believe it's awesome. So the star count is borderline irrelevant.

Open to opinions here.

[Greedquest]

Cristian's will overtake I'm sure ;) Even if it doesn't, 5 stars vs 100 stars to me is a measure of maturity as well as quality. Tim's has had a lot more field testing, and that's one of the factors to consider when browsing for a tool/framework. The description can highlight functional/performance differences.

It's like with stack overflow answers. In your head you normalise the vote count by dividing by age, niche problem area, "brand" of the user who posted it (more so on Code Review). So for same niche problem area, I know the relative brand and age of those two repos and can normalise the star count

[sancarn]

@Greedquest Year really a better measure would be stars/age indeed. I think this kind of change would have to wait until we are officially on awesome. It's already a bit of a stretch including symbology, let alone star rating or otherwise.

Edit: Btw @Greedquest - Don't suppose you ever added your private accessor code review to a github repo? I think I found it

[Greedquest]

@sancarn Personally I would find the stars useful, at the end of the day that's one of the main things I was looking for clicking through the list. Appreciate the competing need to keep in the format of Awesome-Lists, I didn't know that was even a thing.

Glad you found my repo - it contains the final original VBA as well as the new version using twinBASIC (that eliminates a lot of code as you can declare COM interfaces in tB, so a lot less vtable hopping)