Suggestion Box

Suggestions about something related to Haiku? Post here.

webpositive in nightly builds

Forum thread started by farvardin on Mon, 2010-10-18 12:21

hello,

I don't understand why the nightly builds have the TV application or the teapot GL demo which are pretty useless (even if the teapot is cool), and not webpositive, which is essential for using a modern OS connected to internet.

multimonitor support/ more monitor resolutions

Forum thread started by thatguy on Sat, 2010-09-11 18:13

Would be nice to get support for multiple monitors along with more monitor resolutions. I don't want to create a ticket but what exactly does the development team need to implement this ?

support for Epson printers Open source Librarys available now

Forum thread started by thatguy on Thu, 2010-09-09 22:11

http://global.epson.com/technology/driver.htm#printer

they have created a open source driver model for epson printers. commonized language. supporting epson printers looks fiarly easy compared to alot of other devices. If someone is willing to help me I would gladly work on this.

some package management ideas

Forum thread started by danho222 on Tue, 2010-09-07 20:52

This is just a collection of ideas I would like the haiku package manager to have.

The list of all installed packages would be stored in a database, such as sqlite (being fast, constantly developed and suitable for storing this kind of information).

Now when a person downloads and installs a package the database of installed software is updated to store information on the files installed, much like the box package manager does. In addition, for each file belonging to a package and written to the file system there are a set of mandatory file attributes that every package has to store on installation. This is not something that a bundle/package creator has to worry about, it is handled completely transparently by the package manager that writes the attributes to the fs.

For an example every file belonging to a package that that gets installed via the package manager would have mandatory attributes such as Package ( this file belongs to this package ), version and a hash sum. Other mandatory attributes could be added, the aforementioned are just examples.

This approach has some advantages. For example if you are browsing a file system and wonder what some file is or what package it belongs to or just about any information that is present in the form of mandatory attributes, you can just issue a simple "lsattr file.so" command to see all available information. This could also prove to be a powerful feature when using the "query" command. You don't necessarily need separate tools to find information on Packages/Files. Instead you are essentially just using the advanced features that the haikufs has. In other words Programs are not just a collection of zipped files you unpack under your home directory and forget. They become part of the file system and OS. You can install software under a common folder that is available to everyone using the system or users belonging to some user group or just you. The person installing the software can decide as far as his/hers privileges on the system allow. The point of this idea is "coherency".

Another thing is that if the package database gets accidentally wiped or corrupt or a file gets accidentally deleted, you can still have a working system but you don't have any means to uninstall software or know what is installed on your system.
a package recovery tool that scans the whole file system looking for files and checking their attributes can rebuild the database from scratch and "restore" your system to a working state. The hash sum is something that I'm not sure whether it's needed. It could be used in cases like file corruption and virus infections (though a virus can easily bypass this).

For system updates IMHO multiuser capabilities with access permissions would be needed. The package manager in charge of installing .pkg "bundles" would not have access to files belonging to the System/Core package. This just to ensure that a badly created / malicious package wouldn't overwrite important system files.
The system "updater" responsible for updating and extending the core functionality of the OS would instead run with full administrator rights.

For Packages that want to update themselves (and I personally prefer this method having used both windows and various linux distributions and like the simplicity of just having a "Remove Program" option instead of a centralized solution) there might be a need for an API for the package manager to handle these cases so that all file attributes (hashes, versions, all additional attributes) are updated to the filesystem and database accordingly. a Package can of course bypass this but I would consider that "lazy programming".

2/7 GSOC Reports. What was accomplished?

Forum thread started by kvdman on Fri, 2010-09-03 00:23

GSOC for Haiku ended Aug. 16th. In two and a half weeks I've seen only two reports by students summarizing their work.

Haiku Inc. please ask the other students to post their results.

In general I think Haiku should ask a little more of the students. Like posting bi-weekly mandatory summaries of what they've accomplished, to make sure they don't fall behind.

Deskbar Should Autorestart On Crash

Forum thread started by Luiji on Thu, 2010-09-02 16:55

The Deskbar application is vital to the usage of Haiku. Without it, it is almost impossible to do anything. When it randomly crashes (as it did for me), one must search the filesystem for the application to restart it (for those who do not know, /boot/system/Deskbar). Haiku should detect when it crashes and automatically restart it.

P.S. New to Haiku. It is pretty awesome. Keep up the good work.

Integrated digital distribution platform+"package manager"

Forum thread started by Beefeater on Mon, 2010-08-30 18:19

ATTENTION ADMINS: Thanks for restoring this thread! (This post was stuck in a spam check for a day or two) However, I think it's the old version of my post which I accidentally saved before finishing. Can an admin please change the content of the OP to the finished version which I also reported?

One good way to attract commercial developers to Haiku in the future would be to take some effort off their shoulders for distributing their apps in a simple, user friendly marketplace. My idea is to have an open sourced digital distribution platform, free from middle men. Think of a package manager, mixed with a commercial service like Steam, with optional (to the user) torrent functionality.

The idea is that all Haiku apps (commercial, freeware, closed source, open source) are made available in this app manager. Commercial apps would be paid for directly to the developer, and the developer is responsible for hosting.

The developers (well, anyone really, if the license allows anyone to redistribute) would serve as the dedicated host (forgot the word for this in torrent terminology, trackers right?) of the files, with users being able to speed up the process with P2P networking (it should be optional, people should be able to use dedicated hosts only and not seed if they so wish). They would need to specify a category for their "package" (Office, Web, Games, Media...), so it can be easily sorted and found by end users.

I'm not confident that it's possible, but instead of the division that comes with repositories, this imaginary platform could use either:
1: A centralized, Haiku Inc. hosted indexer, much like various torrent sites, or
2: A decentralized one (I mention this because it seems Pirate Bay has switched to this method lately, but I may have misunderstood what it means. I'm thinking of an index that's P2P driven somehow)
The index should list categories (as mentioned), a description as supplied by the distributor, and user reviews.

So there would be a base index that all Haiku apps would use and conform to, including unsecure, possibly dangerous, or development build apps. The indexer itself doesn't necessarily have to search the software for viruses or the like, because this is where filter subscriptions would come into the picture. If you've used AdBlock Plus with Firefox, the idea of subscription filters is where I got this idea from. Anyone (everyday users, companies, organizations) will be able to provide filter subscriptions for different purposes (no malware, Company X's apps, trusted apps only, etc). The best filters would gain the largest amount of users, ensuring that only safe software reaches the common user unless he ignores the filters.

Syndicate content