Re: EMY - receiving an asynchronous request

2018-03-22 Thread Rune Back
I have only ONE section: ** In the *function goingTo(val)* I also have *document.getElementById("viewTitle").innerHTML=getTitle(val)* which updates the title, so the user gets the feeling of moving between different screens. I don't use *emy.ajax()*, but I have made my own function for it. R

Re: EMY - receiving an asynchronous request

2018-03-22 Thread Remi Grumeau
> I like Emy. Me too :) > I use callbacks only in order to send/receive something to/from another App > via the server. I've also made it possible for making a backup of the ldb in > the server and of course to retrieve the ldb from there. At leat 95% of my > code is JavaScript. I tiny

Re: EMY - receiving an asynchronous request

2018-03-22 Thread Rune Back
*I like Emy.* I use callbacks only in order to send/receive something to/from another App via the server. I've also made it possible for making a backup of the ldb in the server and of course to retrieve the ldb from there. At leat 95% of my code is JavaScript. I tiny little bit of my code is in

Re: EMY - receiving an asynchronous request

2018-03-21 Thread Remi Grumeau
Humm I'd rather put this in a DIV rather than a SECTION then. Emy uses all direct SECTION tags child nodes as views. So it won't bother you with this DIV (just put a display:none on it would be enough) But ... if you're doing the ajax call on your side and uses one single section to replace