|
when you can tell who wrote most of the optional text messages to the straw polls. 
i.e. Drink more gin. (Nagy perhaps)
|
|
|
|
|
...unless it's already designed to be cross-platform "aware".
Usually my apps have been web based so cross platform support haven't been a great concern for me.
Even tho, sometimes the same app had several front-ends like Windows, Web and console.
To overcome this all business is always behind a self-contained service and/or dll.
This way I'm sure the behavior is the same no matter from where the action request comes from and I only need to build a team to develop the new UI.
Cheers!
Alex
|
|
|
|
|
I know from several reports that Win8 aint doing so good, but now I see alot of sites pushing App developemnt for Win8, Did M$ treathen business to push Metro*/Win8?
|
|
|
|
|
I'd use all of those (except "Use application hosting environments or automated porting tools in the hope of not doing any coding at all" and "Not even bother. I don't port."), depending on the demands of the application, the requirements of the customer, and my own personal preference for a project.
So far, all attempts I've made to automatically use a hosting or porting solution tends to involve more work than doing the work by hand. Maybe I'm just unlucky.
|
|
|
|
|
I'm afraid CListCtrl is the only meaningful answer in my case. No apps - no porting. I write highly portable server side code these days.
|
|
|
|
|
I follow the port as-is path, because it seems the commercially best fit.
But before, you will se me experimenting with some proof-of-concept how special tasks are handled by the new platform.
I normally interpose some facade-patters ro adaptors to link the "new way" to the old core.
Uli Merkel
|
|
|
|
|
What is the difference between the second and third supposed to be?
"Port an existing application as much as possible, ensuring it works well on the framework" and "Port an existing application as-is, keeping as much as possible the same across different platforms" look like different ways of saying "port it while changing as little as possible/neccesary" to me.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
No. Option 3 is supposed to mean that you rewrite as little as possible, possibly not using all the new features and capabilities. Option 2 means that using the new features has priority over preserving existing code, possibly requiring to write more time and work.
Porting applications had become a secret hobby of mine. Thanks to Mickeysoft. I had a program that started out as a website, then became a Windows Forms client, moved on to WPF and ended up full 3D with an own graphics engine and GUI. Mickeysoft's way of convincing us that Win 8 is a great thing led to yet another long list of things that would have been to be ported or rewritten and I'm not sure I would have been finished by the time they come with their next great idea. Now I'm porting my code for a last time. To C++ and anything else that's helpful and not made by Mickeysoft.
|
|
|
|
|
Here, on the ranch, we have plans to port apps written for DOS O/S directly to web-based as HTML/CSS/php/javaScript - much of the nuts-n-bolts will be bestowed on me, excepting a DBA will be building many SP's so I can appear to be making progress. A massive database migration from a dbase style to SQL Server is also part of the fun. There's really no direct-connect from where we are to where we will be, except:
Experience has shown that the only important part (aside from inhumanly perfect bug-free code) is the look-and-feel be as similar as possible for the transition. This applies to both user and management acceptance.
There's a lot to be said for just starting 'fresh', but there's a lot of legacy data, and more of it every day.
On the bright side, this will really be a great help to the company, and as they've been rather nice to me, a battle I will engage with determination to make it work.
(Why did I write this? What's wrong with me this morning?)
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos wrote: DOS O/S
Is this a new tautology-based O/S version numbering scheme?
1. Disk Operating System (DOS)
2. Disk Operating System O/S (DOSOS)
3. Disk Operating System O/S O/S (DOSOSOS)
|
|
|
|
|
As soon as I copyright it, the answer will be 'yes'.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Is it really happening. I wonder how much '$' & 'time' it cost's for a an application to do from the scratch.
Jibesh V P
|
|
|
|
|
Compared to deal with design flaws - might still be less. Often applications are designed poorly (or not at all, they just grew), so it is less effort and a lot cleaner to start from scratch and maybe some reuse parts of the original application.
It simply depends. When I look at the stuff I wrote 10 years ago I would clearly vote for starting from scratch 
|
|
|
|
|
There's often no choice. If your application is written in .net you more or less have to do a rewrite to put it on Android/iOS devices; even if you use a 3rd party tool to make your C# work on the platform (and on going support for this strikes me as high risk); you still need to create a new UI from scratch due to the difference between touchscreen and keyboard/mouse and (particularly on a phone) screen size.
If your app's written in Java, porting to Windows Metro or iOS you encounter the same thing. (Are cross language compiler tools available for this case?)
Porting a desktop app to the web; need to write a new UI from scratch.
Porting a VB6 app from anything; the code base is probably bad enough that even trying to do an intermediate port to VB6 is a horrible idea.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
If its a cross platform I do agree with that but how about the versions of the same platform?
.Net 2.0 to later version
VC 6 to VC7
Java5 to Java7 etc....
how many of you really re-design the whole application.
Jibesh V P
|
|
|
|
|
Question is "When creating an application for a new platform do you"--that means, as far as I understand it is not about upgrading versions but about different versions - Mobile/Desktop/Tablets etc.
Nitesh K Luharuka
Consultant
http://www.niteshluharuka.com
|
|
|
|
|
I wouldn't consider upgrading to a new version of a framework a platform change at all.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
jibesh wrote: how many of you really re-design the whole application
From VAX Pascal (no graphics) to Turbo Pascal (CGA graphics) to WinForms/C#/.net ... soon to Android/Java?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
