[haiku-development] Re: QT and SDL GCC4 libs and Haik compatible Logo program

  • From: Stephan Assmus <superstippi@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Thu, 02 Jun 2011 21:55:06 +0200

Am 02.06.2011 21:28, schrieb SMC.Collins:
From: Rene Gollent <anevilyak@xxxxxxxxx>
 On Thu, Jun 2, 2011 at 3:09 PM, SMC.Collins wrote:
 > I am linking this picture from my test system. its a link not a
 > attachment. something must be done here.
 >
 >
 > http://www.filedump.net/dumped/screenshot21307041690.png
 >

Short of moving to an iOS-style walled garden, there's very little
that can be done about that. If someone's not motivated enough to do
more than a half-assed port involving as little beyond (./configure ;
make ) as possible, then the prospect of getting a logo for fixing it
isn't likely to motivate them to do it right.

Well, was there any guidlines before to prevent the situation ? In much
the same way you enforce a very nice coding style, is it not simple to
just enforce a few basic tennents and rewards for doing so with the
applications?

Let the users pressure the 3rd party people, but give them a barging chip.

I understand the problem. What you want is some way to tell the good from the bad applications before you download them on Haikuware. There are various ways to provide a solution to this problem. You believe that the Haiku Project setting out guidelines and stamp apps with a logo is going to be the solution. However, that will not work. 1) For any developer who cares how to write a proper Haiku application or do a proper port, it is easy to know what is expected. I mean it is easy to know where files should go and what is expected in terms of integration. I don't think another document is needed. 2) About the logo... it is simply impossible for the project to do this work.

There is an easy solution which scales to any size of a software pool: Users themselves rating, commenting and reviewing the apps. For this to work, there needs to be an easy and accessible way for users to do just that. IMHO it should be integrated with the eventual package management and installation solution. When searching for apps, users should automatically find the good ones first. Unfortunately, I don't have time to help implement this, and I certainly don't want to spend time on anything which IMHO will not be a true solution to the problem, like a logo program.

Best regards,
-Stephan

Other related posts: