visual c++ - Porting C++ w/ MFC to a Touch Screen -


looking gui framework use c++ "modernize" existing interface touchscreen.

i'm novice programmer background in c++/java assigned project involves taking existing c++ program using mfc (3 data views, multiple text/radio controlled dialog boxes, etc.) , redesigning interface "touch-screen friendly" such larger button controls, sliders , whatnot.

i've been given pretty free-reign instructions make "more modern looking interface" opposed typical bare-bones mfc i've been given. know have quite bit learn either way, suggestions helpful.

so far options i've come are:

  1. mfc tweak existing controls accommodate touch input, keep crappy looking interface.
  2. managed c++ or c++/cli figure out how keep underlying c++ structure while being able design new interface wpf or windows forms.
  3. qt new me, seems promising alternative.

really need find way make program wasn't written on 10 years ago, , far in teaching myself mfc, doesn't seem flexible in terms of incorporating sort of graphic-design/themes.


are there other alternatives should looking into? there more mfc meets eye , need learn more it? said, suggestions of things helpful.

what you've listed #1 either of 2 approaches. 1 (call 1a) continue using same version of vc++ , mfc original, , bare minimum of editing increase sizes of controls needed. short of encountering bad luck in how existing code written, might not involve real programming @ all, , relatively quick , easy.

the second (call 1b) update using current version of vc++, mfc, etc. involve some code updates, not terrible (though if it's more 10 years old, significant code updates needed well). care, may able update ui quite bit (e.g., change menus ribbons, include color theme support), still fairly minimal investment.

your #2 end complete rewrite. despite superficial similarities, c++/cli completely different language c++. way makes sense if have quite bit of non-ui code can leave alone completely, , use c++/cli exclusively "bridge" between existing c++ , .net ui (and ui minimal, rather mediocre tool support c++/cli doesn't cause big problem). if ui more trivial, c# has enough better tool support may better choice c++/cli.

your #3 require marginally less rewriting 2, @ least of code that's related ui. while code remain c++, qt quite lot different mfc. big advantage if (might soon) want support other windows (e.g., ios or android). portability, qt has huge advantage on of alternatives you've named.

a lot comes question of how c++ code can retain intact. if have lot of code in "engine" that's cleanly separated ui, , simple ui, retaining existing code make lot of sense, , rewriting ui ground isn't terrible of problem. on other hand, if ui , business logic code heavily intertwined (fairly common) more minor tweaks ui me significant rewriting of rest of code well.

conclusion: if ui heavily intertwined other code, real choice between 1a , 1b. if ui detached other code, choice between 2 , 3 (at least me) 1 of whether portability @ matter (now or time soon).


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -