At 02:52 AM 8/15/2015, JEH via wrote: >Kathryn > >Looking at the Gedview website it appears to only run on Apple >phones/tablets. I need an app that will run on the Windows Phone OS. I'm >hoping that an upgrade to Windows10 for phones might actually allow TMG to >run when that OS is released. Unlikely unless the embedded Win10 includes an emulator for Intel processors. Most devices (phones, tablets) are using some version of ARM based processor -- completely different instruction set. Yes, M$ may be bragging about being able to do development for phones, tablets, desktops using one Win10 API set... But that basically means the source code is common, but the executables are built based upon the target device (using a form of the .NET "managed environment" development tools -- Visual Studio Visual BASIC .NET, C#, maybe C++ in "managed" mode, not native. "managed" in this case being something like Java's system, where there is an underlying native specific runtime supporting one developer view). Heck, just read the current reviews of how disappointing the Win10 on Rasp-Pi turns out to be. http://www.theregister.co.uk/2015/05/21/first_look_windows_10_iot_core_on_raspberry_pi_2/ (does claim native Win32 apps can run, but I suspect very slowly). http://hackaday.com/2015/08/13/raspberry-pi-and-windows-10-iot-core-a-huge-letdown/ Running any database intensive application of a device based on Flash memory is going to be horrendously slow, as any edits will tend to require fetching a whole page of memory, updating the contents, ERASING the page in Flash, then re-flashing the page with the modified contents. Erasing flash forces all bits in the page to "1"; writing data to flash, OTOH, can only convert "1" bits to "0" bits. Since Flash has a limited number of erase/write cycles, you could rapidly wear out the flash -- and the entire device (unless it supports putting the user data on a removable card). -- bieber.genealogy@earthlink.net Dennis Lee Bieber HTTP://home.earthlink.net/~bieber.genealogy/

On 8/15/15 12:57 PM, Dennis Lee Bieber via wrote: > Running any database intensive application of a device based > on Flash memory is going to be horrendously slow, as any edits will > tend to require fetching a whole page of memory, updating the > contents, ERASING the page in Flash, then re-flashing the page with > the modified contents. Erasing flash forces all bits in the page to > "1"; writing data to flash, OTOH, can only convert "1" bits to "0" > bits. Since Flash has a limited number of erase/write cycles, you > could rapidly wear out the flash -- and the entire device (unless it > supports putting the user data on a removable card). > Flash based devices are faster than disk based devices, and modern flash has a reasonable wear time. My own person computer and work computer have had their hard disk replaced with "Flash Devices" (Solid State Disks). I would expect that most phones and tablets use similar grade flash for their memory. Now one thing that will slow things down is replacing RAM with flash (or Hard disk), and Phones and Tablets typically have a lot less RAM than your typical desk top, but an application like TMG isn't really that big as most of the data is off in the database, and not needed to be brought into ram until needed. -- Richard Damon