Comments for stever.org.uk http://stever.org.uk Thu, 14 Jul 2011 01:19:47 +0100 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Windar 0.2.6 by allen http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-243 allen Thu, 14 Jul 2011 01:19:47 +0000 http://stever.org.uk/?p=26554#comment-243 hmm, hadn't heard of coffeescript but looks interesting after some light googling/reading. hmm, hadn’t heard of coffeescript but looks interesting after some light googling/reading.

]]> Comment on Windar 0.2.6 by stever http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-242 stever Wed, 13 Jul 2011 20:52:02 +0000 http://stever.org.uk/?p=26554#comment-242 Looking into it a bit further, there's HTML5 Web Workers, which think I remember reading about now. <blockquote>If your browser supports the Web Worker API, there will be a Worker property on the global window object. If your browser doesn’t support the Web Worker API, the Worker property will be undefined.</blockquote> Detecting HTML5 Features | diveintohtml5.org/detect.html Looking into it a bit further, there’s HTML5 Web Workers, which think I remember reading about now.

If your browser supports the Web Worker API, there will be a Worker property on the global window object. If your browser doesn’t support the Web Worker API, the Worker property will be undefined.

Detecting HTML5 Features | diveintohtml5.org/detect.html

]]> Comment on Windar 0.2.6 by stever http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-241 stever Wed, 13 Jul 2011 20:39:27 +0000 http://stever.org.uk/?p=26554#comment-241 Of course, since Javascript doesn't support multi-threading, it certainly couldn't work the same. Of course, since Javascript doesn’t support multi-threading, it certainly couldn’t work the same.

]]> Comment on Windar 0.2.6 by stever http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-240 stever Wed, 13 Jul 2011 19:50:46 +0000 http://stever.org.uk/?p=26554#comment-240 Personally, while Javascript is not something I'm particularly keen on, I now recognise that having a Playdar in Javascript would be very useful. Being able to produce resolvers in Javascript this way would likely be future-proof, assuming that Playdar in Javascript was available some time. I think someone would be likely to do it, if not me then someone else. I am thinking about it. I almost gave up a domain, jaydar.org and now wondering about using it for an open-source effort along these lines. I'm considering Coffeescript. Have you seen it? I would expect that resolvers could be done in Coffeescript. Personally, while Javascript is not something I’m particularly keen on, I now recognise that having a Playdar in Javascript would be very useful. Being able to produce resolvers in Javascript this way would likely be future-proof, assuming that Playdar in Javascript was available some time. I think someone would be likely to do it, if not me then someone else. I am thinking about it. I almost gave up a domain, jaydar.org and now wondering about using it for an open-source effort along these lines.

I’m considering Coffeescript. Have you seen it?

I would expect that resolvers could be done in Coffeescript.

]]> Comment on Windar 0.2.6 by allen http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-239 allen Wed, 13 Jul 2011 19:43:39 +0000 http://stever.org.uk/?p=26554#comment-239 cool, i'll check out playnode -- i was thinking of porting some existing python resolvers in the playdar source to exe's (i.e. youtube) over to windar, but playnode or tomahawk's js analogs of the rb/py files may seem to be the more efficient route. right now, i'm just looking for a quick-and-dirty way to get the resolvers functioning to perform some search query/results analysis. cool, i’ll check out playnode — i was thinking of porting some existing python resolvers in the playdar source to exe’s (i.e. youtube) over to windar, but playnode or tomahawk’s js analogs of the rb/py files may seem to be the more efficient route. right now, i’m just looking for a quick-and-dirty way to get the resolvers functioning to perform some search query/results analysis.

]]> Comment on Windar 0.2.6 by stever http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-237 stever Wed, 13 Jul 2011 07:58:57 +0000 http://stever.org.uk/?p=26554#comment-237 Hi Allen. Good that you got it sorted. I am surprised that the script resolver list would fail if one of the resolvers wasn't loading. I had believed that this would work regardless of those resolvers being there. I don't write a configuration depending on the resolvers selected, so pretty much depend on that assumption currently. I thought that worked, and I'll have another look some time. Playnode Core is my own implementation of Playdar and designed to replace Windar on Windows. It improves on Windar. I've adopted Scala as a programming language and I'm more interested in maintaining that just now. It may not be well tested yet either, but it does support a LAN resolver, which I couldn't get to work on Erlang on Windows (and it resolves against Playdar on other platforms), and resolvers in Javascript that you can find in the Tomahawk project. While I'm not involved in the Tomahawk project right now, I recommend it also. Hi Allen. Good that you got it sorted. I am surprised that the script resolver list would fail if one of the resolvers wasn’t loading. I had believed that this would work regardless of those resolvers being there. I don’t write a configuration depending on the resolvers selected, so pretty much depend on that assumption currently. I thought that worked, and I’ll have another look some time.

Playnode Core is my own implementation of Playdar and designed to replace Windar on Windows. It improves on Windar. I’ve adopted Scala as a programming language and I’m more interested in maintaining that just now. It may not be well tested yet either, but it does support a LAN resolver, which I couldn’t get to work on Erlang on Windows (and it resolves against Playdar on other platforms), and resolvers in Javascript that you can find in the Tomahawk project. While I’m not involved in the Tomahawk project right now, I recommend it also.

]]> Comment on Windar 0.2.6 by allen http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-236 allen Wed, 13 Jul 2011 02:46:30 +0000 http://stever.org.uk/?p=26554#comment-236 thanks for the pointers steve. i think i figured it out. i did an un-install, confirmed all the old data under "program files" as well as "appdata" was purged and went for a fresh install. following the fresh install, the resolvers still weren't loading but at least going through the logs showed that windar was now at least logging and attempting to load these resolvers. i noticed in the windar.log.# files (which i didn't check previously since i didn't know they existed under appdata) as well as playdar.config that spotify was still in the list of resolvers and the log indicated that spotify was crashing -- that got me thinking whether this crash could possibly bring down the entire process to load _any_ of the specified resolvers. i commented out the spotify line in both config files (under program files and appdata since i wasn't sure which one windar was reading) and voila, the resolvers loaded! success :) thanks for the pointers steve. i think i figured it out.

i did an un-install, confirmed all the old data under “program files” as well as “appdata” was purged and went for a fresh install. following the fresh install, the resolvers still weren’t loading but at least going through the logs showed that windar was now at least logging and attempting to load these resolvers.

i noticed in the windar.log.# files (which i didn’t check previously since i didn’t know they existed under appdata) as well as playdar.config that spotify was still in the list of resolvers and the log indicated that spotify was crashing — that got me thinking whether this crash could possibly bring down the entire process to load _any_ of the specified resolvers. i commented out the spotify line in both config files (under program files and appdata since i wasn’t sure which one windar was reading) and voila, the resolvers loaded! success :)

]]> Comment on Windar 0.2.6 by stever http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-234 stever Tue, 12 Jul 2011 07:46:23 +0000 http://stever.org.uk/?p=26554#comment-234 Initial thoughts are that the old application data wasn't removed, which the installer provides an option for now. You could try uninstalling, and selecting the option to remove user data, and then re-install. I don't think it is writing the Spotify resolver into the configuration file anymore, though I could have left that in. I did change the application folder name a few times too, so you could check that you are looking at the config file used. These were all stored under "%APPDATA%" and folder names that are either Windar or appended with a number such as Windar2, Windar3. You could make sure these are removed before doing a fresh install. Hopefully a fresh install just works as intended. Initial thoughts are that the old application data wasn’t removed, which the installer provides an option for now. You could try uninstalling, and selecting the option to remove user data, and then re-install. I don’t think it is writing the Spotify resolver into the configuration file anymore, though I could have left that in.

I did change the application folder name a few times too, so you could check that you are looking at the config file used. These were all stored under “%APPDATA%” and folder names that are either Windar or appended with a number such as Windar2, Windar3. You could make sure these are removed before doing a fresh install. Hopefully a fresh install just works as intended.

]]> Comment on Windar 0.2.6 by allen http://stever.org.uk/2011/04/03/windar-0-2-6/comment-page-1/#comment-233 allen Tue, 12 Jul 2011 01:16:12 +0000 http://stever.org.uk/?p=26554#comment-233 hey steve -- just downloaded the new windar in hopes of playing with the content resolvers. during install, i specified to include all available resolvers but when i view the "playdar core" section, it only lists 4 resolvers (library_dets, magnatune_resolver, jamendo_resolver, and aolmusic_resolver). however, when i view playdar.conf, i see addt'l resolvers being specified but they are not being loaded (or being shown in the "playdar core" view): {scripts,[ "../SpotifyResolver.exe", "py2exe/audiofarm_resolver.exe", "py2exe/echonest-resolver.exe", "py2exe/mp3tunes-resolver.exe", "py2exe/napster_resolver.exe" ]}. the windar log does not show that these resolvers are even being attempted to load. (also, while playdar.config is under the "etc" dir, should the paths to the py2exe resolvers be relative to the where config file is, i.e. "../py2exe/xxx" or the parent "playdar" dir? either way, it doesn't seem like the config file is influencing the load so the log does not seem to indicated it is even failing silently). any ideas? thanx in advance. hey steve — just downloaded the new windar in hopes of playing with the content resolvers. during install, i specified to include all available resolvers but when i view the “playdar core” section, it only lists 4 resolvers (library_dets, magnatune_resolver, jamendo_resolver, and aolmusic_resolver).

however, when i view playdar.conf, i see addt’l resolvers being specified but they are not being loaded (or being shown in the “playdar core” view):
{scripts,[
"../SpotifyResolver.exe",
"py2exe/audiofarm_resolver.exe",
"py2exe/echonest-resolver.exe",
"py2exe/mp3tunes-resolver.exe",
"py2exe/napster_resolver.exe"
]}.

the windar log does not show that these resolvers are even being attempted to load. (also, while playdar.config is under the “etc” dir, should the paths to the py2exe resolvers be relative to the where config file is, i.e. “../py2exe/xxx” or the parent “playdar” dir? either way, it doesn’t seem like the config file is influencing the load so the log does not seem to indicated it is even failing silently).

any ideas? thanx in advance.

]]> Comment on Windar 0.1.2 by zprocket http://stever.org.uk/2009/12/20/windar-0-1-2/comment-page-1/#comment-69 zprocket Fri, 01 Jan 2010 14:30:50 +0000 http://stever.org.uk/?p=92#comment-69 It "just works" on Playlick. I did see a couple failed to scrobble messages in the log, I'm sure b/c of the unfinished erlscrobbler lib, but all in all this is great. Looking forward to GUI in next release. Thank you ;-) It “just works” on Playlick. I did see a couple failed to scrobble messages in the log, I’m sure b/c of the unfinished erlscrobbler lib, but all in all this is great. Looking forward to GUI in next release. Thank you ;-)

]]>