I would find it nice if more people, who have access to hardware, could test this with Haiku. I
would not encourage anyone to risk his job to make these tests, but if there is a possibility to do this in consultation with the boss or salesman, this would be a great asset for the community.
We put these tests on our knowledge base and expanded them, so you can see at a glance which of the main components are supported and which are not (Thanks toChaotic).
Database lacks desktop motherboard entry and video integrated or not (in separate card), also āNameā entry not enough definite.
And I made mistake (DD3)ā¦
@lelldorin: I repackaged your HPKG by edit the .packageinfo file
FROM
requires {
yabbesly
}
TO
requires {
yab
}
And installs fine at the first attempt.
I noticed that the yabbesly package contains the same files as āyabā from HaikuPorts: the same binaries and libraries; furthermore the yab package from HaikuPorts has more chances to be updated to the latest version
I was thinking that your app deserves a better icon, instead of a generic icon, so, if you are glad about the fact to add an icon to your app, I made/composed an icon about, which recalls the āhardware infoā thing:
This time I just grabbed a pair of premade HVIF icon, and I composed them in Icon-O-Matic, but in past I used autotrace (I have the Haiku binary for autotrace) and WonderBrush to make HVIF icons.
Iāve used WonderBrush several times to create SVGs I can turn into HVIFs. Quite a bit of tweaking is needed in I-O-M, especially as the SVG shapes arenāt nametagged, but itās a lot easier overall.
I didnāt know about autotrace, but I just grabbed it from BeShare. Have had variable success with it initially. The first simple logo I tried got converted to SVG beautifully, but another that looked almost identical came out a total mess! Only handles formats like TGA and PBM, and wants to crash a lot. The source came with the hpkg, though, so maybe something could be done with it. Would be highly useful.
Indeedā¦ Turns out that even though it only handles formats like TGA and PBM, it isnāt even very accomodating with those! I couldnāt resist playing some more, and I eventually tamed it a bit.
The insight came when I realized that the TGA file that worked had actually been created on the BeBox nearly 20 years ago! All the new ones I tried ā created with ArtPaint, or using ImageMagick āconvertā to transform a PNG into TGA ā gave garbage SVGs. And what all the latter have in common is that they have an alpha channel! When i finally used convert on a (high quality) JPG, that also worked.
So the solution, if the original has alpha, is to use, e.g.:
āconvert logo.png -alpha off logo.tgaā
Then autotrace can be quite good at generating an SVG. In fact I was a bit astonished to find that a fairly ārealisticā portrait turned into a handsome HVIF ā if one is willing to live with an ~11K icon!
I have repackages the yabbesly package, because i does not have fun to rebuild all my packages at the moment. i will change this in the future then i make a new build of any program (time by time).