Perhaps making a hash based on app name and version in the appdb, and then have wine reading the hash from the app to check against the appdb.<br><br>If anyone uses Fedora, their ABRT tool generates hashes for different bugs and then searches their bugzilla before submitting the crash dump, to find if a report is already generated. If the report is already in bugz, then it appends to that bug.We could do something similar, but check against the appdb, and notify the user..<br>
<br>Maybe there could be a separate builtin app (like notepad and explorer) to read the appdb and check ratings, and allow access to the appdb without having to fire up the web browser?<br><br clear="all">Thanks<br><br>Tom<br>
<br><br><div class="gmail_quote">On Thu, Sep 9, 2010 at 2:15 PM, Roderick Colenbrander <span dir="ltr"><<a href="mailto:thunderbird2k@gmail.com">thunderbird2k@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, Sep 9, 2010 at 6:12 PM, Damjan Jovanovic <<a href="mailto:damjan.jov@gmail.com">damjan.jov@gmail.com</a>> wrote:<br>
> On Thu, Sep 9, 2010 at 5:47 PM, Austin English <<a href="mailto:austinenglish@gmail.com">austinenglish@gmail.com</a>> wrote:<br>
>> On Thu, Sep 9, 2010 at 8:34 AM, Rosanne DiMesio <<a href="mailto:dimesio@earthlink.net">dimesio@earthlink.net</a>> wrote:<br>
>>> On Thu, 9 Sep 2010 00:59:32 -0700<br>
>>> Dan Kegel <<a href="mailto:dank@kegel.com">dank@kegel.com</a>> wrote:<br>
>>><br>
>>>> Watching Twitter, one fairly frequently seems people trying<br>
>>>> and failing to run iTunes 10 and the like in Wine.<br>
>>>><br>
>>>> Should we let them bash their heads against the wall like that?<br>
>>>><br>
>>>> Maybe we should detect the top ten apps that don't work<br>
>>>> with Wine, and put up a warning dialog saying they are<br>
>>>> known not to work, and people shouldn't try.<br>
>>>> (Kind of like what Windows 7 does when you do something<br>
>>>> dangerous, e.g. try to look at the contents of drive C:.)<br>
>>>><br>
>>>><br>
>>> Do you really want to prevent users from ever testing these apps in new versions of Wine, or trying to find workarounds? I do a fair amount of head-bashing myself, and I would find such a message patronizing and intrusive.<br>
>><br>
>> Agreed. Wine doesn't make efforts to babysit users for most other<br>
>> things, I don't see why this should be any different.<br>
>><br>
>> Also consider that if such a workaround were to go into wine, that<br>
>> code may long outlive the 'affected apps', and the list would quickly<br>
>> grow out of date.<br>
>><br>
>> I suppose if a packager wanted to do something like this for their<br>
>> distro I wouldn't complain too much, unless users started asking about<br>
>> it in #winehq/the forums. But this _should not_ go into vanilla wine.<br>
>><br>
>> --<br>
>> -Austin<br>
>><br>
><br>
> The dialog could suggest upgrading Wine, that would prevent the<br>
> affected app list from getting out of date.<br>
><br>
> Damjan<br>
><br>
><br>
<br>
</div></div>If we would want any application database stuff, perhaps appdb would<br>
be the place to store information like this. There should come some<br>
way to extract this information to an XML file or whatever format<br>
periodically. It could be packaged with a wine build or optionally<br>
downloaded when you run Wine or so.<br>
<font color="#888888"><br>
Roderick<br>
<br>
<br>
</font></blockquote></div><br>