[peeb]

How hard can it be to get this right?

[TETENAL]

Originally Posted by peeb 

How hard can it be to get this right?

Since the widget is JavaScript it comes with the source code. If it's not hard to fix, just do so yourself.

[rickey939]

I simply won't put up with this kind of mediocre programming Apple.

[turtle777]

What's a "programming Apple" ?

-t

[rickey939]

Originally Posted by turtle777 

What's a "programming Apple" ?

-t

Smart fruit.

[turtle777]

Originally Posted by rickey939 

Smart fruit.

I prefer dumb meat. Pork, beef, chicken. Anything.

-t

[peeb]

Originally Posted by TETENAL 

Since the widget is JavaScript it comes with the source code. If it's not hard to fix, just do so yourself.

Are you serious? Even if I wanted to do that, what about every other instance of this widget?

[TETENAL]

Here you go:

Make a copy of the Movies widget into your own ~/Library/Widgets and change line 1201 of ~/Library/Widgets/Movies/Movies.js from

movieObjectForMovieElement.anTheRegex = /^(the|an)\s*(.+)/im;

to

movieObjectForMovieElement.anTheRegex = /^(the |an )\s*(.+)/im;

[ghporter]

It's really just one space that goofs it up? Amazing. That sort of thing is trivial to fix—if you find it and identify that it's a problem. But then, it's trivial for anyone to fix, so until Apple fixes this, why not do it yourself?

One question though: how do you drill down through the widget wrapper to get at the .js file?

[TETENAL]

Originally Posted by ghporter 

One question though: how do you drill down through the widget wrapper to get at the .js file?

"Show package contents" from either the action menu or the contextual menu.

[rickey939]

Neat.

[ghporter]

Uh.....I knew that. We'll go with that instead of a really big "duh!" OK? Thanks!



I actually did know how to do this a while back, but I haven't used it and I forgot. I think that may be worse than just not seeing an option on a context menu...

[turtle777]

Originally Posted by TETENAL 

Here you go:

Make a copy of the Movies widget into your own ~/Library/Widgets and change line 1201 of ~/Library/Widgets/Movies/Movies.js from

movieObjectForMovieElement.anTheRegex = /^(the|an)\s*(.+)/im;

to

movieObjectForMovieElement.anTheRegex = /^(the |an )\s*(.+)/im;

Well, I give you that this is NOT hard to fix once you know what's wrong, and definitely fixable for a programmer, so shame on Apple.

But when you said "If it's not hard to fix, just do so yourself.", did you really think users here would be able to track down the error and fix it themselves ?
I kind a feel stupid now.

-t

[TETENAL]

OK, I read up how regular expressions actually work, and I think the actual fix for this issue should be: change line 1201 of Movies.js from

movieObjectForMovieElement.anTheRegex = /^(the|an)\s*(.+)/im;

to

movieObjectForMovieElement.anTheRegex = /^(the|an)\s+(.+)/im;

It seems to be a simple mistake. It probably just hasn't been reported to Apple yet.

[turtle777]

Could you please highlight the change. I, uhm, don't see it

Edit: Ok, got it. s+ instead of s*.

-t

[peeb]

Thanks for figuring out how to fix that - really useful.