Re: EMY - receiving an asynchronous request

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

> 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

*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

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

Re: EMY buttons

R / Only postpone *bad *things, not good ones! / R :) 2018-01-26 16:01 GMT+02:00 Remi Grumeau : > Hi rune, > > I guess the 100% doesn’t take in account extra margin or padding between > them. Or just the extra pixel inline-block elements can have next to each > others. >

Re: EMY buttons

Hi rune, I guess the 100% doesn’t take in account extra margin or padding between them. Or just the extra pixel inline-block elements can have next to each others. Classic box-model issue. Segment is here to help you out with it yes, using table layout model. But nowdays we have flexbox &

Re: EMY

> ​This rose a lot of questions, until I checked your link below. (I haven't > checked the code as yet.) So you use the password as the key AND you don't > store the password locally, at least not locally. - Right? At very worse, you can store a hash of the password locally, and compare this

Re: EMY

Hi again! ​​ > Key should be set by the user on login. > Never stored in your code. If you store the decryption key in the code, > then don't bother encrypt data. > ​This rose a lot of questions, until I checked your link below. (I haven't checked the code as yet.) So you use the *password as

Re: EMY

> > ​I've got Kb:s in my LDB now and no problem so far.​ - ​I couple of years >> ago I stumbled somewhere over a code of a simple local database, but I >> can't find it anymore. >> >> >> Less than a Mb you should be fine. >> > > ​Great! - I had been wondering/worring about what would happen with

Re: EMY

Remi! > ​I've got Kb:s in my LDB now and no problem so far.​ - ​I couple of years > ago I stumbled somewhere over a code of a simple local database, but I > can't find it anymore. > > > Less than a Mb you should be fine. > ​Great! - I had been wondering/worring about what would happen with the

Re: EMY

> ​I've got Kb:s in my LDB now and no problem so far.​ - ​I couple of years ago > I stumbled somewhere over a code of a simple local database, but I can't find > it anymore. Less than a Mb you should be fine. Mozilla LocalForage ? >> The install prompt is a new spec only available on Google

Re: EMY

Thank you, Remi!​ If you have dozens of Mb of datas, then LocalStorage is a dead end. It has > been designed to be a local cookie (aka not available server-side, so not > sent in every http request). So just to store a string or two (username, > json string of params, ...), not megabytes of text.

Re: EMY

Hi Rune, If you have dozens of Mb of datas, then LocalStorage is a dead end. It has been designed to be a local cookie (aka not available server-side, so not sent in every http request). So just to store a string or two (username, json string of params, ...), not megabytes of text. IndexedDb

Re: emy backButton

Always use *emy.goBack()* !! That's VERY important Remi On Fri, Jun 6, 2014 at 8:22 AM, Rune Back rune.b...@gmail.com wrote: Hi Remi There was a bug in my code. Got it working. - Sorry about that. One more thing: *emy.goBack()* and *window.history.back()* - Can I use either one?

Re: emy backButton

eh eh :) If you don't play the rules, be ready to face those kind of problems ;) Emy deals with going from screen A to screen B by itself. If you want no transitions between screens, just set emy.transitionMode to none

Re: emy backButton

Hi Remi No good Remi. 70%?!! - I was hoping for better news :(( So you go from screen A to B and to C. At C you update some information which means you also need to update screen A and B. So after the update you go straight to screen B and before doing so you update the screen and everything's

Re: emy backButton

Nope, no easy build-in solution. Just like with native apps, you have to do your homework :) By the way, you have events to help you with that. http://www.emy-library.org/documentation/1.0/core-documentation.html#event-custom beforetransition / aftertransition Those events are triggered each

Re: Emy list editing

Btw, added to the milestone list: https://github.com/remi-grumeau/emy/issues/milestones?with_issues=no Anybody to work on that? Remi Le lundi 22 avril 2013 14:05:25 UTC+2, Remi Grumeau a écrit : The shared concept is to keep the main core files small clean. At this stage, both library are

Re: Emy list editing

On Sunday, April 21, 2013 12:24:03 PM UTC-7, Remi Grumeau wrote: Hi Will, What do you mean exactly by list editing? This mailing-list ? A specific demo app? Or a real UI component like this: http://photos.appleinsider.com/12.01.04-Editing.jpg This. The standard TableView editing

Re: Emy list editing

The shared concept is to keep the main core files small clean. At this stage, both library are mainly ready-to-use CSS UI elements + a bit of Javascript to deal with sliding transitions, browser back forward buttons ajax submission. That's pretty much it. That's why any other

Re: Emy list editing

Hi Will, What do you mean exactly by list editing? This mailing-list ? A specific demo app? Or a real UI component like this: http://photos.appleinsider.com/12.01.04-Editing.jpg This last screenshot could be a nice plugin/extension module, definitely something i'd be happy to work on with