These are chat archives for canjs/canjs

29th
Dec 2016
it seems to not be working as expected
Thomas Sieverding
@Bajix
Dec 29 2016 02:48
Use type: ‘*'
Gira Minus
@gKreator
Dec 29 2016 02:49
same issue
Thomas Sieverding
@Bajix
Dec 29 2016 02:49
Also I think you need to do {^@test2}
Gira Minus
@gKreator
Dec 29 2016 02:50
could you perhaps show me what you mean by cloning the jsbin?
I tried what you said and it is not working still
Gira Minus
@gKreator
Dec 29 2016 02:56
Thomas Sieverding
@Bajix
Dec 29 2016 03:07
Hmm maybe this doesn’t work how I expected
Gira Minus
@gKreator
Dec 29 2016 03:07
Yeah same?
Any ideas on this?
Thomas Sieverding
@Bajix
Dec 29 2016 03:08
What’s your use case btw?
Last time I had tried to do this was before 3.x, and it was absolutely awful to do back then
Gira Minus
@gKreator
Dec 29 2016 03:08
I want to fire a function in the scope of the inner component from the outer one
Thomas Sieverding
@Bajix
Dec 29 2016 03:09
I know what you want to do, but why
Gira Minus
@gKreator
Dec 29 2016 03:10
My inner component is technically a stopwatch, i want to start the stopwatch from the parent component
Thomas Sieverding
@Bajix
Dec 29 2016 03:10
You could do type: compute then use @ to export a compute
You’re better off managing that through state
For example, by having active true/false and cross-binding
Gira Minus
@gKreator
Dec 29 2016 03:11
yeah makes sense
Thomas Sieverding
@Bajix
Dec 29 2016 03:12
For more complex use cases you can pass around maps
The the state based approach is almost always better
Frank Lemanschik
@frank-dspeed
Dec 29 2016 09:23
in bigger applications you store the state in the maps
as the state gets composed
you never retrive and send full state objects
thats where websockets become effectiv
if you do a lot of partial upgrades to state
if you transfer always full state rest is much more fast
Justin Meyer
@justinbmeyer
Dec 29 2016 16:11
@Bajix some changes to the stream libs: canjs/can-define-stream#17