Giters

TheNitesWhoSay / RareCpp

Creating a simpler, more intuitive means of C++ reflection

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Project Rebranding

TheNitesWhoSay opened this issue · comments

commented

As I expand the header libraries available on top of reflection, the individual libraries will need some way of succinctly and uniquely referring to them. Right now you'd have to say something like "The JSON library built on top of RandomAccessReflection", which is very clunky.

I'm thinking to call the larger project RareCpp ("Random Access Reflection & Extensions in C++") - then the individual libraries can be referred to as RareCpp[Library Name], e.g.

  • RareCppReflection
  • RareCppJson
  • RareCppXml
  • RareCppMapper
  • RareCppORM
  • RareCppREST
commented

I prepped code to have this be renamed "RareCpp"... but now I'm also considering the inverse... "CppRare"
RareCppReflection <--> CppRareReflection
RareCppJson <--> CppRareJson
RareCppXml <--> CppRareXml
RareCppMapper <--> CppRareMapper
RareCppORM <--> CppRareORM
RareCppREST <--> CppRareREST

The advantage with the latter is that you can more easily drop the prefix when the context is already clearly C++, and just say "RareJson", "RareXml" "RareREST" etc. And when expanding the acronym you can more naturally get something readable...

RareCpp = "Random Access Reflection & Extensions in C++"
CppRare = "C++ Random Access Reflection & Extensions"

RareCppJson = "RARE C++ Json Library" = "RARE Json Library"/"RareJson Library"
CppRareJson = "C++ RARE Json Library" = "RARE Json Library"/"RareJson Library"

The advantage of the former is the cumulative name for all of this reads "Rare C++", which is quite a bit more catchy than "C++ Rare" or "CppRare"...

commented

Perhaps straddling both naming orders and titling certain things one way or the other is the best solution here...

The git repository/visual studios solution could be "RareCpp" and when expanding anywhere around the RareCpp documentation specifically refer to it as "C++ Random Access Reflection & Extensions".

At this point I don't have explicit visual studios projects or folders referring to any RARE extension, I could simply refer to them as "RareJson"/"RareJSON" and never use the Cpp in the context of narrower extension projects and only use Cpp when referring to the larger solution.