Help! I have an MFC SDI application. A splitter window defines two panes. On the left contains a CHtmlView. On the right contains a simple view for drawing images. How do I modify this application so that it can be instantiated inside Internet Explorer such that the CHtmlView uses the IExplore's webcontrol? Any pointers would help. I have looked already into two ideas: make MFC SDI into an Active Document Server or convert the MFC SDI into an ActiveX control. Are these the only ways?

I'm looking for some code that will manage the display of a storyboard found in most digital film editors like Adobe Premiere, Macromedia Director, ULead VideoStudio, etc. Anyone seen anything out there?

Its the "so what" attitude of Microsoft that has led to operating systems which seem to magically suck away all the benefit of increased clock speeds and available RAM. No matter how fast my processor is or how much memory I have, Microsoft products continue to amaze me in how the extra resources vanish to a point where my applications never get the benefit. That suggests a poor, bloated design. Sure, Microsoft can eat as much disk space as it needs for a rich development tool but when it takes four times longer to load Visual Studio .Net and twice as much memory before I am running like VS6, then something is really wrong there. What happenned to the days of living with 4 Mb. RAM and a few floppies for a distribution? That is my point.

Interesting read. Thanks for the pointer. To wine is devine.c

I come from Sun -> Linux -> Microsoft [curse of selling software]. Sure, Java is controlled by Sun but it was a significant concept over what C# has to offer and it was needed at a time when Microsoft was not addressing cross-platform execution. C# is me-too with yet another way to offer the SAME concept. What's the benefit to us developers aside from making Microsoft technology function better?

Java execution support is at least supported on a variety of operating systems and browsers whereas C# requires the Common Execution environment that Microsoft is not likely to make available elsewhere. I guess by "proprietary", I mean "limiting". Yeah, VB is proprietary but my point there was about compatibility.

Not only is the .Net a bloated (1.2 Gb!) distribution [.Net Framework + Visual Studio .Net] but the design principles behind the product are completely motivated by Microsoft's continued need to dominate the technogolies that it perceives drive the marketplace. C# is an obvious rip-off of Java. Does Microsoft think I'm going to continually invest my valuable lifespan learning "new" languages with no tangible benefits over existing languages? C# is proprietary and flys in the face of a multi-platform advantage enjoyed by Java. VB is horribly incompatible with VB 6. Project conversion from VB6 to VB7 is verrrrry slow (almost 1/2 hour to convert a simple project with several forms) and results in hundreds of errors that much be attended to manually due to changes in VB. Each change is a reference to some documentation link that must be visited and absorbed. Tired of going down the same roads...