![]() ![]() So KPhotoAlbum installs a lot of KDE stuff.Ī really lot of GTK+ Applications install the half of GNOME too, just becease they are compiled like then. If you compile KPhotoAlbum yourself you can go with about 60-100mb of dependencys but on Archlinux the packages are compiled in one way! And thats the way that most people want and the most people want a full KDE Integration. That are for example that you can´t choose with which options your applications is compiled. If you choose a simple distribution with a simple package manager like pacman you have to take the disadvantages that pacman brings. Gentoo for example is the opposite of simple, but the existing system is (in the most cases) smaller and with less unused stuff than an Archlinux system. The main problem here is that Arch is simple AND lightweightĪ lot of people think that simple = lightweight but thats not the fact Thats why it tooked so many years that we have the status we have now. They didn´t had a choose and was forced to write from scratch. back in the times were not that much libs existed. And I personally use jumanji.Ĭhromium uses Safaris Engine and Safari uses a changed Version of KHTML which is WebkitĪnd the beginning of Opera, Firefox and Internet Explorer are long long ago. We already had Firefox and Opera, but then Chromium arised, and many people found it to be better. If you had been right, we would still be using Mosaic 19 or Netscape Navigator 11 to browse the web.Īnd the web browsers are good example I think. Look how many window managers, image viewers, web browsers - and even programming languages! - we have now. If I used all features of Digikam, I'd probably won cry about it's dependencies.Ģ) People do really write new applications similar to those which exist. And I'm very surprised that it doesn't yet exist. Tagging and searching is everything I am looking for.Ī GTK+ version of KPhotoAlbum - that's my target, I think. When F-Spot, digiKam, KPhotoAlbum and so on exist, why should someone waste developing time to write a new one instead to increase the usability of the existing one?ġ) F-Spot and Digikam are big applications, with image importing, editing and exporting features. ![]() You cant say "On windows i have no problems with 5GB of dependencys (already installed on my system) but on Linux 300mb is just too much"Īnd the most applications you´ll find will either be written in GTK+ or Qt/KDElibs so either you install GTK+ as dependency or Qt/KDElibs but you cant live without them. NET is larger than a full operating system so you cant blame and the Win API is a full operating system the applications you found for windows are all using (i bet) the Win API or even. When F-Spot, digiKam, KPhotoAlbum and so on exist, why should someone waste developing time to write a new one instead to increase the useability of the existing one? Just that people get a wood with getting there environments as light as possible? Is it that erotic to have TB of unused Harddisk space?ītw. When you decidie to use a lightweight environment you also have to accept that you dont have much features. It would take a lot of time and it woulnd´t have any advantage to other applications.Įven my EeePC with 4GB of Harddisk runs digiKam, you can´t seriously tell me that KDElibs is a too big dependency. Nobody will write something like digikam completely from scratch without a library. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |