Beta7 Whishlist(s)

Large List mode Tracker icons PS: https://review.haiku-os.org/c/haiku/+/10847

I won’t say the name of the person who is holding this change back, but you can look into the PS to find out who it is and he is the reason you can’t have this feature.

He claims to have never heard of any justification for the feature despite you and others requesting it on this forum.

I’m a bit salty about it, I’ve submitted several appeals to the decision but the powers that be don’t want you to have this feature even though it is done and works.

2 Likes

You can push fn + Backspace to get Delete, no need to remap your keymap.

2 Likes

There were several GSoC projects this year to enhance our Bluetooth support. Keep your fingers crossed and you may get this wish in r1b7.

1 Like

On this machine (MacBook Pro mind2012) Haiku does not recognize the fn key. However in US keymap holding down the ctrl key (this key is only on the left side of this keyboard) and pressing backspace act as perssing the delete key, in HU keymap does not work. But still no luck invoking the Team Monitor.

EDIT: I will open a separate thread for this as it is offtopic now.

Based on the suggestions already made, I make my own list for Beta 7.

  • Login screen support.
  • Better bluetooth support.
  • Better usb device support.
  • Implementing transparency in Haiku
  • Mature and fully merged 3D acceleration.
  • Fixing remaining Wayland compositor issues (e.g. dragging)

A few things im eagerly waiting for, which haven’t been mentioned yet:

  • Webcam Support, that works with native and non-native browsers.
  • mDNS resolution
  • AirPrint support (which I think relies on mDNS resolution.)

KDE Plasma recently implemented this and it’s been really nice, especially on keyboards that don’t have a Compose key. Initially the alternate character popup would disappear after a short timeout, but the default behaviour just got changed to not do that anymore (much better). It’d be great to have a similar feature in Haiku too!

Would be nice to have:

  • desktop extending
  • classic floppy drive support

6 posts were split to a new topic: 32bit Haiku on 64bit Haiku

classic floppy driver support

You mean the driver using the old FDD, smaller PATA-like interface!? Why!?

I guess you will get better luck to use an USB adapter for such device. Or simply use an USB-based floppy drive. USB 1.0 is enough for such, which means that pratically all hardware that have an USB port could use that.

I think USB floppy disk device is already supported by Haiku.

  • mDNS resolution
  • AirPrint support (which I think relies on mDNS resolution.)

Only for the auto discovery of the printer. It’s possible to implement IPP Everywhere and PWG/URF rasterization (the standards behind Airprint and driverless printing) without waiting first to have mDNS support. User will just have to enter the printer ip address manually, mostly.

Not really - you can find earlier forum threads about it -
That part of the Haiku community who has actual floppy drive hardwares, so not USB related floppy drives, has issues using a floppy drive in Haiku.
Haiku floppy solution is a special treat, just as Audio CD that automatically converted in Haiku, but Media server does not support the non-native ported media players to use Audio CDs in that converted mode.
Look at those threads about floppy working quirks. Time-to-time someone came up with wish for better, regularly working floppy driver.
Unfortunately I assume
noone who could work on with enough knowledge with Haiku driver development knowledge
– lack indeed a floppy driver or machine as well that would be connected to - as it needs IDE or SCSI floppy controller’s floppy port in a machine - connected via floppy cable
– lack the intent to write such driver, as mostly decided by them that : its obsolete technology already ;- ))

:cowboy_hat_face:

I am about to work on SCSI and Firewire storage, as well as USB CD/DVD writer support. I see no reason why I can’t also take a stab at classic floppy controllers. It would be useful to me. And before we say they are obsolete, I can give you an even more fringe use case. DD floppy disk support. That’s because I would like to be able to read and write floppies for my Mirage sampler. Not even BeOS offered support for DD floppies, if I recall correctly.

You also mentioned the CDDA thing. I made a media server change in my Media-OS project to fix the broken CDDA audio. I also fixed CDDA audio playback in Beton 1.3 that I don’t believe requires the media kit fix. So, it should be possible to get flawless CDDA audio either in the OS itself, or programmatically in the actual application.

3 Likes

Thank you considering to fix and maintain drivers that nowadays matters as legacy stuff for the most of end users.

Will you work on these to be added to the Haiku tree officially, or you involve AI help and then it will be installed from your “repo” ?

I just ask that in both case we users can have it, but in case the latter not automatically with Haiku upgrades - but as our independent effort to have it –
Also in this case it would be more convenient if you really have an independent Haiku repo we can add, or be in an existing Haiku repo if you can agree with any that already existing to have your stuff available from there, so would be available your developments from there - than download packages independently from a site and installing it also separately after downloading …
Sorry, I’m a layman a bit, and have a practical leaning toward conveniency ;- ))

:cowboy_hat_face:

My project is AI assisted, but it is not totally a lost cause in helping Haiku. Users can add packages from my repos to get the cutting-edge drivers now, and while I can’t submit pull requests of code directly to Haiku, I can submit change requests with my findings and hopefully help guide the devs through the process of implementing these, and what to watch out for from my own trials and errors.

3 Likes

Thanks for confirmation, as I know that you use AI help - from my side it is not problematic basically, but I also understand the concerns of devs via AI assisted development
– can get source code into the tree that needs another licence and that way another treat as well

-- sloppy code,
– or code that the developer itself cannot maintain or fix - as just used AI to patch lacking knowledge that needs for the feature he wants to provide.
(I mean for example someone would add LUKS or any other encryption support for an FS on Haiku, but the one cannot know how to implement the encryption algorythms, but would use an existing open source library available, and with help of AI the person wire it into the newky developed solution - he could only fix with again with help of AI - would they develop the most efficient fix or still had remained “gifts” for the future in it ?)
I remember you described your approach and tests, so I can accept your solutions, however I installed already AI assisted SW, from someone else, and finally had to back off it using as caused instability in Haiku in Media server ;- )) and there were no updates after a while …

Also asked the repo we can use with pkgman - as I previously I downloaded your stuff from here and installed too to try out - but would be easier if we could use a pkgman command that downloads, not only installs the package(s). I like the terminal better for admin tasks, than do it on fancy GUI changing from one Window to another that I can get in Terminal window doing some typing or recall from history and just hitting {ENTER} … ;- ))

You missed a few things that are important for retro stuff lovers which an USB floppy drive lacks:

  • No Low-Level Disk Access
  • Inability to Read Non-Standard or Custom Formats
  • No Direct Physical Control
  • Unreliable Formatting Capabilities
1 Like

No, I understand these needs for retro-computing.
I’m just not into that level of retro myself, not having the hardware that old still in good shape enough.

I do have an USB floppy drive bought a decade ago for instance, but no more any pc with an ISA connector for good old FDD.

And I stand corrected, I did currently test today, and USB floppy is not working correctly on Haiku, the usb_disk driver is struggling on inquiry command response. Will open a ticket for that.

EDIT: ticket 20313 opened.

2 Likes

So, To summarize (Things that were mentioned multiple times):

  1. Bluetooth x6
  2. USB improvement x5
  3. multihead x4
  4. Webkit2 x3
  5. eMMc x3
  6. Better Log viewer x2
  7. I2c x2
  8. Touchscreen x2
  9. Login screen x2

I’ll go through these in Order, I think Bluetooth is pretty clear and achievable.

For USB I would need some help to determine what exactly people want by better usb support? I’d ask the people who mentioned this to add a ticket for their USB issue, and I can then group it. (by making this a blocked ticket, you can also add 20316 into the “Blocked by” field)

Multihead is pretty clear, as is webkit2 and emmc.

A better log viewer/syslog and macros stuff is pretty important to me, @Lt_Henry If you are interested we can work on this together.

i2c and touchscreen is also pretty self explanatory. As for a login screen, multiuser, It would be possible but is unlikely to make it into the next or next after that beta… We are still missing severall core features to properly seperate applications from each other. (Personally I would start with some way to revoke permission from apps to use the network, read local files (except for a file picker) etc.)

I’m curious if this wishlist will lead to anything :slight_smile:
If it works out I might do another one for the next release

3 Likes

Hmm. Im not sure, I think supported. And if I good rebember in R5 Personal you can make floppy disk to boot BeOS directly. But for me this is a last thing what we need in Haiku nowadays.