You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(92) |
Dec
(142) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(33) |
Feb
(65) |
Mar
(76) |
Apr
(172) |
May
(124) |
Jun
(45) |
Jul
(76) |
Aug
(78) |
Sep
(1) |
Oct
(20) |
Nov
(6) |
Dec
(2) |
2007 |
Jan
(12) |
Feb
(7) |
Mar
(17) |
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Andrew T. (nilspace) <nil...@us...> - 2006-02-25 14:41:13
|
Wow, things move fast when I don't read my email for about 10 hours. :) I'm liking how it 's all shaking down to a very nice look. A couple of points, questions: * Left-side "mark all as read" * I believe Miles pointed out that this may be confusing. Does this apply to all the feed items, or just to the 'flagged' items. * Item view * I think the feed icon (favicon or whatever it is) should be where the flag currently is and move the flag to the left (or right) of the "mark as read" * "< Next | Previous >" should probably be "< Previous | Next >" ala Western page-turning, and the preference that increase in time/future goes to the right and the past is to the left * Can probably drop the ", paged" on "View all items, paged" as views should always be paged or they have a really good tendency to crash the browser when 1800 feeds and images are being loaded * I'm not sure if the current demo view is "all items", "new items" or "today's items", perhaps some highlighting of the current view in the menu item? Then there may also be a view that will dynamically show up to the left that will be like "Custom View" or "Search View" or something when someone does a special view? Maybe to expand the idea: On the right-hand side is always talking about "this feed or feeds", so if I say view new, view today's that is only applying to the current set of feeds that I have selected in the right-hand side. So on the right side as I flag feeds they will show up in my right-hand side view or there will be a menu button for "view all feeds". New idea, let me know if it doesn't make sense or isn't clear * Tags: I think having two "Tags:" is unnecessary and also doesn't allow for removing tags. What I suggest would be just the single "Tags: wordpress, internet, things | Edit | " - so the user can press the "Edit" or "Edit tags" button (or double-click the word Tags: ?) to change the tags area into a typing box where they can add/delete tags. If we want "quick tags" (i.e. be able to type into a text box and not have to press "Edit" and then "Save" then we can jut provide an empty text area after the listed tags. When a user types in any words and presses the spacebar, it is added the list of tags (ala the magic of Ajax)) * Perhaps the coloring scheme b/w Read and Unread items should be switched? I normally would prefer to read on a white background. We could even gray out (lighten) the text more on read items, or even "fold them up" to just the title bar? When, in this scheme, do feeds "disappear" from my "View new items"? When I click the "Next Items", "mark all as read" or what? * "Save" - please add. Perhaps it's even just a button that adds a "saved" quicktag. (ooh, future feature, the ability for someone to select "quicktags" with a drop-select like Kevin's interface now. If I drop and select a quicktag it is quickly added with no typing necessary - I, for example, would want quicktags for 'save', 'bookmark', 'snippet', 'toforward') K - that's it for now - long winded. Khaled, you're obviously doing a good job, since the better you do, the more people (like me) have little niggles/suggestions as it all gets massaged into place. As for the question of 0.3 release, I wonder about that. Perhaps we want to do a solid, last of it's breed, release as the system currently is, all bugs squashed and dangling, on the edge, feature requests. This will then give a very clear baseline change for 0.3 -> 0.4. I could see all these changes taking quite a little bit of dev time and introducing new bugs (we're all superstar programmers, so i'm *sure* we wouldn't introduce bugs ;) 0.3 won't be a huge press release event or anything. Just a rolling out of a bunch of added features and perhaps even suggest to people to not upgrade, but it's there if they want some of the nifty features that have popped up (tags, saved items, rss output). 0.3 is fairly ready for QA testing, and we would slate 0.4 for perhaps April 1 release (the Fool Edition). :) Andrew -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |
From: khaled A. A. <bro...@gm...> - 2006-02-25 13:52:31
|
I quickly setup a mini site which I'll be skinning in the next couple of days. Basically to actually promote the programme and to make it easier for everyone to see the history of changes and where we were and why we've got what we've got...hmm that's terrible english but you guys hopefully understand what I mean. Anyway here's the link www.brokenkode.com/fofr/ This is where you guys can see the latest version: http://www.brokenkode.com/fofr/framed-user-panel/Version-0.9.jpg |
From: khaled A. A. <bro...@gm...> - 2006-02-25 12:00:19
|
Ok everyone I hope you're all relaxed because I think I've got the framed view down. I have tried to incorporate everyone's thoughts while at the sam= e trying hard to keep it as simple and uncluttered as possible. So lets start with the explanations. Starting from the very top. We've got four major links. These links effectively will change the view in the sidebar. Feeds is as shown, Categor= y will show the different kinds of categories that have been created and on clicking that all feeds in that particular category will be shown. Tags follows the same kind of vision as well. The final addition is Flags. This to me is just a better way that the 'saved' name that is currently being used. An item will be able to be flagged whether it's been read or not. The idea here is that you'll be able to view items that really interested you much later down the line, whether you've read them or not. You don't have t= o go back to a website and trek for the information doing searches and what not. You just see your flagged items and you're good to go. I guess that's where the search feature will come in handy as well. So hopefully Miles tha= t deals with that worry you had :). Done and dusted. On the right hand side we've got the secondary menu bar. Full view is what I'm calling the no-frames view. If you guys have a better name for this I'm all ears :).Refresh, it's important but secondary in nature so it's right there as well. The admin panel is back where it belongs, and as is the logging out of the system. Moving directly down to the sidebar there have been a couple of changes since version 0.7 and I'll explain how I see these working. Right about the sidebar is a link called 'mark all as read' that will do just that. All feeds in the sidebar will be marked as read. If a person wants to mark one feed as completely read then he'll have to click the othe= r mark all as read link on the far right hand side above the main items section. The thing is most people are used to clicking on the title of the feed in the sidebar and then by it turning up it's automatically seen as th= e fact that the entire feed items have been read. FOFR gives additional flexibility. The only draw back is that there is one additional click that the user has to make in order to achieve that effect. It's a small price to pay I believe. One thing that has gone is the age of the feed. I don't think that this is particularly necessary. It clutters things up. Mostly I don't care when something was written (ie 1 day ago or 3 days ago). And anyway for that information I've got the full date written in the feed for that, so I didn'= t feel too bad removing that element from the sidebar. The number of feeds has returned, as has the total number of feeds. This time the total number is found right at the top in the menu section and I was hoping that this could be updated as you read through the items. Not sure how feasible that actually is but there you go. I'll leave that to you guys to decide and sort out, maybe in future versions, but for now I guess the user will have to refresh to get that information? You can flag a whole feed, which I guess is a good option (ie you can save an entire feed). You can update each individual feed as well. Not sure how useful this actually is but alas it's not that cluttering and if you think it'll be use= d then that's cool. Moving to the meat and potatoes of the items there have been a couple of changes additions here. I've added the option to include tags on a feed ite= m basis (thanks Katie, good idea). You'll also notice that I've got the mark as read and unread link and icon in each feed. Once again this is a mere click and it toggles between the two different icons and states. Right abov= e is the mark all as read link, and the pagination of the feed links. I think in the admin panel we'd probably have the option of the maximum number of feeds that can get displayed before a new page is done. I guess it could be an option or for a start we can concentrate it as a default and integrate this in later on. As you can see we can also flag every single item on the left hand side of the title of the item. The website url has been included in there as well, although in a slightly more subtle way. We should make it as a default that external links open in a new window/tab whatever. Katie, you voiced your concren over the fact that the link on the side doesn't collaborate to the stuff shown. That was just indicative of what things will look like. I've made the changes just for you. Chris J Davis in the sidebar, chris j davis in the main feed. And that is all she wrote (although that's enough really). Sorry about bein= g so verbose but it's hard to communicate everything over emails and things and intents get lost. Anyway everyone mull it over have a think about it, there's a lot there, and to be fair in less than a week I've come in and changed a slew of things that you might not be entirely happy with. So just tell me and I'll try and incorporate them into the design. Regarding promotion, I think I can pretty much guarantee that the entire 9rules network will be behind this, I'm setting up a mini-website to showcase the design behind the programme which should get some more interes= t in it all. I know people have been clamouring for something like this... I know I have. So here's the latest version which I believe is very very close to the fina= l thing. http://www.brokenkode.com/fofr/Version-0.9.jpg Khaled www.brokenkode.com |
From: Miles B. <mil...@gm...> - 2006-02-25 03:44:20
|
On 2/24/06, Kevin <ke...@dr...> wrote: > I see the number of unread items in the feed list went missing. are ther= e > plans to add it back? I hope this can be added back as well. I like to know how many unread items are in a feed that way I can decide which feed to read first. Sometimes I do not have a lot of time to read something but I want to check a feed which only has a few articles in it. Without the number of unread displayed that would make harder to know which to read first. How will the "save" functionality be displayed in the layout? This is something that allows you to save an article so it is not marked as read if you do a "mark all read". Then we need something in there also so you can later mark it as read when you are done with it. Thanks for all your work on this. I vote on having the new layout in 0.3 as well. I think it's such a big step forward we may get a lot more users with the new look. Great work! |
From: Kevin <ke...@dr...> - 2006-02-25 03:27:18
|
> It's been a long evening. I'll be sure to explain everything sometime > tomorrow, but in the meantime have a look at version 0.8. I believe it > addresses everything Katie, Miles et all voiced their concerns about. E= ven > though it's more functional and it's got a lot going on, it's actually > less > cluttered than previous versions. This has been something on my mind si= nce > the start. Design something that wasn't cluttered. > > Only two things on my mind which I haven't addressed, the number of fee= ds > and how it's integrated into the design and pagination. > > Regarding the second point can I ask how useful people thing the search > function in an rss aggregator seriously is? Is it something you guys fe= el > is > ABSOLUTELY necessary? In my mind these two elements are currently fight= ing > for the same real estate and I've got to say I'm actually siding with t= he > pagination rather than the search function... > Search is a core feature. It was one of the first added after the FoF code fork. If it is taking up too much room. Perhaps It can be hidden behind an ico= n and toggled into view when clicked on. This is easy using a little javascript. SourceForge does this by putting a little plus sign next to the search button to give more search options. I don't use search much, but find it useful when necessary. I see the number of unread items in the feed list went missing. are ther= e plans to add it back? I like how it's coming along. From what I see, implementing this is goin= g to take a bit of effort. Maybe with a few devs pitching in. Is this going to happen before 0.3 release? I vote yes. --=20 Kevin |
From: khaled A. A. <bro...@gm...> - 2006-02-25 01:50:49
|
It's been a long evening. I'll be sure to explain everything sometime tomorrow, but in the meantime have a look at version 0.8. I believe it addresses everything Katie, Miles et all voiced their concerns about. Even though it's more functional and it's got a lot going on, it's actually less cluttered than previous versions. This has been something on my mind since the start. Design something that wasn't cluttered. Only two things on my mind which I haven't addressed, the number of feeds and how it's integrated into the design and pagination. Regarding the second point can I ask how useful people thing the search function in an rss aggregator seriously is? Is it something you guys feel i= s ABSOLUTELY necessary? In my mind these two elements are currently fighting for the same real estate and I've got to say I'm actually siding with the pagination rather than the search function... www.brokenkode.com/fofr/Version-08.jpg |
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 > |
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: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 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: Katie B. <ka...@ho...> - 2006-02-24 16:34:29
|
On Fri, Feb 24, 2006 at 04:05:19PM +0000, khaled Abou Alfa wrote: > Katie I'd check out version 0.7 for the latest. I think this comment still applies to version 0.7: > > > When reading any particular link we also get the background highlighted > > as > > > indicated. It's a good visual indicator of what we are reading. > > > > Do you mean how in the left frame the feed that you've selected to > > read in the right frame is highlighted? In the examples so far the > > highlighted feed (in light blue) hasn't corresponded to the items in > > the right frame. -- Katie Bechtold http://hoteldetective.org/ |
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: khaled A. A. <bro...@gm...> - 2006-02-24 16:05:26
|
Katie I'd check out version 0.7 for the latest. On 2/24/06, Katie Bechtold <ka...@ho...> wrote: > > On Thu, Feb 23, 2006 at 07:56:33AM +0000, khaled Abou Alfa wrote: > > www.brokenkode.com/fofr/Version-0.4.jpg > > > > New feeds are highlighted in bold. > > What does 'new feeds' mean here? (I'm still catching up with this > interface conversation, so feel free to tell me that's irrelevant > now.) > > > When reading any particular link we also get the background highlighted > as > > indicated. It's a good visual indicator of what we are reading. > > Do you mean how in the left frame the feed that you've selected to > read in the right frame is highlighted? In the examples so far the > highlighted feed (in light blue) hasn't corresponded to the items in > the right frame. > > -- > Katie Bechtold http://hoteldetective.org/ > > > > > ------------------------------------------------------- > 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?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > |
From: Katie B. <ka...@ho...> - 2006-02-24 15:53:49
|
On Thu, Feb 23, 2006 at 07:56:33AM +0000, khaled Abou Alfa wrote: > www.brokenkode.com/fofr/Version-0.4.jpg > > New feeds are highlighted in bold. What does 'new feeds' mean here? (I'm still catching up with this interface conversation, so feel free to tell me that's irrelevant now.) > When reading any particular link we also get the background highlighted as > indicated. It's a good visual indicator of what we are reading. Do you mean how in the left frame the feed that you've selected to read in the right frame is highlighted? In the examples so far the highlighted feed (in light blue) hasn't corresponded to the items in the right frame. -- Katie Bechtold http://hoteldetective.org/ |
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: 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: 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: 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: Miles B. <mil...@gm...> - 2006-02-24 02:52:05
|
On 2/23/06, Andrew Turner (nilspace) <nil...@us...> wrote= : > What about you other devs or people that grab the "Dev" versions of > FoFRedux? Subversion clients aren't as commonly installed by default > as CVS and the command options are different. I'm willing to give SVN > a try as long as it doesn't put too much of a burden on the rest of > our current devs/edge users. I'm willing to give it a shot. |
From: Andrew T. (nilspace) <nil...@us...> - 2006-02-24 00:04:24
|
What about you other devs or people that grab the "Dev" versions of FoFRedux? Subversion clients aren't as commonly installed by default as CVS and the command options are different. I'm willing to give SVN a try as long as it doesn't put too much of a burden on the rest of our current devs/edge users. Andrew On 2/23/06, Kevin <ke...@dr...> wrote: > > I too like SVN, but is there real value for us in migrating the > > already existing project from CVS to SVN? I haven't done it, but I > > assume you can migrate histories as well? > > > > Andrew > > I like the handling of branches and tags better. It's easier and less > error prone. You can rename files and directories while still keeping > history. Some operations can be run locally, without having to hit the > repository. (diff, status are two I use often) > > They do provide an automated migration option. Just submit the request > and the site does it for you. The migration will include all > branches/tags/revisions in the CVS repository. It doesn't alter/remove > the cvs repository so if we decide against it, nothing is lost. > > I'd like to take it for a spin an see how well it works. > > -- > Kevin > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > 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 > -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |
From: Kevin <ke...@dr...> - 2006-02-23 23:56:13
|
> I too like SVN, but is there real value for us in migrating the > already existing project from CVS to SVN? I haven't done it, but I > assume you can migrate histories as well? > > Andrew I like the handling of branches and tags better. It's easier and less error prone. You can rename files and directories while still keeping history. Some operations can be run locally, without having to hit the repository. (diff, status are two I use often) They do provide an automated migration option. Just submit the request and the site does it for you. The migration will include all branches/tags/revisions in the CVS repository. It doesn't alter/remove the cvs repository so if we decide against it, nothing is lost. I'd like to take it for a spin an see how well it works. --=20 Kevin |
From: Andrew T. (nilspace) <nil...@us...> - 2006-02-23 23:31:07
|
I too like SVN, but is there real value for us in migrating the already existing project from CVS to SVN? I haven't done it, but I assume you can migrate histories as well? Andrew On 2/23/06, Kevin <ke...@dr...> wrote: > > Sourceforge now supports Subversion repositories. I think this is great > news. I am a big fan of SVN and think we should migrate FoFR's repositor= y > to it. > > -- > Kevin > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > 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 > -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |
From: Kevin <ke...@dr...> - 2006-02-23 23:27:53
|
Sourceforge now supports Subversion repositories. I think this is great news. I am a big fan of SVN and think we should migrate FoFR's repositor= y to it. --=20 Kevin |
From: khaled A. A. <bro...@gm...> - 2006-02-23 15:36:32
|
Since writing that I've had a bit of a think and it'll all become clear (I hope) in the next iteration. Thanks Miles. On 2/23/06, Miles Beck <mil...@gm...> wrote: > > On 2/23/06, khaled Abou Alfa <bro...@gm...> wrote: > > *snip* > > > Maybe you're right Andrew, maybe the solution is to have 10 unread item= s > (total unread 220) > or whatever. > > What do you mean by this? > > I really like the layout of this. Good work. > > > ------------------------------------------------------- > 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-23 15:31:50
|
On 2/23/06, khaled Abou Alfa <bro...@gm...> wrote: *snip* > Maybe you're right Andrew, maybe the solution is to have 10 unread items = (total unread 220) > or whatever. What do you mean by this? I really like the layout of this. Good work. |