Lab logging vs CODAP

[Piotr Janik]

Hi,

1. Is CODAP is also interested in all the new log messages (e.g. interaction with buttons, sliders, checkboxes, etc.) or not?

2. If so, where are all the interactives that talk to CODAP hosted? lab.concord.org only or some external sites too?

I can send all the new log messages to CODAP too, it's an easy task, but then I'd like to process JSON configurations a bit. I'd like to move all logging code to a new LoggingController and existing ExportController would be focused only on CODAP-specifc data export. I think that JSON configurations should reflect that ("exports" and "logging" sections).

It means it would be kind of breaking change. I could also workaround that in code and make it fully backward compatible, but assuming we have full control over all the interactives that talk to CODAP, I think it's better to run a simple script over them once rather than leave hacky code in Lab.

Thanks,

Piotr

[Dan Damelin]

See below. 

On Nov 16, 2015, at 5:11 AM, Piotr Janik <janikp...@gmail.com> wrote:

Hi,

1. Is CODAP is also interested in all the new log messages (e.g. interaction with buttons, sliders, checkboxes, etc.) or not?

Yes CODAP would be interested in all the log messages. It was initially done the way it is done as a shortcut to capture the most important changes. However, if there was new information available we would log that too.

2. If so, where are all the interactives that talk to CODAP hosted? lab.concord.org only or some external sites too?

They are all hosted at lab.concord.org

I can send all the new log messages to CODAP too, it's an easy task, but then I'd like to process JSON configurations a bit. I'd like to move all logging code to a new LoggingController and existing ExportController would be focused only on CODAP-specifc data export. I think that JSON configurations should reflect that ("exports" and "logging" sections).

It means it would be kind of breaking change. I could also workaround that in code and make it fully backward compatible, but assuming we have full control over all the interactives that talk to CODAP, I think it's better to run a simple script over them once rather than leave hacky code in Lab.

Running a script to fix current lab interactives would be better. 

Thanks,

Piotr

--
--
----
post message :cc-dev...@googlegroups.com
unsubscribe: cc-developer...@googlegroups.com
more options: http://groups.google.com/group/cc-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Concord Consortium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cc-developer...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.