BBS水木清华站∶精华区
发信人: ecoe (阿康), 信区: Linux
标 题: Re: MiniGUI 的前景和应用 (转载)
发信站: BBS 水木清华站 (Tue Aug 3 14:42:38 1999) WWW-POST
【 在 Kongming (没日没夜...) 的大作中提到: 】
∶ 【 以下文字转载自 FreeDevelop 讨论区 】
∶ 【 原文由 Kongming 所发表 】
∶ MiniGUI 的应用前景是很明显的,就是为 Linux 控制台提供一个简单可
∶ 行的 GUI 支持系统,MiniGUI 可以应用在 Windows CE 可以应用的任何场合,
∶ 例如:
∶ 上网机,或电视置顶盒;
∶ 实时控制系统;
∶ 个人电脑助理;
∶ 掌上型电脑;
∶ 等等,就让你自己去想象吧。
∶ 当然,MiniGUI 仍然能够在普通的 Linux 机器上运行,可作为一些小型
∶ 游戏的支持平台,也可为控制台的小型应用提供图形界面支持,比如一个简单
∶ 的文字录入程序、小型浏览器、证券资讯分析程序等等。
∶ 在 MiniGUI 的开发过程中,应始终强调一个"小"字,因为这才是MiniGUI
∶ 真正的特色所在。
呵呵,还有比mini小的吗? Nano .
我看 nanogui 的思路也挺好,不在console上跑,以后搞出来个nano window manager,
现在X上的软件应该好移植一些. 为什么一切要重新开始,不如搞个中文的nanogui,
再改装一个ice之类的轻量级WM.
Introduction
The NanoGUI project is an attempt to produce an Open Source GUI
system for small Linux based systems such as palmtops and embedded POS units.
Status
The Nano-X tiny X server (based originally on Alan Cox's combination
of Mini-X and Bogl) is nearing the stage where it can actually be used for
developing widget sets and other programs on.
Download
The NanoGUI file repository is accessible via both
ftp://ftp.linuxhacker.org/pub/nanogui/ and
http://www.linuxhacker.org/pub/nanogui/
Mailing List
To subscribe to the NanoGUI mailing list, send mail to
nanogui-subscribe@linuxhacker.org. To send mail to the list, use the address
nanogui@linuxhacker.org. To unsubscribe from the list, send mail to the
address nanogui-unsubscribe@linuxhacker.orgfrom the same address that you
subscribed with. To get more information, including instructions on how to
view the list archives or get the mailing list in digest format, send mail
to nanogui-help@linuxhacker.org.
CVS Repository
If you want to be on the raw, cutting, bleeding, a bit septic in places,
edge of NanoGUI development, you can get NanoGUI directly from the CVS
repository at cvs.linuxhacker.org. Log in with the user name anonymous
and no password (just press enter at the prompt) and check out the nanogui
module. The rule for gaining write access is to submit some good patches
to me; once you've proven your competence, I'll give you an account which
lets you check changes in. See the FAQ for detailed instructions.
Frequently Asked Questions
You can get the NanoGUI FAQ from
http://www.linuxhacker.org/pub/nanogui/NanoGUI-FAQ.txt.
The NanoGUI Frequently Asked Questions file.
Alex Holden <alex@linuxhacker.org> - 14/5/99
What's NanoGUI?
NanoGUI is a project intended to bring GUI applications to small Linux
based
systems such as palmtops and embedded Point of Sale units.
Where does Nano-X fit in then?
Nano-X is a program which performs a function similar to an X server for
the
NanoGUI project. It recieves requests from applications to draw things on
the
screen and delivers events such as keypresses to the applications. It is
designed to be not only very small and simple, but also very modular and
scaleable. It supports operating in both the normal client/server mode,
and
in a special "client linked into the server" mode for very low memory
applications.
Is it directly compatible with X then?
No, the X protocols and libraries are large and complex, and hence not
really
appropriate for Nano-X. We will be porting Gtk+ and Gnome to NanoGUI
however,
to make it easier to port applications such as Mozilla.
What license is it under?
After much discussion, we eventually decided to place Nano-X under the MPL
(Mozilla Public License). You can obtain a copy of this at
http://www.mozilla.org/NPL/MPL-1.0.txt
Why not BSD / GPL / LGPL / whatever?
Several of us did not like the idea of the BSD license, even the
no-advertising-clause FreeBSD version, due to the fact that it does not
guarantee that commercial improvements of our code will be contributed
back to the project. Most people would have preferred to have used the
GPL,
but it has an unfortunate side-effect in that it is not allowed to
distribute
GPLed code and commercial code statically linked together. This was
inacceptible
in the case of Nano-X because in some cases it is desirable to distribute
it statically linked to a non Open Source graphics driver (the author may
have
been forced to sign an NDA in order to get the specifications of the
device,
for example) or application. On the other hand, the core code and drivers
which
we wrote should remain protected to a similar level as the GPL. The
Mozilla
public license provides this. Here's a summary of my understanding of the
relevant part of the license, which I posted to the mailing list:
-----------------------------------------------------------------------------
It's in typical lawyer-speak gibberish, but the part of it which applies
here seems to be:
3.7. Larger Works.
You may create a Larger Work by combining Covered Code with other code
not governed by the terms of this License and distribute the Larger
Work as a single product. In such a case, You must make sure the
requirements of this License are fulfilled for the Covered Code.
Where:
1.7. ``Larger Work'' means a work which combines Covered Code or
portions thereof with code not governed by the terms of this License.
1.3. ``Covered Code'' means the Original Code or Modifications or the
combination of the Original Code and Modifications, in each case
including portions thereof.
1.10. ``Original Code'' means Source Code of computer software code
which is described in the Source Code notice required by Exhibit A as
Original Code, and which, at the time of its release under this License
is not already Covered Code governed by this License.
1.9. ``Modifications'' means any addition to or deletion from the
substance or structure of either the Original Code or any previous
Modifications. When Covered Code is released as a series of files, a
Modification is:
A. Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.
B. Any new file that contains any part of the Original Code or
previous Modifications.
If I am interpreting this correctly, we can license the code we have under
the MPL, and then any "Modifications" to our code need to be contributed
back to us, but any new code distributed along with it (and it doesn't
explicitly disallow statically linking to it) can be under whatever
license you want. This would seem to be just what we want.
-----------------------------------------------------------------------------
How do I subscribe to the mailing list?
Send an empty mail to:
nanogui-subscribe@linuxhacker.org
How do I unsubscribe?
Send an empty mail to:
nanogui-unsubscribe@linuxhacker.org
Is the mailing list archived anywhere?
Yes. Send an empty mail to:
nanogui-help@linuxhacker.org
to get instructions on listing and retrieving items from the archive.
How do I get the source from CVS?
Get and install CVS.
Type:
export CVSROOT=:pserver:anonymous@cvs.linuxhacker.org:/home/cvs
cvs login
<press enter at the password prompt>
cvs -z3 checkout NanoGUI
<NB. Currently the CVS isn't being used for development, and probably
isn't
up to date. This may change in the future when we have more developers.>
I can't get the Linux framebuffer driver going. Why doesn't it work?
A lot of people seem to have difficulty setting up the framebuffer for
some
reason. First, make sure you have read the Framebuffer-HOWTO at
http://www.tahallah.demon.co.uk/ , and if you still can't get it working
(remember that not all PC graphics cards are Vesa-2.0 compliant), ask the
mailing list for help, with a full description of what you have done and
what the symptoms of your problem are.
Are you going to port / have you ported a VNC client to NanoGUI?
Yes, we have heard of VNC, and we do plan to port a VNC client to NanoGUI
at some point in the future. There are no immediate plans to do it
however.
Is Mozilla going to be ported to NanoGUI?
Probably.
How can I submit a new entry to the FAQ?
That's easy. Just send it to me at alex@linuxhacker.org, and I'll put it
in
the next update.
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.197.0.1]
BBS水木清华站∶精华区