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."
Microsoft denounces OS yet they contribute... Odd.
Props to GNAA!
Microsoft buys OSDN (and Sourceforge, Slashdot, etc)?
I can't wait to find out how microsoft is screwing me today (tm).
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
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.
Guys, i'm scared, really scared.
I mean, do I download it? Do I use it? Do I trust it?
All of a sudden nothing makes sense anymore!
Error 407 - No creative sig found
Its so hard to hate them sometimes! On one hand they kill competition with shady tactics. On the other, they have some damn good products. Curse you Microsoft!!!
First Windows 2000, now this.
Evidence that pigs do fly has surfaced, new interpretations of the bible by scholars indicate that Hell is actually a frozen wasteland, and RMS backs a decision by Sun not to open Solaris.
Have you noticed that WiX is XML based? And gee... Longhorn is basically purely MS XML base isn't it? I think they're trying to pose as helping the development community, but truly just push their own product line dependency. Scary.
-- Friends don't let friends buy Nokia.
By "single" I mean't that he worked on it alone. He's happily married (chicks dig coders!) ;-)
HOW'S MY POSTING? CALL 1-800-POSTING
Oh the angst! Thousands of geeks struggle valiantly for a way to spin this so as to make Microsoft's release of this software for free look bad... hmmm... criticize the license terms? chant "embrace and extend"?
Oh, fuck it.
"Bill gate is a poopyhead, neener neener neener!"
WTL has been a bit of an embarrassment for Microsoft.
It started life as an MSDN sample app, but (to the surprise of everyone), people started actually using it. It fits nicely between the niches of MFC and ATL, supports a nice big chunk of what you need to do to get a desktop app running, and does it in a very clean, STL-friendly way. I read in an interview that some folks at MS thought it was a major mistake to release it; fortunately for them (at the time) it was pretty obscure.
There's some history of WTL at WikiWiki.
I remember way back then there were a couple of calls for Microsoft to "give it away" (in terms of control, not price--it's always been gratis), but I suppose the time hasn't been politically right within Microsoft until the recent popularity of their installer program release.
Microsoft invents Delphi! gee.. only about 10 years after the fact.. and its not WTL, its written V-C-L! *grin*
meh
There are a lot of GPL GUIs out there, I recommend using them rather than Microsoft's. First off, most of them are cross platform. Secondly, I have never known Microsoft to not have an agenda for anything they did. If you use this toolkit, you may want to beware as to what rights Microsoft may try to claim over it at a later date. Whether the claims were founded or not, I would not want to fight MS in court.
What is so suprising?
They want to have developers work on Windows and support their platform, buy providing easy access to some parts that may help out developers they encourage people to learn how to develope using this sort of stuff.
It's like giving a key away for a motel guest. The guy can look a the key, examine how it works and uses it for no extra charge, but as long as the lock remains closed off then the closed source model will still work in MS's favor.
Baffling!
Microsoft has actually released open-source software.
The CPL was developed by IBM and is OSI approved.
OSI approved
more info
John Hancock
For some reason, the only thing I can see coming out of this is a big bite in the ass...
The perfect sig is a lot like silence, only louder
Sulu: Captain, it's the Borg, again. they want us to integrate their technology.
Spock: Captain, I expect they are doing this so they can still feel relevant in the future open-source, linux-dominated software world.
Kirk: Mr Sulu, set phasers to "ignore"
Sulu: Aye, Captain.
I don't know the meaning of the word 'don't' - J
It's a trap!!
WTL, which is basically a one-person project at microsoft, doesn't really get enough attention of developers.
It's a great lightweight wrapper around Win32 API, does not depend on any external DLLs (like MFC etc).
The only problem with WTL, up to including this release, is that there is absolutely no documentation - there
are a few projects documenting WTL3.0 or older exist, but they are not maintained anymore. Hopefully once this
project is on sourceforge, people will be fixing bugs *and* writing documentation. I'm very looking forward
to this.
The WTL proves that there are some *very* good people at MS: They basically took MFC and redesigned it around templates and the STL; no MFC runtime dlls and even VC6 produces tiny exes that run wickedly fast. They even wrote a VC6/7 addin so you can use the project wizard to create a boilerplate project as a starting point. And to top it off, the two developers were (are?) very active on the ATL mailing list and responded to questions/complaints/bug reports. Way to go guys!
... has the same interface. Go figure.
That all said, Microsoft did practically everything they could to squash this project; it was originally installed as an "oh, by the way" in their SDK package (and not enabled by default...you had to go hunting for it) and then they removed it entirely. Official communcations always seemed to revolve around the message that "We acknowledge that it exists, we would prefer you not use it, and no we're not going to tell you why." I guess they had some fear that everyone was going to dump the millions of lines of existing MFC code for much better written code that
Trust me from one who has used this library in apps that reached production: this is a true gem amist all the cubic zirconia that MS puts out.
So is there documentation for it?
Unless they grant full rights to the code being released like BSD license, they can kiss my ass. why should I spend hours and hours debugging stuff they feel isn't worth fixing?
http://mediagoblin.org/
PORT IT! i want to use it on a linux desktop.
WTL was always open source. It was distributed as a bunch of header files (along with some sample apps and visual studio wizards). The big test here will be if Nenad will accept (direct) contributions from the community, or whether the community will keep track of bugs and document stuff while Nenad will code.
Nenad is amazing and has really been the core developer of the project (he is now the project admin at sourceforge), but it will be interesting to see the OSS process at work here.
But then there are other products like Visio 2002 which are excellent in comparison to their competition.
If I point out that you are incorrect, making me a foe does not make you any more correct.
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.
Wasn't WTL available a long time ago? I thought microsoft didn't *support* it at all. it was use as you wish and the source was available.
did you forget to take your meds?
A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
Shouldn't Steve Ballmer be telling us how the CPL makes you feel good, like communism? Shouldn't they be lobbying governments to ban the CPL because it destroys intellectual property?
Funny, I always thought the GPL would be the best license for a company like Microsoft to use if they wanted to open up some of their software, because it guarantees you won't have to compete against an improved version. I guess they realized they couldn't actually use the GPL for PR reasons so they picked another "viral" license.
Perhaps a better name would be WTF?
Oh you mean that nice product called visio that they did not write but bought?
Got Code?
Microsoft + Sourceforge = The End Of The World
-Imidazole2
As with most Microsoft software of any value, Microsoft didn't write Visio, they bought Visio Corp.
Who's going to port this to Carbon for the Mac, and one or more of the Linux GUIs? If Microsoft wanted to make this viral, goal #1 should be making a cross-platform GUI library.
Sure, there's vxWindows... but it doesn't have a Microsoft heritage, and such a background might impress a corporate IS director into implementing an OS-based solution.
Design for Use, not Construction!
there's no configure,
there's no makefile,
I don't think this stuff is compatible with Linux!
Excellent. It's about time Microsoft started making lasting contributions to the computing culture at large. Rather than releasing huge blobby tur(n)key "solutions" which become obsolete every few years they're beginning to actually release well-designed, extensible stuff with decent shelf-life, and they're actually working with other people to do so (ECMA, now SourceForge...). Bravo Microsoft, welcome to the party! Maybe in 5 to 10 years time the Windows developer culture will be as rich and interesting as the GNU/Linux and *NIX cultures.
So it seems to me that MS can now distribute their version of open source windows applications using the existing open source distribution channels.
And if MS software on SourceForge was just as abundant as non-MS software, it would be interesting to REALLY see MS compete.
Don't underestimate the power of the dark side.
-- A cat is no trade for integrity!
Perhaps microsoft is exploring a little. Just trying out a few things. Theres every chance microsoft has noticed that foss AINT going away, and in some areas (apache) foss is even eating them alive.
Perhaps microsoft is just getting a feel of how it works, so they can respond better to it and/or even participate. Of course these little libraries are a good start, since code is code and perhaps naturally suited to such things.
Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
Microsoft is clearly unloading the source for things that they're no longer interested in. Perhaps they think they can score a few quick PR points by doing this.
Yawn. Wake me up when they publish the source to Windows.Forms, or anything else that's current and relevant in the Microsoft developer world. Then I might believe they're playing nice. Maybe.
Tired of FB/Google censorship? Visit UNCENSORED!
It's a free library, which is only useful to you if you're writing code for the Windows operating system.
Which, I believe, that Justice Department lawsuit requires them to release (i.e., make it easier for 3rd parties to interface to the OS).
It does allow 3rd parties to be better able to program for Windows (so it could negatively impact M$'s ability to protect their own software aps for their OS), but one could also argue that making it easier for 3rd parties to write software for your OS is a disincentive for people to migrate to other OS's. (An extention of the game console arguement - he with the most games wins.)
paintball
does anyone else feel like MS is simply releasing these fairly-trivial items to the "open source community" in an attempt to try and appease the geeks out there? This seems like nothing more than a token gesture - they are still able to lock people in with Windows and Office.
They still have exploitive upgrade paths. And they can always change things in the future, and make future toolkits unavailable except via licensing/$, as their future offerings are undoubtably going to be different.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
Worf: Captain, it's the Borg, again. They want us to integrate their technology.
Riker: They've already assimilated 90% of our allies. This will make it easier to interface with their systems, and if there are any problems, we can just tell them to restart their warp cores.
Picard: On mainscreen.
paintball
OSI CPL
GPL compatiable
Common Public License Version 1.0
This is a free software license but it is incompatible with the GPL.
The Common Public License is incompatible with the GPL because it has various specific requirements that are not in the GPL.
For example, it requires certain patent licenses be given that the GPL does not require. (We don't think those patent license requirements are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL.)
they will almost certainly NOT accept source from other people; (although they may take suggestions, i'm sure).
It doesn't work like this. To get a project hosted at sourceforge, you have to choose a license from a variety of FOSS models (GPL is one, there are many others).
There is nothing stopping someone taking this code and forking it, if the (presumably Microsoft-based) project admins won't take their patches.
Let's port this to Linux! We can call it... Duo!
Since then my computer has rebooted 6 times and I now have a BSOD! I think it's working! :-)
Cwm, fjord-bank glyphs vext quiz
The bad thing is that this library is visual C++ only (by virtue of the fact that ATL is required and that ATL is visual C++ only)
Also, this is the exact same code that was available from MS for WTL before, its just a change of licence to the CPL
Unless microsoft opens ATL to the world also, this doesnt help anyone developing on non-MS compilers
Personally, I think they could gain a LOT of PR by open-sourcing more stuff.
Specificly, releasing (under the CPL for example) more code which is not important to M$ money making machine.
For example, open sourcing their C Runtime (the source code does come with Visual C++ but its missing some bits that only come in binary form)
Or open source the Active Template Library or MFC.
Or "open-source" the Platform SDK (i.e. all the headers and libraries)
Although I suspect that Open Sourcing things like CRT, ATL or MFC would probobly hurt MS since people would be able to use instead of to develop for those libaries.
On the other hand, there is no reason why someone cant come up with a free version of ATL or MFC or whatever that matches the published interface (there are already at least 2 free versions of the MSVCRT.DLL file, unsure exactly how complete they are, there are also free versions of the headers and libraries for talking to MSVCRT.DLL)
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
Didnt Billy Goat say that Linux and Open Source are hill billy developers. M$ said many times their is no open free lunch
with SCO when Darl was Billys sex partner.
So I guess Open Source is eating up M$ market share
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
That's what this is about. With Sourceforge and other open source outlets available to budding developers, I dare say MS has a lot of catching up to do.
With Sourceforge and many other outlets centered around open source readily available for budding developers, I think MS would be wise to do things like this. I mean how many kids can they expect to (legitimately) shell out hundreds of dollars for the tools to develop for their OS?
I suppose that might explain some of the holes in Bill's socks.
paintball
but since I have no experience with it, can anyone give me a link to a tutorial?
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
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
...that I'm seeing many more Linux and OSS projects going into production environments and kicking butt. It's just much easier to get started in an OSS environment.
They're right up there with those Berkley Bastards.
paintball
Dude! You have the Sasser man....
From excellent karma to terible karma with a single +5 funny post...
you know, that's exactly what most OSS-friendly companies are motivated by. They call it "leveraging the value of open-source by encouraging peer review and community-driven quality control" or some such marketing speak. I think it's one of the best reasons to release source code. I can't speak for MS as to whether they "can't be bothered" to fix software bugs, or if they just think this is a more efficient way of hunting down bugs.
As for Windows and IIS et cetera remaining closed, yeah, that does kinda suck. I, for one, could probably be persuaded away from Linux and back to the Dark Side if it were free (beer and speech)... ^_^
Standing at the very edge of my imagination, I peered into the inky void and realised -- I couldn't think up a new sig.
Does anyone know if this even works with watcom c or am I going to have to pay money and get visual studio (which I can't afford) in order to use it?
Does anyone else find it interesting that they'd host their "open" projects on sourceforge instead of on one of the many microsoft.com sites? What's to gain?
* wider open source community acceptance of MS (for releasing something "open source" which was argueably already open source - hello, header files, anyone?)
* strain on the open source community (ie, sourceforge) to further/improve the Win32/MS ballpark (granted, its a negligible strain, but it's pennies which add up to dollars, and so forth, nonetheless)
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
I just want to say this is great news regarding MSFT. Let's encourage this behavior, just in case a Microserf is browsing Slashdot.
Microsoft still has a long way to go in my book before I can even consider trusting them as a company, but clearly some of its individuals "get it" and are taking steps. If it's OSI compatible, I feel much less wary. One thing that could really sway me is making certain critical file formats (like Word/Excel) open. And oh yeah, stop trying to hijack the Internet. That would be nice.
Also, just like the last OSS release from MS, this is not what I would call an important piece of software. In MS's new world .Net is king. So the WTL can go away. However, it is pretty clever to get a little PR out of this release instead of just letting the WTL fade away.
All MS needs to do to make a big positive change of their image, is release ONE important piece of their software as OSS and actaully let the community contribute. I am not talking about a bread-n-butter app like MS Office. Some non-revenue generating app like IE or even explorer.exe. Those two apps could use some serious fixin.
If Tyranny and Oppression come to this land,
it will be in the guise of fighting a foreign enemy. -James Madison
I've written a few WTL programs, and am rather fond of this lightweight wrapper over ATL. WTL allowed me to create small, tight programs without the overhead (and poor design) of MFC (which was created before templates were added to Visual C++).
WTL has always been something of a dirty little secret: it wasn't installed by default by Visual Studio, and the README files suggested that it was an internal project unsupported by management. Yet those of us who disliked MFC found WTL to be quite useful, despite Microsoft's "official" attitude.
As for Microsoft releasing this as Open Source -- MS management never valued WTL in the first place, so "giving it away" is merely a public relations move.
All about me
Rather Insightful.
As it was related to the article and following discussion, I find off topic rather hard to understand.
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! :)
Remember the days when the MS C++ compilers were horrid? After a revs, it got decent, then it got good. Now it's everywhere and their IDEs set the standard that all others are measured against.
Maybe they are getting the hang of sharing the source to get the community benefit?
Agile Artisans
Microsoft denounces Linux, which is a competing operating system. They don't necessarily denounce open source software in general (at least, not that I've heard of.) That would be sort of foolish...I mean, you have to denounce a rival's products, that's obvious. But to denounce the way he makes them when other world class software vendors are considering them would be shooting yourself in the foot.
c net
From http://news.com.com/2100-1001-270684.html?legacy=
Earlier in the year, that feature led Microsoft Chief Executive Steve Ballmer to call open-source software a "cancer" and Windows leader Jim Allchin to call it "an intellectual-property destroyer."
...if the .Net Development Toolset is also a Microsoft project. If so - let's all
donate loads of money to make the Microsoft see that OSDN pays off.
I'm sure you will find a lot of other projects on SourceForge that won't accept outside contributions. Some because they want to hold the copyright and thus be able to do other things besides GPL their code, some because they are arrogant and don't believe anybody else's ideas are good enough, and some for the very realistic reason that they have no time to figure out if the contributed code really is good and worth adding, and some for a combination of all these reasons.
The thing with OSS code is that the user can fork it if the original authors are not interested in accepting their changes. That is the big difference.
If you want to see open source Windows software, just check out DotNetNuke. It started as some Microsoft toolkit, and it's now a fully functional portal solution with an enthusiastic user base. Open source, GPL, the whole bit.
Someone needs to use this to write a GUI to boot Linux off a LiveCD distribution.
As Catbert would say,
That's so evil it makes me want to PURRRRR!
Your password has expired, please login to change it.
It's going to be an interesting couple of years. How will they react when somebody forks their Open Source offerings and makes them cross-platform? How do you win the hearts and minds of developers who are far more saavy than the population as a whole about the many past transgressions of Microsoft? Hell, most people that develop exclusively for Microsoft platforms realize what scum-suckers Microsoft are (except for those snivelling MS-asskisser types, you know the ones I mean).
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?
Is it just me or is it starting to get really cold here? I just saw some red guy with a tail skating around.
No, seriously. Like Quake. I dont know of any non-game examples and id did the right thing when they released their code. "We arent planning on profitting from this anymore, so here, it's free. Not all of it (we retain the copywrite on the characters and concepts), but the code, we got no reason to keep it secret."
-- 'The' Lord and Master Bitman On High, Master Of All
I would generally describing windows as an inoperating system, particularly win98. In that case I believe the statement is true, and that Microsoft is indeed very pro-IOS.
Real stupidity beats artificial intelligence every time.
-- Terry Pratchett, Hogfather
Personally, I don't see it as conflicting that I fall into all of those groups. I would rate myself as pretty fanatical about linux, but I also use win2k and BSD on the side.
I do think you're right about the makeup of /. posters in particular. As for readers and AC-only types, who knows? They might all be windows zealots here for a laugh. Like the people (trolls?) around at the moment with MCSE, Well Respect VBScripting Guru etc. in their sigs.
Real stupidity beats artificial intelligence every time.
-- Terry Pratchett, Hogfather
Microsoft releases code under an open source licene... since the hell has frozen over, the devil down there must have really cold.
fsf has a case (look like windows/lindows case)
people get confused (this is ofcourse what m$ wants).
Development Status: 3 - Alpha
- We are the slashdot. Resistance is futile. Prepare to be moderated -
As I understand it, you can do fully-managed C++ if you want to. C# isn't mandatory for .Net, that was kind of the whole point. It's the legacy Win32 APIs that you should worry about. Wrappers are great, but if it's not wrapping managed code I wouldn't bank on its long-term viability.
Breakfast served all day!
Looks like someone has a case of penis envy.
Fetch an axe.
If you were blocking sigs, you wouldn't have to read this.
is it perhaps to comply with the EU's requirements w.r.t. the anti-monopoly suit of yore?
'WTL is licensed under CPL'
CPL, as we all know, mean Communist Pirate License. Tells it all, really.
Any resemblance to other license acronyms is entirely accidental.
(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
keep on keeping it on
First I wanted to be a chef. Then I wanted to be Napoleon. My ambitions have continued to grow ever since.
While MS might be contributing some small tidbits to open source, they aren't releasing them under the GPL, thus leaving the way clear for them to make the same kinds of claims that SCO has been making.
-All that is gold does not glitter - Tolkien
www.ra
See it as a small victory (with plenty of caveats).
Perhaps they get a discount on their course if they agree to spam message boards about how great MS and Windows is, and how anybody who doesn't like it is some communist hippy Open Source "zealot"?
Dell is being strongarmed by Microsoft, i.e. "if you don't preinstall XP on >95% of your machines, we're going to raise prices on all the XP licenses you *do* install". See?
It sounds like a case of give away crap that nobody uses in order to make themselves look good in the eyes of the Open Source community.
..
Having said that the CPL , the license itself doesnt see too bad and its an officially acceptable open source license.
The really interesting part here would be finding a way to make these projects in some way useful to linux. That would really stir the broth up!
nick
Electronic Music Made Using Linux http://soundcloud.com/polyp
They really did. I read it in print. (I forget a couple key specifics, like which Microsoft manager said it, and whether they specifically accused the GPL or OSS in general; I suspect they singled out the GPL, but perhaps not by name.)
;-)
The use of biological metaphors within Microsoft (digital nervous system, evolution, etc) is also quite common and this is no exception.
And the "but the GPL is a virus!" claim is either artful or ironic spin: who has spread more viruses... GPL licensing or Microsoft slipshod security?
My Gut feeling is that M$ is just using the opensource community as developers. Hey someone wrote a cool app. and in the next release there it is. Or the opensource starts to develop apps that cross platforms then the developers at M$ use the code to stop it in the next patch. then follow up with a software package that will let you cross platforms for a Price......I wouldn't touch this with a 100ft pole.
Never underestimate the power of stupid people in large numbers.
you know, maybe you're right. Maybe the majority of readers aren't sold on Linux. I just know that when I was a Slashdot reader (and not yet a poster) I had a soft spot for Linux in my technological heart (even though I wasn't using Linux).
Standing at the very edge of my imagination, I peered into the inky void and realised -- I couldn't think up a new sig.
do you mean they were exclusively Windows users, or simply that they used Windows? Because I don't think it's possible to work in the world of computers and technology without being exposed to Windows on a regular basis. I still have my (fully legitimate) copy of Windows XP on my hard drive for Flash authoring and a bit of vector art. So I guess that would classify me as a 'Windows user', although I find Linux much more sensible and powerful.
Standing at the very edge of my imagination, I peered into the inky void and realised -- I couldn't think up a new sig.
Microsoft isn't forcing their product on anyone. They are using the leverage of people who do want their product for various reasons to get more people onboard. First, through incompatible file formats, they use early adopters to drive upgrades among the people they share files with. Second, they have specifically tailored their products and marketting of them to appeal to people who make purchasing decisions for other people who then have to live with the consequences of those decisions.
That second factor is what the previous poster was upset about. Microsoft didn't force its product on him or anyone. They made it appeal to his boss, or his boss' boss. Part of that appeal has been any emphasis on usability from the viewpoint of a quick demo to a casual user. The features that make that possible are valuable. There is nothing wrong with having them, and I applaud Microsoft for all of the things they have gotten right. But they made trade-offs, mostly in terms of where to put their development effort, that sacrificed usability by programmers for usability in demos.
Simply put, as a programmer, I want a system where everything I ever have to do with it is completely scriptable. Microsoft is working on that, but it is recent. And I want it to stay up. Basically, I want things that run, run forever, run right, and don't wake me up in the middle of the night by giving someone a reason to page me.
Yes, most of the applications I have worked on have uptime measurable in weeks or months. One of my first ran continuously for 18 months.
I have no complaints about Microsoft putting code on Sourceforge. Personally, I think their products have improved enormously in the past few years. I don't begrudge them a profit or even marketshare. I think Microsoft, their customers, and the open source community would all benefit if they would do a couple of things. First, stop the rhetoric of Linux as the enemy. Linux is competition for Windows. Competitors are not enemies. There are some very important differences. Not that it has to make us all friends.
Second, I'd like to see Microsoft release under an open source license ever product they are no longer supporting. I'm not talking about old releases where there is an upgrade path. And I would apply this more widely than Microsoft. It would increase people's confidence in everyone's products knowing that when support is no longer available from the original vendor, there is not a forced end-of-life in a hurry. Finally, I'd like to see Microsoft release under an open source license, code to read and write all of their data formats. I realize that isn't completely realistic, and it isn't going to happen. However, if we get partial cooperation on it, it is still a win. In the end, computers have become the channel for worldwide communication. We have to be able to read the data we send to each other.
I greatly welcome this news.
Don't get me wrong, I dislike Microsoft intensely, and find it a pain to develop for at work (am a big Linux fan both for development and general use), but am using WTL on both home and work projects to great effect.
It's a good project and I'm finally glad that
Nenad and the team have been able to get the suits to make it more open than it was before.
After all, most ATL applications (probably most modern Win32 apps!) are actually using WTL in some form, even if they don't know it....
ATLControls.h (part of a code sample back in 1996
from MS is widely used in commercial apps, but is actually from Nenad, (the WTL author) and eventually migrated into atlctrls.h in WTL(!)
Mike
Linux fan and Win32 developer
Release Win98 source to the wine project. heh.
Retired from software... maybe. Sort of.
WTL code has been avialible out on web sights and in Windows documentation for at least 3 years now ( I know because I used it in one of my apps) and the liscense for it was pretty much open source ( ie freely distributable / downloadedable ) all that time. Actually they tried to squash the thing for a while. It has been mostly user supported all that time because it is code that "accidentally" escaped from thier labs. Also, WTL is a alternative to using MFC's which is the technology they were pushing at the time. I think what they are doing is tring to get some free publicity in the OSS world by publishing something as OSS that already was. Either that or someone in microsoft who likes WTL wants to see it kept alive and sees this as the best way.
âoeTolerance applies only to persons, but never to truth. Intolerance applies only to truth, but never to persons.
After reading through many of the endless messages here speculating about Microsoft's motives, expressing concern about what this means for OSS, and debating fine points about licensing and whatnot, I came to the conclusion that I could care less.
As a software engineer, I care about code, the design of that code, the patterns used to create that code, and all that. While the rest of you are wringing your hands trying to predict the future, I'm going to download the code and see what I can learn from and what I can ignore. I'm going to look at the source and see if it reflects my preconceptions of Microsoft code, or if I'm going to have to challenge my views.
Actually this is still far from clear. The latest I read was that SP2 will be exactly like SP1 in regards to pirates.
It seems there has been conflicts between various sources of information. I'd wait til SP2 is out to be sure on that one...
Corporation NOT Person
When people start negotiating with car dealers a lot of them seem to forget that they have the option of walking away. If the dealer tells you that they can't do something you want, go to another dealer. Sooner or later, you'll find one who will do it as long as your demands are within reason.
I walked out of a lot of dealerships last time I bought a car. Some of them I walked out of because they didn't have what I wanted. Guess what? Every single one of them offered to go through the catalog with me and order what I wanted. I walked out of others because they wouldn't give me the price I wanted. Eventually, I found a dealer who had what I wanted and gave it to me at the price I wanted to pay. They were also one of the nicest and least pushy dealers but that's not really relevant.
Here's a hint guys: It's a lot easier to do the above if you start looking for a new car before you actually need one. If your car died on you and you really need a new car, you're probably going to get screwed. You have less negotiating power. Start searching before your car dies. If you find someone that gives you an unbelievable deal you can always buy sooner than expected.
I wonder if it would be possible (or desirable) to make this work with GTK+ or QT.
Why didn't they call it WTF..........
Then again, there's always the possibility that this is just what it seems to be. A way to get open source developers to write for the Windows platform.
No. Too obvious.
Where's the bigotry? Microsoft is a monopoly, their software is generally inferior, they interfere with progress in development, their malware and political spin makes our society less secure. It is clear that you are projecting your own worship of a successful corporation, your irrational devotion to Microsoft, onto those who criticize your idol. You are the bigot, the Microsoft fetishist.
--
make install -not war
You sick punk, just because you would rob someone if you could get away with it, doesn't mean we would. As for M$ playing by the rules, their monopoly status was decided by a long process in high court based on their violation of a judicial consent decree (the result of some of their prior monopoly behavior) not to bundle IE with Windows 95. In their defense, they lied, invented fake evidence, lied, delayed, lied, and lied some more. Do you identify with that kind of criminal action?
Why do you defend it? The antimonopoly actions of government protect even you, a slimy lying thief, from the predations of corporations like Microsoft. Just because you worship the idol of theft and extortion, don't expect us to get used to it.
--
make install -not war
As a developer, I switched to wxWidgets not explicitly for the cross-platform capabilities, but because it's a much better API, and quite frankly Win32 and MFC suck so incredibly ridiculously badly that I could not face the thought of using them (and yes I have over 6 years of dev experience with them, they are bad). But now that I've switched to wxWidgets, my applications will require relatively minimal effort for me to make them run on other platforms. If I'd done them on Win32 or MFC, I would be at least a man-year away from being cross-platform. Perhaps Microsoft realises that their APIs are so bad that they're chasing some people into the hands of cross-platform competitor APIs, which is dangerous from their perspective because it means more ISVs building software that runs on other platforms. So perhaps they're hoping to start attracting more ISVs back to strictly Microsoft APIs again to prevent this.
This is non-fact-based speculation, of course, based on my own perceptions.
I don't seem to recall admitting that at all. I think you may have simply made it up to support your argument. I use windows 2000 as well, and I consider that to be fairly unusable too, but less so.
Also, I don't recall mentioning Gnome in my previous argument. As it happens, I do consider Gnome to be a vast improvement over the windows UI, especially XP. I think KDE also has distinct advantages. But, and this is a big but, many of the advantages of the Linux desktops are geared towards people who want to customize every last detail of their work environment, which many windows users (in my experience) don't generally care about.
But, while we're expressing wild, flamebait-type accusations, how about this list:
Real stupidity beats artificial intelligence every time.
-- Terry Pratchett, Hogfather
but... they were criminals - as in stole shit, not "unlawful combatants" or "terrorists".
It's wrong however you look at it, but dude - they weren't terrorists.
I know, dont feed the trolls, but christ... pull your head out of your ass and *look* at the facts!
Not used WTL, but from my experience with ATL I found it very difficult to understand the template code when you need to debug and step into it. Also very difficult to extend the framework. Much prefer a proper oo toolkit. I think templates were designed for the purpose of making generic algorythms and containers and not to be used as an implementation trick wrap an API, anyhow.
ok. i will finally bite. quit bitching about MS blue screens and the interface. BSOD's don't really happen anymore. sure, you have to kill processes from time to time, but that happens with any OS.
i'm not always particularly fond of gui-based OS's, but come on. that's what we have for any number of reasons. someone from the windows world could use kde and feel at home.
the problem with microsoft has to do with trying to decimate competitors through market share.... oh, and they did miss out on how the web might matter and then try to catch up by including scripting capabilities into EVERYHTING.
no security issues there.
Am I the only one here that read the post? The library is to create GUI's on Windows and it's got a license sanctioned by the FSF. Who cares if it works with another O/S or not. Most of the commercial stuff I write is single source C/C++ that compiles on Win32,Solaris,Linux,HPUX and AIX. Front end displays (GUI's) are written specifically for Windows only. Thanks MS your input to OSS is welcomed by this developer. Please ignore the sour grapes of the Linux zealots.
And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
The original post states "the toolkit allows a Windows developer to create quick GUIs in C++.". (It really means MSVC not generic C++.) I have been using MFC since MSVC 1.5, I realize it is a wrapper around the Windows API but if you want to create portable code then you would only use MFC (or this toolkit) for display logic. It makes more sense to seperate the bussiness logic into more Unix friendly modules that can be compiled and linked on multiple platforms. Most Unix stuff is not that hard to port to Windows. However if you are porting in the other direction and the original code uses any of various Windows frameworks then it usually means a complete re-write. When 100% of your customers demand Unix and Windows versions then the frameworks become nothing more than GUI libries.
And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.