Thanks for your work with the file descriptors. That is a good starting point. I have the datatype descriptor for my TIFF datatype . I just need to collect the files to compile and post them. I suspect TIFF datatype may work on AROS x86. Also I don't see HEIC in the list. Do we have it?

Here's some programming advice...

If the programs or features you are looking for aren't available and if no one is available to do the work then sometimes it's easier and faster to do it yourself. Seriously, if you have determined will to do it, you can succeed.

In the AROS programming area especially these things could take a long time since not many people are involved in development.

Here is a text file about AROS datatypes and it also describes my journey in C programming. As far as c programming just start writing and compiling and testing. It won't always work but sometimes it does! That's when it gets more interesting, when everything works.

As far as programming goes don't be afraid to fail. At times my failures are spectacular. Sometimes I crash AROS so hard there is no warning it just restarts. I wonder if the measure of a good programmer is how badly I can crash the operating system?

OK thanks for the info, but at the moment it is not important to save the 'XBM' format, all other graphic formats can be saved.

What is important is that AROS recognises the most commonly used graphic formats on the web and has a tool to display them correctly.

Today I have finished all the Def Icons, created the def_XBM, def_XPM, def_PPM, def_TIF_,def_WEBP, def_SVG, AROS One now automatically recognises and displays most of the graphic formats found on the Web, the supported formats can be seen in the screenshot.

AMIGASYSTEM

Whether or not you can save images with MultiView 1.7 or MultiView 1.8 depends on the datatypes you have on your system. To say a datatype works with one version but not the other doesn't seem right.

As I suspected XBM and XPM are X Windows datatypes but no source code is provided.

So if you are interested you could install a nice Hex Editor and a code editor with syntax highlighting. For Windows 10 I use HxD Hex Editor. For code editing I use Visual Studio Code or ActiPro Code Writer. You already have the Picture Datatype Creation Package.

Now you just need a good pair of reading glasses to do the online research. Start writing you XBM and XPM datatypes by finding the file format documentation for each file type.

Look at some existing datatypes to see how to write the load and save functions. Look at PNM datatype. It's easier to understand. BMP is a little complicated. Happy coding!

XBM & XPM Datatypes are aros-archive

http://archives.a...type/image


With Multiview v1.8 you cannot save XBM & XPM images

With Multiview v1.7 you can only save XBM images

With Multiview v1.8 you can only save PPM images (Save and Save As)

AMIGASYSTEM

Where are the XBM & XPM datatypes located?

Where can I find them so I can verify that they both have save functions?

Many thanks Miker

AMIGASYSTEM & Amiwell79

Thanks for the information.

I also compiled & did some testing with the newest Targa datatype. I opened the 24 bit RLE compressed Targa file with MultiView 1.8 then chose "Save As" from the Project Menu. It saved a good uncompressed 24 bit Targa file to Ram. Also, I opened an 8 bit Targa file & successfully saved it to Ram. I haven't tested 16 bit or 32 bit.

In the next update (41.3) I will complete the Targa RLE (run length encoding). For the moment all Targa files saved with the new datatype (41.2) will be uncompressed. Note that version 0.2 of Targa datatype doesn't save correctly.

Attached is the MultiView screenshot, the new Targa datatype & new MultiView that Amiwell79 mentioned earlier. More datatype updates soon. Please don't repost the Targa datatype. It's still being revised and tested to confirm functions.

PS - I like the new MultiView icon.

miker, I have tested your Multiview v1.8 and Save As works fine with all datatypes except XPM.

Your Multiview v1.8 also displays XPM and XBM images correctly

on archives there is multiview 1.8

Ok miker, io aggiorno AROS One con le nuove Build di deadwood e di conseguenza sul Sistema mi ritrovo Multiview v1.7.

Però strano che i con i Datatypes con LoView Save As funziona bene, e si può salvare le immagini in quattro formati diversi !

@amigamia

Is it possible to get the attachments from the old topics from ae.arosworld.org ?

There are some files I need that I uploaded there.

AMIGASYSTEM

Ah. I see the problem.

Thanks for the video.

This is MultiView 1.8 in my screenshot.

According to your earlier screenshot with Targa & PCX versions you are using MultiView 1.7 where Save As has been removed. It's actually quite useful. Maybe that's why I added it back.

You can't Save As if there is no menu item. But Save As IFF does nothing to test saving Targa & PCX. The datatypes have their own save functions.

I created a small video where you can see the saves of 'Multiview!' and 'LoView'.

AMIGASYSTEM

Did you test the save functions for Targa and PCX datatype by opening the images in MultiView then us Save As from the menu?

Save As IFF will save an ILBM. That won't test the save functions for Targa and PCX datatype.

Tiff datatype will need to be compiled and tested. Until now I only compiled it with the Build System and all testing was done on AROS x86_64. Maybe AROS x86 will perform better.

I will test build and test the latest Targa & PCX. I'll try to build the latest Tiff datatype for x86.

With all the new datatypes available in the build, with "Multiview" I can safely save images in IFF

If instead I use 'LoView' with all the new datatypes available in the build, I can save in IFF, JPG, PNG, BMP.

Practically all the datatypes work perfectly, except TIFF which does not exist, then the HTML datatypes which do not support some web pages would have to be improved.

I avoid using my mobile phone on Forums, too inconvenient!

Here are some instructions for building the datatypes and descriptors.

Targa datatype should support loading and saving 8 bit, 16 bit, 24 bit & 32 bit Targa images. That & RLE compression was the main reason for the current update. The previous version only supported saving the 24 bit Targa images.

For Targa I think the toughest part was writing the 16 bit support & Targa RLE. The Targa run length encoding works at the pixel level rather than at the byte level for PCX. So I had to use memory compare method to compare bytes.

It's easier to write text files than to type on my phone. I'm getting old. LOL

You have probably already used the datatype descriptor tool. That is also in the tools folder.

Trying to find it on AROS Archives is a pain since the search doesn't work for the Picture Datatype Creation Tool so here it is:

AMIGASYSTEM

According to the version screenshot those are the original datatypes without save functions.

If you look at the new versions screenshot and picture datatype screenshot I bumped up the versions to match the main version of the current picture datatype which is 41.6. It has DT_Write which I added so it's the current file.

The Targa version is 41.2. PCX version is 41.3.
I can help you to build and update the datatypes.

Typing on smart phone is tedious. It auto corrects nearly everything. And then after typing a lengthy explanation Arosworld dumps what I wrote without posting it. Then I start again!!

Targa and PCX of the new Builds are very recent (see screenshot), also Multiview allows you to save images in IFF.

If you use LoView you can save Images in IFF, JPG, PNG, BMP (see screenshot), LoView uses Datatypes to display Images.

As already mentioned LoView also shows XPM, and XBM images correctly and can save in the formats described.
Multiview on the other hand shows XPM, and XBM images in Text format !

AMIGASYSTEM

To test the Targa and PCX datatypes you have to first open them in MultiView and select Project - About from the menu. Take note of the Targa & PCX datatype version. Then select Project - Save As. MultiView will save a copy of the file using the current datatype Save function.

If the Targa file and PCX file saves correctly then the save functions are working correctly. 24 bit picture files are the best choice to do testing.

The AROS x86 version of Tiff Library is on the AROS Archives. In Development.