Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Gregg Roemhildt
@roemhildtg
parseInstanceData still is never called, on ios, unless I move it up the list. Is there a good way to know where to place it?
Justin Meyer
@justinbmeyer
@roemhildtg only ios?
Frank Lemanschik
@frank-dspeed
is some one familar with the part what exactly is incompatible with can-component ? https://canjs.com/doc/can-ejs.html#BasicExample
i can't imagin a situation
Gregg Roemhildt
@roemhildtg
Yeah it was working on windows Firefox Chrome just not ios. Took forever to get a debugger working but it showed those methods were ignored. Switched the order and it started working.
Frank Lemanschik
@frank-dspeed
do we got something like this?
SproutCore does one thing which very few frameworks do propertly: being a native like API framework, including built in application state chart
Frank Lemanschik
@frank-dspeed
i think thats already inside right with the viewModel backup rollback stuff?
Frank Lemanschik
@frank-dspeed
CDNUSSR joke is Content Delivery Network Unit Server Side Rendering
Eben
@eben-roux
hello
Mohamed Cherif Bouchelaghem
@cherifGsoul
Hello @eben-roux
Frank Lemanschik
@frank-dspeed
hello again
what do we wanna do today :D
Eben
@eben-roux
it seems as though when I set an attribute on my model then it results in some infinite loop
does that sound familiar?
Frank Lemanschik
@frank-dspeed
ehm nope
but i know a way to produce a infinity loop
Eben
@eben-roux
almost as if the method observes the change and then the change occurs in the method and then back to observing the change
lol
I'm sure you do
Frank Lemanschik
@frank-dspeed
if your defining a setter with a start value that returns a value
Eben
@eben-roux
if you have a fast enough machine then an infinite loop only takes 6 seconds to complete
Mohamed Cherif Bouchelaghem
@cherifGsoul
almost as if the method observes the change and then the change occurs in the method and then back to observing the change
Frank Lemanschik
@frank-dspeed

foo: {
  value: 1,
  set(val) {
    setTimeout(() => { this.foo+=1 }, 1000);
    return val;
  }
}
Mohamed Cherif Bouchelaghem
@cherifGsoul

what you mean by that

almost as if the method observes the change and then the change occurs in the method and then back to observing the change

Frank Lemanschik
@frank-dspeed
this will automatic infinty loop
and what cherif says is also right if you change the value the setter gets recalled and does what ever it does
Eben
@eben-roux
let me see if I can put together a jsbin to illustrate
Mohamed Cherif Bouchelaghem
@cherifGsoul
ok
Eben
@eben-roux
of course I cannot reproduce this with a simple jsbin :( --- typical
anyway, I worked around the issue
what I was doing was actually "sub-optimal"...
Frank Lemanschik
@frank-dspeed
ok
Eben
@eben-roux
using {{#if}} render components or not is actually not the best way to go
Frank Lemanschik
@frank-dspeed
i am happy that we could help you :)
the if thing works great
what else you can do ?
Eben
@eben-roux
it is way better, IMHO, to rather bind to a class attribute like hidden
Frank Lemanschik
@frank-dspeed
hmmm
i understand your issue :)
yes the hidden stuff is also ok
Eben
@eben-roux
I reckon something goes wonky with the binding since, in effect, all the bindings have to be broken down and rebuilt
Mohamed Cherif Bouchelaghem
@cherifGsoul
{{#if}}} render components?? you mean you have a condition to render a component?
Eben
@eben-roux
had the same issue with Ember
@cherifGsoul yip
so mainly I guess it would work ok
Mohamed Cherif Bouchelaghem
@cherifGsoul
it would work
Eben
@eben-roux
in some complex binding scenarios I can understand that a framework would get itself in a bind