Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. .NET to replace MFC????

.NET to replace MFC????

Scheduled Pinned Locked Moved C / C++ / MFC
csharpc++question
22 Posts 6 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Fazlul Kabir

    I don't want fancy bitmapped buttons, grids, sliding windows, etc. in MFC. Hey, that's why I used the word *relative*. MFC's own history tells us that it has extended and improved its GUI components from version to version. Sure most of them are more of a *wrapper* around their Win32 counterparts, but consider other GUI controls that are *extended* beyond this wrapping business (such as CBitmapButton, CCheckListBox etc.). Adding more controls into the library only makes it rich and thus leaving us, the end users to spend more time to make it even richer. // Fazlul


    Get RadVC today! Play RAD in VC++ http://www.capitolsoft.com

    T Offline
    T Offline
    Tomasz Sowinski
    wrote on last edited by
    #21

    Adding more controls into the library only makes it rich and thus leaving us, the end users to spend more time to make it even richer. The problem is that rich library becomes bloated library. Take ISAPI helper classes for example. Sure, there are users who benefit from them, but I think they are not majority. Generally speaking, the life of library writers is not an easy one - they have to hit the bullseye and provide enough functionality within reasonably-sized package. Tomasz Sowinski -- http://www.shooltz.com

    F 1 Reply Last reply
    0
    • T Tomasz Sowinski

      Adding more controls into the library only makes it rich and thus leaving us, the end users to spend more time to make it even richer. The problem is that rich library becomes bloated library. Take ISAPI helper classes for example. Sure, there are users who benefit from them, but I think they are not majority. Generally speaking, the life of library writers is not an easy one - they have to hit the bullseye and provide enough functionality within reasonably-sized package. Tomasz Sowinski -- http://www.shooltz.com

      F Offline
      F Offline
      Fazlul Kabir
      wrote on last edited by
      #22

      The problem is that rich library becomes bloated library. Yep, that can be an issue while redistributing the runtimes. I guess the new approach MS has taken in MFC7 by integrating it more into ATL has the potential to take a lot of load outside the runtime and make it even lighter someday. // Fazlul


      Get RadVC today! Play RAD in VC++ http://www.capitolsoft.com

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups