Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove “block” terminology from client #105

Open
kpreid opened this issue Feb 19, 2018 · 2 comments
Open

Remove “block” terminology from client #105

kpreid opened this issue Feb 19, 2018 · 2 comments

Comments

@kpreid
Copy link
Owner

kpreid commented Feb 19, 2018

The word “block”, as used in the JS client code, actually means “remote object”, or more precisely “object composed mostly of Cells in a particular fashion”, corresponding to ExportedState on the server side. This is left over from very early design where such objects were almost all also GNU Radio blocks on the server side.

Find better vocabulary and use it.

@kpreid kpreid added this to Outcome in Refactoring Feb 26, 2018
@kpreid
Copy link
Owner Author

kpreid commented May 10, 2019

Today I thought of referring to this category of objects as Cellular. Pros: Short and descriptive. Cons: Possibly confused with cellular radio; is more an adjective than a noun.

If I did use this name I would rename both “block” and “ExportedState”.

@kpreid
Copy link
Owner Author

kpreid commented Jul 15, 2019

Another piece of the puzzle is ReferenceT which is the server-side value type referring to ExportedStates. This is arguably a different concept, because it is named what it is because it refers to a value that should be proxied rather than copied to the client — but that's more of a statement about what the type is guaranteed to contain than what it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant