Quite a lot of points, some of which don't have anything to do with Konqueror. But anyway:
Originally posted by jetman
For example, I've customized my KDE config so that I have two extra tabs on the Konqueror Navigation pane, to track the 'smb:/' (LAN) and 'system:/media' (Media) nodes. They work well, but the System Menu applet for Kicker doesn't know anything about these tabs. Therefore, I can't simply choose one of these custom nodes from the System Menu applet and jump to the area/node I'm looking for.
You're right, the System Menu applet doesn't know for one simple reason. It's a System Menu applet
for Kicker and has actually nothing to do with Konqueror except launch Konqueror with the indicated location. There is no correlation whatsoever between what you add in Konqueror and what shows up in the System menu applet.
Actually, the System Menu applet should also account for the 'Root Folder' node, which I believe comes std w/ Konqueror, or at least should be configurable.
No to / (root) folder, but definitely should be configurable. One of my pet issues as well. Why no to root folder? Users shouldn't be bothered by Filesystem details unless they have to. Part of the whole UNIX setup is that non-administrative users shouldn't be able to touch anything outside of their /home. Of course nothing prevents them from seeing the whole filesystem if they want to. So the configurability of the applet definitely will be an advantage.
This also applies to the integrated Terminal Emulator in Konqueror. If one opens the Terminal when visiting the 'Root folder' node, changing directories in the Navigation pane are reflected in the Terminal. Not true, if visiting another a node like the Media node (ie. 'system:/media') or a network node (like smb:/<smb-name>).
There is one problem. KDE/Konqueror is aware of these special URL's called kioslaves. But BASH, the command line interpreter or shell on most Linux system, isn't. In short, the command line doesn't know anything about KIO and wouldn't know how to properly behave. It's a feature that only works on KDE and in the GUI.
PS: The KDE-4 developer's should also know that the KDE-Four-Live disc failed immed, crashing w/ a kernel panic, apparently bec my PC didn't have Linux partitions, so it failed almost immed after attempting to mount/create swap space.
I can only guess they never considered that most PCs aren't using native Linux partitions and neglected NTFS. BTW, NTFS partitions can host Linux swap files. I've been successfully using this facility (ie. FUSE kernel module+NTFS-3g) for many months.
Later....Jet
First, the KDE Four Live CD isn't made by KDE developer
s. It was prepared by
a[/a] KDE Developer. It's not the official KDE 4 Live CD, because there isn't one. The KDE 4 Live CD was made by a KDE Developer who is also an openSUSE Developer, partly to demonstrate KDE 4 alpha/beta, and partly to demonstrate SUSE's Build Service. So if there are problems with the Live CD, please contact that developer. I'm sure he'd be interested to help.
Secondly, a Live CD has nothing to do with your hard drive, much less the filesystems on it. In fact, a Live CD doesn't care if you have a hard drive at all. It's more concerned if you have RAM, because that's where it dumps everything. When I first tried out Linux Live CDs, I didn't have any Linux partitions either. Everything was NTFS. So the kernel panic is most likely caused by something else. Hard disk filesystem has nothing to do with Live CD's, and KDE developers aren't the ones who made those CD's. 
KDE-Forum.org »
KDE »
KDE 4 Brainstorm »
Quoted
Originally posted by jetman
Monday, April 29th 2024, 12:29pm
Go to the top of the page
