All is well
Even though I had some private issues this week, all is going well with the PackageInstall. In its current form it is able to properly install all 3 test BeOS packages I tried on it, creating files and directories along with their data and attributes without flaw. So, what’s left to do right now?
- The package installer GUI right now is implemented using the traditional way - with font sensitivity in mind. Ryan proposed that this might be a good chance to start using the Haiku layout API to get things done better and more readable.
- Package and file collisions. What to do when a package is already installed or a file from the package already exists in the given path? This was given some discussion a while back, but it's still not clear whether any complicated form of operations is needed. Would the standard 'Should I replace XYZ?' suffice?
- Testing. I need to test the package installer on various different packages, whether attributes are inflated and added as they should and all the similar. With this, I will also try to clean up the code a bit, since there are places that could use some rewriting.
- Writing missing support for some features. During the writing of the parser there were a few tags I ignored because of their low significance (e.g. the Plat tag, showing the platforms on which the package can be installed). Nothing that is not completely useless shouldn't be ignored.
After finishing more or less these four steps, I think PackageInstall would be very much ready for public testing. Hell; it’s ready for such tests from the moment it ‘worked’, but it’s better for me to first fix all issues I know about and only then let everyone search for all the bugs I left behind.
Also, I have already started implementing the user interface of the package uninstaller. There was a discussion about what design should be chosen at the Usability Team mailing list a while back, after which we came (more or less) to a satisfactory consensus. The same as before the chosen layout is simple, usable and very ‘Haiku’. The sketch of the design in mind can be seen to the right. Of course, since the work on the application has not started full time yet, it’s not final and can be changed. In fact, there was also another very nice proposition (made by Jonas) for the package uninstaller to look like most BeOS preference applications, meaning having the list of installed applications at the left border of the window. But as Stephan said - the layout is not as important right now, since we can easily change this later on. No one would like this to become the typical “bikeshed” argument ;-)
That’s how the situation looks like. I will probably be busy during the nearest week, so I don’t think some great progress will be made during that time. But as always - stay tuned.
- Haiku almost-monthly activity report - October and November 2019
- Haiku monthly activity report - September 2019
- Node.js now available in Haiku
- Haiku monthly activity report - 08/2019
- GSOC 2019 Final Report
- Haiku Activity Report: Performance Edition
- new PVS studio scan
- Coding week 4,5,6
- [GSoc 2019] Weeks #4, #5 and #6 progress report
- Haiku monthly activity report - 06/2019