Yup, and there is also giFT, which unlike DC++ and emule, work on a completely open protocol. giFT works very similarily to how fasttrack networks like KaZaA work, and was once even able to connect to KaZaA before the kazaa developers changed the protocol to break giFT.
Re:giFT has too many roadblocks for Windows users
on
Shutting down Kazaa
·
· Score: 1
> SSH, CVS, Cygwin, Cygwin Xfree86, Perl, the Ogg libraries, and more; 2. learn how to use Cygwin; 3. configure the dependencies; and
SSH, CVS, Cygwin, XFree86, perl are not giFT dependencies.
Ogg libraries are a optional depedency. CVS is currently required to get the giFT sources, but of course, that will change once giFT is actually released. binaries will of course be provided for win32 users then.
> 4. compile giFT when they could just go on kazaalite.
Completely true, but you have to realize that giFT hasn't officially been released (well, not since the whole OpenFT thing).
It's pretty hard to find very new releases and really old/rare releases on directconnect. And the problem with fake sharing is hurting it more and more, especially with clients like dctc/dc_gui where you can type how much you want to virtually share in GB:p
The problem with eDonkey is that it's pretty centralized in terms of the way OpenNap was centralized (actually more, as there is no "networks" in eDonkey). If the RIAA/MPAA saw eDonkey as a threat, they could easily take down the individual server operators (like the RIAA once did with OpenNap server operators)
Overnet tries to solve it, but it's just not there yet compared to KaZaA and even giFT/openFT. Hopefully it will be in the future, because I love ed2k and related services.
I'm a gamer, who plays quake3, and who has two pretty decent (and modern) monitors. One is CRT (a Viewsonic 19" E90f), and one is a LCD (a Hitachi 17" CML174). The Hitachi DOES have some ghosting--- everything seems to move faster than on the Viewsonic and things sometimes feel blurry. This happens to a point where I only play FPS games on my CRT.
HOWEVER, I use my LCD for 90% of my other work, and I plan to sell my Viewsonic soon. Why? Because text is just so damn readable on the Hitachi. I just love it.
For everyone except very hardcore competitive gamers and other people with special needs, I really recommend LCD's.
The reason Abiword acts, looks and feels native on Windows is because it is. It does NOT use gtk on windows. Rather, it uses the win32api through the Abisource Application Framework, a lightweight and crossplatform wrapper created alongside abiword.
It's actually pretty neat.. the source is in (abiword_source_root/src/af). It provides a level of nativeness that can't ever be acheived through something like gtk+, which is (still) quite half-assed on windows.
Six months ago, I'd would have agreed with you that font rendering (especially AA) in X was not up to font rendering in Windows. However, since then, Xft2 has come out, which offers even better sub-pixel antialiasing support than Microsoft Cleartype. I'm currently running xft2+XFree86 4.2.99 on gentoo, and the fonts look better on my lcd than in WindowsXP.
> I'm really happy with QT (other than stupid reinventing of STL stuff).
Well, Qt and STL happily coexist (especially since Qt3). The reason TT invented their own STL-like classes is because Qt predates the time when STL was fairly portable and standardized across platforms. If Qt was written today, it probably would make full use of the STL.
> Gtkmm is very good for a veneer on top of C language OO, but isn't remotely as clean or consistent.
1. It's cite, not site. 2. I cited evidence of people who like gtkmm. 3. As for my own experiences with gtkmm, I actually used it before I ever used Qt. I went from Apple's C++ MacApp Framework (anyone still remember that?:)) to the BeOS API. When I switched from BeOS to Linux, I used gtkmm before switching to Qt.
> IMHO, I think this is how most open source projects have been run for the last twenty years. By your chacterizations, it sounds like GNOME just seems to be more of a mini-Government than a free software project.
In KDE 3.1, change kcontrol->desktop->panels->menus->Menu Item Format to "Description (Name)".
Most of Qt's users in terms of ISVs are proprietary clients on Windows. Because of the nature of Qt, you would never know if they are using Qt..or something like MFC. On X, on the other hand, it's very easy to tell if someone is using Motif, Qt, or GTK.
If Harmony was ever 100% source compatable with Qt, it would have really been a drop in replacement for Qt. KDE only provides source, and only ever has. The packager could have picked to use Harmony or Qt.
> Considering that so many of the leading KDE developers worked for Trolltech, this didn't look like it would ever happen.
> if C++ is your thing then both Qt and GTKmm are excellent.
Have you actually ever used gtkmm? The only people I've known who ever liked it were complete C++ purists who hated the idea of moc, or people who've never used Qt.
A year ago, Apple would not have been so outspoken against Microsoft. They needed Microsoft to continue their applications for MacOSX. They needed IE and Office, for example. Now, with Apple trying to develop their own strong line of applications (starting with the iSeries of applications), and culminating most recently with their own webbrowser (or, Internet Explorer replacement), Safari.
The next logical step, would, of course, be to have an Apple branded office suite to compete with Microsoft Office (perhaps a mega-AppleWorks). Perhaps they are already porting OpenOffice or KOffice (or Gobe).
Slashdot Mirror
Yup, and there is also giFT, which unlike DC++ and emule, work on a completely open protocol. giFT works very similarily to how fasttrack networks like KaZaA work, and was once even able to connect to KaZaA before the kazaa developers changed the protocol to break giFT.
> SSH, CVS, Cygwin, Cygwin Xfree86, Perl, the Ogg libraries, and more; 2. learn how to use Cygwin; 3. configure the dependencies; and
SSH, CVS, Cygwin, XFree86, perl are not giFT dependencies.
Ogg libraries are a optional depedency.
CVS is currently required to get the giFT sources, but of course, that will change once giFT is actually released. binaries will of course be provided for win32 users then.
> 4. compile giFT when they could just go on kazaalite.
Completely true, but you have to realize that giFT hasn't officially been released (well, not since the whole OpenFT thing).
It's pretty hard to find very new releases and really old/rare releases on directconnect. And the problem with fake sharing is hurting it more and more, especially with clients like dctc/dc_gui where you can type how much you want to virtually share in GB :p
The problem with eDonkey is that it's pretty centralized in terms of the way OpenNap was centralized (actually more, as there is no "networks" in eDonkey). If the RIAA/MPAA saw eDonkey as a threat, they could easily take down the individual server operators (like the RIAA once did with OpenNap server operators)
Overnet tries to solve it, but it's just not there yet compared to KaZaA and even giFT/openFT. Hopefully it will be in the future, because I love ed2k and related services.
> Dammit, when you worked at Netscape, JWZ, Navigator sucked ass. Sorry, dude, but Communicator has improved since you had a hissy fit and left.
That's not true; Netscape 1.0, 2.0, and 3.0 were much better than Netscape 4.x, 5.x, 6.x.
Between NS 3.x and 7.x, I prefer 3.x, without all of 7.x's AOL crap.
While at Netscape, he also invented the blink tag.
> Maybe he gets a bit whiny at times though.
Understatement at best.
laff.. moral of story: always troll with accounts other than your main one ;)
I'm a gamer, who plays quake3, and who has two pretty decent (and modern) monitors. One is CRT (a Viewsonic 19" E90f), and one is a LCD (a Hitachi 17" CML174). The Hitachi DOES have some ghosting--- everything seems to move faster than on the Viewsonic and things sometimes feel blurry. This happens to a point where I only play FPS games on my CRT.
HOWEVER, I use my LCD for 90% of my other work, and I plan to sell my Viewsonic soon. Why? Because text is just so damn readable on the Hitachi. I just love it.
For everyone except very hardcore competitive gamers and other people with special needs, I really recommend LCD's.
Well, Bluecurve isn't exactly 100% propreitary. You can use it under other distros too.
;)
emerge redhat-artwork under gentoo
The reason Abiword acts, looks and feels native on Windows is because it is. It does NOT use gtk on windows. Rather, it uses the win32api through the Abisource Application Framework, a lightweight and crossplatform wrapper created alongside abiword.
It's actually pretty neat.. the source is in (abiword_source_root/src/af). It provides a level of nativeness that can't ever be acheived through something like gtk+, which is (still) quite half-assed on windows.
Six months ago, I'd would have agreed with you that font rendering (especially AA) in X was not up to font rendering in Windows. However, since then, Xft2 has come out, which offers even better sub-pixel antialiasing support than Microsoft Cleartype. I'm currently running xft2+XFree86 4.2.99 on gentoo, and the fonts look better on my lcd than in WindowsXP.
> I'm really happy with QT (other than stupid reinventing of STL stuff).
Well, Qt and STL happily coexist (especially since Qt3). The reason TT invented their own STL-like classes is because Qt predates the time when STL was fairly portable and standardized across platforms. If Qt was written today, it probably would make full use of the STL.
> Gtkmm is very good for a veneer on top of C language OO, but isn't remotely as clean or consistent.
Agreed.
wxWindows uses native widgets on x11 (through gtk), on windows, and macosx
:o
qt uses native widgets in windowsxp (through visual styles) and on x11 (through itself), and on macosx (through aqua)
gtk uses native widgets in x11 (through itself)
swing uses native widgets on x11 (through itself)
ibm eclipse swt uses native widgets in x11 (through gtk usually), on windows, and on macosx
gtk+ is not a native platform
1. It's cite, not site. :)) to the BeOS API. When I switched from BeOS to Linux, I used gtkmm before switching to Qt.
2. I cited evidence of people who like gtkmm.
3. As for my own experiences with gtkmm, I actually used it before I ever used Qt. I went from Apple's C++ MacApp Framework (anyone still remember that?
To tell you the truth... any distro that is not Redhat.
Redhat is also fine, as long as you install third party KDE rpms or build it from source (and don't use the supplied version of KDE)
Also all the *box derivatives from blackbox, such as fluxbox, openbox, (and sorta, waimea), also all deserve recognition.
:)
> Both camps have a lot of vocal jerks in them, who apparently hate each other for NO GOOD REASON.
Well, the fact that GNOME was mainly started as a reaction to KDE probably has something to do with that.
> IMHO, I think this is how most open source projects have been run for the last twenty years. By your chacterizations, it sounds like GNOME just seems to be more of a mini-Government than a free software project.
In KDE 3.1, change kcontrol->desktop->panels->menus->Menu Item Format to "Description (Name)".
whee..
Most of Qt's users in terms of ISVs are proprietary clients on Windows. Because of the nature of Qt, you would never know if they are using Qt..or something like MFC. On X, on the other hand, it's very easy to tell if someone is using Motif, Qt, or GTK.
Trolltech's buisness comes from these people.
If Harmony was ever 100% source compatable with Qt, it would have really been a drop in replacement for Qt. KDE only provides source, and only ever has. The packager could have picked to use Harmony or Qt.
> Considering that so many of the leading KDE developers worked for Trolltech, this didn't look like it would ever happen.
At that time, very few did.
> if C++ is your thing then both Qt and GTKmm are excellent.
Have you actually ever used gtkmm? The only people I've known who ever liked it were complete C++ purists who hated the idea of moc, or people who've never used Qt.
word.
A year ago, Apple would not have been so outspoken against Microsoft. They needed Microsoft to continue their applications for MacOSX. They needed IE and Office, for example. Now, with Apple trying to develop their own strong line of applications (starting with the iSeries of applications), and culminating most recently with their own webbrowser (or, Internet Explorer replacement), Safari.
The next logical step, would, of course, be to have an Apple branded office suite to compete with Microsoft Office (perhaps a mega-AppleWorks). Perhaps they are already porting OpenOffice or KOffice (or Gobe).
Have you ever heard of Opera 7? It actually handles more CSS2 than Gecko does atm.
> As soon as the newer KDE stuff worms its way into the Gentoo package tree.
It's already there (and has been forever)
ACCEPT_KEYWORDS="~x86" emerge kde
> I think you may have a point there: (referenced from http://www.livejournal.com/talkread.bml?journal=jw z&itemid=138051
)
KHTML:
virtual void layout();
Gecko:
NS_IMETHOD Reflow(nsIPresContext* aPresContext, nsHTMLReflowMetrics& aMetrics, const nsHTMLReflowState& aReflowState, nsReflowStatus& aStatus);