Operating Systems > Not Quite Mainstream OSes
New NeXTStep / OSX Based OS
suselinux:
when you guys say Linux what do you mean
RPM based, Deb, Slack, Source Based....
Can I ask why you want to use windowmaker as a starting point for your GUI
I think its great because it the GUI least preverted by the politics of business sofar
I think that this is really exciting!!!
billy_gates:
--- Quote from: suselinux ---when you guys say Linux what do you mean
RPM based, Deb, Slack, Source Based....
I think that this is really exciting!!!
--- End quote ---
I personally do not see a reason to add RPM support. As most apps will use .app packages. I think the RPM support would just slow it down.
And yes... this is very exciting.
My personaly choice for using Window Maker, is because its next based. And so is this. So it will be doubly next based... in a place where doubly is a real word.
I can't wait to get started on this. Unfortunately about all I can do is graphics work. (whis is generally last on big projects like this) However, I would like to stay on board with this project.
And I think we should start with Linux cus I don't have any Intel PC's to beta test on, so there is a problem with using Darwin there.
suselinux:
Is Linux with a FreeBSD Kernel possible?
hm_murdock:
that would be FreeBSD. Remember, it's the kernel that makes it Linux.
As for what we'd base it off of... just a very, very basic, stripped down Linux tree. The kernel, and the most basic utils and commands. Everything that the user is going to interact with will be high-level, built on NeXT libs.
RPM support could be included as a "Linux Utilities" option in the installer. NeXT and OS X don't include any of the UNIX command-line apps by default, you can install them, though. But the normal config won't have support for RPM, as it won't be needed. Drag and drop installof apps is the goal.
System packages, and some apps that install system extentions will use the Package Installer (Installer.app) to do their thing.
NeXT/OS X uses .mpkg bundles to install some things from. Double click the .mpkg bundle and the Installer.app opens and takes care of it all. It puts the Application's bundle in /Applications or whatever folder you specify in the install script. CthulOS will use the similar mechanisms. Package management isn't an issue, because an application consists of one icon. If it installs any extensions, then they'll be clearly labled and always be inside /System/Library/Extensions. they'll probably use a bundle format that I've tenatively dubbed the "Universal Bundle". It's a folder bundle much like a .app or .mpkg bundle, but it can contain drivers, extensions, documents, et cetera. If it isn't an app or installer package, it's a generic bundle, and it contains the file itself, metadata, and resources (icon, et cetera)
The desktop shell will need to be able to work with bundles, which is why WM and GWorkspace would be preferred, as they're designed to work with NeXT-style conventions. GWorkspace will correctly show application bundles as a single icon that runs the app when double clicked (at the command line, .app bundles are simply folders).
To understand the concept of bundles, I suggest reading up on them, as they're a pretty cool idea. Abstract an entire folder tree into one icon, so as to sheild the user from worrying about the binary and all of its support files.
billy_gates:
I guess darwin now works on AMD CPU's
Now we have a hard choice to make. Go easy and use Darwin, or do a little extra work and use Linux?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version