From: khaled A. A. <bro...@gm...> - 2006-02-24 11:16:34
|
Okay I think I've cracked it. Here's the latest iteration: www.brokenkode.com/fofr=AD/Version-0.7.jpg And this is the explanation behind all the change and how it all works. 1. The main header has the following changes. I've future proofed it so tha= t we have an area where we can have the different views. That is the sidebar changes according to the view. So it could be feeds, categories or tags. In time we might even have a history view as well. 2. On the other side, with a slightly grey background to distinguish betwee= n the types of links are the admin stuff. Adding feeds, categories and tags. The refresh button is in here as well. I'm going to be making this slightly tighter and include the admin button in here as well. Making them smaller i= s ok as they are definitely important however not as important as the views buttons which will come into use much more heavily. 3. The light blue in the sidebar highlights the feed that we are currently looking at. Once that LINE is clicked then it is highlighted light blue. When it is hovered over it's light magenta (I'll provide a mockup for that at some point for completist purposes. This I hope makes it generally much more simple for reading the actual feed itself. 4. The sidebar works in such a way that you click on the entire line, rathe= r than a link and it updates the frame on the right hand side. 5. Unread items are in BOLD, those that have been read are in normal text. 6. The total number of unread items is in there as well. 7. UNREAD items are highlighted in light blue on the side. Any of the actua= l feeds are in the grey colours shown above that. That keeps things clear as well. 8. Within the feeds line I've included the update individual icon as requested. 9. Now to explain how I see the smaller toolbar . On the left hand side those links control the sidebar. So you can select all or unselect all the items, and then you can mark them as read or unread. Very simple way of MAS= S deadling with feeds. 10. On the right hand side we've got the three links on viewing things belo= w that section itself. Yes I understand you can't mass do the marking as read and unread here, but to be honest I think having that feature in the sideba= r makes a great deal more sense,=85unless of course you guys feel otherwise. 11. Now this is where the first bit of ajax I can think of comes into mind. Like I said before the individual unread items are in light blue, those tha= t have been read are in grey. My idea is and please tell me if this is possible, once you click on the 'mark as read' tick box it turns it grey. Hell it could fade it from the blue to the grey if we were really wanting t= o be fancy. |
From: khaled A. A. <bro...@gm...> - 2006-02-24 11:31:56
|
Just noticed that the link didn't work for some reason. In any case if you click on the following link then that takes you to the actual directory where all the previous versions are online. www.brokenkode.com/fofr=AD/ Here's the link for the latest www.brokenkode.com/fofr/Version-07.jpg <http://www.brokenkode.com/fofr>=AD On 2/24/06, khaled Abou Alfa <bro...@gm...> wrote: > > Okay I think I've cracked it. > > Here's the latest iteration: > www.brokenkode.com/fofr=AD/Version-0.7.jpg > > And this is the explanation behind all the change and how it all works. > > 1. The main header has the following changes. I've future proofed it so > that we have an area where we can have the different views. That is the > sidebar changes according to the view. So it could be feeds, categories o= r > tags. In time we might even have a history view as well. > > 2. On the other side, with a slightly grey background to distinguish > between the types of links are the admin stuff. Adding feeds, categories = and > tags. The refresh button is in here as well. I'm going to be making this > slightly tighter and include the admin button in here as well. Making the= m > smaller is ok as they are definitely important however not as important a= s > the views buttons which will come into use much more heavily. > > 3. The light blue in the sidebar highlights the feed that we are currentl= y > looking at. Once that LINE is clicked then it is highlighted light blue. > When it is hovered over it's light magenta (I'll provide a mockup for tha= t > at some point for completist purposes. This I hope makes it generally muc= h > more simple for reading the actual feed itself. > > 4. The sidebar works in such a way that you click on the entire line, > rather than a link and it updates the frame on the right hand side. > > 5. Unread items are in BOLD, those that have been read are in normal text= . > > > 6. The total number of unread items is in there as well. > > 7. UNREAD items are highlighted in light blue on the side. Any of the > actual feeds are in the grey colours shown above that. That keeps things > clear as well. > > 8. Within the feeds line I've included the update individual icon as > requested. > > 9. Now to explain how I see the smaller toolbar . On the left hand side > those links control the sidebar. So you can select all or unselect all th= e > items, and then you can mark them as read or unread. Very simple way of M= ASS > deadling with feeds. > > 10. On the right hand side we've got the three links on viewing things > below that section itself. Yes I understand you can't mass do the marking= as > read and unread here, but to be honest I think having that feature in the > sidebar makes a great deal more sense,=85unless of course you guys feel > otherwise. > > 11. Now this is where the first bit of ajax I can think of comes into > mind. Like I said before the individual unread items are in light blue, > those that have been read are in grey. My idea is and please tell me if t= his > is possible, once you click on the 'mark as read' tick box it turns it gr= ey. > Hell it could fade it from the blue to the grey if we were really wanting= to > be fancy. > > > > > |
From: Andrew T. (nilspace) <nil...@us...> - 2006-02-24 12:59:40
|
On 2/24/06, khaled Abou Alfa <bro...@gm...> wrote: > Okay I think I've cracked it. > > Here's the latest iteration: > www.brokenkode.com/fofr=AD/Version-0.7.jpg > > And this is the explanation behind all the change and how it all works. > > 1. The main header has the following changes. I've future proofed it so t= hat > we have an area where we can have the different views. That is the sideba= r > changes according to the view. So it could be feeds, categories or tags. = In > time we might even have a history view as well. I like this change, as a user, I may want to have all of the sidebar goodies on a per-category or per-tag basis. > 2. On the other side, with a slightly grey background to distinguish betw= een > the types of links are the admin stuff. Adding feeds, categories and tags= . > The refresh button is in here as well. I'm going to be making this slight= ly > tighter and include the admin button in here as well. Making them smaller= is > ok as they are definitely important however not as important as the views > buttons which will come into use much more heavily. What happened to login/logout and prefs? > > 3. The light blue in the sidebar highlights the feed that we are currentl= y > looking at. Once that LINE is clicked then it is highlighted light blue. > When it is hovered over it's light magenta (I'll provide a mockup for tha= t > at some point for completist purposes. This I hope makes it generally muc= h > more simple for reading the actual feed itself. Good > 4. The sidebar works in such a way that you click on the entire line, rat= her > than a link and it updates the frame on the right hand side. > > 5. Unread items are in BOLD, those that have been read are in normal text= . > > 6. The total number of unread items is in there as well. > > 7. UNREAD items are highlighted in light blue on the side. Any of the act= ual > feeds are in the grey colours shown above that. That keeps things clear a= s > well. > > 8. Within the feeds line I've included the update individual icon as > requested. > > 9. Now to explain how I see the smaller toolbar . On the left hand side > those links control the sidebar. So you can select all or unselect all th= e > items, and then you can mark them as read or unread. Very simple way of M= ASS > deadling with feeds. > > 10. On the right hand side we've got the three links on viewing things be= low > that section itself. Yes I understand you can't mass do the marking as re= ad > and unread here, but to be honest I think having that feature in the side= bar > makes a great deal more sense,=85unless of course you guys feel otherwise= . Here's how I use FoFR, so maybe it can give you an idea for what at least I would be looking for it "mass marking" the current view: * I bring up either "new items", a specific feed, or a specific category, with max 10 items * I quickly read through all the items in that view (all 10), mark "Save" on the items I want to scrutinize later * When I get to the bottom, I press "Mark All Read", which marks those 10 as read. It's like reading "pages" of feeds. I tend to have variable number of minutes throughout the day to read, sometimes I just through a page, sometimes I'll pound through 5 pages, But marking items read by "page" rather than an entire feed, or individually selecting items, is a necessity for how I use FoFR. Does that make sense? You also took out the "save" on an item, and there is no way to add a new tag on an item? > 11. Now this is where the first bit of ajax I can think of comes into min= d. > Like I said before the individual unread items are in light blue, those t= hat > have been read are in grey. My idea is and please tell me if this is > possible, once you click on the 'mark as read' tick box it turns it grey. > Hell it could fade it from the blue to the grey if we were really wanting= to > be fancy. > Yes, this is definitely possible and actually pretty straight-forward. I would see that you click "mark as read" then the item would change color. Another preference may be to have the item actually dynamically disappear. If you clicked "save" then the item would change another color or also disappear (perhaps color vs. disappear is a user pref?) Of course, this is exactly how TinyTinyRSS operates from what I tried on the demo. Also, I think we would want to ajaxify tagging items, and also having the sidebar update the number of unread as items are marked read. Any thoughts on the non-framed view layout? Thanks for the great work and ideas Khaled. It's really great being able to actually see how something can become so pretty with some skill and knowledge :) Your efforts are really appreciated. Andrew -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |
From: Kevin <ke...@dr...> - 2006-02-24 14:00:45
|
Andrew Turner (nilspace) wrote: > On 2/24/06, khaled Abou Alfa <bro...@gm...> wrote: > >> Okay I think I've cracked it. >> >> Here's the latest iteration: >> www.brokenkode.com/fofr/Version-0.7.jpg >> >> And this is the explanation behind all the change and how it all works. >> >> 1. The main header has the following changes. I've future proofed it so that >> we have an area where we can have the different views. That is the sidebar >> changes according to the view. So it could be feeds, categories or tags. In >> time we might even have a history view as well. >> > > I like this change, as a user, I may want to have all of the sidebar > goodies on a per-category or per-tag basis. > > I've also thought this would be a good feature. I pictured the sidebar having tabs for quick access to the different item groupings we support. [feeds][categories][tags][searches] I sometimes want to read by category and it's not that easy to do, especially in framed view. > >> 4. The sidebar works in such a way that you click on the entire line, rather >> than a link and it updates the frame on the right hand side. >> >> 5. Unread items are in BOLD, those that have been read are in normal text. >> >> 6. The total number of unread items is in there as well. >> >> 7. UNREAD items are highlighted in light blue on the side. Any of the actual >> feeds are in the grey colours shown above that. That keeps things clear as >> well. >> >> 8. Within the feeds line I've included the update individual icon as >> requested. >> >> 9. Now to explain how I see the smaller toolbar . On the left hand side >> those links control the sidebar. So you can select all or unselect all the >> items, and then you can mark them as read or unread. Very simple way of MASS >> deadling with feeds. >> >> 10. On the right hand side we've got the three links on viewing things below >> that section itself. Yes I understand you can't mass do the marking as read >> and unread here, but to be honest I think having that feature in the sidebar >> makes a great deal more sense,…unless of course you guys feel otherwise. >> > > Here's how I use FoFR, so maybe it can give you an idea for what at > least I would be looking for it "mass marking" the current view: > * I bring up either "new items", a specific feed, or a specific > category, with max 10 items > * I quickly read through all the items in that view (all 10), mark > "Save" on the items I want to scrutinize later > * When I get to the bottom, I press "Mark All Read", which marks > those 10 as read. > > It's like reading "pages" of feeds. I tend to have variable number of > minutes throughout the day to read, sometimes I just through a page, > sometimes I'll pound through 5 pages, But marking items read by "page" > rather than an entire feed, or individually selecting items, is a > necessity for how I use FoFR. > I also read this way. I'll sort by oldest first and read/scan through the items, flagging them as I go along. If I haven't gotten to the bottom, I'll mark read what's been flagged. >> 11. Now this is where the first bit of ajax I can think of comes into mind. >> Like I said before the individual unread items are in light blue, those that >> have been read are in grey. My idea is and please tell me if this is >> possible, once you click on the 'mark as read' tick box it turns it grey. >> Hell it could fade it from the blue to the grey if we were really wanting to >> be fancy. >> >> > ... > > Any thoughts on the non-framed view layout? > > The reason I use non-framed view is to get the sidebar out of the way. What I miss is the links in the top left corner for marking/tagging and switching views. If sidebar could be hidden while still keeping the top menu, that would be great. I picture the true *non-framed* view looking very similar to the mock ups Khaled has made. The top menu would be included at the top of the panel or view page and not be in it's own frame. Excellent work, Khaled. I can't wait to see it in action. -Kevin |
From: Katie B. <ka...@ho...> - 2006-02-24 16:33:20
|
On Fri, Feb 24, 2006 at 11:16:28AM +0000, khaled Abou Alfa wrote: > www.brokenkode.com/fofr/Version-0.7.jpg I think the 'Add Tag' action may be unnecessary. In the tag paradigms I've seen so far, tags exist only by virtue of being associated with things. A tag wouldn't exist until the user types it in to associate with a particular item, and it would cease to exist when all the items with which it's associated are deleted. (This brings to mind the question: where in the new interface do we associated categories with feeds and tags with items?) > 9. Now to explain how I see the smaller toolbar . On the left hand side > those links control the sidebar. So you can select all or unselect all the > items, and then you can mark them as read or unread. I'd suggest renaming the 'mark all read' link there to 'mark as read'. When it says 'mark all read', I think the user could reasonably be confused as to whether all items in all feeds would be marked as read or whether all items in the selected feeds would be marked as read. > My idea is and please tell me if this is > possible, once you click on the 'mark as read' tick box it turns it grey. I'd suggest changing the 'mark as read' interface from a tick box to a link, since its action will now be immediate. Also, I'd suggest that read items (in gray) have a 'mark as unread' link instead of a 'mark as read' link as does the one in the example. Perhaps in the right frame, for each item the Categories list could appear closer to the Site Source over in the upper right area of each item. This might help make clear the major distinction between categories and tags, that the former apply to feeds and the latter to items. How I currently use fofredux is this: in the panel view I scan down the list to see which feeds have new items. I'll then click on the red links to get to each feed's new items; on that page, I'll either mark-as-read one by one or click 'mark all items as read' and then be frustrated that I'm returned to that feed's empty page of new items instead of to the panel view page. I've never used the 'flag all up to this item', 'flag all items', or 'unflag all items' links. The only reason I don't use the frames view is because of the inconsistent refreshing of the frames when you do something in one of them. (The orthogonality-loving side of me protests that there's no need for a 'mark all items as read' links when there are 'flag all items' and 'mark [flagged items] as read' links. But the actual user side of me clicks the 'mark all items as read' link every time. :) ) -- Katie Bechtold http://hoteldetective.org/ |
From: Miles B. <mil...@gm...> - 2006-02-24 16:58:29
|
Here is how I use FOFRedux and how I would like to see the links used. When I open a feed sometimes I will "flag all items" then "mark as read" in the non-frame view. I also frequently use the link "flag up to this item" link. I see that is now missing and hope we can somehow still include this. Or, maybe when saved articles is implemented this will make the "flag up to this item" link not needed anymore. Are you going to do a version for the non-frame view? This looks really good. I also will be very pleased to see this in a released build. |
From: khaled A. A. <bro...@gm...> - 2006-02-24 17:32:25
|
I'll be answering and addressing Katie's concerns and points in my next iteration. I think I'll need a few more iterations before we're completely there. Miles, I will be looking into the non-frames view but not until I've sorted this one, the admin panel, login page, and adding items view first because = I actually have a clear view of them in my head. The non-frames view, I can see being very popular but it'll be a different beast I think, simply because in that particular case the main things that need to be larger than usual or the links that are realtively sub-dued in the frames version (i.eview latest, view today etc). hmm I'll have a little think about this. Damn you Miles :). On 2/24/06, Miles Beck <mil...@gm...> wrote: > > Here is how I use FOFRedux and how I would like to see the links used. > > When I open a feed sometimes I will "flag all items" then "mark as > read" in the non-frame view. > > I also frequently use the link "flag up to this item" link. I see that > is now missing and hope we can somehow still include this. Or, maybe > when saved articles is implemented this will make the "flag up to this > item" link not needed anymore. > > Are you going to do a version for the non-frame view? > > This looks really good. I also will be very pleased to see this in a > released build. > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > |
From: Miles B. <mil...@gm...> - 2006-02-24 17:36:41
|
On 2/24/06, khaled Abou Alfa <bro...@gm...> wrote: > Miles, I will be looking into the non-frames view but not until I've sort= ed > this one, the admin panel, login page, and adding items view first becaus= e I > actually have a clear view of them in my head. The non-frames view, I can > see being very popular but it'll be a different beast I think, simply > because in that particular case the main things that need to be larger th= an > usual or the links that are realtively sub-dued in the frames version ( i= .e > view latest, view today etc). > > hmm I'll have a little think about this. Damn you Miles :). Heh, sorry. But I think it's best to get this all hammered out now. :) I don't like the frames view and do not anticipate ever using it. On the plus side, I can give feedback on the non-frames view for you. ;) |
From: khaled A. A. <bro...@gm...> - 2006-02-24 17:56:38
|
No worries dude, and yes this is why we're doing all this so that when version 0.3 comes out it looks like version 1 :). On 2/24/06, Miles Beck <mil...@gm...> wrote: > > On 2/24/06, khaled Abou Alfa <bro...@gm...> wrote: > > > Miles, I will be looking into the non-frames view but not until I've > sorted > > this one, the admin panel, login page, and adding items view first > because I > > actually have a clear view of them in my head. The non-frames view, I > can > > see being very popular but it'll be a different beast I think, simply > > because in that particular case the main things that need to be larger > than > > usual or the links that are realtively sub-dued in the frames version ( > i.e > > view latest, view today etc). > > > > hmm I'll have a little think about this. Damn you Miles :). > > Heh, sorry. > > But I think it's best to get this all hammered out now. :) > > I don't like the frames view and do not anticipate ever using it. On > the plus side, I can give feedback on the non-frames view for you. ;) > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > |