I've seen that also, in more than one place. Two things would be needed for a total replacement: more horsepower, and the power apps (Photoshop, AutoCad) to be rewritten to run under ARM (RISC) processors. I can see that in 5 years. I've seen it as being worked on, but without the power apps it can't happen all the way.

>Someone wrote - I forget who - that the cpu of a phone or tablet could replace the desktop cpu as something that hosts monitors, hard drives, keyboards, printers, etc.. or that you could slide a phone into a slot on a laptop to act as the cpu, the way we used slide those pcmi cards into them.
>
>Those are mind blowing thoughts.
>
>
>>Hi Bill,
>>
>>I'm not sure a year from now, except in dev versions, but 3 years from now we'll be looking at virtual screens and manipulating with our fingers in air. The fingers in air is now, as in Leap Motion, which is going into all new Asus top line notebooks. The virtual screen specs, and I mean 1920 x 1080 etc., will be a few years until they are affordable on Amazon. Quite amazing. And existing touch apps will run on them just fine, in fact. So even though the hardware will change, I don't see the basic topology of the software changing.
>>
>>What do you see in the pipeline?
>>
>>Hank
>>
>>>Hank
>>>I was referring to the hardware.
>>>
>>>>re: mobile world looking different a year from now
>>>>
>>>>iOS and Android will be substantially the same a year from now; and even 3 years from now. The install base of apps is too large to make breaking changes.
>>>>
>>>>The only question is whether WinRT or BB10 will be more relevant. BB10 is getting rave reactions that WinRT has not gotten, so I think that one is pretty much up in the air. But if your app covers iOS and Android a year from now, or even 3 years from now, and can run in the browser and the desktop, then I think you will be in very good shape, in terms of meeting market demand.
>>>>
>>>>As for writing it differently from each platform: that depends a lot on your business model. If your business model includes teams for all the different UI platforms, then more power to you. However, the trend is away from managing huge development teams: as Ray Ozzie noted some time ago, when dev teams get above a certain level, more energy is put into communication than into production. Or communication fails, and chaos reigns.
>>>>
>>>>Hank
>>>>
>>>>
>>>>
>>>>>That sounds like a sensible approach, Walter.
>>>>>
>>>>>The mobile world is evolving quickly and will certainly look a lot different even a year from now than it does today.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>Regarding Lianja, it's hard to opine about something that doesn't exist and has no track record.
>>>>>>>
>>>>>>>Your requirements that you use existing code and run on all platforms preclude everything that is currently available so your choices are:
>>>>>>>-do nothing and hope that something comes along to meet your requirements.
>>>>>>>-change your requirements
>>>>>>
>>>>>>Its a given that we have to do something in the next few years. Currently I'm thinking of either Lianja or Windev. Servoy is out of the picture as it is just too expensive.
>>>>>>
>>>>>>Lianja is to be released next month and we surely will take the time to see how this evolves before we make any decision.
>>>>>>
>>>>>>
>>>>>>Another option would be to just transform our product to run on the web. Since we are nearing completion to make it 4-tier. It would just be an investment to get the GUI tier replaced with something that runs in the browser. Then the usage of VFP in the biz objects and dataobjects is not that critical anymore as it is irrelevant to the looks of the GUI and the client where it need to run on.
>>>>>>
>>>>>>Walter,