nanogui: Thread: nanogui widget set


[<<] [<] Page 3 of 6 [>] [>>]
Subject: Re: nanogui widget set
From: Alan Cox ####@####.####
Date: 11 Jun 1999 22:54:35 -0000
Message-Id: <E10sa67-0003im-00@the-village.bc.nu>

> For me, the main restriction is not the RAM size, but the boot device
> size. What is your aim: 1M with kernel and nanoX+widget?

That sounds well reasonable
> 
> Alan, for an extremly small, the gpm driver is not suitable, imho.

Indeed, but to get it working first gpm is the easier path ?

Subject: Re: nanogui widget set
From: Sebastien HUET ####@####.####
Date: 12 Jun 1999 12:39:24 -0000
Message-Id: <376253BF.F22250DE@linuxembedded.com>

Greg Haerr wrote:

> In the meantime, I've started working on another project, Micro-Windows.
> Micro-Windows runs on top of the device-independent draw engine that I developed
> for nano-X.  Micro-Windows currently sports a full-blown window manager, including
> window captions, close boxes, user-moveable windows, and a 3d look-and-feel.
> Micro-Windows supports full-blown 24-bit RGB color support with 256 color palettes.
> 256 color device-independent bitmaps, in 1, 4 and 8 bpp are implemented.  Conversion
> programs for GIF and BMP files is included.  Micro-Windows supports child windows,
> which are required for decent widget or custom control creation, in addition to
> support for any number of ROM or custom proportional fonts.  MS-Windows font
> and BIOS ROM font conversion programs are written.

Hi Greg,

Your MW looks like i am looking for...
I would like to make a GUI Builder under Windows and run the GUI builded under linux
so MS-Windows fonts support will help me a lot.

When a dowloadable version ?

Bye

Seb


Subject: RE: nanogui widget set
From: Alex Holden ####@####.####
Date: 12 Jun 1999 12:40:57 -0000
Message-Id: <Pine.LNX.4.04.9906121323320.388-100000@hyperspace>

On Fri, 11 Jun 1999, Greg Haerr wrote:
> My last submission was 0.4, which completely works.  Alex Holden has

0.5pre1 is what you wanted to submit as 0.5. However, it only works on 8
bit framebuffers, and the networking code is badly broken.

> been working on some things, and introduced a pre-release numbering
> system.  You'll have to check with him to see what versions work and don't work.

The latest development release is pretty stable, and should theoretically
work with 8, 16, 24, and 32 bit framebuffers (I don't think anybody has
tried it at other than 8 though. I bought a new ATI graphics card, but the
ATYFB driver doesn't work with it, and I haven't had the time to fix it
yet). The new networking code isn't in there, but I'm fairly close to
finishing it, I just need to find a spare three or four hours somewhere.

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

Subject: RE: nanogui widget set
From: Greg Haerr ####@####.####
Date: 15 Jun 1999 20:24:36 -0000
Message-Id: <01BEB739.492DCDB0.greg@censoft.com>

: Nothing more than what you described earlier.
: Support for windows font is the paradise for me.
: what i need is
: "What you see on windows is what you get on nano X"
: the look matters more than the api.
: 

The way that the font-converter works is this:

	First, the nano-engine supports it's own (currently in-core) "C" based
font structure, which supports fixed and proportional fonts of 1-256 characters.
These character images are stored as a monochrome bitmap array and a character
width array.  The image bits are right-aligned to a word boundary.  (I started
with the design that Ben Pfaff came up with, and extended it a little.)

	Then I wrote two converters:  One reads the PC bios ROM fonts and
writes them into a "C" file FONT structure.  The second one is a win32 program
running under windows that creates a win32 HFONT, selects it into a DC, and
then displays each character on the screen.  The program then reads the raster
bits from the screen (regardless of whether the font is a raster font or truetype font)
and writes them into a C file.  In this way, I have the MS-Windows System and Dialog
fonts. (System 14x16 and MSSansSerif 11x13).  All the font files are kept in
a library, and linked into micro-windows by the programmer's request.  The programmer
selects a font by number, which is currently an array of bound-in fonts.  Also, there's
a .bdf file converter from Ben, that I also made work.

	Someday I plan on using Ben's code to read in .bdf files into my in-core
structure, but currently with micro-win, there's not much need for more than the System
and MSSansSerif fonts yet.

Greg
Subject: Re: nanogui widget set
From: Alan Cox ####@####.####
Date: 15 Jun 1999 21:46:58 -0000
Message-Id: <E10u0w0-0007iG-00@the-village.bc.nu>

> and writes them into a C file.  In this way, I have the MS-Windows System and Dialog
> fonts. (System 14x16 and MSSansSerif 11x13).  All the font files are kept in
> a library, and linked into micro-windows by the programmer's request.  The programmer

You can expect to get your butt kicked by MS if you do anything with that
generally of course 8)


Subject: RE: nanogui widget set
From: Greg Haerr ####@####.####
Date: 15 Jun 1999 22:19:50 -0000
Message-Id: <01BEB748.B2B9C540.greg@censoft.com>

On Tuesday, June 15, 1999 3:40 PM, Alan Cox ####@####.#### wrote:
: > and writes them into a C file.  In this way, I have the MS-Windows System and Dialog
: > fonts. (System 14x16 and MSSansSerif 11x13).  All the font files are kept in
: > a library, and linked into micro-windows by the programmer's request.  The programmer
: 
: You can expect to get your butt kicked by MS if you do anything with that
: generally of course 8)
:
	Yeah, I thought that, and that's one reason I haven't released it yet,
I think I'll have to remove the font files, and people will have to use the font converter
to convert fonts from a system they have an MS-license for.

Greg
Subject: Re: nanogui widget set
From: Ben Pfaff ####@####.####
Date: 15 Jun 1999 22:31:10 -0000
Message-Id: <87hfo9ksin.fsf@pfaffben.user.msu.edu>

Alan Cox ####@####.#### writes:

   > and writes them into a C file.  In this way, I have the MS-Windows System and Dialog
   > fonts. (System 14x16 and MSSansSerif 11x13).  All the font files are kept in
   > a library, and linked into micro-windows by the programmer's request.  The programmer

   You can expect to get your butt kicked by MS if you do anything with that
   generally of course 8)

Actually, no.  The fonts that he refers to are both bitmap fonts.
Referring to the comp.fonts FAQ at
	http://www.faqs.org/faqs/fonts-faq/part2/
we learn that:

  [...]
  "First, the short answer in the USA: Typefaces are not
  copyrightable; bitmapped fonts are not copyrightable, but scalable
  fonts are copyrightable.  Authorities for these conclusions follow.
  [...]

So he's safe from Microsoft in this case in the US at least.
-- 
Can I go now?  I have a program I'm working on.
  from _The Tao of Programming_
Subject: Re: nanogui widget set
From: Alan Cox ####@####.####
Date: 15 Jun 1999 22:36:13 -0000
Message-Id: <E10u1hI-0007m8-00@the-village.bc.nu>

> Actually, no.  The fonts that he refers to are both bitmap fonts.
> Referring to the comp.fonts FAQ at
> 	http://www.faqs.org/faqs/fonts-faq/part2/
> we learn that:

Actually yes

>   "First, the short answer in the USA: Typefaces are not
>   copyrightable; bitmapped fonts are not copyrightable, but scalable
>   fonts are copyrightable.  Authorities for these conclusions follow.
>   [...]
> 
> So he's safe from Microsoft in this case in the US at least.

The moment they hit a mirror in the EU you get clobbered. Its happened to 
people before

Subject: RE: nanogui widget set
From: Alex Holden ####@####.####
Date: 16 Jun 1999 08:02:24 -0000
Message-Id: <Pine.LNX.4.04.9906160856110.9817-100000@www.linuxhacker.org>

On Tue, 15 Jun 1999, Greg Haerr wrote:
> 	Yeah, I thought that, and that's one reason I haven't released it yet,
> I think I'll have to remove the font files, and people will have to use the font converter
> to convert fonts from a system they have an MS-license for.

I'm not sure that'd work either, unless they buy a windoze license for
every copy of Nano-windows (you're not allowed to buy one license and
use it on several machines). Probably finding some which look the same but
are freeware would be a better idea. The same probably goes for the bios
fonts, if you were thinking of distributing them with the system (and not
all machines have a bios, if they are loaded at runtime). Have you tried
creating a loader for Linux console fonts?

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

Subject: RE: nanogui widget set
From: "Darran D. Rimron" ####@####.####
Date: 16 Jun 1999 11:45:25 -0000
Message-Id: <NCBBLCEDENCINNMFNPBCIEMCCMAA.darran@rimron.co.uk>

[where do we get nano-gui/nano-windows fonts from]

It's been a long time since I played with it, but, WINE? That's GPL'ed
isn't it, and they seem to run Windose Applications with relative
sucsess.  Failing that can't we "look close" at the MS font and design
one based upon it with a just a minor difference, I've done a little
font design before, it's not that hard :)  If push comes to shove, I'll
make a GPL'ed look-a-like font based on MS-System but not using a single
byte of MS code in the process. A single pixel here and there /in
theory/ should be enough, yesno?

	-Darran
--
Darran D. Rimron                              ####@####.####
Mobile: +44 17808 49 25 49                 Pager: +44 76543 07647
Rimron Design & Consultancy              http://www.rimron.co.uk/
Phone: +44 1708 766 959                     Fax: +44 1708 766 959

[<<] [<] Page 3 of 6 [>] [>>]


Powered by ezmlm-browse 0.20.