All we need to do is tune the UI a little, but you can see bookmarks <-> shortcuts, history/cache/storage <-> file system, extensions <-> plugins/system helpers.
"The network is the computer," indeed!
cheers,
mike
- OS: PuppyOS
http://www.PuppyOS.com/
- Mozilla platform: SeaMonkey
http://www.Mozilla.org/projects/seamonkey/
Duly cross-posted to:
http://www.PuppyOS.net/forum/?Ideas
http://groups.Google.com/group/mozilla.dev.apps.seamonkey/topics
Thank you,
Eddie Maddox
SeaMonkey Surfer
It's not an OS, but it is indeed a platform. Really it's middle-ware
that is ported to a number of OS's. On each OS it is implemented
differently, on top of or along side an existing native GUI, because
there isn't a Mozilla desktop. The thing is that XUL beats the socks
off of any other GUI (IMO), and it seems unfair for it not to have a
dedicated OS where it is the native GUI instead of just mimicking the
look n' feels of all these others. It wouldn't be a monumental task to
create a desktop with XUL. It would first be a matter of tying in the
things that are now currently borrowed from the native API, like find
file dialogs. Then we'd need to make a Mozilla-based graphical shell.
Doing what Gnome and KDE have done should not take nearly as much
effort because most of the work is already done. XUL is already an
incredibly powerful widget toolkit with all the works (widgets,
locales, skinning, etc...) built into it already.
cheers,
mike
> cheers,
> mike
I'm not suggesting dealing with any of that pain. That's all handled
by the kernel. I'm only suggesting competing with Gnome and KDE as
graphical desktops, because the Mozilla platform already does almost
all of what they do, and does it better. Currently we use familiar
skinning to match the look n' feel of these desktops so that it
*feels* native. Why shouldn't XUL *be* the native GUI? Furthermore,
because XUL is already so incredibly good at mimicking its would-be
competitors, that will be a huge reason for developers to use this
desktop as their main developing environment (the GTK+ and Qt ports
are dreadful). I think one of the main things stopping developers from
using XUL is because it has a reputation, wrong as it may be, for
being a memory hog, specifically because it [must] replicates a lot of
functionality already present in the native API and already occupying
memory (for good reason; relying on native widgets would be
impractical, and extremely limiting, i.e. wxWidgets). That would not
be an issue if Mozilla were the native API. In other words, one reason
for a Mozilla OS would be to get rid of the needless overhead that
another OS would add for running applications not built with Mozilla.
And because it would simply be a better desktop in general I think.
XUL makes beautiful interfaces.
There's also the advantage of being able to escape the GPL, and
instead use the MPL which I very much prefer.
(Mezzo Desktop Environment, "desklet system")
http://shots.OSDir.com/slideshows/slideshow.php?release=644&slide=20
"Symphony OS 2006-05 Beta
Quick Links: boot, installation, desktop, taskbar, menu,
configuration."
SymphonyOS 2006-12 Now Available at LinuxTracker.org
http://Digg.com/linux_unix/SymphonyOS_2006_12_Now_Available_at_LinuxTracker_org
"LinuxTracker.org is pleased to announce the availability of
SymphonyOS 2006-12 on the linuxtracker bittorrent network. ..."
Symphony OS 2006-12 $9.99
http://On-Disk.com/product_info.php/products_id/192
"Unity, Beauty, Simplicity...
Symphony OS is a GNU/Linux based operating system
which uses it's own Mezzo desktop environment. ..."
Eddie
Mezzo uses Gecko, at least, IIRC. I'm not sure about XUL, etc.
The SymphonyOS project has had financial and other challenges the last
several months. Nevertheless, they did manage to get a release out
last December.
Eddie
cheers,
-Alex
----- Original Message -----
From: "Mike Beltzner" <belt...@mozilla.com>
To: "emery denuccio" <emery.d...@gmail.com>, "dev.planning" <dev-pl...@lists.mozilla.org>
Sent: Friday, March 16, 2007 5:24:21 PM (GMT-0800) America/Los_Angeles
Subject: Re: Any plans for a Mozilla-based OS?
I don't see the advantage of being an OS as you describe it. Let the OSes deal with the pain of device drivers, memory allocation, filesystems, network interface layers and I/O. Let us work on improving the cross-platform layer that helps users get to their applications, online data, and friends, pushing the web forward.
cheers,
mike
_______________________________________________
dev-planning mailing list
dev-pl...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-planning
Firefox isn't quite a shell on its own. It holds all of the
characteristics of an application, and it would not be so simple, or
quite make sense, to adapt it to a desktop. The best and easiest
solution would be to keep Firefox a browser, extend its use to
browsing the local file system as well, and make a seperate desktop
for managing applications (which includes opening directory views in
Firefox). This is similar to Explorer on Windows, except that Windows
has Explorer and Internet Explorer as seperate applications, even
though they are almost identical. The differences are minor, and I
think unnecessary. Microsoft decided to keep a small apparent gap
between the Web browser and the file browser, having the latter mostly
just exclude a few Web-specific toolbar buttons, like "home". Explorer
is also the desktop, including the taskbar, start menu, etc... I
believe Konqueror is a better example of a file/web browser as part of
the KDE desktop environment, but seperate from the rest of the shell.
All this leaves is to make a desktop, extend Firefox to display files
and folders better, and add features for file manipulation (move,
copy, delete, etc...) to Firefox (this is a much needed improvement,
that I suspect is probably already being done since Firefox currently
cannot do this with FTP either without an extension like FireFTP), and
fill in the few GUI elements from XUL that are currently taken from
the native GUI (top-level windows, file selector, basic text
rendering?).
Why not use a java web operating system, then port over what we really
need for boot from netbsd, so it'll run on anything?
Good idea, have been working on it for 5 years now.
Perfect, you guys made it to slashdot.
--> http://slashdot.org/articles/07/03/20/0048245.shtml
Now all the slashdot folks think, that Mozilla has gone totally mad :-(
So how about developing something, instead of discussing this? Do
something, come back in 6 months and show us what you've got.
EOD
Simon
--
Sunbird/Lightning Website Maintainer:
http://www.mozilla.org/projects/calendar
Sunbird/Lightning blog: http://weblogs.mozillazine.org/calendar
If you could nail down why it's so slow it could speed up
firefox and thunderbird.
Olafur Arason
You need to investigate the "Penzilla" (a terrible name IMO) project,
which may still be around. It was done by a company called OEOne a few
years ago. Unlike almost every other startup at the time, they had a
great product but terrible marketing.
Gerv
Be careful, in a few years they'll make you bundle IE with it...
I recommend you all think long and hard about this. I am an Ubuntu
user on my T60 and I don't dual boot. I love the fact that Ubuntu is
like an appliance -- all the software (pretty much anyway) comes from
a few limited repositories and has been tailored to my system. Things
just work. When I add an app, I always go to the same place and when
I remove an app, it's gone as far as I know (even though the install
deb stays on the disk).
Just a thin slice of upside here are this:
1) It's stable.
2) It's a single app for maintaining the software on my system.
3) It reminds me of apple in 1990 in terms of ease and simplicity.
4) Gone are the disk churn and CPU burn with Windows virus checking
and cleanup.
If Mozilla were to undertake an OS, would they use the Apple model of
supporting limited hardware so they could ensure stabilility and
features?? Or, would they strip features and drivers in an attempt to
support a broad range of hardware? These are key decisions in any OS
approach. I wouldn't recommend Mozilla take this on but if they did,
supporting a limited hardware set but doing it well is an approach
that has merit as the alternative of supporting all the x86 universe
seems prohibitive in terms of scope. If there were an org to take on
an OS for a limited hardware set, Mozilla would be a great partner to
this org and that is probably the better way for this to happen.
I would rather both google and Mozilla stay out of the OS.
If Mozilla were to add a new direction, I would rather it be in voice
apps on smart phones. I would rather the Internet messaging and
communication focus Mozilla has now extend into voice and into smart
phones. If Mozilla is going to introduce a full OS and application
platform anywhere, I would recommend it be on a smart phone. Imagine
a Samsung SGH-i600 which is a quad band phone with WIFI that runs all
your cellular phone voice apps + runs Skype over wifi and cellular
internet + runs the VOIP app of your choice over WIFI. And is running
some brand of Linux/BSD so you can sync with your PC based on cron
jobs and on the fly and in the background. Nice. This product just
took a hunk of your cell phone bill away, gives you the ability to
make and take calls anywhere in the world where you can get wifi, and
can extend all the Mozilla application framework into the phone
space.
On top of all this is asterisk which has a role in my view if the
current PC and smart phone get on a common, open platform.
The phone has the branding and revenue potential of Firefox also which
not too many applications have.
This is where Mozilla should be looking in my view.
--
Good luck with the project.
have you seen symphony os? it's a linux desktop running on top of
gecko.
(look for some reviews on distrowatch.com)
I've learned something about Slashdot from this discussion, namely
it's complete lack of information. I, a single person who hasn't
contributed anything to Mozilla (yet), am referred to as the entire
collective Mozilla development team. This is just an idea I was
throwing out there to see if people thought it was a good, bad, or
already done. I'm not even going to get into the nonsensical comments
and arguments that followed that "article".
Thanks again!
First, the (Sh)Ice-naming is Debian's way, so it should be their thing
to use. And then, given how useful that approach looks to many people
here, IceBerg would probably be a better name.
Robert Kaiser