fofredux-devel — Developers discussion, bug fixing, and coding of fofredux

[Fofredux-devel] Re: other issues / comments

[Benjamin S. <bs...@cr...>]

Update, 2 seconds later:  yes, the existing HEAD does not like not
having any categories defined.  As soon as I defined one, panel started
working (though view still has the problem defined below), and a second
problem is that the panel immediately listed the feeds I had added
without a category as belonging to the new category (obviously wrong).  

Anyway, I'm just going to wait until tags land to worry about this too
much.  

Kevin, what database schema are you planning on using for tags?

--Benjy

On Sun, Nov 27, 2005 at 03:44:24PM -0800, Benjamin Stewart wrote:
> * on a vanilla install, add feeds does not seem to be working.    I
>  suspect this might have something to do with php settings of register
> globals vs. .. whatever the other options are.  Switching add.php to use
> _REQUEST instead of _GET and _POST fixed it, and I checked in the fix to
> head.
> 
> * Even on the vanilla install, I'm not getting a working installation.
>  the panel only lists one feed (even though I've subscribed to many), 
> does not list the feed's name, and view does not list any results. Am
> investigating.  Possibly related to not having any categories defined?
> If so, will hack around this pending categories via tags.
> 
> * I guess we should handle feed: urls (thanks a billion, apple.).
> Anyone interested, or should we add it to wherever "the" todo list
> lives?

[Fofredux-devel] other issues / comments

[Benjamin S. <bs...@cr...>]

* on a vanilla install, add feeds does not seem to be working.    I
 suspect this might have something to do with php settings of register
globals vs. .. whatever the other options are.  Switching add.php to use
_REQUEST instead of _GET and _POST fixed it, and I checked in the fix to
head.

* Even on the vanilla install, I'm not getting a working installation.
 the panel only lists one feed (even though I've subscribed to many), 
does not list the feed's name, and view does not list any results. Am
investigating.  Possibly related to not having any categories defined?
If so, will hack around this pending categories via tags.

* I guess we should handle feed: urls (thanks a billion, apple.).
Anyone interested, or should we add it to wherever "the" todo list
lives?

[Fofredux-devel] Re: unknown column feed.latitude (upgrade issues)

[Benjamin S. <bs...@cr...>]

Okay, I'm giving up figuring out what's wrong with upgrading for the
moment and I'm going to work against a clean DB, but I don't think I'd
call it an RC until upgrade / backwards compatability issues are sorted
out.  If we want FOF users to check it out, I think it should be
backwards compatible so FOF users can check it out but switch back to
FOF if they want.

If no one else wants to work on the upgrade issues, I might have time to
work on it in the next week, but am going to integrate keyboard
shortcuts onto a branch today.

--Benjy

On Sun, Nov 27, 2005 at 03:13:31PM -0800, Benjamin Stewart wrote:
> So the next problems I was having were because my category and
> categoryXfeed tables had not been created.  This may have been because I
> didn't add the table defitions to my config.php before running install,
> but I have not followed up on this possibility.
> 
> Regardless, we should handle the case of the idiot who does not read
> documnetion when trying to upgrade.
> 
> Any insights as to what the problem might have been before I back up and
> dig into that?
> 
> --Benjy
> 
> On Sun, Nov 27, 2005 at 03:06:15PM -0800, Benjamin Stewart wrote:
> > So I just checked out off the head and copied my config.php over to try
> > to use my existing FOF database;  It correctly asks "cache dir not found
> > / writable whatever have you run install?" so I ran install, and hit the
> > panel, and got this error:
> > 
> > [select feed.id, feed.url, feed.title, feed.link,
> > feed.description,feed.latitude,feed.longitude, feed.category_id,
> > cat.name from px_feeds feed, FOF_CATEGORY_TABLE cat WHERE cat.id =
> > feed.category_id order by feed.title]: 0.0022
> > Cannot query database. Have you run install.php? MySQL says: Unknown
> > column 'feed.latitude' in 'field list'
> > 
> > The problem is fairly obvious;  I guess we just need to make sure
> > upgrades from FOF work seemlessly, and ideally are backwards compatible
> > for now?   (This mainly relies on stevem not having any select *'s or
> > insert into table select * from other table in his code, but we should
> > also be good and add new columns to the end to give any select *s a
> > *chance* of working)
> > 
> > So uh, i tried altering my tables with the below sql, and I'm still
> > getting some errors.  I'll follow up when I isolate exactly what else
> > will be need for an upgrade.
> > 
> > (must be run in order at the moment:)
> > 
> > alter table px_feeds add column category_id int(11) default NULL;
> > alter table px_feeds add column latitude float default '0.0';
> > alter table px_feeds add column longitude float default '0.0';
> > alter table px_items add column flag tinyint(4) default NULL 
> > alter table px_items add column latitude float default '0.0';  
> > alter table px_items add column longitude float default '0.0';
> > 
> > (Oh, this does bring up the question of whether or not we want to change
> > the name of the 'read' column at some point, so we can stop confusing
> > mysql)
> > 
> > --Benjy

[Fofredux-devel] Re: unknown column feed.latitude (upgrade issues)

[Benjamin S. <bs...@cr...>]

So the next problems I was having were because my category and
categoryXfeed tables had not been created.  This may have been because I
didn't add the table defitions to my config.php before running install,
but I have not followed up on this possibility.

Regardless, we should handle the case of the idiot who does not read
documnetion when trying to upgrade.

Any insights as to what the problem might have been before I back up and
dig into that?

--Benjy

On Sun, Nov 27, 2005 at 03:06:15PM -0800, Benjamin Stewart wrote:
> So I just checked out off the head and copied my config.php over to try
> to use my existing FOF database;  It correctly asks "cache dir not found
> / writable whatever have you run install?" so I ran install, and hit the
> panel, and got this error:
> 
> [select feed.id, feed.url, feed.title, feed.link,
> feed.description,feed.latitude,feed.longitude, feed.category_id,
> cat.name from px_feeds feed, FOF_CATEGORY_TABLE cat WHERE cat.id =
> feed.category_id order by feed.title]: 0.0022
> Cannot query database. Have you run install.php? MySQL says: Unknown
> column 'feed.latitude' in 'field list'
> 
> The problem is fairly obvious;  I guess we just need to make sure
> upgrades from FOF work seemlessly, and ideally are backwards compatible
> for now?   (This mainly relies on stevem not having any select *'s or
> insert into table select * from other table in his code, but we should
> also be good and add new columns to the end to give any select *s a
> *chance* of working)
> 
> So uh, i tried altering my tables with the below sql, and I'm still
> getting some errors.  I'll follow up when I isolate exactly what else
> will be need for an upgrade.
> 
> (must be run in order at the moment:)
> 
> alter table px_feeds add column category_id int(11) default NULL;
> alter table px_feeds add column latitude float default '0.0';
> alter table px_feeds add column longitude float default '0.0';
> alter table px_items add column flag tinyint(4) default NULL 
> alter table px_items add column latitude float default '0.0';  
> alter table px_items add column longitude float default '0.0';
> 
> (Oh, this does bring up the question of whether or not we want to change
> the name of the 'read' column at some point, so we can stop confusing
> mysql)
> 
> --Benjy

[Fofredux-devel] unknown column feed.latitude (upgrade issues)

[Benjamin S. <bs...@cr...>]

So I just checked out off the head and copied my config.php over to try
to use my existing FOF database;  It correctly asks "cache dir not found
/ writable whatever have you run install?" so I ran install, and hit the
panel, and got this error:

[select feed.id, feed.url, feed.title, feed.link,
feed.description,feed.latitude,feed.longitude, feed.category_id,
cat.name from px_feeds feed, FOF_CATEGORY_TABLE cat WHERE cat.id =
feed.category_id order by feed.title]: 0.0022
Cannot query database. Have you run install.php? MySQL says: Unknown
column 'feed.latitude' in 'field list'

The problem is fairly obvious;  I guess we just need to make sure
upgrades from FOF work seemlessly, and ideally are backwards compatible
for now?   (This mainly relies on stevem not having any select *'s or
insert into table select * from other table in his code, but we should
also be good and add new columns to the end to give any select *s a
*chance* of working)

So uh, i tried altering my tables with the below sql, and I'm still
getting some errors.  I'll follow up when I isolate exactly what else
will be need for an upgrade.

(must be run in order at the moment:)

alter table px_feeds add column category_id int(11) default NULL;
alter table px_feeds add column latitude float default '0.0';
alter table px_feeds add column longitude float default '0.0';
alter table px_items add column flag tinyint(4) default NULL 
alter table px_items add column latitude float default '0.0';  
alter table px_items add column longitude float default '0.0';

(Oh, this does bring up the question of whether or not we want to change
the name of the 'read' column at some point, so we can stop confusing
mysql)

--Benjy

[Fofredux-devel] Release v0.2 and Tags?

[Andrew T. (nilspace) <nil...@us...>]

Great job Kevin & Carlos for fixing already existant bugs (in my code,
nonetheless) and getting FoFRedux solid for v0.2.

What do you all think about tagging the current repository as v0.2 RC
(release candidate) and testing and then marking it "Release". I think
we're at a pretty good point for our "baseline" to really start adding
all of the planned features.

Any idea on when tags may be ready to try out? ;)

Andrew

--
Andrew Turner
nil...@us...

Re: [Fofredux-devel] Devs assigned

[Andrew T. (nilspace) <nil...@us...>]

Branches and tags are different, but related, things.

Tags are used to mark a specific revision of files, or more
importantly, the repository. For example, we will probably tag
Release-0_2, RC-0_3, etc. THis allows Devs & Users to go and get a
specific tag/release of code using the name.

A Branch is like a fork in the code. A dev may want to go and work on
a bunch of changes, be able to check those changes in, work with other
devs, etc. But not "mess up" HEAD. Therefore, they will create a
branch (BRANCH_AJAX). A branch can have it's own tags. At some point a
branch can come back to the HEAD, or it can always just be a branch
and you can merge files to the branch or from the branch to the HEAD.


Andrew


On 11/27/05, Kevin <ke...@dr...> wrote:
> Andrew Turner wrote:
>
> >Well, to check what's changed in your CVS do:
> >
> >cvs -n up
> >
> >U : updated in CVS
> >M : local copy changed
> >P : differences in local copy to CVS copy (needs to merge)
> >C : conflict - merged into local copy - you need to search the local
> >copy and resolve the code between the <<<< and >>>>> flags
> >
> >You can also check out this:
> >http://ximbiot.com/cvs/cvshome/docs/blandy.html
> >or
> >http://www.cvsnt.org/manual/html/Modifying-tags.html
> >
> >or grab MacCVS or WinCVS which are decent GUI's for CVS.
> >
> >I guess I can see the benefit of doing this kind of tagging. FoFRedux
> >is a rather small codebase (which is good - let's keep it that way)
> >which can mean a lot more conflicts occuring with overlapping code.
> >This may be a reason Steve M. originally kept the project to himself.
> >
> >Anyways, I guess you are suggesting:
> >PRE_ADDEDTAGS
> >PRE_CR_ADDEDTAGS
> >POST_ADDEDTAGS
> >
> >as an example? Perhaps use LABELS from a marked Feature Request, Bug,
> >Support, from Sourceforge. Make sure and put what LABEL is used in the
> >Sourceforge bug notes
> >
> >therefore, you would:
> >1) update before any modifications (-d adds any new directories)
> >  cvs up -d
> >2) modify code
> >3) Check for what files you modified
> >  cvs -n up
> >2) Tag now as pre-mod
> >  cvs tag PRE_ADDEDTAGS index.php init.php
> >3) commit modifications
> >  cvs commit index.php init.php
> >4) Tag Code Review (whole repository?)
> >  cvs tag PRE_CR_ADDEDTAGS
> >5) Wait for others to verify modifications
> >6) Tag
> >  cvs tag POST_ADDEDTAGS
> >
> >
> Okay.  I understand it a bit better.  It's all done with revision tags,
> but my checkins are against the HEAD branch.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> 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
idealistic technocrat

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] Devs assigned

[Kevin <ke...@dr...>]

Andrew Turner wrote:

>Well, to check what's changed in your CVS do:
>
>cvs -n up
>
>U : updated in CVS
>M : local copy changed
>P : differences in local copy to CVS copy (needs to merge)
>C : conflict - merged into local copy - you need to search the local
>copy and resolve the code between the <<<< and >>>>> flags
>
>You can also check out this:
>http://ximbiot.com/cvs/cvshome/docs/blandy.html
>or
>http://www.cvsnt.org/manual/html/Modifying-tags.html
>
>or grab MacCVS or WinCVS which are decent GUI's for CVS.
>
>I guess I can see the benefit of doing this kind of tagging. FoFRedux
>is a rather small codebase (which is good - let's keep it that way)
>which can mean a lot more conflicts occuring with overlapping code.
>This may be a reason Steve M. originally kept the project to himself.
>
>Anyways, I guess you are suggesting:
>PRE_ADDEDTAGS
>PRE_CR_ADDEDTAGS
>POST_ADDEDTAGS
>
>as an example? Perhaps use LABELS from a marked Feature Request, Bug,
>Support, from Sourceforge. Make sure and put what LABEL is used in the
>Sourceforge bug notes
>
>therefore, you would:
>1) update before any modifications (-d adds any new directories)
>  cvs up -d
>2) modify code
>3) Check for what files you modified
>  cvs -n up
>2) Tag now as pre-mod
>  cvs tag PRE_ADDEDTAGS index.php init.php
>3) commit modifications
>  cvs commit index.php init.php
>4) Tag Code Review (whole repository?)
>  cvs tag PRE_CR_ADDEDTAGS
>5) Wait for others to verify modifications
>6) Tag
>  cvs tag POST_ADDEDTAGS
>  
>
Okay.  I understand it a bit better.  It's all done with revision tags, 
but my checkins are against the HEAD branch.

Re: [Fofredux-devel] Devs assigned

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

Well, to check what's changed in your CVS do:

cvs -n up

U : updated in CVS
M : local copy changed
P : differences in local copy to CVS copy (needs to merge)
C : conflict - merged into local copy - you need to search the local
copy and resolve the code between the <<<< and >>>>> flags

You can also check out this:
http://ximbiot.com/cvs/cvshome/docs/blandy.html
or
http://www.cvsnt.org/manual/html/Modifying-tags.html

or grab MacCVS or WinCVS which are decent GUI's for CVS.

I guess I can see the benefit of doing this kind of tagging. FoFRedux
is a rather small codebase (which is good - let's keep it that way)
which can mean a lot more conflicts occuring with overlapping code.
This may be a reason Steve M. originally kept the project to himself.

Anyways, I guess you are suggesting:
PRE_ADDEDTAGS
PRE_CR_ADDEDTAGS
POST_ADDEDTAGS

as an example? Perhaps use LABELS from a marked Feature Request, Bug,
Support, from Sourceforge. Make sure and put what LABEL is used in the
Sourceforge bug notes

therefore, you would:
1) update before any modifications (-d adds any new directories)
  cvs up -d
2) modify code
3) Check for what files you modified
  cvs -n up
2) Tag now as pre-mod
  cvs tag PRE_ADDEDTAGS index.php init.php
3) commit modifications
  cvs commit index.php init.php
4) Tag Code Review (whole repository?)
  cvs tag PRE_CR_ADDEDTAGS
5) Wait for others to verify modifications
6) Tag
  cvs tag POST_ADDEDTAGS

Andy
On 11/27/05, Kevin <ke...@dr...> wrote:
> Benjamin Stewart wrote:
>
> >Do we have plans for code reviewing going forward?    Like, here's my
> >diff, here are comments from someone else, dev responds to comments,
> >changes made, and done?
> >
> >Here's what I've found works really well when working with branches in
> >cvs:
> >
> >1. once you're ready to submit, make a LIST of your files.
> >2. add a tag PRE_CHECKINLABEL to ONLY those files (using your list)
> >3. check in
> >4. add a tag PRE_CR_CHECKINLABEL (Code Review) to ONLY those files
> >5. make changes as appropriate for the CR and check in again and get CR
> >approval
> >6. add a tag POST_CHECKINLABEL to ONLY those files
> >
> >This way, you can double -j when merging those changes around based on
> >the tags, and you're not relying on cvs's insane file versions, and the
> >pre cr tag allows you to back a change out a lot easier.  And I *think*
> >the reason to only tag your specific files is because it makes it easier
> >to figure out what files are changed by any given change, though I'm not
> >sure that's it -- whatever it was, we had a really good reaosn for that
> >policy (and I don't think it was just that some of my fellow engineers
> >were idiots and I didn't trust them not to check in all of their global
> >changes if they weren't using file lists).
> >
> >
> >
> It looks like a good idea for major enhancements or code
> refactoring.(like tags, for instance)  For those of us with less CVS
> experience, could you give examples of what cvs commands are run at each
> step?
>
> Thanks,
>     Kevin
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> 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
idealistic technocrat

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] Devs assigned

[Kevin <ke...@dr...>]

Benjamin Stewart wrote:

>Do we have plans for code reviewing going forward?    Like, here's my
>diff, here are comments from someone else, dev responds to comments,
>changes made, and done?  
>
>Here's what I've found works really well when working with branches in
>cvs:
>
>1. once you're ready to submit, make a LIST of your files.
>2. add a tag PRE_CHECKINLABEL to ONLY those files (using your list)
>3. check in 
>4. add a tag PRE_CR_CHECKINLABEL (Code Review) to ONLY those files
>5. make changes as appropriate for the CR and check in again and get CR
>approval
>6. add a tag POST_CHECKINLABEL to ONLY those files
>
>This way, you can double -j when merging those changes around based on
>the tags, and you're not relying on cvs's insane file versions, and the
>pre cr tag allows you to back a change out a lot easier.  And I *think*
>the reason to only tag your specific files is because it makes it easier
>to figure out what files are changed by any given change, though I'm not
>sure that's it -- whatever it was, we had a really good reaosn for that
>policy (and I don't think it was just that some of my fellow engineers
>were idiots and I didn't trust them not to check in all of their global
>changes if they weren't using file lists).
>
>  
>
It looks like a good idea for major enhancements or code 
refactoring.(like tags, for instance)  For those of us with less CVS 
experience, could you give examples of what cvs commands are run at each 
step?

Thanks,
    Kevin

Re: [Fofredux-devel] Devs assigned

[Kevin <ke...@dr...>]

Carlos Kozuszko wrote:

>Andy said:
>  
>
>>Carlos, can you apply thetimestamp patch of yours?
>>    
>>
>
>Of course, i'll do it.
>
>  
>
I thew in a change to work around mysql errors I was getting when 
$timestamp was empty.  I only saw your patch after I made my commit.  It 
only changes the behavior of $timestamp not $dcdate.

Re: [Fofredux-devel] Devs assigned

[Carlos K. <ck...@gm...>]

Andy said:
>Carlos, can you apply thetimestamp patch of yours?

Of course, i'll do it.

Re: [Fofredux-devel] Devs assigned

[Benjamin S. <bs...@cr...>]

Do we have plans for code reviewing going forward?    Like, here's my
diff, here are comments from someone else, dev responds to comments,
changes made, and done? =20

Here's what I've found works really well when working with branches in
cvs:

1. once you're ready to submit, make a LIST of your files.
2. add a tag PRE_CHECKINLABEL to ONLY those files (using your list)
3. check in=20
4. add a tag PRE_CR_CHECKINLABEL (Code Review) to ONLY those files
5. make changes as appropriate for the CR and check in again and get CR
approval
6. add a tag POST_CHECKINLABEL to ONLY those files

This way, you can double -j when merging those changes around based on
the tags, and you're not relying on cvs's insane file versions, and the
pre cr tag allows you to back a change out a lot easier.  And I *think*
the reason to only tag your specific files is because it makes it easier
to figure out what files are changed by any given change, though I'm not
sure that's it -- whatever it was, we had a really good reaosn for that
policy (and I don't think it was just that some of my fellow engineers
were idiots and I didn't trust them not to check in all of their global
changes if they weren't using file lists).

That said, I highly advocate you ONLY use cvs with a file list if you're
doing operations that add/delete/commit/tag/otherwise write data to the
repository.  It's not worth the mistake of accidentally checking in
something you didn't mean to check in -- everyone's done it.


My plan is to spend a little bit of time over thanksgiving merging my
keyboard shortcuts onto what Andy did, and hopefully have a checkin on a
branch by Monday or Tuesday of next week. =20

In general, though, what I've done will be pretty easy to redo with
whatever changes other people make, so it's not a big deal if that gets
delayed a touch.

For an initial release, I think having *any* keyboard shortcuts without
ajax features is fine;  We can add ajax features later, and I think the
ability to fly through posts is a bigger deal.

-Benjy

On Tue, Nov 22, 2005 at 11:04:13PM -0500, Andrew Turner (nilspace) wrote:
> Hi all,
> I've added Carlos & Kevin to the FoFRedux developers. You will be able
> to check in and out now.
>=20
> I've also assigned your respective tasks. Carlos, can you apply the
> timestamp patch of yours? Also, Kevin, I think you mentioned you could
> add tags?
>=20
> Andy
>=20
> --
> Andrew Turner
> ajt...@hi...        42.4266N x 83.4931W
> http://highearthorbit.com              Northville, Michigan, USA
> idealistic technocrat
>=20
> Photos - http://flickr.com/photos/ajturner
> Travel   - http://highearthorbit.com/projects/location/
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&op=3Dclick
> _______________________________________________
> Fofredux-devel mailing list
> Fof...@li...
> https://lists.sourceforge.net/lists/listinfo/fofredux-devel

Re: [Fofredux-devel] FoFRedux mailing list

[Benjamin S. <bs...@cr...>]

> > * And my external viewer mode [2] lets you gather roughly the same data,
> >   but could also track other user activity.
> 
> That data would only be calculated correctly if the user uses the keyboard 
> interfase ?

It'd be really hard to gather this data accurately otherwise.  Mouse
based attention gathering techniques cannot be assumed to be reliable.

[Fofredux-devel] Devs assigned

[Andrew T. (nilspace) <nil...@us...>]

Hi all,
I've added Carlos & Kevin to the FoFRedux developers. You will be able
to check in and out now.

I've also assigned your respective tasks. Carlos, can you apply the
timestamp patch of yours? Also, Kevin, I think you mentioned you could
add tags?

Andy

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

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] beta v0.2 ready for testing

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

I think what I'm trying to say is tags are great - but are often too
explicit/small. For example, in my del.icio.us tags, I tend to have 3
or 4 bookmarks with any 1 tag. This makes them not that useful for
broad readings. I want more than just "cocoa" or "auto" tags. I want
"Politics" or "Technology".

I guess I'm just being too picky. Using tags in general would let me
go ahead and mark these broad generalizations for feeds and then read
a group of feeds based on "Technology" etc. So I think just supporting
tags is fine (albeit much harder).

What about the problem of "tag soup". People are very liberal with
tagging - and not always consistent either. Any suggestions?

Andy
nilspace

On 11/21/05, Kevin <ke...@dr...> wrote:
>            Andrew Turner wrote:
>
> >   I can see the benefits of having a user-defined taxonomy of tags. For
> >one thing, many feeds supply the blog's categories for the item - so we
> >could optionally apply these tags by default.  I would also like to keep
> >categories for a more general genre type of organization of feeds. For
> >example, I want to pull up all of my "technology" feeds, but may not wan=
t
> >to have that as a tag (where tags would be like mac, programming, php).
> >But maybe not.
>
> Let me see if I understand you correctly.  You see categories as either:
>
> 1) a completely separate concept separate of tags.  (containers are used
> with feeds only, tags are used with items only)
> 2) a higher level grouping or container of tags.
>
> I really don't have an opinion either way.  I *can* say that implementing
> option #1 will be much easier.
>
> --
> Kevin
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick
> _______________________________________________
> 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
idealistic technocrat

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] beta v0.2 ready for testing

[Kevin <ke...@dr...>]

           Andrew Turner wrote:

>   I can see the benefits of having a user-defined taxonomy of tags. For
>one thing, many feeds supply the blog's categories for the item - so we
>could optionally apply these tags by default.  I would also like to keep
>categories for a more general genre type of organization of feeds. For
>example, I want to pull up all of my "technology" feeds, but may not wan=
t
>to have that as a tag (where tags would be like mac, programming, php).
>But maybe not.

Let me see if I understand you correctly.  You see categories as either:

1) a completely separate concept separate of tags.  (containers are used
with feeds only, tags are used with items only)
2) a higher level grouping or container of tags.

I really don't have an opinion either way.  I *can* say that implementing
option #1 will be much easier.

--=20
Kevin

[Fofredux-devel] Adding Developers to fofredux

[Andrew T. (nilspace) <nil...@us...>]

If you are interested in getting Dev access to fofredux (and therefore
assigned patches, bugs, features et al ;) drop me your SourceForge id

On a side note, sourceforge recently redid their layout and it looks
pretty nice.

Andy
nilspace

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

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] beta v0.2 ready for testing

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

Ok - fixed the bugs that cropped up for you. If you could please test it ag=
ain.

I, or someone, still needs to apply the timestamp patch - b/c the
date/times aren't really working.

I can see the benefits of having a user-defined taxonomy of tags. For
one thing, many feeds supply the blog's categories for the item - so
we could optionally apply these tags by default.

I would also like to keep categories for a more general genre type of
organization of feeds. For example, I want to pull up all of my
"technology" feeds, but may not want to have that as a tag (where tags
would be like mac, programming, php). But maybe not.

If we are going to have tags - that iwll be a large infrastructure
addition. For one thing, will need to begin by filling out the
tag-item table, and then pulling this extra tables into all of the
functions, etc. Anyone want to sign-up to implement tags? :)

Andy

On 11/19/05, Kevin <ke...@dr...> wrote:
> Benjamin Stewart wrote:
>
> >On Fri, Nov 18, 2005 at 11:32:24PM -0500, Andrew Turner wrote:
> >
> >
> >>Thanks for the bug report Kevin - I will fix those this weekend and do
> >>a checkin.
> >>
> >>Any more thoughts on categories/tagging?
> >>
> >>
> >
> >Yes:  the short version is, I think feed categories should be handled by
> >tagging, and an ability to tag individual posts should exist via the
> >same mechanism.  Regardless of whether or not we're going to walk down
> >the reblog path, I think the ability for a user to tag specific entries
> >for future reference will add additional functionality above and beyond
> >the ability to "save / mark / star / whatever you want to call it"
> >entries.
> >
> >Re-using the same mechanism for doing feed categories seems only
> >logical.
> >
> >--Benjy
> >
> >
> It sounds like category vs. tag are very similar in functionality.   To
> me, it sounds like category is a specialized type (subtype) of a tag.
>
> I guess the question is:  What do categories give use that tagging does
> not.  Is there any feature/behavior a category must do that can not be
> naturally supported by tags.
>
> I can think of one case where using tags on items as "categories" could
> break or at least require extra work to get the functionality to work as
> expected.  What happens when a user decides to change the category(s)
> for a feed.  If we are tagging new items to a category when they are
> inserted, what about all the old items already in the db.  All those
> items would have to be updated to reflect the change in category for the
> feed they are in.
>
> --Kevin
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> 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
idealistic technocrat

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] beta v0.2 ready for testing

[Kevin <ke...@dr...>]

Benjamin Stewart wrote:

>On Fri, Nov 18, 2005 at 11:32:24PM -0500, Andrew Turner wrote:
>  
>
>>Thanks for the bug report Kevin - I will fix those this weekend and do
>>a checkin.
>>
>>Any more thoughts on categories/tagging?
>>    
>>
>
>Yes:  the short version is, I think feed categories should be handled by
>tagging, and an ability to tag individual posts should exist via the
>same mechanism.  Regardless of whether or not we're going to walk down
>the reblog path, I think the ability for a user to tag specific entries
>for future reference will add additional functionality above and beyond
>the ability to "save / mark / star / whatever you want to call it"
>entries.
>
>Re-using the same mechanism for doing feed categories seems only
>logical.
>
>--Benjy
>  
>
It sounds like category vs. tag are very similar in functionality.   To 
me, it sounds like category is a specialized type (subtype) of a tag.

I guess the question is:  What do categories give use that tagging does 
not.  Is there any feature/behavior a category must do that can not be 
naturally supported by tags.

I can think of one case where using tags on items as "categories" could 
break or at least require extra work to get the functionality to work as 
expected.  What happens when a user decides to change the category(s) 
for a feed.  If we are tagging new items to a category when they are 
inserted, what about all the old items already in the db.  All those 
items would have to be updated to reflect the change in category for the 
feed they are in.

--Kevin

Re: [Fofredux-devel] beta v0.2 ready for testing

[Benjamin S. <bs...@cr...>]

On Fri, Nov 18, 2005 at 11:32:24PM -0500, Andrew Turner wrote:
> Thanks for the bug report Kevin - I will fix those this weekend and do
> a checkin.
> 
> Any more thoughts on categories/tagging?

Yes:  the short version is, I think feed categories should be handled by
tagging, and an ability to tag individual posts should exist via the
same mechanism.  Regardless of whether or not we're going to walk down
the reblog path, I think the ability for a user to tag specific entries
for future reference will add additional functionality above and beyond
the ability to "save / mark / star / whatever you want to call it"
entries.

Re-using the same mechanism for doing feed categories seems only
logical.

--Benjy

Re: [Fofredux-devel] beta v0.2 ready for testing

[Carlos K. <ck...@gm...>]

El S=E1bado, 19 de Noviembre de 2005 00:21, Kevin escribi=F3:
> A few issues.
>
> 1) I got an error on install.php where it was trying to create a table
> with an empty name.  I had to add this line to init.php.
> $FOF_X_CATEGORY_FEED_TABLE =3D FOF_X_CATEGORY_FEED_TABLE;

At installing type i've also had problems with the default values for some=
=20
fields, i solved it with this change:=20

$query =3D <<<EOQ
 CREATE TABLE `$FOF_X_CATEGORY_FEED_TABLE` (
   `id` int(11) NOT NULL auto_increment,
=2D  `category_id` int(11) NOT NULL default '',
=2D  `feed_id` int(11) NOT NULL default '',
+  `category_id` int(11) NOT NULL default 0,
+  `feed_id` int(11) NOT NULL default 0,
   PRIMARY KEY  (`id`)
 ) TYPE=3DMyISAM;
 EOQ;

Carlos.

=2D-=20
Web Site: http://www.ckozus.com.ar
Blog: http://www.ckozus.com.ar/blog
Mis links: http://del.icio.us/ckozus

Re: [Fofredux-devel] beta v0.2 ready for testing

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

Thanks for the bug report Kevin - I will fix those this weekend and do
a checkin.

Any more thoughts on categories/tagging?

Andy

On 11/18/05, Kevin <ke...@dr...> wrote:
> A few issues.
>
> 1) I got an error on install.php where it was trying to create a table
> with an empty name.  I had to add this line to init.php.
> $FOF_X_CATEGORY_FEED_TABLE =3D FOF_X_CATEGORY_FEED_TABLE;
>
> 2) Now i get this error when trying to view index.php
> Warning: main(panel.php) [function.main
> <http://www/%7Ekev/fofr_cvs/function.main>]: failed to open stream: No
> such file or directory in /data1/home/kev/WWW/fofr_cvs/index.php on line =
23
>
> 3) on this page:  menu.php?view=3Dframes,   The add feeds link has a
> typeo.  '&' when it should be '?'
>
> 4) when I click on "view today's items"  I get this error:
> Cannot query database. Have you run install.php
> <http://www/%7Ekev/fofr_cvs/install.php>? MySQL says: Unknown column
> 'category_description' in 'field list'
>
> 5) when clicking any links in the upper left frame, the target is that
> frame instead of the right frame.
>
> Looks good, thought.
>
> -Kevin
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> 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
idealistic technocrat

Photos - http://flickr.com/photos/ajturner
Travel   - http://highearthorbit.com/projects/location/

Re: [Fofredux-devel] beta v0.2 ready for testing

[Kevin <ke...@dr...>]

A few issues.

1) I got an error on install.php where it was trying to create a table 
with an empty name.  I had to add this line to init.php.
$FOF_X_CATEGORY_FEED_TABLE = FOF_X_CATEGORY_FEED_TABLE;

2) Now i get this error when trying to view index.php
Warning: main(panel.php) [function.main 
<http://www/%7Ekev/fofr_cvs/function.main>]: failed to open stream: No 
such file or directory in /data1/home/kev/WWW/fofr_cvs/index.php on line 23

3) on this page:  menu.php?view=frames,   The add feeds link has a 
typeo.  '&' when it should be '?'

4) when I click on "view today's items"  I get this error:
Cannot query database. Have you run install.php 
<http://www/%7Ekev/fofr_cvs/install.php>? MySQL says: Unknown column 
'category_description' in 'field list'

5) when clicking any links in the upper left frame, the target is that 
frame instead of the right frame.

Looks good, thought.

-Kevin

Re: Re: [Fofredux-devel] beta v0.2 ready for testing

[Carlos K. <ck...@gm...>]

andy said:
>Yes - the current CVS checkin doesn't have any of patches applied
toit. Devs should now go through and add these patches, etc. and
checkback in...

Should I send the patch to this list or add it in the Patches section
of the site ?

> To review my suggestion:
> 3) mark all articles that aren't "flagged" as "read"

An option to mark as read all articles that are flagged would do too.

A question: What is the difference between your approach to categorize
feeds and tagging ?
I'd like to clarify that i was talking about tagging feeds mainly,
although articles could be tagged too.

Another idea, what do you think about internationalization ? I could
easily translate the interface to spanish.