|
This is my first attempt at writing a firefox extension. It will allow looking
up information about sets mentioned in posts on various LEGO sites. See
screenshots, examples and install it from here:
http://www.peeron.com/inv/Firefox_Extensions
I hope this might be useful!
Dan
FUT lugnet.off-topic.geek
|
|
|
In lugnet.announce.peeron, Dan Boger wrote:
> This is my first attempt at writing a firefox extension. It will allow looking
> up information about sets mentioned in posts on various LEGO sites. See
> screenshots, examples and install it from here:
>
> http://www.peeron.com/inv/Firefox_Extensions
>
> I hope this might be useful!
>
> Dan
>
> FUT lugnet.off-topic.geek
WOW! works fine, but you should add a note telling that firefox could block the
installation of add-ons based on your settings. at least I had to allow the
installation and had to add peeron to the list of harmless sites.
w.
|
|
|
In lugnet.announce.peeron, Dan Boger wrote:
> This is my first attempt at writing a firefox extension. It will allow looking
> up information about sets mentioned in posts on various LEGO sites. See
> screenshots, examples and install it from here:
>
> http://www.peeron.com/inv/Firefox_Extensions
>
> I hope this might be useful!
Hi Dan, I have 2 questions:
1. It doesn't seem to work for all pages, see
http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why that may be?
2. Is it possible to put the counter on the status bar instead of over the page
corner? If the page is not scrollable it can obscure text on the page, and even
if it is scrollable, it's a pain to have to scroll to read something.
ROSCO
|
|
|
In lugnet.off-topic.geek, Ross Crawford wrote:
> In lugnet.announce.peeron, Dan Boger wrote:
> > This is my first attempt at writing a firefox extension. It will allow looking
> > up information about sets mentioned in posts on various LEGO sites. See
> > screenshots, examples and install it from here:
> >
> > http://www.peeron.com/inv/Firefox_Extensions
> >
> > I hope this might be useful!
>
> Hi Dan, I have 2 questions:
>
> 1. It doesn't seem to work for all pages, see
> http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why that may be?
> 2. Is it possible to put the counter on the status bar instead of over the page
> corner? If the page is not scrollable it can obscure text on the page, and even
> if it is scrollable, it's a pain to have to scroll to read something.
3. If the link is near the right side of the page, clicking the kitty extends
the page to the right, often introducing a horizontal scrollbar. But closing the
info window does not reset the page width. Is it possible to right-align the
info window rather than increasing the page width?
ROSCO
|
|
|
On Mon, Oct 16, 2006 at 10:28:53PM +0000, Ross Crawford wrote:
> 1. It doesn't seem to work for all pages, see
> http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why
> that may be?
Simple - it's only set up to run on certain sites... I'll add yours to
the list though.
> 2. Is it possible to put the counter on the status bar instead of over
> the page corner? If the page is not scrollable it can obscure text on
> the page, and even if it is scrollable, it's a pain to have to scroll
> to read something.
I'll look into that - if I can figure out how to do it, sure :)
> 3. If the link is near the right side of the page, clicking the kitty
> extends the page to the right, often introducing a horizontal
> scrollbar. But closing the info window does not reset the page width.
> Is it possible to right-align the info window rather than increasing
> the page width?
I noticed that - if you could help me figure out the CSS for the
peeron_popup, I'd be happy to update it. I'm still trying to figure out
all this JS/CSS stuff :)
--
Dan Boger
dan@peeron.com
|
|
|
On Mon, Oct 16, 2006 at 08:57:08PM +0000, Willy Tschager wrote:
> WOW! works fine, but you should add a note telling that firefox could
> block the installation of add-ons based on your settings. at least I
> had to allow the installation and had to add peeron to the list of
> harmless sites.
Updated.
--
Dan Boger
dan@peeron.com
|
|
|
In lugnet.off-topic.geek, Dan Boger wrote:
> On Mon, Oct 16, 2006 at 10:28:53PM +0000, Ross Crawford wrote:
> > 1. It doesn't seem to work for all pages, see
> > http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why
> > that may be?
>
> Simple - it's only set up to run on certain sites... I'll add yours to
> the list though.
>
> > 2. Is it possible to put the counter on the status bar instead of over
> > the page corner? If the page is not scrollable it can obscure text on
> > the page, and even if it is scrollable, it's a pain to have to scroll
> > to read something.
>
> I'll look into that - if I can figure out how to do it, sure :)
>
> > 3. If the link is near the right side of the page, clicking the kitty
> > extends the page to the right, often introducing a horizontal
> > scrollbar. But closing the info window does not reset the page width.
> > Is it possible to right-align the info window rather than increasing
> > the page width?
>
> I noticed that - if you could help me figure out the CSS for the
> peeron_popup, I'd be happy to update it. I'm still trying to figure out
> all this JS/CSS stuff :)
Well I'm no expert either, but there seem to be right and left CSS properties
that may be able to do it. I haven't really played with CSS much though, Tim G
would be the guy to ask.
ROSCO
|
|
|
In lugnet.off-topic.geek, Ross Crawford wrote:
> In lugnet.off-topic.geek, Dan Boger wrote:
> > On Mon, Oct 16, 2006 at 10:28:53PM +0000, Ross Crawford wrote:
> > > 1. It doesn't seem to work for all pages, see
> > > http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why
> > > that may be?
> >
> > Simple - it's only set up to run on certain sites... I'll add yours to
> > the list though.
> >
> > > 2. Is it possible to put the counter on the status bar instead of over
> > > the page corner? If the page is not scrollable it can obscure text on
> > > the page, and even if it is scrollable, it's a pain to have to scroll
> > > to read something.
> >
> > I'll look into that - if I can figure out how to do it, sure :)
> >
> > > 3. If the link is near the right side of the page, clicking the kitty
> > > extends the page to the right, often introducing a horizontal
> > > scrollbar. But closing the info window does not reset the page width.
> > > Is it possible to right-align the info window rather than increasing
> > > the page width?
> >
> > I noticed that - if you could help me figure out the CSS for the
> > peeron_popup, I'd be happy to update it. I'm still trying to figure out
> > all this JS/CSS stuff :)
>
> Well I'm no expert either, but there seem to be right and left CSS properties
> that may be able to do it. I haven't really played with CSS much though, Tim G
> would be the guy to ask.
>
> ROSCO
Well I was trying to do this and discovered a fairly major bug in the extension.
When trying to edit a post on jlug (phpBB) which contained a set number it found
the set number and promptly blanked the entire text edit box.
Tim
|
|
|
On Tue, Oct 17, 2006 at 01:24:31AM +0000, Tim Gould wrote:
> Well I was trying to do this and discovered a fairly major bug in the
> extension. When trying to edit a post on jlug (phpBB) which contained
> a set number it found the set number and promptly blanked the entire
> text edit box.
Whoa! I'll take a look at that tomorrow morning. Probably could just
add "textarea" to the tags to be left alone.
--
Dan Boger
dan@peeron.com
|
|
|
In lugnet.announce.peeron, Dan Boger wrote:
> This is my first attempt at writing a firefox extension. It will allow looking
> up information about sets mentioned in posts on various LEGO sites. See
> screenshots, examples and install it from here:
>
> http://www.peeron.com/inv/Firefox_Extensions
>
> I hope this might be useful!
>
> Dan
>
> FUT lugnet.off-topic.geek
G'day,
Probably just me being difficult, but would it be possibe to:
1) have the window close when the mouse leaves it, instead of relying on
clicking the 'X'
2) Have a seperate link in the info area for the inventory and instructions, so
that if someone on limited bandwidth or "pay per download" wanted to look at the
instructions, they weren't forced to look at the inventory page first.
Additionally, this would help people see what instructions are currently
available.
Anyway, that's just my thoughts...and me being difficult :)
Benjamin Whytcross
|
|
|
On Tue, Oct 17, 2006 at 09:07:22AM +0000, Benjamin Whytcross wrote:
> Probably just me being difficult, but would it be possibe to:
>
> 1) have the window close when the mouse leaves it, instead of relying
> on clicking the 'X'
That was my original plan - however I found that it actually is somewhat
annoying, because too often the window would close by mistake. Also, by
leaving it open, it allows comparing multiple sets (popups) at the same
time.
Maybe once I add some preferences, I could allow changing that behaviour
per user.
> 2) Have a seperate link in the info area for the inventory and
> instructions, so that if someone on limited bandwidth or "pay per
> download" wanted to look at the instructions, they weren't forced to
> look at the inventory page first. Additionally, this would help
> people see what instructions are currently available.
Yes, I actually do plan on doing something very similar to that.
> Anyway, that's just my thoughts...and me being difficult :)
Not at all! I appriciate the suggestions :)
--
Dan Boger
dan@peeron.com
|
|
|
In lugnet.off-topic.geek, Timothy Gould wrote:
|
Well I was trying to do this and discovered a fairly major bug in the
extension. When trying to edit a post on jlug (phpBB) which contained a set
number it found the set number and promptly blanked the entire text edit box.
|
For some people, this would be considered a positive function of that
extension ;-)
|
|
|
In lugnet.off-topic.geek, Dan Boger wrote:
> On Mon, Oct 16, 2006 at 10:28:53PM +0000, Ross Crawford wrote:
> > 1. It doesn't seem to work for all pages, see
> > http://www.br-eng.info/words/?page_id=29&ins_qry=4884 any idea why
> > that may be?
>
> Simple - it's only set up to run on certain sites... I'll add yours to
> the list though.
Hmmmm, Google ads. Check out the above page now that the extension has been
available, especially the bottom left corner of the ad box. Weird.
ROSCO
|
|
|
On Tue, Oct 17, 2006 at 07:58:00PM +0000, Ross Crawford wrote:
> Hmmmm, Google ads. Check out the above page now that the extension has
> been available, especially the bottom left corner of the ad box.
> Weird.
Interesting. I guess the browser treats the iframe as it's own window.
Which I guess is what it's supposed to do.
I just released 0.5, telling the extension to ignore googlesyndication
windows. Check for updates in your extension window, see if that helps.
--
Dan Boger
dan@peeron.com
|
|
|
On Tue, Oct 17, 2006 at 04:34:05AM +0000, Dan Boger wrote:
> On Tue, Oct 17, 2006 at 01:24:31AM +0000, Tim Gould wrote:
> > Well I was trying to do this and discovered a fairly major bug in
> > the extension. When trying to edit a post on jlug (phpBB) which
> > contained a set number it found the set number and promptly blanked
> > the entire text edit box.
>
> Whoa! I'll take a look at that tomorrow morning. Probably could just
> add "textarea" to the tags to be left alone.
Yup, I think that did the trick. Try the 0.5 update?
--
Dan Boger
dan@peeron.com
|
|
|
In lugnet.announce.peeron, Dan Boger wrote:
> This is my first attempt at writing a firefox extension. It will allow looking
> up information about sets mentioned in posts on various LEGO sites. See
> screenshots, examples and install it from here:
>
> http://www.peeron.com/inv/Firefox_Extensions
>
> I hope this might be useful!
>
> Dan
>
> FUT lugnet.off-topic.geek
Great work.
Playing with it a bit I noticed that it's not consistant with set detection.
Take this message:
http://news.lugnet.com/market/shopping/?n=12540
The script doesn't seem to detect any of the set number listed.
I'm using the greasemonkey version if that helps. If I get time, I'll peek
throught the script to see if I can find out whats going on
-Orion
|
|
|
In lugnet.off-topic.geek, Dan Boger wrote:
> On Tue, Oct 17, 2006 at 07:58:00PM +0000, Ross Crawford wrote:
> > Hmmmm, Google ads. Check out the above page now that the extension has
> > been available, especially the bottom left corner of the ad box.
> > Weird.
>
> Interesting. I guess the browser treats the iframe as it's own window.
> Which I guess is what it's supposed to do.
>
> I just released 0.5, telling the extension to ignore googlesyndication
> windows. Check for updates in your extension window, see if that helps.
Hmmm, it's saying no updates found, I'm using 0.4.
ROSCO
|
|
|
In lugnet.announce.peeron, Dan Boger wrote:
> This is my first attempt at writing a firefox extension. It will allow looking
> up information about sets mentioned in posts on various LEGO sites. See
> screenshots, examples and install it from here:
>
> http://www.peeron.com/inv/Firefox_Extensions
>
> I hope this might be useful!
>
> Dan
>
> FUT lugnet.off-topic.geek
G'day,
minor niggle number 2 (or is that 3?):
When searching the set guide on lugnet, You can't always find the set
information from peeron. For example:
http://guide.lugnet.com/set/?q=260-270
returns a result on only "VW 1200 Limousine with Garage" (set 261)...and the
sets found are not the one listed, being sets 1200-1 and 1200-2.
Is there a way of fixing this, so that users aren't reliant on opening the
individual pages for each set to see if an inventory or instructions are
available.
Of course, this may be going in a different direction from that you wish the
software to work.
Benjamin Whytcross
|
|
|
On Wed, Oct 18, 2006 at 07:38:04AM +0000, Benjamin Whytcross wrote:
> minor niggle number 2 (or is that 3?):
>
> When searching the set guide on lugnet, You can't always find the set
> information from peeron. For example:
> http://guide.lugnet.com/set/?q=260-270 returns a result on only "VW
> 1200 Limousine with Garage" (set 261)...and the sets found are not the
> one listed, being sets 1200-1 and 1200-2.
>
> Is there a way of fixing this, so that users aren't reliant on opening
> the individual pages for each set to see if an inventory or
> instructions are available.
The problem is that it only looks up 4 digit numbers, or numbers in the
form of nnnn-n. Oh, and it ignores numbers between 1900-2100. I could
easily make it look at 3 digit numbers as well, but you'd end up with
that many more false-positives. For instance, the '159 elements' in the
entry for 263-2 will show up as a link.
Would that be preferred?
I still plan on adding inv/inst info directly in the popup, so that you
wouldn't have to follow the link anyway.
--
Dan Boger
dan@peeron.com
|
|
|
In lugnet.off-topic.geek, Dan Boger wrote:
> On Wed, Oct 18, 2006 at 07:38:04AM +0000, Benjamin Whytcross wrote:
> > minor niggle number 2 (or is that 3?):
> >
> > When searching the set guide on lugnet, You can't always find the set
> > information from peeron. For example:
> > http://guide.lugnet.com/set/?q=260-270 returns a result on only "VW
> > 1200 Limousine with Garage" (set 261)...and the sets found are not the
> > one listed, being sets 1200-1 and 1200-2.
> >
> > Is there a way of fixing this, so that users aren't reliant on opening
> > the individual pages for each set to see if an inventory or
> > instructions are available.
>
> The problem is that it only looks up 4 digit numbers, or numbers in the
> form of nnnn-n. Oh, and it ignores numbers between 1900-2100. I could
> easily make it look at 3 digit numbers as well, but you'd end up with
> that many more false-positives. For instance, the '159 elements' in the
> entry for 263-2 will show up as a link.
>
> Would that be preferred?
>
> I still plan on adding inv/inst info directly in the popup, so that you
> wouldn't have to follow the link anyway.
How about looking for numbers in the nnnn_n or nnn_n in links. At least then the
set pictures may trigger recognition in the set guides, and the 1900-2100 range
would also be picked up.
Alternatively, add an option in a menu that will enable/disable these range
checks.
Anyway, false positives shouldn't be too much of a problem, as most users of
this should be able to see where a set number is meant to appear, and where
another non-set number should have been.
Anyway, Just my thoughts :)
Benjamin Whytcross
|
|
|
On Tue, Oct 17, 2006 at 10:53:00PM +0000, Orion Pobursky wrote:
> Playing with it a bit I noticed that it's not consistant with set
> detection. Take this message:
> http://news.lugnet.com/market/shopping/?n=12540
> The script doesn't seem to detect any of the set number listed.
This should work now. Apparently, JS doesn't reset it's RE engine when
the input changes. So it would end up returning 'null' after every
successful match. Which means it'd skip every other entry.
Updated both the Extension and the GM versions.
--
Dan Boger
dan@peeron.com
|
|
|
Dan Boger wrote:
> This is my first attempt at writing a firefox extension.
Dan,
FYI, version 0.8 worked fine on the test page using Firefox 1.5 on Linux
(Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060802
Mandriva/1.5.0.7-0.1.20060mdk (2006.0) Firefox/1.5.0.7. )
Thanks!
A couple things I noticed:
1) the popup windows seem to be layered according to "normal flow" order. This
means if I open a later window then an earlier window, the latter may appear
partially behind the former. Is there a way to raise the newly opened popup
window to the top?
2) If I click on the counter before it's finished "counting", I'll get Peeron
buttons for the sets already counted. This is fine. But if I then click the
counter after it has counted a few more sets, the originally appearing Peeron
buttons are toggled off, and the newly counted ones are toggled on. Clicking the
counter a third time causes the originally counted ones to toggle on and the
newly counted to toggle off.
I don't think you'd want to reset the toggle state after each button is loaded
(impatient users would get annoyed). But maybe you could have the toggle state
of each new button match the toggle state of the first button instead of
defaulting them to off.
3) (I know, I said "a couple".) It would be nice to have a visual indicator on
the counter showing the current toggle state (I suggest the Peeron kitten if
it's not too difficult). This would be helpful when none of the Peeron buttons
are within the viewport (i.e. visible window). (I can infer from 2) that there
is no page-wide toggle state, but you could have it echo the state of the first
Peeron button).
Great work!
-Brian
|
|
|
In lugnet.off-topic.geek, Brian B. Alano wrote:
> Dan Boger wrote:
> > This is my first attempt at writing a firefox extension.
>
> Dan,
>
> FYI, version 0.8 worked fine on the test page using Firefox 1.5 on Linux
> (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060802
> Mandriva/1.5.0.7-0.1.20060mdk (2006.0) Firefox/1.5.0.7. )
There's a version 0.8? I can only find 0.6.
BTW, FF 2.0 is out now, and it says the plugin is incompatible - I'm guessing
it's just a version number change or something.
ROSCO
|
|
|