Google Windows Apps Coming To Linux 298
skaet writes "DesktopLinux.com reports that Google is working together with CodeWeavers to bring their photo editing and sharing program Picasa, formerly only available on Windows, over to Linux. From the article: 'The program is now in a limited beta test. If this program is successful, other Google applications will be following it to the Linux desktop, sources say. The Linux Picasa implementation includes the full feature set of the Windows Picasa 2.x software. It is not, strictly speaking, a port of Picasa to Linux. Instead, Linux Picasa combines Windows Picasa code and Wine technology to run Windows Picasa on Linux. This, however, will be transparent to Linux users, when they download, install, and run the free program on their systems.'"
Google earth?? (Score:2, Insightful)
Re:Google earth?? (Score:2)
Re:Google earth?? (Score:3, Informative)
I believe it's using Qt, at least in its OS X version, because when Google Earth beta for Mac was issued a few months ago, there were lots of complains that it just didn't "feel" like a Mac app, and the reason for this was it was using Qt instead of one of Apple's toolkits.
No, port WorldWind instead (Score:3, Interesting)
-russ
Who'd have guessed? (Score:2, Funny)
Wine Source Code Patching (Score:5, Interesting)
Re:Wine Source Code Patching (Score:3, Interesting)
Re:Wine Source Code Patching (Score:2, Insightful)
Re:Wine Source Code Patching (Score:3, Informative)
Re:Wine Source Code Patching (Score:4, Interesting)
Re:Wine Source Code Patching (Score:4, Insightful)
Usually however, people don't have the windows source, so the runtime implementations are used and the calls become dynamic. There's the same code behind of course.
There should be a Wine expert along shortly to point out the gross over-simplification in what I've just said
Justin.
Re:Wine Source Code Patching (Score:5, Funny)
Re:Wine Source Code Patching (Score:3, Interesting)
I predicted there'd be a WINE expert along to point out the gross over-simplification. If you can help with that, go right ahead...
Justin.
Re:Wine Source Code Patching (Score:3, Interesting)
On the other hand, I would hardly call this a mainstream application, even though it comes from a well known corporate vendor.
I am not normally the pessimist
Re:Wine Source Code Patching (Score:2)
LOKI did not use wine (Score:3, Informative)
They really ported the games to linux, meaning that the games were linux pure binary with no
"emulation" layer (even thought that WINE Is Not an Emulator).
They job were "simpler" because most of the time they had to translate
direct3D to openGL (if the game did not have an openGL driver),
DirectSound to OpenAudio (or something like that equivalent to openGL for
sound that they created) and the rest of DirectX to SDL.
Basically the game source became mostly thru cross-plata
Re:Wine Source Code Patching (Score:2)
Re:Wine Source Code Patching (Score:2)
Re:Wine Source Code Patching (Score:3, Insightful)
Valid, unless you actually want your application to WORK.
Re:Wine Source Code Patching (Score:2)
and there's no Funny-Sad mod.
Re:Wine Source Code Patching (Score:3, Interesting)
Ughhh..... (Score:2, Insightful)
Re:Ughhh..... (Score:5, Insightful)
Sort of. If they're porting it in the usual way, it'll still use the Windows API but will be a Linux ELF binary. (The actual program binary *might* be a shared object, depending on whether CodeWeavers use the standard wineport tools or some custom-developed toolkit of their own).
Re:Ughhh..... (Score:2, Interesting)
http://picasa.google.com/support/bin/answer.py?an
Re:Ughhh..... (Score:2)
Re:Ughhh..... (Score:2)
Can you provide an example? I was under the impression that netcode was in standard dll API libraries.
Re:Ughhh..... (Score:2)
Re:Ughhh..... (Score:4, Insightful)
It is not a hack you need to do and support yourself in the back of the original developer.
In any cross-platform development you try to limit the difference between different platform source trees, generally you isolate all platform specific functions in a common framework and only port the common framework on different platforms, leaving the rest of code unchanged.
There are plenty of cross-platform frameworks for plenty of use ( from simply using stdio.h to opengl ), in this case they choosed WINE. That is surprising yes, but that does make sense for a project that need to be crossplatform retroactively.
You can see that Google apps are still Windows applications but you can see them as using a cross platform framework developped conjointly by Microsoft on Windows and WINE team on Linux
Re:Ughhh..... (Score:2)
Re:Ughhh..... (Score:2)
If Google ports all their applications to Linux, people that do not feel confortable with the KiDzE style of some of linux end user applications will have a familiar application to use in Linux.
The more propietary applications are ported to Linux the more users it will attract and the more Corporations will be attracted to port th
Re:Ughhh..... (Score:2)
When I can 'agt-get install picasso' and it "just works" (well) then I'll use it.
Yuck (Score:5, Insightful)
The solution to complaints that Google makes no effort to port their software to Linux isn't to get CodeWeavers to make it run when used with winelib. It's to port the software to Linux. Otherwise just tell Linux users to sod off, because that's basically what linking with wine is doing.
Re:Yuck (Score:5, Insightful)
Second: If any step succeeds, another is likely to be taken.
Third: Other companies will be watching Google, and they may decide it's worth the time to at least start with wine. A foot in the door may lead to a complete port.
Not a good way to do it, however. (Score:2, Insightful)
Re:Not a good way to do it, however. (Score:5, Insightful)
They also have the advantage in that they can modify Wine to suit the program and the program to suit Linux should they need it, and advantage that you don't have running Wine on your average computer. They can, for example, rewrite the file loading code to take advantage of the GTK file selecter and grab the files directly from the operating system. They don't *need* to go through the C:\ file system emulation, one of the bigger issues with Wine. They can also probably with small modifications route their audio through GStreamer, cutting out the Wine audio library which is sometimes considered buggy. If a certain section of the program proves buggy, they can simply port that section and do the rest through Wine.
Seriously, I think if a Linux version of Picasso ends up buggy then it's Google's fault, not Wine.
Re:Not a good way to do it, however. (Score:2)
iirc it is just a canvas and some menus.
Re:Yuck (Score:5, Insightful)
Re:Yuck (Score:3, Insightful)
Re:Yuck (Score:2)
Re:Yuck (Score:3, Informative)
But this is only a "Good Thing". This will encourage Google to implement any functions that happen to be missing in Wine. I've been working with and learning the codebase of Wine for the last few months, and it's quite solid. The functions are all
Re:Yuck (Score:4, Insightful)
However, if you are a developer using it as a compatability library, presumably you test your applications so they perform the way you intend. If a feature doesn't work right, or it's too slow, then you do it a different way. There's always a different way. Generally your first cut is pretty far from what you'd wish on any implementation of any set of APIs, which is why you test in the first place.
Users trying to run software in which running against WINE are in a completely different position. They're hoping that an app will run well against WINE, even though it has never been tested against it. If it doesn't run well, not having source code they don't have any recourse. Given these unfavorable preconditions, WINE works remarkably well.
The only reason to use WINE as a developer is to port existing Win32 apps to non-Windows platforms. If you are targetting Unix, or intending Unix/Win32 compatibility from the outset, there are better choices.
There is no reason in principle porting your app to Win32 using WINE with a bit of testing can't work, but whether it is practical depends on how much tweaking you need to do to make things work well on both platforms. My guess is that most people looking at this choice don't think it is practical. If getting your Win2000 app to work on WINE as as easy as getting it to work on Windows XP, then I'm sure many more people would be eager to make a Linux offering.
Google has money and is technically innovative. Having a player like this attempt a port of their Win32 app to WINE could be a very interesting development. If they're only going to throw out a half baked version of their closed source Win32 apps, it's hardly important news. But if they contribute back improvements to WINE or create an open source facade that abstracts the differences between the two, it could be very significant.
Re:Yuck (Score:3, Interesting)
We have to remember that Google does pay for Linux apps through bounties so they are giving something back. I doubt we will see real ports until a killer worm takes out 50% of all Microsoft Windows boxes.
Re:Yuck (Score:2)
We all joke about it a lot, but you really should rtfa before complaining.
You needn't manage a wine installation to run this ported app in linux. The install is just gonna be a matter of installing Picasa by itself. The needed parts of wine will be statically linked and not something you need to touch or fret at all. It will not use your existing wine install. One of the goals listed is that they intend to make
Will it be as bad as Kylix? (Score:2, Interesting)
It was slow, crash-prone, and just plain messy to install. While WINE has likely improved since then, I'm still not convinced that it is suitable for use in production applications.
Re:Will it be as bad as Kylix? (Score:2)
Re:Will it be as bad as Kylix? (Score:2)
Three days isn't really enough time to tell if a more than trivial program is going to crash, especially given that your code coverage of the IDE's codebase was very unlikely to have been anywhere near 100% in that short period of time.
Re:Will it be as bad as Kylix? (Score:2)
BTW I suspect "using winelib" is a far cry from running under the full Wine emulator.
Re:Will it be as bad as Kylix? (Score:2)
Google and "limited beta"? (Score:5, Funny)
Btw, anyone want a GMail account?
PPC Linux support? SPARC Linux support? (Score:2, Insightful)
Wine, however, is only for x86-compatible systems. Will this software from Google only run on x86 Linux systems, and not on PPC Linux and SPARC Linux, amongst other Linux ports?
Re:PPC Linux support? SPARC Linux support? (Score:2)
This is not the WINE you have used, which allows run-t
Re:PPC Linux support? SPARC Linux support? (Score:2)
This gives me a very odd feeling. (Score:4, Interesting)
The new program is reportedly re-tooled to work perfectly under CodeWeaver's CrossOver Office Wine emulation. This may mean that Linux Picasa is using the program's own native Windows DLLs (dynamic link libraries).
This gives me a very odd feeling.
While for one side this will be very good for Linux users as this technology may be used in the future, allowing a fast deployment and development of very good programs, will this also mark a real beginning for Linux closed-source programs and binary installations?
Re: This gives me a very odd feeling. (Score:2)
To be specific, it'll give users of vanilla, x86, current, supported Linux distros a choice. Hard to see how it's giving users of other distros, or on other platforms, much of a choice...
Quick question... (Score:4, Interesting)
Re:Quick question... (Score:2, Informative)
Headline: (Score:5, Insightful)
An old, marrowless, dried up, bone, with no meat on it, and, yet, there it is.
Basically they're making a Windows app run on Linux, using Wine. Why didn't we think of that?
People will moan and bitch about more free stuff (Score:5, Interesting)
Given Google don't make any money from Picasa, the Linux client is a loss-leader. So, it makes sense to get the first Linux version in the easiest way possible. And that is Wine. That's what it was written for. In the free software world, there is always someone who will say "I want that for free!", and "Now that I have it for free, I want it better". If you do that in a restaurant, they'll sprinkle crumbled turd on your food. On the internet, all they can do is ignore you.
Check out the code contributions - there are lots of bugs found & fixed by the Google guys that are working on this. It's not like they are saying "Go run on wine, we don't care", it's "Go run on wine, and we've given you the most help we can".
A tool like Picasa, which was written from the ground up for Windows, is not a candidate for a "Linux Port". It would need a "Linux re-write". Maybe a future version could be built using tools to help with platform independance...but Google have much bigger things to worry about.
John
Re:People will moan and bitch about more free stuf (Score:2, Insightful)
Re:People will moan and bitch about more free stuf (Score:2, Insightful)
Re:People will moan and bitch about more free stuf (Score:2)
Re:People will moan and bitch about more free stuf (Score:2, Insightful)
Re:People will moan and bitch about more free stuf (Score:2)
They don't make money for sure but they get exposure. People will recognize the brand "Google", use their search engines more, click on adds supplied by Google and $PROFIT$! My mother, a total computer illiterate, uses Google above anything else. For her Google is the internet. And IMO that is what google is doing by giving away free software. It's a PR move, pure and simple, to promote the brand, Google.
Companies don't give out
Re:People will moan and bitch about more free stuf (Score:2)
All in all, I like what they are doing, but I am a bit unhappy that Windows is treated so special.
Re:People will moan and bitch about more free stuf (Score:2)
Well, in the case of Picasa, the reason is that they didn't actually write it at all. They bought it.
Earthiness? (Score:2, Interesting)
A hint of things to come? (Score:5, Interesting)
native (Score:2, Insightful)
Re:native (Score:2, Insightful)
Re:native (Score:3, Insightful)
Transparent to users, huh? (Score:2)
Wine has come a long way since then, so I suppose it could be translucent.
Cool (Score:3, Informative)
People complaining should be happy that anyone at all these day is bothering with porting over desktop apps to linux.
Re:Cool (Score:5, Insightful)
Google Earth (Score:3, Informative)
Yeah, it already works in Wine [gentoo-wiki.com], but it would be nice to be able to run it without that.
Oh goody. Can't wait. (Score:3, Insightful)
Why are they bothering? This is going to be greeted with all the enthusiasm of someone breaking wind in a swimming pool. It's great that Google have realized that it has people who want to use it's services that run linux but unless they are going to do the porting job properly I don't think they should do it at all.
Perhaps that's a little harsh but I don't want some clunky Windows app with a ton of Wine libs following it around cluttering up my system. Personally I find digiCam to be as good if not better than Picasa so I think I'll stick with that - certainly on Linux I feel that is the application they are competing against.
Good for Google. (Score:2, Insightful)
So... is Wine an emulator? (Score:2, Funny)
Wine is not, as has sometimes been said, a Windows emulator...
Next Paragraph:
The new program is reportedly re-tooled to work perfectly under CodeWeaver's CrossOver Office Wine emulation.
If I hadn't spent countless hours trying to get ANYTHING useful running in Wine, I might be confused.
Why do it half assed (Score:4, Insightful)
And don't fool yourselves, Wine IS an emulator. Anything that has to mediate between native software code and native OS/Hardware code is an emulator. It may not be a hardware emulator (i.e. not translating to machine code the software code wasn't written for), but it is a software emulator translating windows calls to Linux calls. And in any case, emulators are slow.
Re:Why do it half assed (Score:3, Insightful)
Are GTK, QT, and Mono emulators?
Hell, what about XGL and/or Xorg? Or GTK on Win32? What about Cygwin? What about Xen, or VMware, or Java?
What is an emulator, anyways? What's the difference between "native" and "foreign"? How many layers of translation are okay? What if an app relies on libc? That's "translation" between native (assembly) code and the hardware.
Your understanding of these things is very, ver
Ha! (Score:2)
Wha? what do you mean "only runs on intel processors"? You mean this is x86-binary only? Yeah that mindset served us really well in the past...
Maybe that's just me, but until they GPL their code this is a non-story. Wine getting more bugfixes on the other hand is good news. It's always nice to see an open source project progress - especially with help from commercial vendors.
Wordperfect Office 2000 for Linux anyone? (Score:3, Insightful)
Corel forked wine to add some custom features they needed that head wine didn't have (fonts and printing, for example). This fork proved their undoing. It was never synced back to the head branch and soon died, orphaning their version of wine. Further glibc advances broke wine with every release, effectively preventing corel's wine from running on anything newer than RH 7.
As long as google doesn't do the same thing, we'll probably be okay.
Re:transparent crap (Score:2, Interesting)
It'll probably be like any application that comes with its own GUI, networking, etc, library.
Hopefully Google will make it transparent enough to only need a single shared Wine install between different Google applications,
Re:Are they going to use winelib? (Score:2)
You are correct, the CodeWeavers always sew the apps neatly.
Re:IBM nah Google. (Score:5, Insightful)
Then you go on to say, "the other guys just R & D it". Oh please, it'll be years, if ever, before Google can claim that they've produced a fraction of the amount of Open Source code as IBM and Sun. There is no company that the R & D statement would apply to more than Google. IBM and Sun produce a ton of Open Source code, whereas Google produces almost nothing. These aren't even going to be native Linux apps and several of those apps already work in Wine.
I love the words you used as well, "Google by some magic". Sheesh...
Re:IBM nah Google. (Score:2)
Re:IBM nah Google. (Score:3, Informative)
(Though I'd use a Picasa port before I use F-Spot, the latter is still too incosistent for me.)
Re:IBM nah Google. (Score:2)
What IBM and Sun are doing for desktop Java (SWT and the next version of Swing) is going have a much greater long-term impact on "Desktop Linux" than a photo app will.
[No, this is not a cue to start bitching about Java.]
Picasa is NOT a photo editing tool. (Score:5, Insightful)
Rather, it is some sort of photo organizer/viewer. It does have a few (very simple and easy to use) tools to enhance contrast/color etc., but it's purpose is nothing like Photoshop/Gimp/PaintShopPro/etc.
Sorry for not being more clear about what it really is. It's probably because I still wonder myself... Maybe someone who has actually found a use for it can be clearer.
Re:Picasa is NOT a photo editing tool. (Score:3, Informative)
And that is what makes Picasa the right applications for the majority of users, since it does fill their limited needs when it comes to photo editing. The average user simply do not need all the functionality you find in the likes of Photoshop/Gimp/PaintShopPro/etc. Using Photoshop/Gimp/PaintShopPro/etc when you only do basic tasks like cropping and rede
Re:IBM nah Google. (Score:2)
Re:Just F***n' Great (Score:2)
Re:Just F***n' Great (Score:2)
Re:"free" as in free beer (Score:2)
Re:"free" as in free beer (Score:2)
Re:"free" as in free beer (Score:2)
So that's what you call it.
Re:Boneheads (Score:4, Informative)
It is 2006 and win32 is 97% of the market for desktop apps like Picassa.
Re:Boneheads (Score:2)
Re:not another Goomur, but almost... (Score:4, Informative)
Still, this is a decent start. I'd be more excited about them porting the desktop search (as long as I can still disable the sharing of info. to Google).
Re:not another Goomur, but almost... (Score:2, Informative)
Wrong approach. (Score:2)
Don't get me wrong, Codeweavers are doing a great job with Office-type programs, but they're still far from perfrect in execution. If you've used Crossover for any length if time, you'd know that running most apps for more than a few minutes at a time requires multiple "Terminate Windows Applications" per day. And they probably will never run as w