Re: [Fofredux-devel] Some features to think about

[Andrew T. <ajt...@hi...>]

We had discussed moving read/unread/saved to tags, which provides you
with the mixed case scenario you gave. It also takes out a lot of
"special handling" in the logic. Perhaps just keep the "read" flag but
move the saved to a tag.

As for the #saved items or saved feed, this will really just be a
sub-set of a saved search, where the search is for all items with the
tag "save". So when the functionality for saving searches/views is in
the model/controller code, we can add that.

I'll be picking up and putting together the UI this weekend.

Andrew

On 5/17/06, Evan Roth <eva...@gm...> wrote:
> miles,
> it should be pretty simple to add that, since it's really just a counter,
> which we have several of already.
>
> i've got the next week off, after a grueling 2 weeks in the office, so i'=
ll
> start attacking some of those features.  i've seen that kevin has been
> making major headway on the refactoring of everything.
>
> i think my first goal, since i've got a week set aside...barring anything
> strange happening...will be to start to really implement multi-user.  i'v=
e
> got it mentally laid out, but there is tons of database work which means
> dissecting some tables and moving the data around a bit.  all of that is
> easy to start from, but it's trickier to try to mold an existing database
> with real data in there.
> which gets me to my point.  in there is the status flag, which will need =
to
> be saved for each user to each item.  currently, we have 1 flag, with 3
> possible values (unread, read, or saved)
> -- does it make sense to build on this?
> 1st thought is to split those into 2 flags, read and saved, which means t=
hat
> an item would be read or unread AND saved or not saved.  Does anyone see =
any
> use for this?  my thought would be that, especially for people with tons =
of
> feeds, they could flip through and save the items they want to read later=
,
> and then work those off form an alternaview of unread saved items.  and
> thus, there's a built in filter of special saved items as well as the
> massive amount of standard items.  (and saved items will never be wiped f=
rom
> the database, whether read or unread)  make sense...or would noone really
> use such a capability?
>
> any other ideas on flags?  or views that might be easier...without some s=
ort
> of text filter at this stage?
>
> /evan
>
>
>
> On 5/17/06, Miles Beck <mil...@gm...> wrote:
> > Speaking of features, would it be a lot of work/time to implement a
> > feature I added on the feature request page?
> >
> > The feature number is: 1445226
> >
> > Saved items feed
> > What I'm really after here is something like a feed display that could
> > show you on the main page how many items were in the View Saved Items
> > section. This way you could easily see at a glance how many you had
> > marked as saved.
> >
> > It would be great if this could be implemented for 0.4. Hopefully we
> > can also see some of the UI redesign make it into SVN soon.
> >
> > I'd also like to thank everyone for all the great work, this is coming
> > along nicely.
> >
> > -Miles
> >
> >
> > -------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, securit=
y?
> > Get stuff done quickly with pre-integrated technology to make your job
> easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron=
imo
> >
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=120709&bid&3057&dat=121642
> > _______________________________________________
> > Fofredux-devel mailing list
> > Fof...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/fofredux-devel
> >
>
>


--=20
Andrew Turner
ajt...@hi...        42.4266N x 83.4931W
http://highearthorbit.com              Northville, Michigan, USA