*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 the server.

The link may look like this: *href="javascript:goingTo(11);"*

In *goingTo(val)* I have *switch (val)* ...

...
*case 11: MAKE_MAIN(); break*
...

*MAKE_MAIN()* stuffs the html code into a variable *dump*, and finally I
have
*document.getElementById("HOME").innerHTML=dump*

I have two variables "comingFrom" and "whereAmI". I have a back button up
in the right corner with goingTo(comingFrom). As I already mentioned, it's
very fast.

*If not Emy, what then?*

Rune


2018-03-22 0:31 GMT+02:00 Remi Grumeau <remi.grum...@gmail.com>:

> 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 its content without any navigation transition, why using
> Emy ? :)
>
> Also, <div id="dump" hidden>, you forgot a "
>
> Remi
>
> Le 21 mars 2018 à 16:49, Rune Back <rune.b...@gmail.com> a écrit :
>
> I tried...
>
> <p id="DUMP" hidden></p>
>
>
> ​...​
> and theat seems to work fine
> ​, so far at least​
> . / R
>
> 2018-03-21 10:08 GMT+02:00 Rune Back <rune.b...@gmail.com>:
>
>> Hi!
>>
>> I use only one section tag "HOME" in my code. When the user navigates to
>> "another" section tag, I only change the code of the section tag. - *Very
>> fast!*
>>
>> I do have another section tag called "DUMP", for *internal *use only.
>> That's where I receive the answers for any asynchronous requests sent to
>> the server. After I've sent something to the server I check the "DUMP"
>> every second.
>>
>> It seems to me that the section tag isn't the right tag for this use. -
>> Any suggestions?
>>
>>
>> Thanks,
>>
>> Rune
>>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "iPhoneWebDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iphonewebdev+unsubscr...@googlegroups.com.
> To post to this group, send email to iphonewebdev@googlegroups.com.
> Visit this group at https://groups.google.com/group/iphonewebdev.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "iPhoneWebDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iphonewebdev+unsubscr...@googlegroups.com.
> To post to this group, send email to iphonewebdev@googlegroups.com.
> Visit this group at https://groups.google.com/group/iphonewebdev.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to iphonewebdev+unsubscr...@googlegroups.com.
To post to this group, send email to iphonewebdev@googlegroups.com.
Visit this group at https://groups.google.com/group/iphonewebdev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to