Get desktop application:
View/edit binary Protocol Buffers messages
* array/list/matrix/frame type
Used in:
* unifying call and response, since there are some fuzzy cases, callbacks, and so on. it makes sense for this to be a single message with a switch. FIXME: let's revert "callback" to a separate field for clarity, even though it has the same type as function_call; we have space. FIXME: we now have two errors -- one in here (top level) and one in variable (via result). is that useful? it certainly is confusing. I suppose it distinguishes between errors in the function call and results that are errors...
FIXME: this can go? should we always require full transactions?
FIXME: use error type? [yes, work towards that]
console maybe should be a separate root message, it doesn't need a response
can we just include a "repeated" element as a union member? [A: no]
Used in:
* distinction between calls and accessors (and accesor type)
Used in:
,* why not have a single string and then split on the RX side?
Used in:
* although colors are passed as 4x 32-bit, they're actually only 8 bits each. FIXME: who passes colors as 128 bits? that's not a thing.
Used in:
* complex numbers
Used in:
* consolidating function call, callback, COM function call, and control/system calls with arguments
Used in:
* console message
Used in:
Used in:
* for COM enums
Used in:
* error has a type and/or message
Used in:
* error types
Used in:
* now we're getting less and less general. not sure that's a good thing.
Used in:
d'oh (don't use the name "interface")
FunctionList functions = 3;
* this type describes a function. adding type so we can reuse this for COM
Used in:
,* to date, we've been constructing function descriptions by packing them in normal variables. for R, we can use the "name" attribute to identify them. that's not available in Julia (and wouldn't be in some other languages either). this results in inconsitent data arriving at Excel, which requires language-specific handling. in an effort to normalize this data, and recognizing that this message scheme is application-specific, we'll define specific types for function descriptors (AND com calls, below). this type can be used for both the function itself and arguments.
Used in:
not used atm
added for COM
* list of functions. union type can't include arrays, so we need an array.
Used in:
* we're now adding graphics to support a console graphics device in R. might extend to julia, although that will probably be based on GR and so a little simpler. packing in a variety of different parameters here, this may need to get streamlined... we can also do some creative reuse.
Used in:
flag -- should go in context?
flag
device type
Used in:
this is a three-value enum (actually defines, but only 3 states)
also a three-value enum
this is another set of flags
Used in:
Used in:
Used in:
* sheet reference
Used in:
* basic variable type, optionally named
Used in:
, , , ,taking over, maybe drop the other one