Not logged in. · Lost password · Register
Page:  1  2  3  next 

All posts by Tom W.M. (40)

topic: AjaxAmp  in the forum: Skins
Avatar
Tom W.M. #1
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
The problem is probably the MIME-type. BrowseAmp sends files whose MIME-types are not specified in mime.ini as application/binary. Firefox is (and browsers other than IE are in general) more strict about such things--it may be rejecting it.
I understand what you're saying, but I don't understand why it's a problem for you and not me. I'm using FF 1.5.0.4 on Win2K. You would think I would have had the same problem?

I can't say.  Actually, it wasn't a problem that I had--my mime.ini already had the JavaScript line because it's required for my skin.

The only problem that I've had is that it doesn't like really large (e.g. 2000+ items) playlists--Firefox's "stop this script" warning pops up, and pressing "Stop" doesn't stop it from popping up again! Since you're using innerHTML to update the playlist, I suppose that the issue must be MochiKit.Sortable.
Yeah, I noticed that too. It was a problem I didn't really think was worth going after since my playlists are not usually that long. If you can come up with a fix I'd be happy to update the skin.

I'm not sure that it's really worth fixing.  Any fix that you did do would probably involve basically rewriting MochiKit.Sortable.  You'd have to split up DOM manipulation so that it doesn't cause the "stop the script" error message.  I've done this for my syntax highlighting script, but it freezes up the browser for quite a while as it does it's stuff (e.g., http://freecog.net/scripts/MochiKit.js?pretty).  Since you use innerHTML to recreate the entire list, this would be repeated every time the playlist is updated.  That wouldn't work well from a usability perspective.  What I'd do is add a warning to the button that switches playlist modes--if <#playlist_numtracks> is rather large, ask the user if they really want to switch modes.  Another option might be to disable drag-'n'-drop sorting if <#playlist_numtracks> is too large, using more traditional up/down buttons instead.

Tom
topic: AjaxAmp  in the forum: Skins
Avatar
Tom W.M. #2
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
The problem is probably the MIME-type.  BrowseAmp sends files whose MIME-types are not specified in mime.ini as application/binary.  Firefox is (and browsers other than IE are in general) more strict about such things--it may be rejecting it.  Clearly this is a BrowseAmp problem--there should be a reasonable set of built-in MIME-types, and you shouldn't have to enable processing of a file to make it work.

This is a really slick skin.  It's clean and responsive, with a nice design.  The only problem that I've had is that it doesn't like really large (e.g. 2000+ items) playlists--Firefox's "stop this script" warning pops up, and pressing "Stop" doesn't stop it from popping up again!  Since you're using innerHTML to update the playlist, I suppose that the issue must be MochiKit.Sortable.
topic: AjaxAmp  in the forum: Skins
Avatar
Tom W.M. #3
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Your best bet is to simply upload it to your site (slick design, BTW).  Henry, the BrowseAmp dev, has been only infrequently available for a long while now.  My JSAmp skin was supposed to be added to the skins page long ago....

I'm looking forward to seeing how you dealt with the distinctly non-AJAXy way that BrowseAmp is constructed.  Especially if you have been able to manage client-side playlist sorting.  I couldn't figure out an efficient way short of writing a proxy server in Python that interfaces with the client in a different manner.
topic: updating <#playlist_numtracks> and <#playlist_leng  in the forum: General discussion
Avatar
Tom W.M. #4
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Huh.  Weird bug.  Henry?

Thanks for finding a workaround--this may come in handy later.
topic: updating <#playlist_numtracks> and <#playlist_leng  in the forum: General discussion
Avatar
Tom W.M. #5
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Does a force refresh--Ctrl]-[F5]--make any difference?
topic: BrowseAmp Issues  in the forum: General discussion
Avatar
Tom W.M. #6
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Sorry, no.  My collection is significantly less massive than yours, and I haven't run into the problem.  Henry?
topic: dynamic playlist offset? (are dynamic playlist offsets possible?)  in the forum: General discussion
Avatar
Tom W.M. #7
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Nope.  The only way that I can think of to do this would be to run the request through a proxy script, which would dynamically create the template and then spit it out as BrowseAmp interprets it.  That would be insane.
topic: BrowseAmp Issues  in the forum: General discussion
Avatar
Tom W.M. #8
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
To get the value of <#CurrentTrackFilename>:
var string = unescape("<#CurrentTrackFilename urlencoded=true>");
BrowseAmp lacks a method for real JS-compatible escaping.  I requested it some time ago.

As for externally storing the script, BrowseAmp doesn't parse tags in JavaScript files by default.  Thus, in the previous example, "<#CurrentTrackFilename urlencoded=true>" would not be replaced with the path.  In many other contexts this causes an error.  You can enable parsing of .js files by adding the following line to mime.ini:
js=text/javascript
This post was edited on 2006-06-02, 02:36 by Unknown user.
topic: Announcing JsAmp! (A Winamp look-alike BrowseAmp skin.)  in the forum: Skins
Avatar
Tom W.M. #9
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Pedee,

I have no idea why a Java update would affect JsAmp.  JsAmp makes heavy use of JavaScript, true, but Java and JavaScript are totally unrelated technologies, despite their similar names.
topic: No Logout feature (No Logout feature)  in the forum: General discussion
Avatar
Tom W.M. #10
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
BrowseAmp uses HTTP authentication, which is managed by the browser (it is the browser that prompts you for your password).  I am not sure whether the login can be cleared from the server, but I know that right now (and through the forseeable future) BrowseAmp does not support logging out.
topic: string replace  in the forum: General discussion
Avatar
Tom W.M. #11
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
If WML is XML, you should be able to wrap the song title in a CDATA block, and avoid the whole escaping issue.  E.g.:

<![CDATA[<#MetaData field=title>]]>
Of course, it's not guranteed that the cell phone browser supports CDATA blocks.

I would appreciate more extensive escaping options for BrowseAmp's output.  I would like an XML escape (&, <, >, "), and JavaScript escape (\\, \', \", \/, \b, \f, \n, \r, \t, \x##, \u####, \U########, etc., as specified at JSON.org).

UTF-8 support would be nice, too. (If it's not already there--I can't figure this out.)
This post was edited on 2006-01-10, 00:16 by Unknown user.
topic: Announcing JsAmp! (A Winamp look-alike BrowseAmp skin.)  in the forum: Skins
Avatar
Tom W.M. #12
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Quote by Crazy MC on 2005-11-15, 00:27:
And yes, I copied the new mime.ini... and even restartet winamp.
Er, do you mean that you replaced the old mime.ini?  The new lines are supposed to be added to the current ones, making the entire file something like:
; this File contains the file extensions and their mime type of the files
; that are parsed for BrowseAmp tags.
;
; see http://hostutopia.com/support/s058.html for more MIME Types

[mime]
htm=text/html
html=text/html
xml=text/xml
wml=text/vnd.wap.wml

; JsAmp mime types
css=text/css
js=text/javascript
xhtml=application/xml
svg=application/xml
txt=text/plain
topic: Announcing JsAmp! (A Winamp look-alike BrowseAmp skin.)  in the forum: Skins
Avatar
Tom W.M. #13
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
MC,

It sounds like what's happening is that Firefox is not recognizing the XHTML file as such (presumably it's being sent with a non-XML mime-type), and downloading it to a temporary directory.  From there, it opens it (since it's set as the default opener for .xhtml files).  When it opens it and encounters a BrowseAmp "HTML-tag" it shows an error message, becuase the hash symbols ("#") in the tag means that it's not valid XML.  So, BrowseAmp must not be sending the XHTML file as XML.  Indeed, since the "HTML-tag" has not been replaced, it must not event be parsing it.

So my best guess is that something went wrong when you copied in the stuff from mime.ini.  Would you post your entire mime.ini file?
topic: Announcing JsAmp! (A Winamp look-alike BrowseAmp skin.)  in the forum: Skins
Avatar
Tom W.M. #14
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Okay, it seems to work in Opera 9 Preview (for Windows).  Unfortunately, it's really slow, and there are slight delays where things would be fading in on Firefox (Opera doesn't support the CSS property opacity, or a proprietary equivalent).  For now, I recommend using Firefox 1.5 PR1, as it's blistering fast at this sort of DHTML (even on my less than speedy computer).
topic: Announcing JsAmp! (A Winamp look-alike BrowseAmp skin.)  in the forum: Skins
Avatar
Tom W.M. #15
Member since Feb 2003 · 40 posts · Location: La Crosse, WI, USA
Group memberships: Members
Show profile · Link to this post
Oops!  That's me, above.
Close Smaller – Larger + Reply to this post:
Special characters:
Page:  1  2  3  next 
Special queries
Go to forum
This board is powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2015 by Yves Goergen
Page created in 243.9 ms (162.8 ms) · 125 database queries in 127.9 ms
Current time: 2019-09-21, 23:38:20 (UTC +00:00)