-Will there be support for other filesystems in the future
Yes, I don't know when but others will be supported. We have FAT (12/16/32), NTFS and CDFS (ISO9660/Joliet) right now, support for EXT2/3/4 would be good and there is quite a bit of information around including some pascal source to start from. Possibly exFAT (or FAT64) might be useful and the CDFS module needs expanding to support UDF for DVDs. The interface is modular so any file system could be added, it just depends on what is needed.
-Is it posible to use SSL with the network components
Not yet but work is underway to add it, the core ciphers and hashes (like AES, DES, SHA256 etc) were committed to the code last month and there is ongoing work to add the other layers needed for TLS etc.
-Which kind of dyn liberies use ultibo .dll, .so,...
Currently libraries are not supported, it is likely to be possible in future since it opens up access to non pascal code. It would probably be .so format initially to be consistent with the toolchain used by the compiler.
-Will there be support for the pi-touchscreens in the future
Yes, the official pi touchscreen already works as a display and the details of the touch interface are known from the Linux driver. Other touchscreens could be supported if there is enough information available for them.
@taazz
Had you sucess with your qemu emlation of ultibo, I have try it the last couple days without sucess.
There is some detailed information here https://www.pcsteps.com/1199-raspberry-pi-emulation-for-windows-qemu/ and a prepackaged download here https://sourceforge.net/projects/rpiqemuwindows/ for Raspberry Pi QEMU. This only supports Raspberry Pi 1 (Model A, B etc) and not the Pi 2 or 3, also remember that when they are talking about a .img file they mean a disk image not the kernel.img produced by Ultibo. You need to create a disk image file from an SD card using something like Win32 Disk Imager.
EDIT: Just did a quick test of the prepackaged RPi QEMU download, it seems to be loading the kernel image at 0x10000 instead of the normal 0x8000 and crashes immediately which is what I would expect. Other articles suggest this is the normal load address for QEMU so I don't think it will work unless there are other sources which have a more exact RPi emulation.EDIT: Disregard that, the latest official QEMU now has support for -M raspi or -M raspi2 which should be much closer to what is needed for Ultibo, I need to find some documentation about what parameters are required and what is supported.