Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
103 user(s) are online (61 user(s) are browsing Forums)

Members: 3
Guests: 100

trixie, skynet, afxgroup, more...

Headlines

Forum Index


Board index » All Posts (joerg)




Re: Icon Wunschkonzert - AISS Edition
Just can't stay away
Just can't stay away


@Wanderer

Quote:
Yes, OS4.1 might have scaling for icons, as well as AfA OS 4.2 does.
But what's the use of it if you are an app programmer?
Do you want to limit yourself to OS4.1?
AmigaOS 4.x, icon scaling was supported by the AmigaOS 4.0 icon.library already, AmigaOS 4.0 just didn't use it itself yet like the AmigaOS 4.1 workbench does.

Quote:
I don't want to cause a flame war now, but I like my apps run everywhere.
For that you either have to implement everything 4 times, especially the GUI parts (AmigaOS 4.x ReAction, MorphOS MUI4, an AROS GUI for AROS, and either ReAction if you only want to support AmigaOS 3.5+, but still different to the AmigaOS 4.x ReAction GUI because of missing features and bugs in the old AmigaOS 3.5/3.9 classes, or even something completely different for AmigaOS 3.0+), or you only use the common AmigaOS 3.1 API and it's crap everywhere (gadtools GUI, no support for charsets other than ISO-8859-1, no mouse wheel support, etc.).

Go to top


Re: Icon Wunschkonzert - AISS Edition
Just can't stay away
Just can't stay away


@orgin

Quote:
Dunno, perhaps the composition engine (cairo) of OS4.1 already can do all of the stuff mentioned here. Or at least should be used for something like this.
It doesn't matter if graphics.library, Cairo or another library like the one proposed here is used for scaling the images, adding computed effects, etc., for a GUI such low level graphics functions are useless, you need an image class which supports these features and can be used as replacement for the current image classes (bitmap.image, etc.).
Such an image class can use Cairo or toolbar.library internally, but they can't be used directly in BOOPSI GUIs.

Go to top


Re: Icon Wunschkonzert - AISS Edition
Just can't stay away
Just can't stay away


@Wanderer

Quote:
Like (peudo Code)

LoadBitmap(TBImages:cut24x24);

or

LoadIcon("MyIcon.info",24,16)

would load the icon in the specified (maximum-)size.
You, as the application developer dont care about it's actual size.
This is very handy for toolbars and everywhere you display Icons, when you want to force them to have uniform sizes.
On AmigaOS 4.x it would only add the scaling for images, not for icons since icon.library does support scaling icons itself. It's used for example in the new AmigaOS 4.1 Workbench text mode.

Quote:
So I decided to put it into a library. But if MUI and Reaction access the images by themselves, this only has a benefit if you need the resizing and/or effects.
For both it would have to be a BOOPSI image class. Although you can use old style struct Image images as well they have several limits, they are not only at most 8 bit palette mapped ones without alpha but a struct Image is of course only a single image and even if you can add 3 different struct Image images to a button like for example in buton.gadget (BUTTON_RenderImage, BUTTON_SelectImage and BUTTON_DisabledImage) it's still incomplete compared to a single image class image which can have more states, which you could compute from a single source image:
IDS_NORMAL
IDS_SELECTED /* for selected gadgets */
IDS_DISABLED /* for disabled gadgets */
IDS_BUSY /* for future functionality */
IDS_INDETERMINATE /* for future functionality */
IDS_INACTIVENORMAL /* normal, in inactive window border */
IDS_INACTIVESELECTED /* selected, in inactive border */
IDS_INACTIVEDISABLED /* disabled, in inactive border */
IDS_SELECTEDDISABLED /* disabled and selected */

Using a 32 bit ARGB struct Bitmap returned by your library with the bitmap.image class and the image created by bitmap.image in a button.gadget would make it possible to use true colour images with alpha, but it wouldn't solve the problem of the additional states, bitmap.image is limited to 3 sources for 3 states (BITMAP_BitMap or BITMAP_SourceFile, BITMAP_SelectBitMap or BITMAP_SelectSourceFile and BITMAP_DisabledBitMap or BITMAP_DisabledSourceFile) as well.

Go to top


Re: Icon Wunschkonzert - AISS Edition
Just can't stay away
Just can't stay away


@Wanderer

Quote:
The idea is to complete AISS by having an interface to access the images. Not everybody is firm in laoding and blitting images with alpha channel.
Of course you don't have to do anything like that yourself in any of the usual AmigaOS GUI systems (ReAction, MUI, Feelin, ...). It would only help in programs not using a GUI system but manually drawing something in a window instead.

Quote:
The library provides scaling and caching, so that two programs won't load the same images 2 times.
At least on AmigaOS 4.x it would only add scaling, and maybe computed effects for the selected and ghosted images instead of loading 3 separate images, but not caching since the intuition #?BitMap(Source|Instance)#? functions used by classes like bitmap.image cache the images and share them between multiple users already.

Go to top


Re: Icon Wunschkonzert - AISS Edition
Just can't stay away
Just can't stay away


@Wanderer

Quote:
The interface works like this:

aissbutton aiss_Open("TBImages:cut",width,height);
aiss_Blit(button,state,x,y,RastPort);
aiss_Close(button);
With such a low level interface it would be quite useless, it has to be a BOOPSI image class which can be used as replacement for something like
cutimage BitMapObject,
              
BITMAP_Screenscreen,
              
BITMAP_MaskingTRUE,
              
BITMAP_TransparentTRUE,
              
BITMAP_SourceFile"TBImages:cut",
              
BITMAP_SelectSourceFile"TBImages:cut_s",
              
BITMAP_DisabledSourceFile"TBImages:cut_g",
           
BitMapEnd;

Go to top


Re: OWB 2.11 !!
Just can't stay away
Just can't stay away


@Crumb

Quote:
-OS4.0 compatibility: for CSPPC OS4 owners
OWB 2.9+ doesn't need AmigaOS 4.1, 4.0 is enough, but it needs a current version of Cairo. The one from 2005 on os4depot.net is too old and unless someone else builds a current version for AmigaOS 4.0 the only one usable for OWB is the one included in AmigaOS 4.1, I don't have the time to port libraries OWB needs myself.

Go to top


Re: OWB 2.11 !!
Just can't stay away
Just can't stay away


@JCC

Quote:
I would *REALLY* like to be able to log into my Linksys router. I get "401 Unauthorized" instead of a login request window.
I've checked what's required for that, but it seems it would need additional code in at least 4 different parts of OWB to support it

An easy way may be adding it to libcurl instead, but I don't know if it caches usernames and passwords, it could be that you'd get the requester for each request, i.e. if there are 20 images on the page 21 requesters and you'd have to enter the username and password 21 times which would be unusable as well and much worse than having to enter the full URL with username and password, something like http://username:password@192.168.1.1/ , which works already.

Go to top


Re: OWB 2.11 !!
Just can't stay away
Just can't stay away


@sofistisoftware

Quote:
the % of cpu usage with 2.10 version is too high also when you leave it in st.by, example with amigans home page the cpu is busy about 50-85%,
FireFox needs even more CPU time on amigans.net, partially because of X11. It's because of the "4.1"s at the top.

Quote:
owb 1.25 use cpu on the same page about 10-30% and the scroll is a lot better in this old version
Did you have the "LOWMEM" tooltype enabled in 1.25 when comparing them? If not they do something completely different:
OWB Blastoise renders the complete page into an image, which, once that's completed, of course makes everything much faster, especially scrolling since it only has to blit parts of the pre-rendered page image on the screen, but that needs several 100 MB RAM for large pages.
OWB Doduo, like all other browsers incl. the AmigaOS 4.x port of OWB Blastoise with "LOWMEM" tooltype enabled, only renders the currently visible parts of the page and when scrolling it has to render the new parts (only in the AmigaOS 4.x port, on Linux it rerenders the complete visible part even when scrolling only a single line).

Go to top


Re: OWB 2.11 !!
Just can't stay away
Just can't stay away


@HammerD

Quote:
-better fonts (current one is a bit wide)
It's configurable with the XPDI and YDPI tooltypes. The correct values would be 72 for both, but since that was too small for most users the default XDPI is currently 80.

Quote:
-memory cache for pages and images
It has a memory cache. It just uses constants (256 MB total RAM, some percent of that are used for the cache size) unless specific code for each OS is added, the next AmigaOS 4.x version will use the correct size.

Quote:
-speed optimizations
You should test OWB on other systems
The AmigaOS 4.x port is very fast already, rendering is probably around 10 times faster on average than on Linux. It's very unlikely that even more noticeable speed-ups are possible.

Go to top


Re: sfssalv for 68k?
Just can't stay away
Just can't stay away


@csynt

Quote:
Is there any SFSsalv or repair utility for SFS under 68000 ??
SFSSalv is m68k and included in the full SFS archives, but if you really mean 68000 I'm not sure, it could be a 68020+ executable since SFS itself, at least my versions, needs at least a 68020 CPU as well.

Go to top


Re: Ranger does not run at all
Just can't stay away
Just can't stay away


@Granada

Quote:
Line 32 seems to be the beginning of the end ... Any ideas?
Tell Steven that he should check the hardware and don't try to use nonvolatile.library on classic Amigas. There are nonvolatile libraries on classic Amigas and the AmigaOne, but despite the same name they are something different.

Go to top


Re: Floating "4.1" on this site
Just can't stay away
Just can't stay away


@Atheist

Quote:
FOUR % on a Quad core you say??? I think they're trying to make a point, and succeeded, hehehe!

Boy, windos is strange! A little bit of anime, and it requires 2.6 GHz * 4 Core * 4% = 416 MHz for a few falling CHARACTERS. AND, I'm not even including the SIX HUNDRED + MHz GPU in there!
It has nothing to do with the OS or CPU, on an AmigaOne with AmigaOS 4.1 it needs about 85% CPU time, i.e. 680 MHz for a few falling chars - which requires constantly relayouting at least parts of the page, or more likely even the complete page since the changes are at the top.

Go to top


Re: OWB 2.10 out
Just can't stay away
Just can't stay away


@Kicko

Quote:
The pointer is ok but the shadow is too fat under the pointer which makes it look like it has alot of smoothed dirt under it ;)
You can simply delete the pointers you don't like, if a pointer is missing it uses the AmigaOS ones (busy pointer for the waitCursor, normal pointer for everything else) instead.

Quote:
Please make the shadow narrower/smaller.
That's something for Mason, but if you have something you like better already you can replace them in the Resources directory. The same format as for the the 32 bit def_pointer and def_busypointer ones is used: A single image, truecolour icon with X/YOFFSET tooltypes for the hotspot.

Go to top


Re: OWB 2.10 out
Just can't stay away
Just can't stay away


@Ami603

Quote:
no downloads implemented yet?
No, and no uploads yet either.
Using a hack like in the AmigaOS4 port of OWB Blastoise for downloads, it cancelled the transfer and started a separate task downloading it again, would probably be as easy in OWB Doduo, but I want to implement it correctly.

Go to top


Re: OWB 2.10 out
Just can't stay away
Just can't stay away


@nubechecorre

Quote:
But so, if someone like me has a mason pointer installed had to change the softsprite to yes ?...
Radeon gfx cards support truecolour pointers and you shouldn't enable softsprite, only with other gfx cards which only support 2 colour pointers, on the AmigaOne Voodoo and Permedia2 gfx cards, it's required.

Go to top


Re: OWB 2.10 out
Just can't stay away
Just can't stay away


@TMTisFree

Quote:
PS: do you have received my installion script?
Yes, but there is only one file which has to be installed (curl-ca-bundle.crt) and starting with the next version I can use the AmiUpdate script to install/update it. The shared objects don't have to be copied to SOBJS:, it doesn't make any difference if they are in SOBJS: or in the same directory as the OWB executable.

Go to top


Re: No charakter display in OWB (OS4 Classic)
Just can't stay away
Just can't stay away


@Granada

Quote:
I am happy that OWB finally works. Hopefully there will once be OS4.1 for Classic - it is inacceptable to have the CPU at 90% load while writing this post.
Only a current Cairo port for OS 4.0 would be needed, but it wouldn't reduce the CPU load, even the FireFox on my AmigaOne I'm currently using for the reply has nearly as much CPU load. It's caused by the little "4.1"s at the top of amigans.net
On other pages, especially if they have no gif anims either, the CPU load should be very low even on a classic Amiga, but only after the page was loaded completely, and scrolling around is probably very slow on classic Amigas as well but there isn't much which can be done, a browser like OWB needs a lot of CPU time.

Go to top


Re: No charakter display in OWB (OS4 Classic)
Just can't stay away
Just can't stay away


@Granada

Quote:
Just two days ago I turned it on again, did install some Updates and saw that there was OWB 2.8 out now (even 2.9 by now, but this version needs Cairo). OWB 2.8 claims that it would not any longer make use of the core fonts but uses the amigaOS'es internal font engine.
That was the case with 1.21 as well, both use the core fonts if they are installed, but they are and always were optional, if they are not installed OWB uses the DejaVu fonts included in AmigaOS 4.x instead.

Quote:
But still the problem remains: OWB comes up, loads its default home page amigans.net, but it does not display any text at all.

What could that be?
Read 2.5 of http://www.amigans.net/modules/AMS/article.php?storyid=24 and check if you installed everything correctly, especially not only the .font and .otag files from my corefonts.lha but the actual fonts (the .TTF files) as well.
If that wasn't the problem create a directory somewhere on your SYS: partition and move all .font and .otag files from FONTS: which weren't included in AmigaOS 4.0 there. OWB should work now and use the DejaVu fonts. If that's that case please move one font after each other, both the .font and .otag files, back to FONTS: and as soon as it stops working please send me the problematic .font and .otag files. Several users have problems with fonts working correctly in other applications but not in OWB, but without getting the .font and .otag files which don't work with OWB I can't check what the problem is and fix it.

Go to top


Re: OWB 2.9 Released !
Just can't stay away
Just can't stay away


@Vulture

Quote:
would you at least consider making a last cairo-less version of OWB with working downloads and , maybe , bookmarks?
No, besides the double work for maintaining 2 different versions just building one OWB executable takes several hours.

OWB 2.9 doesn't use any new AmigaOS 4.1 features, all I need for an AmigaOS 4.0 version is an up to date Cairo port for it, the one on os4depot.net is too old. I don't have the time dto do it myself, but AFAIK Cairo can be build without any changes in the sources and if someone else builds a current verision of Cairo I'll build AmigaOS 4.0 executables of OWB 2.9 and newer versions with it.

Go to top


Re: OWB 2.9 Released !
Just can't stay away
Just can't stay away


@Vulture

Quote:
So, will you still update OWB for us classic OS4 users who may never see Cairo implemeted?
Maintaining 2 different versions of OWB is too much work. There is an old AmigaOS 4.0 Cairo port on os4dept.net, if it's working without problems I'll build an AmigaOS 4.0 version of OWB 2.9 with it, but if it doesn't work someone else will have to port the current version of Cairo to AmigaOS 4.0, I don't have the time to port libraries needed by OWB myself as well.

Edit: I just tried building OWB with the Cairo library from os4depot.net but it seems to be too old, the following functions are missing: cairo_clip_extents(), cairo_has_current_point(), cairo_pop_group_to_source(), cairo_push_group(), cairo_surface_get_content(), cairo_image_surface_get_data() and cairo_image_surface_get_stride().


Edited by joerg on 2008/9/14 16:46:37
Go to top



TopTop
« 1 ... 56 57 58 (59) 60 61 62 ... 85 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project