Congratulations Bernd! Great work!

_________________
Modern Retro Experience

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

My concern is to have stability over speed, so I am not concerned to have patch upon patch upon patch just to have my icons draw faster. I would rather keep patches to a minimum and am happy to use original, slower C= code that has been shown to work reliably for thousands of users for many years, than AROS rewrites that haven't really been used in anger by more than a handful of people.

In the case of anti alias fonts however, the benefits of the enhancement outweigh the risk of system stability so I would consider installing it.

How do I go about just installing that one 'upgrade'?

_________________

AfA news are always great news!

This give a little bit more of life to my old steroided A2000.

I enjoy every single AfA update!

Quote:

How do I go about just installing that one 'upgrade'?

AfA_OS consists of several external libraries that do the trick. It is enough to remove some of them in order to disable specific patches. However I do not know exactly which library is responsible for truetype fonts...

EDIT: or you can use "IconBeFast" available on Aminet...
EDIT2: oh, sorry for confusing, IconBeFast is actually for speeding up the icon loading, not TrueType...

Last edited by glwxxx on 15-Apr-2006 at 07:21 PM.
Last edited by glwxxx on 14-Apr-2006 at 11:28 PM.
Last edited by glwxxx on 14-Apr-2006 at 11:13 PM.
Last edited by glwxxx on 14-Apr-2006 at 11:13 PM.

_________________
Modern Retro Experience

Quote:

Now all important new functions of OS4 and MOS are add.

What in particular does this refer to?

_________________
Matt

@mattk

It sound like stupid "marketing". I doubt OS4 level can be reached soon. From 3.0 to OS4 there is a GIANT leap.

Anyway it is a welcome news, maybe i'll try that on my expanded 1200. Thanks.

Last edited by ikir on 15-Apr-2006 at 12:02 PM.

_________________
ikir

>My concern is to have stability over speed, so I am not concerned
>to have patch upon patch upon patch just to have my icons draw faster.
>I would rather keep patches to

A patch use the Setfunction function from amigaOS add some new code and call then the old OS function.
Because AFA replace complete OS function with new code from AROS that is known as 100% compatible it patches
nothing.A replace of the whole function is done,because there is no original OS source.So cant
merge new code in old AOS code.

So it is important if you want other Amiga Patches that AFA OS is start before the patches.
Thats the reason wy now only few functions from now on of AFA exec can use .Because i dont know which
functions the powerup rom of bvision PPC patch.

But the diskfont.library picture.datatype ilbm.datatype is replace complete.And one fine day hopefully
no old AOS code must use.I think thats easiest way to have always a working comaptible OS and very fast new
features

for truetype fonts with AA or not too no old amigaOS code is used.same happen with the faster icons.
here the complete obtainbestpenA funtion is replaced by new code.

maybe AFA look like a patch because you need not replace original libraries
because it is a exe that is start from a loader it have lots advantage
boot without AFA is easy to see if the probelm come from AFA or program.
only the start of the exe must avoid.

For developer it is usefull when a program crash in a OS function you get not only $fc2345 crash.You get now
what library crash and when you have install segtracker you get a offset.Now you can load the AFA library
in a asm debugger (maybe barfly)and look what function on this adress stand.so you see what OS function crash

>Quote:
>Now all important new functions of OS4 and MOS are add.

>What in particular does this refer to?

truetype fonts with antialiasing.additional in AFA is that there are too slider so you can set AA strength.
If you use no TFT it is not need that you AA very few contrasts between Text and Background
This result in sharper Text and faster speed,because not so much pixels must calculate

Best quality settings depend on your display device and matter of taste,you can check in realtime with the
afa prefs preferences program for best setting

because most important for a OS is that it make it easy to write programs,thats the most needs of OS3.x

there are new OS funcs that allow alphablendet blitting.This need the cd player 2.1 for his nice alpha
blendet buttons.

also allocpooled can be task safe now and diffrent tasks can use the same mempool

you can use the draw functions without allocate and use a Pen by set direct the Draw color

SetRPAttrsA (*rp,RPTAG_FgColor,$ff0000,0,0)
Text *rp,"this text should red",20

amistart can use that feature and use 1 Pen few and draw flickerfree the taskbar text

Also more programs can now use this new features to get around the Pen Limit on workbench
Because all Amiga OS support that,there is no need to stay on the Pens.This make developing easy i think

the picture.datatype allow the load of png´s with alphachannels with the 68k akpng datatype.
In praxis you can see that working in amistart that you can now use a analog clock background

because AFA is only develop since 6 Months in hobbytime the other important features i want
are not in

To make developing more easy AFA should easy log OS calls print warning on illegal OS Call use
and or stop the program in safer system mode.For a warning requester there must implement lock tracking.because if the task
do a locklayer then it cant stop

Now AFA OS SaferSystem Mode support only few OS calls to be crasgsafe safe with wrong pars

I have now ask Stefan if he plan MUI4.0 for AFA OS or if he wants thats not possible
tell me what features he miss.
But currently no answer.I like the shaded MUI buttons and nice look.So it seem next step before above
i must do is port Zune to AFA


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

best is install AFA and remove picture_datatype.exe ilbm.datatype.exe and exec_lib.exe from afa_os_libs
and dont activate safer system and fast icons

Last edited by bernd_afa on 15-Apr-2006 at 12:52 PM.

Quote:

For developer it is usefull when a program crash in a OS function you get not only $fc2345 crash.You get now what library crash and when you have install segtracker you get a offset.Now you can load the AFA library in a asm debugger (maybe barfly)and look what function on this adress stand.so you see what OS function crash

I think it was Richard Körber who once wrote a program called 'function' which delivers the name of the OS function when you pass the ROM address to it. It works with ROM based libraries as well as diskbased libraries. So this feature is nothing really new

_________________
Stephan Rupprecht - AmigaOS4 developer

@bernd_afa

(First of all, welcome to AmigaWorld.net! )

Thanks for the information on the AFA features that compare with OS4/MOS. I think we probably have quite different ideas about what is considered to be 'important' features though. Good work nonetheless.

Quote:

SetRPAttrsA (*rp,RPTAG_FgColor,$ff0000,0,0)

Who's API does this 'FgColor' tag come from? That's not AmigaOS.

_________________
Matt

Quote:

Who's API does this 'FgColor' tag come from? That's not AmigaOS.

That's a MOS extension, as Bernd said, which has been incorporated in AROS as well. And now, with Afa, you can use it in AmigaOS3.x too.

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford

@falemagn

AROS is using MOS extensions? Who's bright idea was that?

Argh! This is so wrong/messy on so many different levels. 'FgColor' isn't even consistently named within it's own tag value range. That's why it jumped out at me. (Or does MOS rename the other tags as well?)

Anyway, just a small reminder that the AmigaOS SDK is freely available to download now...

_________________
Matt

Quote:

AROS is using MOS extensions? Who's bright idea was that?

What matters is that it was a bright idea, doesn't it?

And if not, why not?

Quote:

Argh! This is so wrong/messy on so many different levels. 'FgColor' isn't even consistently named within it's own tag value range. That's why it jumped out at me. (Or does MOS rename the other tags as well?)

What does it mean "'FgColor' isn't even consistently named within it's own tag value range"? And on what levels it's wrong and messy?


Quote:

Anyway, just a small reminder that the AmigaOS SDK is freely available to download now...

I guess anyone who's reading this thread noticed it, as the news is still on the front page. How's it related to Afa, though?

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford

@falemagn

If you're just going to play dumb with me, then there is not much point discussing this.

Anyone can see the obvious shortcomings of putting incompatible and inconsistent tags into a supposedly 'AmigaOS source compatible' project. And then furthermore taking that and moving it to AmigaOS itself for even more developers to trip over. This particular instance is probably easy to fix, but it makes a very clear example of how such efforts have further muddied the AmigaOS landscape.

The official AmigaOS SDK is publically available, so there are no excuses for making up any old API of your own and trying to convince everyone that this is still AmigaOS compatible.

_________________
Matt

>Thanks for the information on the AFA features that compare with OS4/MOS.
>I think we probably have quite different ideas about what is considered to
>be 'important' features though. Good work nonetheless.

I dont know what is for you important.I have lots of wishes(i better dont write not that Post get too long ).
but too few time.Because AFA is Opensource everyone can enhance it or enhance AROS.The results are now
for both OS

>think it was Richard Körber who once wrote a program called 'function' which delivers the name of the
>OS function when you pass the ROM address to it.
>It works with ROM based libraries as well as diskbased libraries. So this feature is nothing really new

Oh that was a lot work if this really 100% work.
find out in all diffrent Kickroms the adress of the function

if a API function call a subroutine a subroutine call another func its hard to find out.
But you know in exe files segtracker show too the calling function

>That's a MOS extension, as Bernd said, which has been incorporated in AROS as well. And now, with Afa, you can use it in AmigaOS3.x too.

Yes but this feature is easy make source compatible to OS4 too.OS4 use for this the name RPTAG_APen_Color

so only you need to do is.

#define RPTAG_APen_Color RPTAG_FgColor in a header file you always include

Then you can use too OS4 sources that use that feature.

In MOS and AROS you must switch the penfree mode on with a TAG.

in AFA it is enable automatic when you set RPTAG_FgColor.when do a SetAPen the Penfree mode is then disable
That happen on MOS too.

A reason wy MOS do not switch penfree mode on automatic I dont see.Also i see no sourcecode incompatibility
so i do switch automatic on in AFA so OS4 sources can too easy port

Quote:

If you're just going to play dumb with me, then there is not much point discussing this.

I'm sorry if you felt dumb. It certainly isn't my fault, though.

I just asked questions about the things you claimed, being genuilely interested in the answers.

Quote:

Anyone can see the obvious shortcomings of putting incompatible and inconsistent tags into a supposedly 'AmigaOS source compatible' project.

"Anyone" being you, and...? I don't see any shortcomings in adding functionalities to AROS OS, even making it complatible with MOS, with which there's an exchange of sources and ideas.

Now there are 3 OS's which support this extension: AOS3.x, AROS and MOS. Incompatible with what, AmigaOS4? So?

And, again, what do you mean by "inconsistent"?

Quote:

And then furthermore taking that and moving it to AmigaOS itself for even more developers to trip over. This particular instance is probably easy to fix, but it makes a very clear example of how such efforts have further muddied the AmigaOS landscape.

Sorry if I still fail to understand what exactly are you rambling about... "Easy to fix", you say? Fix what? I see no problems that need fixing. Bernd added this functionality to Afa 'cause some programs available for MOS need it, and this way that program could be recompiled for 68k and made available to the classic users.

Moreover, it's a clear improvement over one of the shortcomings of AOS3.x.

Exactly where's the problem with that?

Quote:

The official AmigaOS SDK is publically available, so there are no excuses for making up any old API of your own and trying to convince everyone that this is still AmigaOS compatible.

I won't comment on that... it'd be like shooting at the red cross.

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford

>The official AmigaOS SDK is publically available, so there are no excuses
>for making up any old API of your own and trying to convince everyone that this is still AmigaOS compatible.

amiga OS have no penfree draw mode.This is introduce with OS4.But OS4 sdk is only out since 1 week.

All new PPC OS offer new features that are same
but with diffrent syntax.I look how the writepixelarrayalpha blttemplatealpha funcs implement in OS4 some day
If thats not too much diffrent,i add this to AFA.this is only a lib stub i think

I also like if the AROS and MOS team add the define i write a post before to their includes and switch on the
penfree mode automatic when a rptag_fgcolor is set.So both Tags can use.All amiga OS are compatible in that way
with penfree mode.So a developer that write a program need no nasty ifdef

AFA have also changed the Flag that indicate truetype antialias Fonts from MOS to OS4 way.
This is necessary because the MUI texteditor class check that.
The 68k version is compiled automatic in OS4 way and check the flag.so no extra AFA define is need
For MOS there es extra a define

when MOS and AROS do too the OS4 way the #ifdef
in texteditor class can gone.

I think its not much work to be compatible and make the app developers the future use of new funcs easy as OS3.1 funcs

Georg have done the change for AFA because that the truetype font on MOS is indicate as a colorfont with a diffrent
structure the reqtools fontrequester dont like and give a enforcer hit

Quote:

Oh that was a lot work if this really 100% work. find out in all diffrent Kickroms the adress of the function

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

_________________
Stephan Rupprecht - AmigaOS4 developer

@bernd_afa

Quote:

Yes but this feature is easy make source compatible to OS4 too.OS4 use for this the name RPTAG_APen_Color

Yes, RPTAG_APenColor and RPTAG_BPenColor. I assumed it might be easy to fix. And I would highly recommend adding such a define to the AFA includes.

Unfortunetly, if AFA is to be using the AROS API, (which in turn appears to be using the some poorly considered MOS API now), then it seems likely that keeping such compatibility in check will become increasingly difficult. It's clear to me where the fault lies.

Anyway, good luck with it. It's good to see AROS being useful for something.

_________________
Matt

@bernd_afa

Quote:

amiga OS have no penfree draw mode.This is introduce with OS4.But OS4 sdk is only out since 1 week.

I know some people hate others reminding them of this fact; but AmigaOS4 is AmigaOS.

Quote:

I also like if the AROS and MOS team add the define i write a post before to their includes and switch on the penfree mode automatic when a rptag_fgcolor is set.So both Tags can use.All amiga OS are compatible in that way with penfree mode.

I agree. But I suspect the politics will mean they'd rather add Windows API extensions rather than follow the same path OS4 has set. [shrug]

Quote:

I think its not much work to be compatible and make the app developers the future use of new funcs easy as OS3.1 funcs

It would certainly be a good idea to have developers set a define to tell AFA what API they want to use. That way the developer is making a decision to use 'alternative' APIs instead, and the headers can hide the rest. This at least would avoid the problem of developers accidentally mixing different APIs.

_________________
Matt

Quote:

I know some people hate others reminding them of this fact; but AmigaOS4 is AmigaOS.

He was obviously referring to AOS3.x, given than he talked about AOS4 as well.

Quote:

I agree. But I suspect the politics will mean they'd rather add Windows API extensions rather than follow the same path OS4 has set. [shrug]

Why not, if it makes more sense than chosing whatever AOS4 implemented.

It might excape you, but there's no rule and no reason by which AOS4 should dictate what AROS and MOS do.

Quote:

It would certainly be a good idea to have developers set a define to tell AFA what API they want to use.

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

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford