New Picture Datatypes

[miker1264]

I've been working some long hours over the last couple weeks.

And I've been doing some C# programming on my Virtual Disk Image Explorer program.

After doing C programming for AROS for the last 5 years C# seems really easy. I suppose I could do C and C# both at the same time. 

Later today I will compile my updated TGA and PCX datatypes.

[AMIGASYSTEM]

Thanks miker for your great work, about "iconclone 68k" is there any news?

[OlafS3]

I've been working some long hours over the last couple weeks.

And I've been doing some C# programming on my Virtual Disk Image Explorer program.

After doing C programming for AROS for the last 5 years C# seems really easy. I suppose I could do C and C# both at the same time. 

Later today I will compile my updated TGA and PCX datatypes.

both C and C# have common base. C# also automatically frees memory of variables what is a nice feature and avoids errors (garbage collection). The most complicated part with modern high languages is knowing where to find something in the huge class library and use it the best way. And of course you need strange things like debugger and online help. A little in contrast to what is at amiga or aros programming mostly  available  gcc is already a exception but visual studio is a good development tool.

[miker1264]

@OlafS3

Yes. When developing for AROS it's a long series of tasks that can be very repetitive and very tedious.

I edit the code with Visual Studio Code Editor or Scintilla Text Editor because they offer syntax highlighting and VS Code has Goto and Code Search. Then I conpile with the Linux Crosstools. Then I copy the binary to an SD Card to load into AROS using VirtualBox for further testing and refinement. It takes 5min for each iteration from editing to compiling to testing to editing.

Whereas with Visual Studio I can edit within the IDE itself with all the benefits of VS Code. Then I can build the solution in a few seconds. Then "Start Debugging" will run the binary for testing. The entire process from editing to testing is about 30 seconds!

That's a huge difference. It will take some getting used to C# again after using C code especially not having to be concerned so much with memory management and string handling. But DotNet Framework is very slow compared to lightning fast C.

[deadwood]

Maybe take a look at workflow based on linux-hosted AROS? Binary is available for testing right after compilation (no need to copy) and you can use GDB to debug it, which makes development cycles faster in my opinion.

[miker1264]

Maybe take a look at workflow based on linux-hosted AROS? Binary is available for testing right after compilation (no need to copy) and you can use GDB to debug it, which makes development cycles faster in my opinion.

That's true. I'm considering that approach to make it easier.

When I originally setup my Testing Environments they were in VirtualBox. So I have several flavors of AROS running there. Some are Native and some are Hosted on Ubuntu 16.04.

I had later acquired VMWare Workstation and my first Build System was for ABIv1. So at the beginning the Build System was seperate from the Testing Environments. Then later I installed Build Systems for AROS 68k and after that ABIv11. Recently I included ABIv0. So I have four Build Systems in VMWare on Ubuntu 18.04. There's no reason I can't run both Build System and Testing Environment in the same VM.

I will need to reconfigure my workflow to make things easier in the near future. Recently I purchased a new 2TB SSD because  I'm running out of hard drive space. If I move my Icaros setup from VirtualBox on Ubuntu 16.04 to VMWare on Ubuntu 18.04 then with all my test files and apps that's about 4GB of data.

I'm currently using a 1TB SSD for development but it's too small.

[miker1264]

I'm currently revising my updated TGA and PCX datatypes so that they compile correctly for AROS x86.

There are several small errors that need to be fixed before they can be compiled and tested for x86.

[paolone]

I'm currently revising my updated TGA and PCX datatypes so that they compile correctly for AROS x86.

There are several small errors that need to be fixed before they can be compiled and tested for x86.

Many thanks.