I have no idea if any of the features listed below are being implemented, but this is what I’d like to see in the “perfect OS”.
Virtual desktop space
Virtual hard drive space combining (hard drive partition 1 + hard drive partition 2 = 1 new virtual drive).
I’ve always wanted this feature: mounting of HTTP and/or FTP directories as drives/folders when connected to the internet. Be able to navigate through them like a local drive, double click a file, it downloads, then executes.
Be able to customize current color scheme with HTML hex colors, not just RGB format (Windows ).
Number pad can act as mouse if none is present like in XWin
I have no idea if any of the features listed below are being implemented, but this is what I'd like to see in the "perfect OS". :wink:
Virtual desktop space
Assuming I understand what you mean, this already works in BeOS 5, dependent on your graphics card.
Quote:
- I've always wanted this feature: mounting of HTTP and/or FTP directories as drives/folders when connected to the internet. Be able to navigate through them like a local drive, double click a file, it downloads, then executes.
BeBits, get FTP-FS. There you go, for FTP anyway
Quote:
- Be able to customize current color scheme with HTML hex colors, not just RGB format (Windows :cry: ).
Hex codes = RGB encoded in Hex. Same difference. Support for this would probably take only minutes to code, as the Backgrounds app would take care of it.
Quote:
- Number pad can act as mouse if none is present like in XWin
keep in mind: i am new to beos, i’ve never been able to use it, as i’ve always had problems with it booting. but visually and systematically interesting, i’ve always been intrigued, hopefully haiku lets me experience it when the final product is released. these are only ideas from a distant point-of-view.
- I've always wanted this feature: mounting of HTTP and/or FTP directories as drives/folders when connected to the internet. Be able to navigate through them like a local drive, double click a file, it downloads, then executes.
I agree with this one. Plus add ISO and CUE/BIN too like Daemon tools works under Windows. :wink:
The feature I really want in Haiku R1 is built-in Remote Desktop capabilities. I want to be able to log into my BeOS PC from distance or from another computer. (And no VNC)
The feature I really want in Haiku R1 is built-in Remote Desktop capabilities. I want to be able to log into my BeOS PC from distance or from another computer. (And no VNC)
Security issues aside, OS’s get bloated by having too much built into them. Best to leave things that most people won’t use to 3rd parties. BeOS is supposed to be slick and quick. Adding and adding won’t do much for the speed and overhead (coughwindowscough).
- I've always wanted this feature: mounting of HTTP and/or FTP directories as drives/folders when connected to the internet. Be able to navigate through them like a local drive, double click a file, it downloads, then executes.
I agree with this one. Plus add ISO and CUE/BIN too like Daemon tools works under Windows. :wink:
The feature I really want in Haiku R1 is built-in Remote Desktop capabilities. I want to be able to log into my BeOS PC from distance or from another computer. (And no VNC)
You could probably do a X type jobbie and disconnect the remote app and input servers and attach them to the local machine. probably. I don’t want to be the one that codes it though, as it could be horribly messy.
The feature I really want in Haiku R1 is built-in Remote Desktop capabilities. I want to be able to log into my BeOS PC from distance or from another computer. (And no VNC)
Security issues aside, OS’s get bloated by having too much built into them. Best to leave things that most people won’t use to 3rd parties. BeOS is supposed to be slick and quick. Adding and adding won’t do much for the speed and overhead (coughwindowscough).
I guess this entire “Feature Request” forum is useless then and I should quit posting.
Security issues aside, OS's get bloated by having too much built into them. Best to leave things that most people won't use to 3rd parties. BeOS is supposed to be slick and quick. Adding and adding won't do much for the speed and overhead (*coughwindowscough*).
If you want to avoid bloating, then get let's get rid of the worst offender: theming. All os who have that built-in are horribly fat and are poor performer (GNOME, KDE, etc...)
And as for security, there is none in BeOS. It’s a free for all environment. One bad email attachment and boom, BeOS is gone in a flash.
olaf wrote:
I guess this entire "Feature Request" forum is useless then and I should quit posting.
Don't take it like that.
He’s trying to get his(her) point across. I don’t agree with him since Remote Desktop is the greatest thing to ever happen (no need for KVMs!!!)
Remote desktop definitely won’t make it into R1. I think there is probably a pretty good chance of it being in R2, since it shouldn’t be too bad to fit into the current architecture of the app_server.
If you want to avoid bloating, then get let's get rid of the worst offender: theming. All os who have that built-in are horribly fat and are poor performer (GNOME, KDE, etc...)
I think I would have to disagree with you on that, I believe that if done properly, with some compromises, theming can be fast(er).
I think that in many cases, theming support is added after the fact, in an unoptimized way - and to make things worse, the theme-developers tend to ignore performance and use monstrous graphics that chew up tons of memory.
After-all, the GUI has to have SOME kind of theme, BeOS has a very simple theme that doesn’t involve a lot of graphics and colors, making it easy to draw.
I think my number one complaint about themes are that they encourage people to change the look-and-feel of the standard GUI making it difficult for them to cope with it as-is (they don’t like to use other people’s computers), and makes it difficult for everyone else to use theirs. There’s little reason NOT to support themes in some fashion (even if that means just changing colors) as long as the user has the option to choose a high-performance basic theme for performance when necessary.
BTW, if you haven’t seen it, check out SkyOS - they use a “themable” GUI layer called WindUI that allows very comprehensive theming, and I don’t think anyone is calling it slow (yet).
If you want to avoid bloating, then get let's get rid of the worst offender: theming. All os who have that built-in are horribly fat and are poor performer (GNOME, KDE, etc...)
I think I would have to disagree with you on that, I believe that if done properly, with some compromises, theming can be fast(er).
I think that in many cases, theming support is added after the fact, in an unoptimized way - and to make things worse, the theme-developers tend to ignore performance and use monstrous graphics that chew up tons of memory.
After-all, the GUI has to have SOME kind of theme, BeOS has a very simple theme that doesn’t involve a lot of graphics and colors, making it easy to draw.
…
And as for security, there is none in BeOS. It's a free for all environment. One bad email attachment and boom, BeOS is gone in a flash.
...
He's trying to get his(her) point across. I don't agree with him since Remote Desktop is the greatest thing to ever happen (no need for KVMs!!!)
Ah yes, no security in BeOS plus remote access = all sorts of fun... for the crackers that is.
Let’s get it clear though. I’m not saying that Haiku shouldn’t have a remote desktop. I’m saying that it shouldn’t be built into the system as it opens up far too much and this decision should be left up to the user. Perhaps it could come along as a 3rd party app that is an option to install like some did in BeOS R5.
There have been many exploits on other systems that the service was supposed to be turned off but was running anyway, etc. So, why make that decision for the user if even some don’t want it.
IMO, in todays world, build an OS that doesn’t have security in the design from square 1 is foolish indeed. And it’ll probably end up worse than windows when it comes to security. Since securityfocus made a mailing list for windows all to itself because it produced so many holes that is saying something now isn’t it.
Ah yes, no security in BeOS plus remote access = all sorts of fun... for the crackers that is.
Let’s get it clear though. I’m not saying that Haiku shouldn’t have a remote desktop. I’m saying that it shouldn’t be built into the system as it opens up far too much and this decision should be left up to the user. Perhaps it could come along as a 3rd party app that is an option to install like some did in BeOS R5.
There have been many exploits on other systems that the service was supposed to be turned off but was running anyway, etc. So, why make that decision for the user if even some don’t want it.
IMO, in todays world, build an OS that doesn’t have security in the design from square 1 is foolish indeed. And it’ll probably end up worse than windows when it comes to security. Since securityfocus made a mailing list for windows all to itself because it produced so many holes that is saying something now isn’t it.
I doubt Remote Desktop for BeOS would be the best target to do some mayhem. Email is much more conveniant. :lol:
@umccullough
I don’t agree about the theming part. IMO it’s wasted and Haiku people should focus on a great default widgets for R2 just like Apple did with MacOS X.
I doubt Remote Desktop for BeOS would be the best target to do some mayhem. Email is much more conveniant. :lol: :wink:
Wasn't it Win2000 that someone could reach across the inet and just take over your computer. With a remote desktop taking over someones computer is like taking root on a *NIX sytem - the ultimate goal - so I do think that it'll be a target and a major one at that.
olaf:
In case you haven’t noticed peoples conversations tend to deviate somewhat. Since we are in the Feature Requests forum and are debating a feature (and one that was mentinoed within this thread I might add), I’d tend to think that we aren’t really off topic. Especially since I’ve seen a thread talking about drivers start a debate about licenses.
Wasn't it Win2000 that someone could reach across the inet and just take over your computer. With a remote desktop taking over someones computer is like taking root on a *NIX sytem - the ultimate goal - so I do think that it'll be a target and a major one at that.
Remote Desktop would be harder because you have to know the IP address of the machine's internet connection.
While emails can be harvested from BeOS newsgroups/forums/sites to ensure that those malicius scripts will be run on computers running BeOS. A lot less work if you ask me.
Remote Desktop would be harder because you have to know the IP address of the machine's internet connection.
While emails can be harvested from BeOS newsgroups/forums/sites to ensure that those malicius scripts will be run on computers running BeOS. A lot less work if you ask me.
the first line in the description in man nmap:
Nmap is designed to allow system administrators and curious individuals to scan large networks to determine which hosts are up and what services they are offering.
ie it isn’t that hard at all for those who know what they are doing. As in the people that will be doing this.
More specific scripts could be written to exploit the Haiku specific security flaw. eg Run script that beeps when exploitable system found, watch TV until your system beeps. Yes, I feel the sweat on my brow.
Nmap is designed to allow system administrators and curious individuals to scan large networks to determine which hosts are up and what services they are offering.
ie it isn’t that hard at all for those who know what they are doing. As in the people that will be doing this.
More specific scripts could be written to exploit the Haiku specific security flaw. eg Run script that beeps when exploitable system found, watch TV until your system beeps. Yes, I feel the sweat on my brow.
You won’t need to sweat. As I mentionned previously, such a service should be disabled by default.
The malicious intruder will still have to crack the username/password.
You won't need to sweat. As I mentionned previously, such a service should be disabled by default. :wink:
The malicious intruder will still have to crack the username/password.
should
And I still stand by my stance that this should not be part of the distro. Only tried tested and true methods should be used, and even those have there problems and they are designed with security in mind by the experts from the ground up ie openssh. So, you’ll have to pardon me if I don’t believe in such things here.
).
