[Ext] Brief 1.1 - feed reading extension
-
- Posts: 6922
- Joined: July 29th, 2003, 1:09 pm
Here's what I tried in my style:
.article-container {
padding-bottom: 2cm;
background-color: #B0C4DE;
border: 2px #72745b solid;
-moz-border-radius: 2px;
margin: 0 1em 0.7em 1em;
All that did was add blank space at the bottom of articles; the odd scroll bar was still there, as the area of the text of the feed did not change.
.article-container {
padding-bottom: 2cm;
background-color: #B0C4DE;
border: 2px #72745b solid;
-moz-border-radius: 2px;
margin: 0 1em 0.7em 1em;
All that did was add blank space at the bottom of articles; the odd scroll bar was still there, as the area of the text of the feed did not change.
-
- Posts: 6922
- Joined: July 29th, 2003, 1:09 pm
Just noticed another oddity: As there were only twenty-four new entries in Brief, I looked at all of them at once, rather than feed by feed.
One of the twenty-four was a Slashdot entry, complete with its own scroll bar. Although that entry was there, it had no effect on my use of the space bar.
Something is spacey....
One of the twenty-four was a Slashdot entry, complete with its own scroll bar. Although that entry was there, it had no effect on my use of the space bar.
Something is spacey....
-
- Posts: 6922
- Joined: July 29th, 2003, 1:09 pm
Just a FYI: Brief is incompatible with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1 - Build ID: 2007110904; that is Release Candidate 3 for Beta 1, and, therefore, changes are entirely likely before the official release of Beta 1.
This is just to alert you to the problem if you are not yet aware of it. I tried to override the incompatibility check, but that did not help.
(I did get it installed in a different profile, but found that, although it was there, it could not find the bookmark folders, and, thus, could not be used; that is, I suspect, part of its incompatibility. I had set at least two overrides to allow non-compatible extensions to be installed, just to see what would happen when they were installed. One small extension, for example, disabled the right-click menu on the tool bar, making it a wee bit difficult to change anything there. That's ignoring the odd bug that, if one does use the Customize menu, the toolbar becomes inactive and FF has to be restarted.)
This is just to alert you to the problem if you are not yet aware of it. I tried to override the incompatibility check, but that did not help.
(I did get it installed in a different profile, but found that, although it was there, it could not find the bookmark folders, and, thus, could not be used; that is, I suspect, part of its incompatibility. I had set at least two overrides to allow non-compatible extensions to be installed, just to see what would happen when they were installed. One small extension, for example, disabled the right-click menu on the tool bar, making it a wee bit difficult to change anything there. That's ignoring the odd bug that, if one does use the Customize menu, the toolbar becomes inactive and FF has to be restarted.)
-
- Posts: 240
- Joined: February 5th, 2004, 8:11 pm
- Location: U.S.A
- Contact:
-
- Posts: 252
- Joined: May 7th, 2005, 12:51 pm
war59312, I think that if I was to provide a similar option, it would rather be to mark entries as read as you scroll through them, which would probably also cover your needs. I am not sure yet if I'm gonna do it, though. I always evaluate every feature very carefully before adding it, because above all I want to keep Brief simple.
-
- Posts: 252
- Joined: May 7th, 2005, 12:51 pm
Announcement: from now on please use the dedicated forum on brief.mozdev.org instead of this topic.
I will still follow this thread but it would be great if we could move the majority of the discussions to the dedicated forum on Brief's website. Thanks!
I will still follow this thread but it would be great if we could move the majority of the discussions to the dedicated forum on Brief's website. Thanks!
-
- Posts: 7
- Joined: November 10th, 2004, 6:42 am
Try to used forum, but can't add post.
I may found a bug. I'm using the 1.03b but i noticed same pb with 0.8
I'm set filter to see only unread items.
When there is only one item to read, when i click on title, the entry is set to read, but article is not display. Only no unread item message is displayed.
Hope you will fixe the forum, it will be better that this huge thread.
I may found a bug. I'm using the 1.03b but i noticed same pb with 0.8
I'm set filter to see only unread items.
When there is only one item to read, when i click on title, the entry is set to read, but article is not display. Only no unread item message is displayed.
Hope you will fixe the forum, it will be better that this huge thread.
-
- Posts: 252
- Joined: May 7th, 2005, 12:51 pm
Brief 1.0 is released, available from http://brief.mozdev.org. Automatic updates will start when it is accepted in addons.mozilla.org.
-
- Posts: 240
- Joined: February 5th, 2004, 8:11 pm
- Location: U.S.A
- Contact:
I tired posting over there too and just getting a blank white page when I try and login.
I would like that, still pretty simple if you ask me.
Ancestor wrote:war59312, I think that if I was to provide a similar option, it would rather be to mark entries as read as you scroll through them, which would probably also cover your needs. I am not sure yet if I'm gonna do it, though. I always evaluate every feature very carefully before adding it, because above all I want to keep Brief simple.
I would like that, still pretty simple if you ask me.
God Bless America
-
- Posts: 252
- Joined: May 7th, 2005, 12:51 pm
war59312 wrote:I tired posting over there too and just getting a blank white page when I try and login. :(Ancestor wrote:war59312, I think that if I was to provide a similar option, it would rather be to mark entries as read as you scroll through them, which would probably also cover your needs. I am not sure yet if I'm gonna do it, though. I always evaluate every feature very carefully before adding it, because above all I want to keep Brief simple.
I would like that, still pretty simple if you ask me.
Let me rephrase this. Yes, this particular option would be pretty simple and adding it wouldn't carry much cost. However, there are requests for many simple features all the time, each of which makes some sense and is somewhat useful. When evaluating them separately you may be inclined to approve them thinking "sure, why not?" and very soon you'll find that tens of little features imperceptibly rendered the extension bloated.
How do you avoid it? You must have a vision of how the extension should look like and what are the primary use cases.
That's why I always look at the bigger picture before implementing a feature.