Rename Proposal

[Jamie Thomas]

Based on recent changes to push logic from ExoWeb and ExoRule upstream to ExoGraph, the ExoGraph library has dramatically increased its model-centric behavior.  It now exposes a significant amount of model metadata such as property labels, and now includes robust formatting with .NET format specifiers and custom entity format expressions.  As such, while writing the code and working on the documentation, I continue to feel more convinced that the name of the library itself does a poor job of explaining what it does.

 

My proposal, as part of moving everyone to the updated Server Rendering branch, is to rename ExoGraph to ExoModel.  This is a fairly easy change to make based on my analysis because the projects that use ExoGraph barely ever reference the types within this library directly, instead leveraging ExoRule and ExoWeb to perform the heavy lifting.  Also, the word Graph is infrequently used, so a judicious search replace does not take long to perform.

 

For reference, I converted all of the public libraries to use this new name (including local variables and comments) as well as Leisure Star, in less than an hour.  The only thing I have not does is perform the folder renames, as this is something I would prefer to coordinate with Bryan on.  Additionally, if this is something that would be easier to do immediately following the merge of Server Rendering, I would be fine going through the process again at that point, knowing that it is fairly quick and that there were *no* caveats (simple case sensitive search replace on *.cs would have worked fine had I known).

 

Please vote using the voting buttons to let me know your thoughts on this.  If the voting buttons do not work, just email me directly.

 

Thanks,

Jamie

[Keith La Force]

I believe this makes sense, and it is obviously better to make these changes while the project is still maturing instead of waiting until it is being leveraged by other projects besides ExoRule and ExoWeb.

 

Keith