Slashdot Mirror
Microsoft Releases WTL To SourceForge
prostoalex writes "Microsoft's WTL (Windows Template Library) toolkit source code has been released to SourceForge.net [also part of OSDN, like Slashdot.] InternetNews explains that the toolkit allows a Windows developer to create quick GUIs in C++. According to the project page, WTL extends ATL (Active Template Library) and provides a set of classes for controls, dialogs, frame windows, GDI objects, and more. WTL is licensed under CPL, which is the license Microsoft chose for the SourceForge release of the WiX installer."
WTL up to this point, has been done by a single guy at MS. It's a lot nicer to use compared to MFC, and regular ATL, in that it follows the "KISS" aphorism
HOW'S MY POSTING? CALL 1-800-POSTING
for some reason, i don't think it's a coincidence that both their sf projects are under a non GPL-compatible license.
Marge, get me your address book, 4 beers, and my conversation hat.
Microsoft denounces OS yet they contribute... Odd.
If they can't kill it, then they have to resort to "embrace and extend"...
they may have opened the source, but it is not anywhere near what you OSS developers like.
they will almost certainly NOT accept source from other people; (although they may take suggestions, i'm sure).
the purpose of this is not to make their product better by allowing the community to help, but rather to allow people to customize their own toolkits or to at least better understand what they're using.
http://mediagoblin.org/
I've tried WTL. It seems great for small, stand-alone executables. However the learning curve is sort of high and you really need to know a bit about ATL. The documentation also isn't near as complete as MFC (even though MFC is ugly).
That being said, the best way to create GUIs in Windows nowadays is to use Windows Forms either in C# or C++. Compared to MFC/WTL/whatever, its a dream come true.
GPL: If there is something in this software that is patented, by you or someone else, you can't distribute this software unless a free license to use that patent is available for all. (If a patent prevents anyone you give this to or they give this to from freely distributing this software, you can't distribute it either.)
CPL: If there is something in this software that is patented, and was patented at the time of contribution to the software, this software may still be distributed even if a patent is required to use it.
So it depends on your definition of "free". CPL says you're allowed to distribute the software whether it's patent encumberred or not, GPL says that if it's patent encumberred, you can't redistribute it. So CPL is more BSD-like free. Free as in "Here it is, do what you want", not free as in "Here it is, anything you add has to be free too."
Maybe that wasn't all that short.
paintball
I finished school just before the tech bubble burst, and had occasion to travel out to the Silicon Valley on business to our corporate headquaters.
There have been few times in my life where I have been more amazed than I was at the number of ways a girl could work some variation of "How much money do you make?" into the first three sentences of a conversation.
I'm happy to report, however, that these women are no longer there.
In retrospect, however, I probably should have just said "A Googillion".
paintball
I started Win32 programming with WTL. No MFC experience at all.
.NET seeps deeper into the Windows Platform, I am afraid that MS is going to try to root out such a quick and painless way to whip out applications in unmanaged code. There's life in C++ yet, I just don't know if MS believes that.
For those of you who may be curious about this technology, here are a couple of points:
WTL is a collection of header files with the source inlined in. Personally I find the source reasonably understandable. I have had not much trouble stepping through and debugging WTL calls.
It's a light wrapper around the Win32 API. Some people commented on the lack of documentation regarding the WTL. The truth is, MSDN's API and common controls documentation pretty much covers what you need to know. For most cases the library does little fudging between your app and the API behavior.
For the application I am coding, I use strictly STL strings, containers, and various Boost libraries. With WTL, I don't feel that I am paying for things I am not using like CStrings and such. For non-UI OS calls, I use ATL. In short, WTL, STL, & ATL let me produce efficient code without worrying about reinventing solutions.
One thing I am worried about is the future of WTL. Open-sourcing is great, but I don't know what direction the Windows API is heading. As
So I hope the response from this PR stunt that registers on their radar is that we appreciate OSS-esque gestures (that's really all they've been, really: gestures) but need something substantial before their image truly changes. Open sourcing IE or explorer to community improvements would be absolutely immense. IE could rocket past even Firefox and the ignorant masses of AOL types out there would have a real web browser by default. Microsoft seems as interested in fixing IE themselves as they were with WTL. Maybe this IE thing CAN happen! :)
I'm in complete agreement with what you said. I was merely attempting to point out that Microsoft cannot kill "OSS" as a concept, technique, philosophy, whathaveyou.
What you're describing falls into the "Microsoft creates a good operating system" alternative. I honestly think it could and probably will happen once Linux eats up a little more marketshare. Microsoft is known for adapting, albeit often late, to stay alive and I think OSS will eventually become at least some part of Microsoft's daily life.
It will take time before they grow up, but it will eventually happen or the monopoly will fall. History doesn't repeat itself, but it does rhyme (Mark Twain?).
Cheers
~Dalcius
Rome wasn't burnt in a day.
Lots of people around here write software for a living, not just as a hobby. Unless you write web software, embedded software or other niche software, it's safe to say that you have to worry about people buying and using the software you write, which means using Windows. No, I'd say the fact that MS buys ads on OSDN indicates they understand the audience on Slashdot fairly well and in fact they want to be associated in these developers minds with the positive aspects of the Open Source community.
Anyway, I am an active Slashdot poster, and I know a fair number of other active Slashdot posters, and as far as I know, relatively few of them can say they exclusively use Linux, FreeBSD, or other Free/Open Source operating systems. I don't know if I would call myself "platform agnostic" - I'm not a zealot, and I recognize the strengths and weaknesses of Linux and Windows, but when it comes down to it, I need people to buy my software, and ignoring that fact is a fast road to being broke.
I assume that Microsoft has twice chosen Sourceforge to host their OSS projects because of the visibility and credibility it lends their open source steps. However, MS certainly doesn't need SF's resources. Does anyone know if MS has made any donation -- monetary or otherwise -- to SF?
No, but the malware people are shooting plenty of bullets.
MS just stops providing patches and the pressure to switch increases. Win95 without patches isn't that unsafe - you can remove all the network services. But it's hard to do that with Win2K, XP etc.
It seems to be that no matter what MS does, it's got evil intentions, lacks sincerity somehow, "is merely a public relations move", or whatever.
/. pretty much weekly which, with your cynic-coloured glasses off, are actually positive. Blogging, releasing product source, increased participation in communities, relaxing licensing restrictions, WinXP SP2, etc.
That could be true if it were a few isolated incidents, but there are things up on
Maybe the OSS community is the big lumbering beast which is slow to change while MS is getting on with changing what needs to be changed. Each small change by itself isn't ground breaking, but a trend, well, maybe that is.
Read reviews of shopping cart software
To this point in Microsoft's history, they have done NOTHING that I can think of out of the kindness of their hearts. Everything can be written up as enough to get by with as much money as they can take from customers and carry to the bank.
I can think of two things:
1.) Supporting a $100 O.S. for 6 years with official updates and patches. Quite a deal, one that you certainly won't see from redhat.
2.) Allowing pirated copies of windows XP to install service pack 2. A clip from the article: "Microsoft group product manager Barry Goffe told ComputerTimes that [...] it was more important to keep user safe than to be 'concerned about the revenue issue.'"
~Will
sig?
I think the why is quite obvious. It is in the interests of microsoft to have people develop software for their OS, and if that means giving away free source code and wizards to help people do that then thats fine. Of course, most windows developers already have a copy of VS and thus ALT, WTL MFC etc. The major advantage to a software developer is being able to know that you have the latest, bug fixed version of this toolkit, and that we now have a clear route for submitting bug reports direct to the dev team.
Of course, WTL has never really been a product, so much as a development framework, and the licence has always been pretty open so thats not a really dramatic step, but unlike the Wix thing this is actually really useful and we've (my dev group) already learnt that there are fixes and changes in this version of WTL that we didn't know about, so thats pretty cool.
Kudos to Microsoft on this one I think.
You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
I prefer:
1) Refrain from obtaining money from people by illegally exploiting your monoploy power, thereby leaving millions of individuals and companies more money to use as they see fit.
to
2) Illegally exploit your monopoly to gain much more money than you would have otherwise had, and then give some of it to charity so people think they are nice.
-- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz
(this is not a troll: Slashdot editors mod anything with the word 'sucks' as a troll).
.NET platform.
Although it is nice to see the software giant contribute to open source, WTL sucks. It is really no different than MFC, carrying with it all the disadvantages of it:
a) the window creation process: first you create the C++ object, then you call 'create', and then 'preCreate', 'postCreate' and other silly stuff is being called. Contrast that with QT where you simply create a C++ object...
b) message maps: it violates object-oriented programming; introduces macro hell; makes code very sensitive to changes, to the point where if something goes wrong the IDE can not parse the code any more.
c) menus and commands based on numeric ids: maintaining the list of ids is easy at first, but it grows exponentially harder as the project grows, and after a while it becomes unmanageable to the point that it needs serious manual intervention.
d) the stupid UI updating architecture: your UI elements will be updated only when there is no other message in the message loop. You don't know when your UI will be updated.
e) the classes don't make any sense. For example, there is a CMessageLoop class. For crying out loud, who would have thought to make a class out of a message loop ? only MS twisted minds.
f) more string classes.
To me, it seems that releasing WTL is all about making themselves more innocent to the open source world. They now can say "look, we are contributing to OSS, you can't blame us!".
I would have much respect for them if they released anything serious to open source...for example the
If I recall correcly, WTL was never a Microsoft product. Nor is their name mentioned anywhere on the sourceforge site. WTL has been provided on the Platform SDK as an example, or something like that. It is the result of mainly one person (nenad) who, encoureged by the quick adoption by a lot of developers, continued to develop it. He is a Microsoft employee though, so he probabily needed some kind of "approval" from MS for this move, but I don't think it denotes anything more from MS's part.