Umm, what are you running? Everything installs via apt-get without a hitch on my Debian Sarge servers and similarly with urpmi on my Mandriva 2006 desktop. Do you have a very strange configuration, or a system that doesn't auto-meet dependencies? If you're on Debian or Mandriva feel free to email me and I'll try to help you out.
Is there something wrong with those apps? I have GTK apps like GAIM open for weeks on my KDE desktop. I mean sure it's somewhat disadvantageous because you have the memory requirements of both libraries, but I think that would pale next to the app-internal memory for the 3D rendering or whatever. So if these apps are unstable, then there's something wrong with that partiular app or your hardware or something, this is not just a general GNOME/KDE desktop inter-op issue like theming or something.
Works on KDE as a kio-slave. Just use fish:// in Konqueror or a file dialog for access. And before you say something about how this is a Mac discussion, remember that KDE runs on Mac:-). But yeah, I often find myself wishing for that feature when I'm forced to use a Windows system.
The web component of Kiko is completely free, and will stay that way. We're currently developing Outlook/mobile phone sync, which we'll probably charge for, and also a number of companies have expressed interest in licensing Kiko for internal use. But remember that we only have four full-time employees, so we don't need to rake in revenue the way a highly-capitalized service like Trumba or 30boxes does. Do let us know, by the way, if there are any other features you need, and we'll do our best to integrate them.
Real question (and you're not the first person I've heard this kind of comment from about web apps):
Why is leaving another program open all the time any different than just leaving a browser window open all the time? Especially because if you can install another program on your desktop, you can probably install Firefox, and then just leave Kiko open in a tab.
I just really don't understand this complaint, despite it's frequency, and I'd be happy if you could explain it to me.
Really. We don't yet have real groupware features, like shared calendars for resources, though we're working on those. But if you create a calendar for your group, we give you multiple ways to get it onto your users' calendars. If they use Kiko, any invitations sent out will automatically appear on their calendars, but even if they aren't Kiko users they'll still get invitations via email and be able to view an RSS feed. And our email/reminder send is now very stable. So try it out, and if you think there's a missing feature, let us know and we'll add it.
and better calendar display options
on
Google Calendar
·
· Score: 1
Also, I like Kiko's interface where you can easily turn labels on and off depending on what you want to see. I believe they're going to implement the share-by-label system as well.
It's interesting to see how the arms race continues--just before Google calendar released, Kiko added iCal feed consumption as well. I wonder what other features will debut as Kiko, Google, and others all try to one-up each other in the calendar wars....
2) Take the box off the new while it's doing the sim. Thus, sim gets done, box doesn't get owned, net stays secure.
3/4) These aren't evidence that your IT department values security over ease-of-use, but rather that they're totally incompetent, utterly crazy, or both.
So when Slashdot hosts a blog carnival, can we all officially stop pretending that Slashdot isn't a blog? As a purely professional blogger (philosophy--see the link above), and one who reads mostly academic blogs (CrookedTimber, LanguageLog), I'm tired of Slashdotters ranting about blogs, which despite their quality-control-issues (not so different from/., eh?) are NOT simply endless whining.
Kat is a major cpu hog, even if a cool "keeping up with Win/Mac on the cheap" tech. Turn that off and you'll find that KDE 3.4 is getting you some major speed improvements.
Not everyone, I'm still on Mandriva. I know everyone says it's just for new people, but no one has given me a reason to switch: SuSE's YaST screws up hand-edited config files, Fedora requires much more set up to get running, and Ubuntu--why? Slackware and Gentoo just don't make sense for a laptop user who upgrades frequently. So why the beef with Mandriva--what's the downside? Everything they write is GPL, too.
Besides, Mandriva has a fairly good community, as I'll demonstrate here by reiterating my offer to provide free email/IM support to any Slashdot-reading Mandriva user (or potential switcher). I'm not a kernel-hacker or anything, but I have been using it on desktops, laptops, and servers for 4 years now, and I can fix most things when they break.
Interesting comments. I recently converted the six separate Wordpress installs on my site into one Drupal codebase, and the only major problems were with importing posts, which I suppose is difficult anytime you're not doing something obvious like MT->WP or suchlike (and perhaps even then). After taking the time to figure out (definitely its own vocabulary-world) how Drupal works, I started using it for my paid projects and found it extremely flexible.
I encountered the same basic problem you did with sections, and just decided to use multiple 'sites' with shared tables as my fix. Oh, and I agree with you 100% about the Drupal forums.
I don't really know anything about Mambo/Joomla. I see that it has the kind of "sections" support that you (and I) were looking for from Drupal...but does it have anything as flexible as the taxonomy and flexinode modules? And most importantly for my uses, does it have anything with the power of organic groups? I didn't really find a lot of features information on the Joomla website, and no indication of anything like that in the demo, but presumably it doesn't have all the modules/plugins loaded. Also, why the name change/fork? That's not really explained either.
If you ever want to pick a brain on Drupal stuff with better response times than the forums, feel free to email me (I don't have time to cruise the forums).
I was looking for something similar, and I think in the end you're going to end up with either Mambo or Drupal. Mambo has friendlier forums and seems easier to get going, but Drupal is better architected for growth--both of features and of userbase. Both are actively developed. If you have questions about Drupal before you start out or need help installing it, feel free to drop me an email.
Drupal does everything you want out of the box, except in order to get different style-sheets for each blog you'd have to upload the stylesheet yourself and set it as usable--but that's perhaps desirable as a security feature anyway, otherwise your users could be writing their own javascript without oversight.
Hope that helps, and good luck to you no matter what you choose.
You realize Drupal is actually what runs The Onion? You can have it up and running smoothly in a day--a week if you're doing substantial skinning or have to write SQL scripts to import previous content (though some are available). If you do go with Drupal and stall out in the forums, feel free to email me with questions.
If you're making a living off of the pictures you put in your books, perhaps it's worth your while to opt-out. But the vast majority of the books out there are almost exclusively text, for which the resolution is meaningless. Besides, do you think Google is going to display your images at 600dpi? That seems awfully unlikely.
Sorry to respond so late, but just install the framework (by dropping it into a web-accessible folder), then just drop each module in a folder inside that. It really is that simple. Then just drop the *.dist off of *.php.dist in the config files, and use the web configurator. Have any snags, email me.
1) Qt/KDevelop 2) It already is. You just need a no-bloat distro. And forget OpenOffice. 3) Are you crazy? There's way more code free for the taking for Linux than there is for Win.
Installing.rpms or.debs is trivial. Not packaging your program for Linux is no different than no packaging your program with Installshield on Windows, leaving most users unable to deal with the compiling, etc. I think all you're seeing there is that most Linux apps are the equivalent of shareware, and it takes work to figure out which ones are decent. After all, professionally packaged stuff like nvidia drivers install like a charm on a huge variety of systems.
The hardware and the applications, of course, won't really come until there's a tipping-point for some other reason. Especially vertical-market-apps, which are the last to transition to a new program (remember all the POS systems and stuff running on DOS longer after Win was out?).
One of the tricky things about OSS is that no-one has the money for shelf displays or TV ads, so there's less information available (or rather, it takes more work to find it) about which applications are the best for a given task.
That said, this is a classic case of just using the wrong application. Next time, given that you're using Fedora and have GTK installed, use GRIP. You won't be dissappointed.
Just like shareware in the Windows world, there are often many applications which claim to do something but don't do it well.
because Linux is just the kernel, and the main problem with the kernel is lack of hardware drivers, which Linux has more of than SkyOS and Zeta have. The killer app and Windows compatibility are also more likely to come on Linux because its user-base and corporate backing are already larger.
In desktop distros like Mandriva, the home folder is already the default view of the system, meaning everything the user sees is directly relevant to him/her.
So it sounds like your "Linux" gripes are really Desktop gripes, and GNOME is already moving in the directions you propose. If you think they need to move further, why not goad them in that direction rather than suggesting that people jump ship, which will only exacerbate the problems you mention due to dissipating the critical mass necessary for driver development to happen.
Umm, what are you running? Everything installs via apt-get without a hitch on my Debian Sarge servers and similarly with urpmi on my Mandriva 2006 desktop. Do you have a very strange configuration, or a system that doesn't auto-meet dependencies? If you're on Debian or Mandriva feel free to email me and I'll try to help you out.
Is there something wrong with those apps? I have GTK apps like GAIM open for weeks on my KDE desktop. I mean sure it's somewhat disadvantageous because you have the memory requirements of both libraries, but I think that would pale next to the app-internal memory for the 3D rendering or whatever. So if these apps are unstable, then there's something wrong with that partiular app or your hardware or something, this is not just a general GNOME/KDE desktop inter-op issue like theming or something.
Works on KDE as a kio-slave. Just use fish:// in Konqueror or a file dialog for access. And before you say something about how this is a Mac discussion, remember that KDE runs on Mac :-). But yeah, I often find myself wishing for that feature when I'm forced to use a Windows system.
The web component of Kiko is completely free, and will stay that way. We're currently developing Outlook/mobile phone sync, which we'll probably charge for, and also a number of companies have expressed interest in licensing Kiko for internal use. But remember that we only have four full-time employees, so we don't need to rake in revenue the way a highly-capitalized service like Trumba or 30boxes does. Do let us know, by the way, if there are any other features you need, and we'll do our best to integrate them.
Real question (and you're not the first person I've heard this kind of comment from about web apps):
Why is leaving another program open all the time any different than just leaving a browser window open all the time? Especially because if you can install another program on your desktop, you can probably install Firefox, and then just leave Kiko open in a tab.
I just really don't understand this complaint, despite it's frequency, and I'd be happy if you could explain it to me.
Glad to hear it. Do let us know if you have any bug reports or feature requests, and we'll do our best to address them.
Really. We don't yet have real groupware features, like shared calendars for resources, though we're working on those. But if you create a calendar for your group, we give you multiple ways to get it onto your users' calendars. If they use Kiko, any invitations sent out will automatically appear on their calendars, but even if they aren't Kiko users they'll still get invitations via email and be able to view an RSS feed. And our email/reminder send is now very stable. So try it out, and if you think there's a missing feature, let us know and we'll add it.
Also, I like Kiko's interface where you can easily turn labels on and off depending on what you want to see. I believe they're going to implement the share-by-label system as well.
It's interesting to see how the arms race continues--just before Google calendar released, Kiko added iCal feed consumption as well. I wonder what other features will debut as Kiko, Google, and others all try to one-up each other in the calendar wars....
1) Ever heard of a file server?
2) Take the box off the new while it's doing the sim. Thus, sim gets done, box doesn't get owned, net stays secure.
3/4) These aren't evidence that your IT department values security over ease-of-use, but rather that they're totally incompetent, utterly crazy, or both.
So when Slashdot hosts a blog carnival, can we all officially stop pretending that Slashdot isn't a blog? As a purely professional blogger (philosophy--see the link above), and one who reads mostly academic blogs (CrookedTimber, LanguageLog), I'm tired of Slashdotters ranting about blogs, which despite their quality-control-issues (not so different from /., eh?) are NOT simply endless whining.
Kat is a major cpu hog, even if a cool "keeping up with Win/Mac on the cheap" tech. Turn that off and you'll find that KDE 3.4 is getting you some major speed improvements.
Not everyone, I'm still on Mandriva. I know everyone says it's just for new people, but no one has given me a reason to switch: SuSE's YaST screws up hand-edited config files, Fedora requires much more set up to get running, and Ubuntu--why? Slackware and Gentoo just don't make sense for a laptop user who upgrades frequently. So why the beef with Mandriva--what's the downside? Everything they write is GPL, too.
Besides, Mandriva has a fairly good community, as I'll demonstrate here by reiterating my offer to provide free email/IM support to any Slashdot-reading Mandriva user (or potential switcher). I'm not a kernel-hacker or anything, but I have been using it on desktops, laptops, and servers for 4 years now, and I can fix most things when they break.
Interesting comments. I recently converted the six separate Wordpress installs on my site into one Drupal codebase, and the only major problems were with importing posts, which I suppose is difficult anytime you're not doing something obvious like MT->WP or suchlike (and perhaps even then). After taking the time to figure out (definitely its own vocabulary-world) how Drupal works, I started using it for my paid projects and found it extremely flexible.
I encountered the same basic problem you did with sections, and just decided to use multiple 'sites' with shared tables as my fix. Oh, and I agree with you 100% about the Drupal forums.
I don't really know anything about Mambo/Joomla. I see that it has the kind of "sections" support that you (and I) were looking for from Drupal...but does it have anything as flexible as the taxonomy and flexinode modules? And most importantly for my uses, does it have anything with the power of organic groups? I didn't really find a lot of features information on the Joomla website, and no indication of anything like that in the demo, but presumably it doesn't have all the modules/plugins loaded. Also, why the name change/fork? That's not really explained either.
If you ever want to pick a brain on Drupal stuff with better response times than the forums, feel free to email me (I don't have time to cruise the forums).
I saw speeds as high as 700mb in 3m, YMMV.
I was looking for something similar, and I think in the end you're going to end up with either Mambo or Drupal. Mambo has friendlier forums and seems easier to get going, but Drupal is better architected for growth--both of features and of userbase. Both are actively developed. If you have questions about Drupal before you start out or need help installing it, feel free to drop me an email.
Drupal does everything you want out of the box, except in order to get different style-sheets for each blog you'd have to upload the stylesheet yourself and set it as usable--but that's perhaps desirable as a security feature anyway, otherwise your users could be writing their own javascript without oversight.
Hope that helps, and good luck to you no matter what you choose.
You realize Drupal is actually what runs The Onion? You can have it up and running smoothly in a day--a week if you're doing substantial skinning or have to write SQL scripts to import previous content (though some are available). If you do go with Drupal and stall out in the forums, feel free to email me with questions.
If you're looking for something dead-simple, use Wordpress, stuff it with plugins, and skin the hell out of it.
If you're making a living off of the pictures you put in your books, perhaps it's worth your while to opt-out. But the vast majority of the books out there are almost exclusively text, for which the resolution is meaningless. Besides, do you think Google is going to display your images at 600dpi? That seems awfully unlikely.
Sorry to respond so late, but just install the framework (by dropping it into a web-accessible folder), then just drop each module in a folder inside that. It really is that simple. Then just drop the *.dist off of *.php.dist in the config files, and use the web configurator. Have any snags, email me.
1) Qt/KDevelop
2) It already is. You just need a no-bloat distro. And forget OpenOffice.
3) Are you crazy? There's way more code free for the taking for Linux than there is for Win.
Installing .rpms or .debs is trivial. Not packaging your program for Linux is no different than no packaging your program with Installshield on Windows, leaving most users unable to deal with the compiling, etc. I think all you're seeing there is that most Linux apps are the equivalent of shareware, and it takes work to figure out which ones are decent. After all, professionally packaged stuff like nvidia drivers install like a charm on a huge variety of systems.
The hardware and the applications, of course, won't really come until there's a tipping-point for some other reason. Especially vertical-market-apps, which are the last to transition to a new program (remember all the POS systems and stuff running on DOS longer after Win was out?).
One of the tricky things about OSS is that no-one has the money for shelf displays or TV ads, so there's less information available (or rather, it takes more work to find it) about which applications are the best for a given task.
That said, this is a classic case of just using the wrong application. Next time, given that you're using Fedora and have GTK installed, use GRIP. You won't be dissappointed.
Just like shareware in the Windows world, there are often many applications which claim to do something but don't do it well.
Any details on the WPA difficulty? My Mandriva 2006 install runs WPA fine on my Ralink 2500 chipset no brand wireless card.
because Linux is just the kernel, and the main problem with the kernel is lack of hardware drivers, which Linux has more of than SkyOS and Zeta have. The killer app and Windows compatibility are also more likely to come on Linux because its user-base and corporate backing are already larger.
In desktop distros like Mandriva, the home folder is already the default view of the system, meaning everything the user sees is directly relevant to him/her.
So it sounds like your "Linux" gripes are really Desktop gripes, and GNOME is already moving in the directions you propose. If you think they need to move further, why not goad them in that direction rather than suggesting that people jump ship, which will only exacerbate the problems you mention due to dissipating the critical mass necessary for driver development to happen.