Anyone who knows Windows NT administration understands the reference in the title (and likely cringed.) IMHO, Microsoft did not implement it well and caused more headaches than was necessary.
What I think would be very helpful, and not difficult, would be to create an open system of synchronizing certain things (maybe via plug-ins for easy expansion) between computers or platforms. A system which can take a person’s e-mail settings, addressbook, browser configuration and bookmarks, convert them to standard XML files and upload them to a remote system. Most ISPs that I have ever dealt with give users some space on their webserver and this is where the synchronizing files can be stored.
This way when I leave BeOS and go to Windows/Linux/etc, there could be a program in my BeOS shutdown script which creates and stores the XML and (hopefully someday) another which would download and incorporate them.
Does anyone think this would work? I know I really hate it when I open Outlook and don’t have an e-mail address I know I have in BeOS…
It’s all very nice but Haiku V1 won’t have any multi-user support!
yes multi-user support will come with R2 … and will most likely do roaming profiles alot better than MS could hope to achieve.
I’ll bet MS were hoping BSD would write it for them
My idea has nothing to do with multiple user profiles. Just storing certain settings so that when I make a new bookmark in Firefox in BeOS I can synchronize it with my Firefox at work, or on the same computer but in Windows.
I have BeOS and Windows (sometimes Linux too) installed on the same computer. When I log off of BeOS I would like for a program to create XML files specifying my browser configuration (security, bookmarks, visable toobars, etc), my e-mail settings (account names, servers, not passwords) and my People files and upload them to my ISP. Then when I log into Windows another program could download these and incorporate them. The People files would be exported to XML, then imported into Outlook’s addressbook.
The biggest problem I see here is Windows.
Basically, because it should be possible for BeOS’s Firefox to get its configuration from a Windows drive but Windows reading a BFS drive isn’t possible unless some budding Win32 developer writes something.
but Windows reading a BFS drive isn't possible unless some budding Win32 developer writes something.
The SDK for filesystem drivers ins’t free… Not that I’m that big of a developer! :oops:
upload them to my ISP
Can you guy’s read? (sorry that might be a bit rude… but seriously)
There will be NO limitations in filesystems.
Store the setting. UPLOAD to a server on THE internet!
ANY OS will be able to fetch the information. And the bookmarks etc. could be shared btw. different OSer and eaven different browsers with a nifty application for syncronizing.
The idea is great!
I think it’s a good idea… not sure if it’s entirely Haiku-specific, but it would be something handy to have.
It's all very nice but Haiku V1 won't have any multi-user support!
Hopefully atleast some ground work for multiuser support is being laid out now… I can’t imagine that its easy to migrate from single user to multiuser if the basic groundwork isn’t planned out at the beginning.
I think it's a good idea... not sure if it's entirely Haiku-specific, but it would be something handy to have.
You are right. This is not HAIKU specific.
This would be an application devloped for as many OS’es as possible.
But the idea remains good…
Not at all BeOS/Haiku specific, but something that would be nice to have and something that we wouldn’t have to wait until Haiku was officially released to implement as this could easily be programmed now for current BeOS systems.
I’m not a mac user and I have never used mac.com, but I think they had ideas(not quite as grand as ours) of doing something along these lines. If we could slowly build up to something like this with the possible haiku mail system that Deej is looking into setting up, it could turn out to be a win/win solution for all. At that point, all that would be needed is a program to syncrhonize the data between the local system and the server and plugins for the applications to apply said data for as many systems as reasonably possible.