leeoniya

Hi, When I run "Check all for updates only, do not download", Ketarin seems to update the DB to the retrieved version, so a subsequent update does not detect that the current version is outdated. thanks!

yep, D/L broken

Latest Scintilla dll can be found inside scite228.zip here http://sourceforge.net/projects/scintilla/files/SciTE/ v2.28 seems to work fine. System.Data.SQLite.DLL is here http://sourceforge.net/projects/sqlite-dotnet2/files/SQLite%20for%20ADO.NET%202.0/ 1.0.66.0 breaks Ketarin 1.6.1.434 FYI

hello, is it possible to choose a custom app icon? i have a lot of portable apps that are in .7z files and all appear as archives. would be pretty slick if you can choose custom icons (like Portable Start Menu). thanks, leon

thanks, i set 'build' to be used for change detection but it didn't seem to work. i have 2 apps, chromium canary and heidisql. when i press update all, the versions for everything get retrieved fine and the columns get updated. the chromium download begins, and the heidi download just sits with a fully green (100%) progress bar (without any % indicator) and after chrome finishes downloading and installing, the bar goes away and everything gets marked as up to date, but no download of heidi actually occurs. i'm gonna try it with another build and if that doesnt work, then just say screw it and use the full constructed latest build url from the download page parsing. still it seems like the sitting progress bar while chrome downloads is a bug of some sort.

hi peeps, often i have to force-download HeidiSQL after it fails to get the exe file from the following url: http://www.heidisql.com/latest_build.php any ideas why? i have a {ver} and {build} variables set up for "Version" and "Build" display columns that get retrieved correctly from here: http://code.google.com/feeds/p/heidisql/svnchanges/basic http://www.heidisql.com/download.php i guess the alternative would be to grab the full url of the build from that download.php page: http://www.heidisql.com/builds/heidisql.r3834.exe just wondering why latest_build.php often fails to detect changes? thanks, leon

first, I LOVE POSTS LIKE THIS! second, "doesn't work as expected"? it works as documented. RTFM, sir - http://wiki.ketarin.org/index.php/Ketarin_Wiki finally, thank you for your insightful input and through review. come again!

it was great having you here, good luck with everything!

i wouldn't consider program icons "clutter". it would still be distinct, because there would be a dedicated column which would work exactly the same way as it does now. however, there would be a lot of additional benefit to retaining program icons and splitting off the update status column. conserving 16px of horizontal space can be done in numerous other ways, such as displaying a percentage instead of progress bar, i feel like there's too much benefit that can be attained through dividing the functionally different visuals.

i dont think the program icons should be replaced at all, the indicator needs to be split off entirely in my opinion, keeping it both distinct and separate.

breaking out the update indicator into a different column would allow you to sort/group all apps that need to be updated together which is very handy if you have a large list of apps for which you run "check updates only". alternitively it would be okay to optionally auto-filter out packages that dont need updates after the check-only, this may be a good compromise. another reason to break out the indicator is if the package has an associated icon that is displayed with it already, it would make sense for it to always be displayed to visually locate packages quickly. i dont understand why the update indicator replaces the package icon, it kind of defeats the purpose of having the icon there to begin with if it cant be counted on to be seen all the time. the last idea can give you an indication of how big the version jump will be between updates. perhaps you only want to run minor updates rather than major, as it may break APIs, license key files and such. having a version-to-be-updated-to column, as well as current version column, can give a user indication of whether or not s/he wants to run the update manually or not. i think an "update available" status indicator should not be the same as "updated" indicator. i guess some of the suggestions are more of a workflow preference, but it would be nice to have more manual control over the process for the reasons indicated.

currently, if you do "Only check for updates" and then try to update only some packages manually, the update indicator icons all reset as soon as any update is initiated. it would be more useful for them to remain because you may choose to update one package at a time without losing the ability to see what still needs to be updated. i'm still going say that the update indicators should NOT replace the icons, but should be broken out into their own sortable column. and perhaps make a different color indicator (light blue?) for showing an update is available, rather than reusing the "updated" icon for this. it would also be cool if the available update version (eg {ver}) was broken out into a different column. with these in place, 1.0 time! very excite! Leon

heidisql still broken : ( http://forum.cdburnerxp.se/viewtopic.php?f=2&t=6518&st=0&sk=t&sd=a&start=75#p24341 also XPredit not working: http://xpredit.pcbox.gr/dload.php?action=download&file_id=1 nice to see a "was updated" indicator finally land any chance of a last downloaded/current version column from a reserved user var? thx.