Welcome, Guest! Log In | Create Account

 
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Popular ideas Here are random ideas about Zero Install.

Dependency hell  
Written by morswin55-11 the 15 Sep 09 at 10:34. New
Actually 0 install have 2 bugs:
- Download too more dependency, so our hard drive space will shrink very speed(like in Windows)
- Don't support system packaging system
0
votes
up equal down
Solution #1: Use PackageKit when it possible
Written by morswin55-11 the 15 Sep 09 at 10:34.
PackageKit introduce common naming scheme, so ex. Wesnoth will have the same name in each distribution on PackageKit. 0 install should first look for dependency in PackageKit. If PackageKit couldn't satisfy our package, we will install it by 0 install. Also, if user don't prompt root password, we will install dependency by 0 install.

Add a comment or propose a solution >>

Make it easier to package legacy programs  
Written by tal197 the 31 May 09 at 19:13. New
Some programs (mainly GNOME apps) hard-code pathnames such as /usr/share/myprog. These programs don't currently work with Zero Install.
1
votes
up equal down
Solution #1: Add hacks to support them
Written by tal197 the 31 May 09 at 19:13.
Use file-system manipulation (plash, plasticfs, etc) or rewriting (see Mark's patch series) to support these programs, even if it makes 0launch a bit hacky.

Add a comment or propose a solution >>

Support Windows  
Written by tal197 the 31 May 09 at 19:16. New
Zero Install doesn't work well on Windows, due to its lack of support for common POSIX features.
1
votes
up equal down
Solution #1: Create a working Windows version
Written by tal197 the 31 May 09 at 19:16.
Find someone who knows how to use Windows and persuade them to port it. Make a .msi or setup.exe to install it.
1
votes
up equal down
Solution #2: box on website, donationcoder, stackoverflow
Written by insert_nick the 31 May 09 at 20:18.
On the zero-install website, there should be a box or something (always visible, e.g. in template): "Windows developer? Do you think you are able to port this thing on Windows?".

Posting the request on donationcoder.com forum could be a way towards finding someone: there are a lot of nice and capable windows coders reading there.

Maybe starting asking some little specific questions on stackoverflow.com could also help.

Add a comment or propose a solution >>

Support deltas  
Written by tal197 the 19 Jul 09 at 16:03. New
Instead of downloading a complete new version, users who already have the previous version should be able to download a small delta (automatically).
0
votes
up equal down
Solution #1: Courgette
Written by tal197 the 19 Jul 09 at 16:03.
There are various systems around for this. Google has just announced an interesting one:

http://dev.chromium.org/developers/design-documents/software-updates-courgette

Add a comment or propose a solution >>

Zero-install is not known/used by developers, so few apps ready, so few users of  
Written by insert_nick the 2 Jun 09 at 13:43. New
There are some problems blocking spread of zero-install, given its great potential: not so much software ready to be used with the system, not so many developers caring, not so many developers knowing it, etc. Instead, we should find a way to avoid begging developers to make their packages available with zero-install.
0
votes
up equal down
Solution #1: 0launch should become the very center of daily PC action for users
Written by insert_nick the 2 Jun 09 at 13:43.
I propose to use the solution proposed in the following message (read also the other message linked inside of it):

http://www.nabble.com/Publicity-for-Zero-Install-tp23685741p23792558.html
0
votes
up equal down
Solution #2: Make a pimped version of 0launch with a lot more functionality
Written by insert_nick the 2 Jun 09 at 17:38.
Make a pimped version of 0launch:

- synched with a user-contributed (with user registration) web service where everyone can put a link to a linux software, and add entries associated with it, each entry answering to the question "what can you do with it?"; and AT LEAST a search engine looking through these entries, into software description, and into software name; the desktop version of 0launch should have the same stuff of the web service, i.e. a data grid and a search engine - you find the app, and play it. The service should aim to collect links to MOST OF THE EXISTING LINUX SOFTWARE AROUND (by a collaborative approach) - it doesn't matter if it works or not with zero-install; there should be also a nice query input box asking "what do you want to do?" (and it searches through those entries...)

- if you click an app that is not flagged by many users as a working zero-install feed, 0launch should say that it can try to run it but it's not sure it will succeed; if user answer is "ok, try please" some sort of deb2zero execution is triggered, and the software (eventually) runs locally; when it's closed, 0launch asks to the user if it seemed ok, asking to choose one option from a list (e.g. extensively tested, tested a little, etc.) and an option from another list (e.g.: works perfect, works almost perfect, useable but some problems, etc.); if the answers are overall nice, 0launch asks to the user if it can upload it on the remote server, and thank you;

- user can light stars and hearts for apps from 0launch itself (rate, put among personal favourites, etc.)

Add a comment or propose a solution >>

Provide more help to the user to evaluate trust  
Written by tal197 the 31 May 09 at 19:07. New
When asking for approval of a new key, 0launch currently displays:

- Other keys trusted for this site
- The key fingerprint
- Other sites for which the key is trusted
- A hint from the built-in database of known keys

The more information we can provide to help the user decide whether to trust the key, the better.
1
votes
up equal down
Solution #1: tell the user if the author is trusted by Debian, etc
Written by tal197 the 31 May 09 at 19:07.
The Debian keyring contains the GPG keys of all Debian developers (people authorised to update official Debian packages). We should check whether the key is one of these people and inform the user if so.

We should also use the Ubuntu, Fedora, etc keyrings in a similar way.

Finally, we could (perhaps) treat all of these keys as trusted for the purpose of identifying other keys. e.g. if the author isn't a Debian developer, but the author's key is signed by someone who is, mention that.

See the 1 comments or propose a solution >>

Syndicate content