Quote:

>I'm interested to know how to just install the capability to have anti aliased fonts, without any of the other changes.

Quote:

best is install AFA and remove picture_datatype.exe ilbm.datatype.exe and exec_lib.exe from afa_os_libs

Thanks, that did the trick. The anti aliasing works well, and anyway I found that AmiDock and other apps like AWeb couldn't load images when the datatype patches were active.

Do you know if the freetype2.library is built with the full bytecode interpreter?

Also the fonts required lots of tweaking with the font manager to make them look right - using Vera Mono I got double spaces between characters. Maybe more metrics could be read from the font itself to set the defaults. For example, the older ttflib (not to be confused with ttengine) does a much better job of interpreting the files' metrics.

_________________

Why not simply port AROS to Amiga 68k or blizzard PPC? and then add the missing parts with 3.9 exes instead the inverse like you have done

Last edited by Fransexy on 16-Apr-2006 at 12:32 AM.

_________________
No PowerPC, No Fun
Make Amiga Great Again

Thanks for explanation--

'Afa stands for AROS For Amiga, hence it's quite obvious what API it uses...

_________________

@Snuffy

Quote:

Thanks for explanation-- 'Afa stands for AROS For Amiga, hence it's quite obvious what API it uses...

Yes: the MorphOS one.

(But what does 'AROS' stand for these days?)

_________________
Matt

>This is computed at run time and still works when a function branches to another routine (well, most of the time

I search for function on Aminet,but nothing found.sure teh name is correct ?

This tool is usefull too.I like to have the best possibility tzo find Bugs

>Why not simply port AROS to Amiga 68k or blizzard PPC? and then add the missing parts with 3.9
>exes instead the inverse like you have done

because OS3.x miss not much features to get new MOS and OS4 features.also GFX harddrive CD drivers must written when use
AROS.
gfx drivers are need because on amigaOS there is no public GFX driver writing possible.On CGX or P96 only the developers
can write GFX drivers.So old drivers cant use in AROS because AROS have too a own GFX driver concept that is of course
public for all to write GFX Card drivers

most problem for filesystem is that AROS have no dospackets.so no 68k filedrivers work.also asyncio library dont work

Also AROS miss lot of features to get compatible.
Because AOS is not very good documentet there are much undocumentet features in.

All know that developers dont like write docu.So it is sure that original AOS have lots more "developer friendly features"
as documentet.

But this was only find by test the real world.rcftp crash and rawbinfo crash when move a png icon on it.

Because the amiga have the problem that most software is not furtherdevelop i think it is better be AOS compatible.
For example:On OS3.x it is save to use FreeMem with mempointer=0.No total AOS crash.
But this stand not in the RKM.In RKM stand only that FreeVec is save to work with mempointer=0.
But on OS3.x all AmigaOS freemem funcs are save to work with 0 pointer.
this reduce the risc of crash whole system and avoid that the developer must write extra code and cant create a Bug
and create a total OS Crash because the OS function do that

if (mempointer)FreeMem(mempointer,size); is strict RKM
FreeMem(mempointer,size); is undocumentet OS3.x feature.Now add to AFA and AROS too and hopefully update the RKM docs
(copy the line from freevec to freemem freepooled)

"
INPUTS
memoryBlock - pointer to the memory block to free, or NULL.
"

It is much more easy to develop a OS that implement only the RKM features.But it help nothing when you have a OS that offer only exact the RKM features but many programs dont work and noone
fix them and cost additional developer time.if development cost too much time there are other OS out that make life more
easy a developer think and result is byebye amiga.

some undocumentet usefull features happen too with the picture datatype.It sound stupid,but this simple small piece of code
cost me ca 80% of develop time in AFA.And thats only because original picture datatype is not here.To get alpha
support only ca 4-6 lines must add to original datatype.

A simple rule is.The more new code you use the more new Bugs can appear.So i do all step by step.
No hurry,if a AFA module is not 100% compatible you can remove it easy and use old code.You allways have a full
working OS and you miss no old features.

I dont believe when i compile AROS for 68k diropus magellan or scalos or workbench run on AROS.
They sit to deep in the system
So it have the same limits AROS currently have.No good usable desktop.

So i see the chance near 0 that a 68k AROS really can run much more programs than a X86 or PPC AROS.

>and anyway I found that AmiDock and other apps like AWeb couldn't load images >when the datatype patches were active.

What format are the pictures ?.Iff jpeg or something other ?.

>Also the fonts required lots of tweaking with the font manager to make them look >right - using Vera Mono I got double spaces between characters.

This happen when you use no diskfont_lib.exe.with old the space in fixed space fonts is too large but proportional fints are show correct.

How freetype work i dont know.Freetype.library is port from the MOS team and made available in exchange to AROS diskfont library written from Georg Steger

Also a AROS dos library was available as source with packet support add from MOS team.also MOS Team have add to AROS intuition lib skin support.normaly it is a code exchange

I hear in 2003 as OS4 was not out,they say that this libs should not out for public.not that the OS4 team can grab code.The AROS team agree.

But now OS4 is here the situation have changed.I dont think that OS4 now need grab code.packets and skins help AROS and is MOS use AROS code it is right to make available

Quote:

Also the fonts required lots of tweaking with the font manager to make them look right - using Vera Mono I got double spaces between characters.

Reinstall the font with ftmanager but change "Space Width" settings to 4263.

@Bernd:

In ftmanager.c for some reason they had the first check (is font fixed width) commented out. If I remove comment, the space width calculated is correct (like ttflib). Then for fixed fonts, the space width is always taken from face->max_advance_width and not from SPACE char if possible. It can also be that the SPACE char width calculation is wrong as it is strange that it ends up being greater than face->max_advance_width.

if (//!(face->face_flags & FT_FACE_FLAG_FIXED_WIDTH) &&
FT_Set_Char_Size(face, 250 * 64, 250 * 64, 2540, 2540) == 0 &&
FT_Load_Char(face, ' ', FT_LOAD_DEFAULT) == 0)
{

As I don't know why that check was commented out it can also be that it is there for a reason and causes problems with some fixed fonts.

Quote:

>This is computed at run time and still works when a function branches to another routine (well, most of the time I search for function on Aminet,but nothing found.sure teh name is correct ?

It's part of a software package, can't remember which one it is (maybe identify_lib or patchwork).

_________________
Stephan Rupprecht - AmigaOS4 developer

For better OS4 source compatibility.I look in the Free OS4 SDK doku and see no Tag for penfreemode

i see in file graphics.doc from 23 Feb 2005

and picasso96api.doc from 30.Oct 2005

alpha channel is declare as unused
i see no OS4 functions that work with alphachannel.

so SDK look as OS4 dont have this features

graphics.library/SetRPAttrsA graphics.library/SetRPAttrsA

NAME
SetRPAttrsA -- modify rastport settings via a tag list
SetRPAttrs -- varargs stub for SetRPAttrsA

SYNOPSIS
SetRPAttrsA(rp, tags)

VOID SetRPAttrsA(struct RastPort *, CONST struct TagItem *);

SetRPAttrs(rp, tag1, ...);

FUNCTION
Modify settings of a rastport, based on the taglist passed.
currently available tags are:

RPTAG_Font Font for Text()
RPTAG_APen Primary rendering pen
RPTAG_BPen Secondary rendering pen
RPTAG_DrMd Drawing mode (see graphics/rastport.h)
RPTAG_OutlinePen Area Outline pen
RPTAG_WriteMask Bit Mask for writing.
RPTAG_MaxPen Maximum pen to render (see SetMaxPen())

INPUTS
rp - pointer to the RastPort to modify.
tags - a standard tag list



Picasso96API.library/--color formats--
The Picasso96API.library supports different color formats:
Chunky:
CLUT: 8bit chunky with palette
HiColor:
R5G5B5: 15bit HiColor (0rrrrrgggggbbbbb)
R5G5B5PC: 15bit HiColor (gggbbbbb0rrrrrgg)
B5G5R5PC: 15bit HiColor (gggrrrrr0bbbbbbgg)
R5G6B5: 16bit HiColor (rrrrrggggggbbbbb)
R5G6B5PC: 16bit HiColor (gggbbbbbrrrrrggg)
B5G6R5PC: 16bit HiColor (gggrrrrrbbbbbggg)
TrueColor:
R8G8B8: 24bit TrueColor (8 bit each)
B8G8R8: 24bit TrueColor (8 bit each)
A8R8G8B8: 32bit TrueColor ARGB (A unused alpha channel)
A8B8G8R8: 32bit TrueColor ABGR (A unused alpha channel)
R8G8B8A8: 32bit TrueColor RGBA (A unused alpha channel)
B8G8R8A8: 32bit TrueColor BGRA (A unused alpha channel)
YUV:
RGBFB_Y4U2V2: 2byte TrueColor (CCIR recommendation CCIR601)
RGBFB_Y4U1V1: 1byte TrueColor ACCUPAK (used on Cirrus GD5446)

@bernd_afa

Hmm, looks like the graphics autodoc is out of date. Have a look at graphics/rpattr.h instead:

RPTAG_Font
RPTAG_APen
RPTAG_BPen
RPTAG_DrMd
RPTAG_OutLinePen
RPTAG_OutlinePen
RPTAG_WriteMask
RPTAG_MaxPen
RPTAG_DrawBounds
RPTAG_APenColor
RPTAG_BPenColor
RPTAG_OPenColor
RPTAG_CloneRP
RPTAG_BitMap

APenColor and BPenColor take an 0xaarrggbb value.

_________________
Matt

Splendid job Bernd (and Georg), thank you for breathing new life into the classic AmigaOS.

Cheers,
James
x

I see that OS4 support no alpha blit functions.there is a third party lib.libablit.

"""
The ABLIT library provides a BltBitMap() compatible function call which adds the
missing alpha channel and blend support to AmigaOS (4.0). It also contains some
"""

I look into it and look that AFA create the lib on the fly in the graphics_lib.exe and wrap the functions.so OS4 sources can use too.
But better is if this library is build for every system(the SDL funcs dont need)

But i think that the AUthor of the lib create a lib for 68k is impossible in PPC War.
So developers are the main rule in the Split of amiga OS