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

Re: [Fofredux-devel] Version 0.4

[khaled A. A. <bro...@gm...>]

I'll explain what my thinking regarding the action tickbox was all about. I=
t
really is a question of how far we actually want to go down this particular
road.

So here are the options:
1. On the sidebar we have the option to actually select all, unselect, mark
them as read and then mark them as unread. The action ticklist is there to
choose inidivdual items off or on the list that we would like to mark as
read or whatever.

2. We could then go one step further and have individual read tick boxes in
the full items on the right hand side? They could all be done in that light
blue colour and once the check box has been ticked then they turn the grey
colour shown? It would be very easy to edit them as a 'paged', so that work=
s
very well as well. This might neeed some funky ajax going for it (or maybe
not).

3. Regarding marking something and updating an individual feed, we're
'marking' them works best with the action button. Now Kevin you mentioned
saving or unsaving them...we have that functionality? Saving individual
feeds would be very nice. I'd also like a history view as well (this idea i=
s
stolen directly from Feedlounge to be honest, but it works well).

4. One final point about the Updating on each individual feed, I'll include
another icon in there, because it is a good idea to give you full control o=
f
each feed.

5. I think putting the total number of feeds in the admin panel works bette=
r
because that's also where we'll be dealing with the actual editing of the
feeds that it makes sense to put that information there.

6. Finally I'll be looking to not having any links in the sidebar. The
entire line will be a link of sorts that opens up the individual feeds on
the right hand side. You control the links from above and the update icon
discussed above and the action tickbox. I think that makes it less cluttere=
d
and more intuative to the user. It'll become clearer when I sort out my nex=
t
iteration

Which will hopefully come later on this evening.




On 2/23/06, Kevin < ke...@dr...> wrote:
>
> khaled Abou Alfa wrote:
> > Tonight came fast didn't it :). As I was typing out the previous email
> > the ideas just kept coming and I haven't even had breakfast yet
> > (honestly this kind of inspiration is unprecedented), usually I'm
> > busting my head trying to work things out, but here's the latest
> > iteration.
> >
> > www.brokenkode.com/fofr/Version-0.4.jpg
> > < http://www.brokenkode.com/fofr/Version-0.4.jpg>
> >
> >
> > The changes include that the flag items has been changed to select
> > items. A check box now replaces the remove button which we can do
> > things like mark as read or whatever.
> >
> +1 on renaming the action from Flag to Select.   I'm not so sure about
> the action checkbox, thought.  I think the "m" and "u" links in the feed
> list should be added back in place of the action checkbox.  Perhaps as
> icons, instead of links.  (m =3D mark feed as read,  u =3D update feed)
>
> > New feeds are highlighted in bold. I'm still working on where to put
> > the total number of unread feeds. Maybe you're right Andrew, maybe the
> > solution is to have 10 unread items (total unread 220) or whatever.
> > I'll have a play around with that aspect.
> >
> For me, the total number of items in a feed is not that important.  I'm
> more interested in the unread count.  What if the total count was put in
> a title attribute that would show when you hover your mouse on the feed?
>
> > I've included an admin panel link, since that's where we'll store the
> > user information (password, login, email) and deleting feeds.
> >
> +1 on adding an admin page.   Currently the un-framed (Panel) view also
> has links for admin functions. (import, export, edit options, etc)  I
> think it's better to move the admin functions to it's own view.
>
>
>
> -------------------------------------------------------
> 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
>

Re: [Fofredux-devel] project developer guide

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

Kevin wrote:
> Andrew Turner (nilspace) wrote:
>
>> Looks great! I made editing changes (line wraps, spelling). Also you
>> specified that you cannot merge to a stable branch - yet there are
>> bugfixes. A bugfix may entail a 'merge', right?
>>
>>  
>>
> Yes, a bugfix will mandate a merge, but the opposite of what you are 
> thinking.  The bugfix should be commited to the stable branch first, 
> then the change should be merged onto HEAD.   This will avoid 
> inadvertently introducing additional bugs/features/etc that may exist 
> on HEAD at the time of the merge.
>> Also, we probably want a section on dev practices within the project
>> itself. Architecture, function and variable naming conventions, etc.
>> How we suggest modifying/patching.  When/if we have a "plugin" arch,
>> how to write a plugin.
>>  
>>
> All good stuff to have in there.  Another thing I am trying to figure 
> out is how to correctly use the vendor branch of CVS for 3rd party 
> stuff we include with fofr. (magpierss, etc)  This will avoid the 
> problem we had where a local patch was overwritten by an upgrade of 
> the 3rd party source.
So, I got around the proper usage of "cvs import".  I updated the 
developer guide to include the procedure to update the bundled third 
party software.  (Magpierss and ADODB Lite)   This should be followed 
for anything else we bundle with our distribution. (AJAX lib, etc)

-Kevin

Re: [Fofredux-devel] Version 0.4

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

khaled Abou Alfa wrote:
> Tonight came fast didn't it :). As I was typing out the previous email 
> the ideas just kept coming and I haven't even had breakfast yet 
> (honestly this kind of inspiration is unprecedented), usually I'm 
> busting my head trying to work things out, but here's the latest 
> iteration.
>
> www.brokenkode.com/fofr/Version-0.4.jpg 
> <http://www.brokenkode.com/fofr/Version-0.4.jpg>
>
>
> The changes include that the flag items has been changed to select 
> items. A check box now replaces the remove button which we can do 
> things like mark as read or whatever.
>
+1 on renaming the action from Flag to Select.   I'm not so sure about 
the action checkbox, thought.  I think the "m" and "u" links in the feed 
list should be added back in place of the action checkbox.  Perhaps as 
icons, instead of links.  (m = mark feed as read,  u = update feed)

> New feeds are highlighted in bold. I'm still working on where to put 
> the total number of unread feeds. Maybe you're right Andrew, maybe the 
> solution is to have 10 unread items (total unread 220) or whatever. 
> I'll have a play around with that aspect.
>
For me, the total number of items in a feed is not that important.  I'm 
more interested in the unread count.  What if the total count was put in 
a title attribute that would show when you hover your mouse on the feed?  

> I've included an admin panel link, since that's where we'll store the 
> user information (password, login, email) and deleting feeds.
>
+1 on adding an admin page.   Currently the un-framed (Panel) view also 
has links for admin functions. (import, export, edit options, etc)  I 
think it's better to move the admin functions to it's own view.

[Fofredux-devel] Version 0.4

[khaled A. A. <bro...@gm...>]

Tonight came fast didn't it :). As I was typing out the previous email the
ideas just kept coming and I haven't even had breakfast yet (honestly this
kind of inspiration is unprecedented), usually I'm busting my head trying t=
o
work things out, but here's the latest iteration.

www.brokenkode.com/fofr/Version-0.4.jpg


The changes include that the flag items has been changed to select items. A
check box now replaces the remove button which we can do things like mark a=
s
read or whatever.

New feeds are highlighted in bold. I'm still working on where to put the
total number of unread feeds. Maybe you're right Andrew, maybe the solution
is to have 10 unread items (total unread 220) or whatever. I'll have a play
around with that aspect.

When reading any particular link we also get the background highlighted as
indicated. It's a good visual indicator of what we are reading.

Reading preferences have been flipped over to the other side, since it make=
s
more sense there.

I've included an admin panel link, since that's where we'll store the user
information (password, login, email) and deleting feeds.

Regarding the categories and tags links in the main items, yes we'd make
them wrap at 50% of the length or something like that. I guess more often
than not this won't be an issue. I usuaully put 3 or 4 tags, and maybe a
couple of categories however for those that go a bit mental that's cool as
well. Putting them underneath each other for the sake of a couple of times
isn't really worth it IMHO, but that can easily be modified to do things

Re: [Fofredux-devel] Version 0.2

[khaled A. A. <bro...@gm...>]

That's one indepth review there Andrew :). It's a pleasure to be part of
this as I really see a hell of a lot of future in it, (and we all know the
future is open source).

I'll address the update/flag/read changes soon as I've had a look and I
realise how this could all work now. versio 0.4 will come later on this
evening.

With regards to Ajax and what FOFr should be, I think it should be good at
what it does, and not try hard to be everything else. It's a feed reader
first then everything else second. So I think we should try and make it the
best looking, best functioning one out there. I think once a few issues are
addressed ten it's easily on it's way there.

With regards to Ajax, I hope everyone realises that I am not a coder :). I
kinda know what is achieveable (mostly although because I've not hacked awa=
y
at any javascript libaries I'm not 100% sure in this department) and what
isn't. Once I've gotten a couple of more screenshots under the belt
hopefully it'll become clear what I'm thinking. It's not ajax or javascript
for that sake, but rather to enhance the usability of the application.

To be fair it seem that anything I come up with you guys will probably be
able to bat it out of there. Once again just want to say that it's great
getting involved with this project.

On 2/23/06, Andrew Turner (nilspace) <nil...@us...> wrote=
:
>
> On 2/22/06, Kevin <ke...@dr...> wrote:
> > khaled Abou Alfa wrote:
> > > I can guarantee you that this almost never happens, but tonight I
> > > really had a lot of inspiration for this project. Everything just fel=
l
> > > into place pretty nicely so here is the mockup that is actually prett=
y
> > > close to where I was originally thinking for fofredux.
> > >
> > > here's where to download it:
> > > www.brokenkode.com/fofr/Version-0.3.jpg
> > > <http://www.brokenkode.com/fofr/Version-0.3.jpg>
> > >
> > > Top Navigation.
> > > The things that new users will be interested in is adding feeds.
> > > That's why it's the very first thing in the top left hand corner.
> > > Since it's good to keep the place nice and tidy, that category and ta=
g
> > > links are next to that. For the icons I've used those provided by
> > > famfamfam ( http://www.famfamfam.com/) which I really like and haven'=
t
> > > used in a project yet. Generally open source applications seem to lac=
k
> > > these and yet they really will make everything pop at the user and
> > > make it that much more instinctive. I can play around with the colour
> > > of the add feed icon without much problems, if anyone's got an issue
> > > with the rest of the icons just shout out.
> > >
> > Excellent work.  This is the professional look FoFR is lacking.  We hav=
e
> > decent features but not UI to express it.
> >
> Agreed - excellent start Khaled. I like the simple look, yet
> effectiveness of the interface.  Icons are definitely a nice little
> touch to an application over just text links to add some quick UI
> reference for users to identify and use.
>
> A couple of notes:
> Sidebar:
> * 'feeds' column should really have '10 unread items' and I think
> should possibly have 10 unread (220 total) or something. Maybe not, as
> seeing the undaunting '10' is happier than seeing 220 :) But either
> way the naming scheme is:
>   fofredux has feeds
>   feeds have items
>   feeds belong to categories
>   items have tags
> maybe that simple layout of naming hierarchies can induce some ideas
> in your great UI schema.
>
> > > Logging in.
> > > To me this is the single most important feature that needs to be adde=
d
> > > to fofredux. Having a proper login feature in here. I will be tacklin=
g
> > > this area once I've got this page and adding elements (such as feeds
> > > and categories done). Logging out is in the top right hand corner as
> > > is standard convention.
> Yes, a user system appears to be a definitely forward looking future.
> I believe currently all users are "1-up" personal hackers/enthusiats.
> but having the ability to provide your friends, family, groups, etc.
> with their own FoFR view would be great.
>
>
> > >
> > > Secondary Navigation:
> > > This one here is how we're viewing the feeds etc. Slightly
> > > understated, but that's ok I guess as it something that ideally shoul=
d
> > > be cached (not the case right now I guess, or am I wrong?).
> > > Can I ask what flagging items actually does? I've not been able to
> > > work that one out, so a little help in that direction would be much
> > > appreciated.
> > >
> > Flagging items means identifying a group of items in order to perform
> > some operation on them.   This could be one of the following:
> >
> > *mark as read
> > *mark as unread
> > *mark as saved
> > *mark as unsaved
> > *add a tag to the item
> >
> > The actual "flag" is the checkbox in the item within the view.  The
> > links for "flag all" and "unflag all" are just helpers that check or
> > uncheck every item in the page.
>
> I think you should separate the "view new items    view today's items,
> etc." from the "Flag All items" The first 3 are changing "what" I'm
> seeing and the "Flag *" and "Mark As" are doing something *to* the
> items I'm currently seeing.
>
>
> > > Links:
> > > You'll notice two distinct colours for the links. The first being in
> > > aqua blue. These are for links that are effectively OUTSIDE the
> > > programme. The magenta links are for all the internal areas.
> > >
>
> Great separation - ala wiki's with the "out" icon for exteranl links too.
>
> > > Sidebar: This one has the most changes that will need to be discussed
> > > further with everyone. I like the age of the feed column, need the
> > > name of the site where the feed is coming from. And then to make
> > > reading easier and also make it clear that this is what people should
> > > be clicking on if they want to read anything from this particular sit=
e
> > > is the feeds column.
> > >
> > > I've made the remove column a bit special by making it into an icon
> here.
>
> I think we should remove the "remove" column as it really is "too
> accessible" from this view. Any modifying of feeds (name, delete,
> etc.) should happen from the admin panel, and not possible from just
> clicking in the view sidebar over by several pixels. I think the
> "remove" column could be replaced with the "update" column mentioned
> by Kevin.
>
> > > Okay that's it for tonight. Do we have a javascript/XMLHttpRequest
> > > guru on board? The reason I ask is because I've got a pretty cool ide=
a
> > > of how we can get the add feed, categories and tags sorted out but I
> > > don't want to jump the gun. The current changes are a simple question
> > > of changing the css file, so it's not major but what I've got in mind
> > > will require some programming kung-fu.
> > >
> > I think we agree that implementing some features using AJAX is a good
> > thing.  None of us has claimed the title of "guru" yet.(certainly not
> > me)  Whatever is decided.  converting the action to AJAX shouldn't be
> > that difficult.
>
> I've implemented AJAX on several other projects but have held off on
> FoFRedux b/c it hasn't been clear what our goal is. Are we a simple,
> no-nonsense feedreader, a customizable, solid good code one, just
> another one written in PHP, one that offers new features such as
> tagging, geotagging/mapping, social syncronization, independent
> install on personal servers (all of which are pretty cool and not very
> well done by others), or what?
>
> I have a lot of experience with the scriptaculous/prototype libraries,
> but I think Moo.fx might be a better, lightweight, option. Really, the
> functionality we need are: marking, then hiding feeds are
> read/unread/tagged; updating feeds; and perhaps a slick dynamic,
> live-preview, search. Khaled, if  you have experience/expertise in
> Ajax, I definitely would like your suggestions on what would be
> simple, yet effective, there too.
>
> I've read the reviews Katie posted, as well as some others I've
> crossed. They tend to diss Gregarious and others for having a little
> heavy handed Ajax for the sake of Ajax, and I really don't think we
> want that.
>
> Ok - so a couple of other things to end the email:
> * Need to add a "flag" area to each item's header. Even with ajax,
> each item should have a "mark as read" or similar icon/link for either
> flagging or asyncronously marking as read and then hiding
> * What happens when categories/tags are longer than your example? Does
> the css handle them wrapping nicely?
> * Search may have a drop down for doing a search on criteria: Search
> this feed, search new, search using "cool design" + my query, etc?
>
> Looks really great Khaled, thanks for the infusion of design and art
> into our otherwise very geeky/techical app ;)
>
> Andrew
>
> --
> Andrew Turner
> ajt...@hi...        42.4266N x 83.4931W
> http://highearthorbit.com              Northville, Michigan, USA
>
>
> -------------------------------------------------------
> 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
>

Re: [Fofredux-devel] Version 0.2

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

On 2/22/06, Kevin <ke...@dr...> wrote:
> khaled Abou Alfa wrote:
> > I can guarantee you that this almost never happens, but tonight I
> > really had a lot of inspiration for this project. Everything just fell
> > into place pretty nicely so here is the mockup that is actually pretty
> > close to where I was originally thinking for fofredux.
> >
> > here's where to download it:
> > www.brokenkode.com/fofr/Version-0.3.jpg
> > <http://www.brokenkode.com/fofr/Version-0.3.jpg>
> >
> > Top Navigation.
> > The things that new users will be interested in is adding feeds.
> > That's why it's the very first thing in the top left hand corner.
> > Since it's good to keep the place nice and tidy, that category and tag
> > links are next to that. For the icons I've used those provided by
> > famfamfam ( http://www.famfamfam.com/) which I really like and haven't
> > used in a project yet. Generally open source applications seem to lack
> > these and yet they really will make everything pop at the user and
> > make it that much more instinctive. I can play around with the colour
> > of the add feed icon without much problems, if anyone's got an issue
> > with the rest of the icons just shout out.
> >
> Excellent work.  This is the professional look FoFR is lacking.  We have
> decent features but not UI to express it.
>
Agreed - excellent start Khaled. I like the simple look, yet
effectiveness of the interface.  Icons are definitely a nice little
touch to an application over just text links to add some quick UI
reference for users to identify and use.

A couple of notes:
Sidebar:
 * 'feeds' column should really have '10 unread items' and I think
should possibly have 10 unread (220 total) or something. Maybe not, as
seeing the undaunting '10' is happier than seeing 220 :) But either
way the naming scheme is:
  fofredux has feeds
  feeds have items
  feeds belong to categories
  items have tags
maybe that simple layout of naming hierarchies can induce some ideas
in your great UI schema.

> > Logging in.
> > To me this is the single most important feature that needs to be added
> > to fofredux. Having a proper login feature in here. I will be tackling
> > this area once I've got this page and adding elements (such as feeds
> > and categories done). Logging out is in the top right hand corner as
> > is standard convention.
Yes, a user system appears to be a definitely forward looking future.
I believe currently all users are "1-up" personal hackers/enthusiats.
but having the ability to provide your friends, family, groups, etc.
with their own FoFR view would be great.


> >
> > Secondary Navigation:
> > This one here is how we're viewing the feeds etc. Slightly
> > understated, but that's ok I guess as it something that ideally should
> > be cached (not the case right now I guess, or am I wrong?).
> > Can I ask what flagging items actually does? I've not been able to
> > work that one out, so a little help in that direction would be much
> > appreciated.
> >
> Flagging items means identifying a group of items in order to perform
> some operation on them.   This could be one of the following:
>
> *mark as read
> *mark as unread
> *mark as saved
> *mark as unsaved
> *add a tag to the item
>
> The actual "flag" is the checkbox in the item within the view.  The
> links for "flag all" and "unflag all" are just helpers that check or
> uncheck every item in the page.

I think you should separate the "view new items    view today's items,
etc." from the "Flag All items" The first 3 are changing "what" I'm
seeing and the "Flag *" and "Mark As" are doing something *to* the
items I'm currently seeing.


> > Links:
> > You'll notice two distinct colours for the links. The first being in
> > aqua blue. These are for links that are effectively OUTSIDE the
> > programme. The magenta links are for all the internal areas.
> >

Great separation - ala wiki's with the "out" icon for exteranl links too.

> > Sidebar: This one has the most changes that will need to be discussed
> > further with everyone. I like the age of the feed column, need the
> > name of the site where the feed is coming from. And then to make
> > reading easier and also make it clear that this is what people should
> > be clicking on if they want to read anything from this particular site
> > is the feeds column.
 > >
> > I've made the remove column a bit special by making it into an icon her=
e.

I think we should remove the "remove" column as it really is "too
accessible" from this view. Any modifying of feeds (name, delete,
etc.) should happen from the admin panel, and not possible from just
clicking in the view sidebar over by several pixels. I think the
"remove" column could be replaced with the "update" column mentioned
by Kevin.

> > Okay that's it for tonight. Do we have a javascript/XMLHttpRequest
> > guru on board? The reason I ask is because I've got a pretty cool idea
> > of how we can get the add feed, categories and tags sorted out but I
> > don't want to jump the gun. The current changes are a simple question
> > of changing the css file, so it's not major but what I've got in mind
> > will require some programming kung-fu.
> >
> I think we agree that implementing some features using AJAX is a good
> thing.  None of us has claimed the title of "guru" yet.(certainly not
> me)  Whatever is decided.  converting the action to AJAX shouldn't be
> that difficult.

I've implemented AJAX on several other projects but have held off on
FoFRedux b/c it hasn't been clear what our goal is. Are we a simple,
no-nonsense feedreader, a customizable, solid good code one, just
another one written in PHP, one that offers new features such as
tagging, geotagging/mapping, social syncronization, independent
install on personal servers (all of which are pretty cool and not very
well done by others), or what?

I have a lot of experience with the scriptaculous/prototype libraries,
but I think Moo.fx might be a better, lightweight, option. Really, the
functionality we need are: marking, then hiding feeds are
read/unread/tagged; updating feeds; and perhaps a slick dynamic,
live-preview, search. Khaled, if  you have experience/expertise in
Ajax, I definitely would like your suggestions on what would be
simple, yet effective, there too.

I've read the reviews Katie posted, as well as some others I've
crossed. They tend to diss Gregarious and others for having a little
heavy handed Ajax for the sake of Ajax, and I really don't think we
want that.

Ok - so a couple of other things to end the email:
* Need to add a "flag" area to each item's header. Even with ajax,
each item should have a "mark as read" or similar icon/link for either
flagging or asyncronously marking as read and then hiding
* What happens when categories/tags are longer than your example? Does
the css handle them wrapping nicely?
* Search may have a drop down for doing a search on criteria: Search
this feed, search new, search using "cool design" + my query, etc?

Looks really great Khaled, thanks for the infusion of design and art
into our otherwise very geeky/techical app ;)

Andrew

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

Re: [Fofredux-devel] Version 0.2

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

khaled Abou Alfa wrote:
> I can guarantee you that this almost never happens, but tonight I 
> really had a lot of inspiration for this project. Everything just fell 
> into place pretty nicely so here is the mockup that is actually pretty 
> close to where I was originally thinking for fofredux.
>
> here's where to download it:
> www.brokenkode.com/fofr/Version-0.3.jpg 
> <http://www.brokenkode.com/fofr/Version-0.3.jpg>
>
> Top Navigation.
> The things that new users will be interested in is adding feeds. 
> That's why it's the very first thing in the top left hand corner. 
> Since it's good to keep the place nice and tidy, that category and tag 
> links are next to that. For the icons I've used those provided by 
> famfamfam ( http://www.famfamfam.com/) which I really like and haven't 
> used in a project yet. Generally open source applications seem to lack 
> these and yet they really will make everything pop at the user and 
> make it that much more instinctive. I can play around with the colour 
> of the add feed icon without much problems, if anyone's got an issue 
> with the rest of the icons just shout out.
>
Excellent work.  This is the professional look FoFR is lacking.  We have 
decent features but not UI to express it.

> Logging in.
> To me this is the single most important feature that needs to be added 
> to fofredux. Having a proper login feature in here. I will be tackling 
> this area once I've got this page and adding elements (such as feeds 
> and categories done). Logging out is in the top right hand corner as 
> is standard convention.
>
> Secondary Navigation:
> This one here is how we're viewing the feeds etc. Slightly 
> understated, but that's ok I guess as it something that ideally should 
> be cached (not the case right now I guess, or am I wrong?).
> Can I ask what flagging items actually does? I've not been able to 
> work that one out, so a little help in that direction would be much 
> appreciated.
>
Flagging items means identifying a group of items in order to perform 
some operation on them.   This could be one of the following:

*mark as read
*mark as unread
*mark as saved
*mark as unsaved
*add a tag to the item

The actual "flag" is the checkbox in the item within the view.  The 
links for "flag all" and "unflag all" are just helpers that check or 
uncheck every item in the page.

> Links:
> You'll notice two distinct colours for the links. The first being in 
> aqua blue. These are for links that are effectively OUTSIDE the 
> programme. The magenta links are for all the internal areas.
>
> Sidebar: This one has the most changes that will need to be discussed 
> further with everyone. I like the age of the feed column, need the 
> name of the site where the feed is coming from. And then to make 
> reading easier and also make it clear that this is what people should 
> be clicking on if they want to read anything from this particular site 
> is the feeds column.
>
> I've made the remove column a bit special by making it into an icon here.
>
> Now what you'll find is that the unmark column has been taken away. I 
> guess it could be added in there, but I simply don't want to clutter 
> everything. However if people think that this is an extremely 
> important feature I'm sure I can come up with an icon for it as well, 
> do people think that the big refresh button at the top is not enough?
>
I think the column for "u" is update.  That should be included.  Perhaps 
it is not needed in the framed view, but it should be included in the 
panel view.
> I'm missing the mark as read button (just noticed that) so I'll add it 
> into the next iteration.
>
> Meat and potatoes:
> Very simple layout. All the information located at the top, the actual 
> post located on the bottom. Clean and clear what everything is.
>
> Okay that's it for tonight. Do we have a javascript/XMLHttpRequest 
> guru on board? The reason I ask is because I've got a pretty cool idea 
> of how we can get the add feed, categories and tags sorted out but I 
> don't want to jump the gun. The current changes are a simple question 
> of changing the css file, so it's not major but what I've got in mind 
> will require some programming kung-fu.
>
I think we agree that implementing some features using AJAX is a good 
thing.  None of us has claimed the title of "guru" yet.(certainly not 
me)  Whatever is decided.  converting the action to AJAX shouldn't be 
that difficult.

Cheers,
    Kevin

[Fofredux-devel] Version 0.2

[khaled A. A. <bro...@gm...>]

I can guarantee you that this almost never happens, but tonight I really ha=
d
a lot of inspiration for this project. Everything just fell into place
pretty nicely so here is the mockup that is actually pretty close to where =
I
was originally thinking for fofredux.

here's where to download it:
www.brokenkode.com/fofr/Version-0.3.jpg

Top Navigation.
The things that new users will be interested in is adding feeds. That's why
it's the very first thing in the top left hand corner. Since it's good to
keep the place nice and tidy, that category and tag links are next to that.
For the icons I've used those provided by famfamfam (
http://www.famfamfam.com/) which I really like and haven't used in a projec=
t
yet. Generally open source applications seem to lack these and yet they
really will make everything pop at the user and make it that much more
instinctive. I can play around with the colour of the add feed icon without
much problems, if anyone's got an issue with the rest of the icons just
shout out.

Logging in.
To me this is the single most important feature that needs to be added to
fofredux. Having a proper login feature in here. I will be tackling this
area once I've got this page and adding elements (such as feeds and
categories done). Logging out is in the top right hand corner as is standar=
d
convention.

Secondary Navigation:
This one here is how we're viewing the feeds etc. Slightly understated, but
that's ok I guess as it something that ideally should be cached (not the
case right now I guess, or am I wrong?).
Can I ask what flagging items actually does? I've not been able to work tha=
t
one out, so a little help in that direction would be much appreciated.

Links:
You'll notice two distinct colours for the links. The first being in aqua
blue. These are for links that are effectively OUTSIDE the programme. The
magenta links are for all the internal areas.

Sidebar: This one has the most changes that will need to be discussed
further with everyone. I like the age of the feed column, need the name of
the site where the feed is coming from. And then to make reading easier and
also make it clear that this is what people should be clicking on if they
want to read anything from this particular site is the feeds column.

I've made the remove column a bit special by making it into an icon here.

Now what you'll find is that the unmark column has been taken away. I guess
it could be added in there, but I simply don't want to clutter everything.
However if people think that this is an extremely important feature I'm sur=
e
I can come up with an icon for it as well, do people think that the big
refresh button at the top is not enough?

I'm missing the mark as read button (just noticed that) so I'll add it into
the next iteration.

Meat and potatoes:
Very simple layout. All the information located at the top, the actual post
located on the bottom. Clean and clear what everything is.

Okay that's it for tonight. Do we have a javascript/XMLHttpRequest guru on
board? The reason I ask is because I've got a pretty cool idea of how we ca=
n
get the add feed, categories and tags sorted out but I don't want to jump
the gun. The current changes are a simple question of changing the css file=
,
so it's not major but what I've got in mind will require some programming
kung-fu.

Khaled
www.brokenkode.com

Re: [Fofredux-devel] Admin Panel Version 0.1

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

> I sent a previous email with a jpg of the current version I'm working o=
n
> for
> the panel, but since it's bigger than 40k it's waiting in the moderatio=
n
> queue. For all those wanting to check it out, get it from here:
>
> www.brokenkode.com/fofr/Version-0.1.jpg
>
> I know I promised this on Sunday, but life got in the way. Just to expl=
ain
> this is me just putting a few thoughts down. This is effectively just t=
o
> give everyone a teaser of sorts to know what to expect. If there's
> something
> you don't like that's cool, just flag it up. I fully expect to go throu=
gh
> many MANY alterations before we have out design set. As always with the=
se
> things, it's good to talk :). Colour wise I've chosen black and greys j=
ust
> because they're the most unobtrusive. I've got a couple of different
> colour
> schemes I want to go through but this is just to wet everyone's whisker=
s.
>

I like it.  The bar across the top with all the adminstrative tasks and
navigation links is nice.  It's compact which leaves more screen real
estate for actual content.


--=20
Kevin

[Fofredux-devel] Admin Panel Version 0.1

[khaled A. A. <bro...@gm...>]

I sent a previous email with a jpg of the current version I'm working on fo=
r
the panel, but since it's bigger than 40k it's waiting in the moderation
queue. For all those wanting to check it out, get it from here:

www.brokenkode.com/fofr/Version-0.1.jpg

I know I promised this on Sunday, but life got in the way. Just to explain
this is me just putting a few thoughts down. This is effectively just to
give everyone a teaser of sorts to know what to expect. If there's somethin=
g
you don't like that's cool, just flag it up. I fully expect to go through
many MANY alterations before we have out design set. As always with these
things, it's good to talk :). Colour wise I've chosen black and greys just
because they're the most unobtrusive. I've got a couple of different colour
schemes I want to go through but this is just to wet everyone's whiskers.

[Fofredux-devel] Design feedback: saved searches

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

I'm implementing the "saved searches" for FoFRedux and wanted to get
some feedback since I'm adding a database table.

There will be the following columns: id, name, search term. with a
future column perhaps for a foreign key of the user to whom the search
belongs.

The search term will be the actual php parameter string. E.g.
>> category=3D1,14,28&feed=3D8,14&term=3Dprius hack NOT breaks

this makes it very easy to use a search as it is a single DB select
and then applied directly to the URL wihtout more complex parsing of
terms each request of the search.

This may then get named: "Working Prius Hacks", An RSS feed would be
able to be gen'd or a view on this:

>> view.php?search=3D4

Also, a user can use this saved search as a basis for a new search criteria=
:
Search: free
using search: "Working Prius Hacks"

The UI will provide a user to checkbox select (or multi-select from a
list?) any categories, or feeds, and enter a complex search criteria.

Does this design seem to cover our desired features, now and for the
future (multi-users imparticular)? Should a user be able to search on
feed/item metadata (search for all items with dc:creator =3D "Bill
Gates" or geo: within bounds 50 miles of (30, -50.3)?


Andrew

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

Re: [Fofredux-devel] ADOdb Library Cross Site Scripting

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

Miles Beck wrote:
> Just an FYI so this can be upgraded if needed.
>
>
> http://www.gulftech.org/?node=research&article_id=00101-02182006
>
>   
We use ADODB Lite.   It's a leaner, faster version of ADODB.  It doesn't 
include the file 'adodb-pager.inc.php'.  So, I'm fairly certain we 
aren't affected by this XSS exploit.

-Kevin

[Fofredux-devel] ADOdb Library Cross Site Scripting

[Miles B. <mil...@gm...>]

Just an FYI so this can be upgraded if needed.


http://www.gulftech.org/?node=3Dresearch&article_id=3D00101-02182006

Re: [Fofredux-devel] Interface Design

[khaled A. A. <bro...@gm...>]

I have a lot of faith in this project. I can seriously seeing it being the
ultimate feedreader. Open source is the future and it's all going to be dow=
n
to collaborative effort. From my part I just intend to make things look
nicer. Make things look more functional to use, more intuative. I'm actuall=
y
working on this this weekend so everyone should have a clue about where I'm
coming from by the end of the weekend.

The idea is just to put things in a particular order and give fofredux it's
own distinct look (I'll say that currently I'm playing around with light
blue/green grey and pink as the colours of choice). You'll see where I'm
coming from soon. It's not going taking what we've got now to the next
level. I've got enough ideas.

As for themability, I'm all up for it, just want to make sure that fofredux
has it's own look that is the norm, that people can come to and judge from
day one before I jumping into changing it. It's going to happen for sure,
but for the average user they're going to be looking for something that
looks the part from the word go.

Effectively once the interface is done we won't really have to be dealing
with people talking about the interface..ever, at least that's the plan
anyway.


On 2/17/06, Andrew Turner (nilspace) <nil...@us...> wrote=
:
>
> Thanks for the info Katie - perhaps my screenshot with "A Christmas
> Gory" also gives an icky feeling. :) I'll get a more happy/better
> looking screenshot.
>
> But this is a very good point. Hopefully Khaled comes up with some
> nice design ideas.
>
> What about "themeability". Of course, it's all CSS and *hopefully*
> XHTML compliant (though I haven't checked), so themeability is "free".
> We should just come up with some examples, etc.
>
> But That doesn't address the overall navigation button/links which are
> growing rather large and scary looking. Gregarious uses tabs in the
> sidebar for selecting b/w Feed/Tags/Categories,. and generic top-line
> button bars.
>
> How much do we want to pull from other newsreaders? Any other
> suggestions? Bueller? :)
>
> Andrew
>
> On 2/17/06, Katie Bechtold <ka...@ho...> wrote:
> > On Thu, Feb 02, 2006 at 01:18:13PM -0500, Andrew Turner wrote:
> > > We definitely appreciate and welcome input for FoFRedux. I agree that
> > > the interface is getting a little mucky as we add more features. And
> > > our roadmap calls for more features that will need better placement,
> > > layout, etc.
> >
> > One of the weblogs I read had a post earlier this week asking for a
> > feed reader recommendation: http://joeshaw.org/2006/02/13/378
> > I was one of several respondents, and naturally I suggested
> > FoFRedux.
> >
> > Today there's an update wherein the author describes his experiences
> > trying out each of the suggestions: http://joeshaw.org/2006/02/17/379
> >
> > Here's what he had to say about FoFRedux:
> > "FoF Redux - I didn't even try this. It has the scariest [link to
> > http://fofredux.sourceforge.net/images/ViewFrames.jpg]
> > user-interface I've ever seen in a feed reader. I'm a tech guy,
> > I'm a hacker, but these days I just don't want to deal with
> > complicated software anymore."
> >
> > I'm sharing this here not to try to drum up a campaign to change
> > this guy's mind about FoFRedux, but rather to show what a potential
> > user thinks when he sees our user interface.  It's that bad.
> >
> > --
> > Katie Bechtold         http://hoteldetective.org/
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > _______________________________________________
> > 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
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> Fofredux-devel mailing list
> Fof...@li...
> https://lists.sourceforge.net/lists/listinfo/fofredux-devel
>

Re: [Fofredux-devel] Interface Design

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

Thanks for the info Katie - perhaps my screenshot with "A Christmas
Gory" also gives an icky feeling. :) I'll get a more happy/better
looking screenshot.

But this is a very good point. Hopefully Khaled comes up with some
nice design ideas.

What about "themeability". Of course, it's all CSS and *hopefully*
XHTML compliant (though I haven't checked), so themeability is "free".
We should just come up with some examples, etc.

But That doesn't address the overall navigation button/links which are
growing rather large and scary looking. Gregarious uses tabs in the
sidebar for selecting b/w Feed/Tags/Categories,. and generic top-line
button bars.

How much do we want to pull from other newsreaders? Any other
suggestions? Bueller? :)

Andrew

On 2/17/06, Katie Bechtold <ka...@ho...> wrote:
> On Thu, Feb 02, 2006 at 01:18:13PM -0500, Andrew Turner wrote:
> > We definitely appreciate and welcome input for FoFRedux. I agree that
> > the interface is getting a little mucky as we add more features. And
> > our roadmap calls for more features that will need better placement,
> > layout, etc.
>
> One of the weblogs I read had a post earlier this week asking for a
> feed reader recommendation: http://joeshaw.org/2006/02/13/378
> I was one of several respondents, and naturally I suggested
> FoFRedux.
>
> Today there's an update wherein the author describes his experiences
> trying out each of the suggestions: http://joeshaw.org/2006/02/17/379
>
> Here's what he had to say about FoFRedux:
> "FoF Redux - I didn't even try this. It has the scariest [link to
> http://fofredux.sourceforge.net/images/ViewFrames.jpg]
> user-interface I've ever seen in a feed reader. I'm a tech guy,
> I'm a hacker, but these days I just don't want to deal with
> complicated software anymore."
>
> I'm sharing this here not to try to drum up a campaign to change
> this guy's mind about FoFRedux, but rather to show what a potential
> user thinks when he sees our user interface.  It's that bad.
>
> --
> Katie Bechtold         http://hoteldetective.org/
>
>
>
>
> -------------------------------------------------------
> 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://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> 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

Re: [Fofredux-devel] Interface Design

[Katie B. <ka...@ho...>]

On Thu, Feb 02, 2006 at 01:18:13PM -0500, Andrew Turner wrote:
> We definitely appreciate and welcome input for FoFRedux. I agree that
> the interface is getting a little mucky as we add more features. And
> our roadmap calls for more features that will need better placement,
> layout, etc.

One of the weblogs I read had a post earlier this week asking for a
feed reader recommendation: http://joeshaw.org/2006/02/13/378
I was one of several respondents, and naturally I suggested
FoFRedux.

Today there's an update wherein the author describes his experiences
trying out each of the suggestions: http://joeshaw.org/2006/02/17/379

Here's what he had to say about FoFRedux:
"FoF Redux - I didn't even try this. It has the scariest [link to
http://fofredux.sourceforge.net/images/ViewFrames.jpg]
user-interface I've ever seen in a feed reader. I'm a tech guy,
I'm a hacker, but these days I just don't want to deal with
complicated software anymore."

I'm sharing this here not to try to drum up a campaign to change
this guy's mind about FoFRedux, but rather to show what a potential
user thinks when he sees our user interface.  It's that bad.

-- 
Katie Bechtold         http://hoteldetective.org/

Re: [Fofredux-devel] tagging question

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

Andrew Turner (nilspace) wrote:
> Kevin (and group) I was curious what the "Auto Tag" feature did or is
> supposed to do? I haven't poured through the code - so I was hoping
> you could provide some talk on how/what the current tagging
> architecture is like and what you see being changed in the future.
>   
Auto tagging is:
     Any category/tag type data available in the source RSS will be 
carried over as an FoFR tag when update runs.  Different rss feeds 
encode the categories differently.  I look in <category>, <dc><subject>, 
and <media><category>.(this last one is for Flicr tags)   For each 
category/tag found in the RSS, that tag is added to the item being 
processed.  If the tag name does not exist in FoFR, it is created on the 
fly.  Tag aliases are used to help cut down on "tag explosion".  An FoFR 
tag can have multiple names associated with it.  Example:  "PHP", "PhP", 
"Php", "my php stuff" can all be rewritten to the FoFR tag: "PHP")   The 
aliases are only used for auto tagging.
There are two fields in the feed table to support this:
*auto_tag*:  a boolean flag to enable auto tagging for that feed.  It is 
disabled by default.
*auto_tag_separator*:  Some feeds overload the value of <category> and 
<dc><subject> by throwing a comma or space separated list of values 
instead of including multiple instances of the element.  I can't 
autodetect which overloading format is used, so the user will have to 
configure it on a per-feed basis.  Most feeds use comma so that will be 
the default value.  Flicr and del.icio.us use a space separator.

I'm considering moving these to the config table instead.  It would make 
it easier to change the default value if need be.

50% of this is still in my head.  have a look at the fof_update_feed() 
function to see the code written so far.

> Also - we should start talking/thinking about v0.3 release, what that
> will entail (we've already pulled in some 0.4 features, but other 0.3
> features are further out). We've gotten a lot of new features since
> 0.2 and it might be nice to do a finish up of some of the bugs, QA and
> release.
>
> I know looking at my list, I have a bunch of bugs/features to
> squash/implement - and will try to get them out of the way this
> weekend.
>   

[Fofredux-devel] tagging question

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

Kevin (and group) I was curious what the "Auto Tag" feature did or is
supposed to do? I haven't poured through the code - so I was hoping
you could provide some talk on how/what the current tagging
architecture is like and what you see being changed in the future.

Also - we should start talking/thinking about v0.3 release, what that
will entail (we've already pulled in some 0.4 features, but other 0.3
features are further out). We've gotten a lot of new features since
0.2 and it might be nice to do a finish up of some of the bugs, QA and
release.

I know looking at my list, I have a bunch of bugs/features to
squash/implement - and will try to get them out of the way this
weekend.

Thanks team!
Andrew


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

Re: [Fofredux-devel] Interface Design

[khaled A. A. <bro...@gm...>]

Sorry Andrew, must have gotten inbetween the cracks (I've been getting
hammered by the spammers lately). I can definitely see where you're coming
from. Just thinking about this very briefly I don't think something like
this is a call for graphics and making it look pretty with loads of images.
I would try and make everything fit together in a logical order and would
only provide any sort of image if it was adding and contributing to the
usage of the thing.

This wouldn't be the first interface to a programme that I get down to
designing, as I'm currently involved with two others (one of which is
wordpress) and I can easily feed on the knownledge I've amassed from there.
Let me do a quick and ready sketch for everyone to have a look at (it won't
take long) to just put things in a slightly less haphazard fashion. Give it
a clear direction so to speak.

In terms of new features and whatnot I guess that will come out in the wash=
.
I'm just interested in using a feed aggregator that sits on my server that
looks and acts the part. I honestly believe that FOFR could become the
wordpress of aggregators and I'd honestly like it to look the part as well.

On 2/2/06, Andrew Turner <ajt...@hi...> wrote:
>
> Hi Khaled, I left a comment on your site. Maybe it didn't come through?
>
> We definitely appreciate and welcome input for FoFRedux. I agree that
> the interface is getting a little mucky as we add more features. And
> our roadmap calls for more features that will need better placement,
> layout, etc.
>
> However, there are probably a couple things to keep in mind, and
> should be laid out by the team for future design decisions. I
> personally picked up FoF because 1) the code was easy to understand
> and modify, 2) it had a simplified interface that allowed me to just
> *read* my news rather than ogle the UI and 3) the UI runs on my
> desktop, laptop, mobile phone, handheld devices, etc.
>
> I don't know if this is the case for all the devs/users, and we should
> start a discussion regarding this. There are already other feedreaders
> out there that do the full-on Ajax with silver bars, etc. (e.g.
> Gregarious, fitting name :). FoFRedux is part personal (and hopefully
> soon multi-user) feedreader, but also an aggregator (ergo the 'Feed
> On' part) to be used for providing feeds to weblogs, other users,
> screensavers, etc. So it's also a server-based 'utility'.
>
> Anyways, if anyone else wants to chime in, please do. And Khaled,
> perhaps you can discuss some of your ideas before doing mockups, just
> so we can all agree on the path we want FoFRedux to take.
>
> Thanks for the interest!
> Andrew
>
> On 2/2/06, khaled Abou Alfa <bro...@gm...> wrote:
> > Hey everyone, was wondering if anyone has decided to actually sort out
> the
> > interface design of the application? I'd be more than willing to jump
> with
> > two feet into this and start sending out mockups that people can commen=
t
> on.
> > Thoughts?
> >
> > Khaled
> > www.brokenkode.com
> >
>
>
> --
> Andrew Turner
> ajt...@hi...        42.4266N x 83.4931W
> http://highearthorbit.com              Northville, Michigan, USA
>

Re: [Fofredux-devel] Interface Design

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

Hi Khaled, I left a comment on your site. Maybe it didn't come through?

We definitely appreciate and welcome input for FoFRedux. I agree that
the interface is getting a little mucky as we add more features. And
our roadmap calls for more features that will need better placement,
layout, etc.

However, there are probably a couple things to keep in mind, and
should be laid out by the team for future design decisions. I
personally picked up FoF because 1) the code was easy to understand
and modify, 2) it had a simplified interface that allowed me to just
*read* my news rather than ogle the UI and 3) the UI runs on my
desktop, laptop, mobile phone, handheld devices, etc.

I don't know if this is the case for all the devs/users, and we should
start a discussion regarding this. There are already other feedreaders
out there that do the full-on Ajax with silver bars, etc. (e.g.
Gregarious, fitting name :). FoFRedux is part personal (and hopefully
soon multi-user) feedreader, but also an aggregator (ergo the 'Feed
On' part) to be used for providing feeds to weblogs, other users,
screensavers, etc. So it's also a server-based 'utility'.

Anyways, if anyone else wants to chime in, please do. And Khaled,
perhaps you can discuss some of your ideas before doing mockups, just
so we can all agree on the path we want FoFRedux to take.

Thanks for the interest!
Andrew

On 2/2/06, khaled Abou Alfa <bro...@gm...> wrote:
> Hey everyone, was wondering if anyone has decided to actually sort out th=
e
> interface design of the application? I'd be more than willing to jump wit=
h
> two feet into this and start sending out mockups that people can comment =
on.
> Thoughts?
>
> Khaled
> www.brokenkode.com
>


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

[Fofredux-devel] Interface Design

[khaled A. A. <bro...@gm...>]

Hey everyone, was wondering if anyone has decided to actually sort out the
interface design of the application? I'd be more than willing to jump with
two feet into this and start sending out mockups that people can comment on=
.
Thoughts?

Khaled
www.brokenkode.com

Re: [Fofredux-devel] mysql versions

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

Katie Bechtold wrote:
> On Thu, Feb 02, 2006 at 06:35:50AM -0500, Andrew Turner (nilspace) wrote:
>   
>> What are the MySQL versions we should be testing with releases?
>> ...
>> So far we need to test: 4.0, 4.1, 5.0
>>     
>
> It might not be too early to include testing with version 5.1 as
> well.
>
>   
Since 5.0 doesn't work currently,  I'm not overly concerned with 5.1.  
It's good to keep in mind, thought.   I hope my efforts with ADODB will 
help with this somewhat.  Although, most of the compatibility problems 
I've seen have to do with SQL syntax, which ADODB will *not* resolve.  
We'll just have to be very meticulous in writing compatible SQL.

-Kevin

[Fofredux-devel] mysql versions

[Katie B. <ke...@us...>]

On Thu, Feb 02, 2006 at 06:35:50AM -0500, Andrew Turner (nilspace) wrote:
> What are the MySQL versions we should be testing with releases?
> ...
> So far we need to test: 4.0, 4.1, 5.0

It might not be too early to include testing with version 5.1 as
well.

-- 
Katie Bechtold         http://hoteldetective.org/

Re: [Fofredux-devel] Unknown table 'fr_x_tag_item' in MULTI DELETE

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

What are the MySQL versions we should be testing with releases? I
believe this issue has (and will) come up again regarding which
versions we all happen to have or upgrade to for testing, vs. what a
user may run into.

So far we need to test: 4.0, 4.1, 5.0

I'm not sure of the major revisions/flavors of MySQL, so perhaps
someone else can chime in on the big versions that should be tested
with.

Andy

On 2/2/06, Kevin <ke...@dr...> wrote:
> Kevin wrote:
> >> With the current CVS head branch of fofredux, when I try to delete
> >> any feed by invoking delete.php, I get the error:
> >>   Cannot query database. Have you run install.php? MySQL says:
> >>   Unknown table 'fr_x_tag_item' in MULTI DELETE
> >>
> >>
> >
> > Merge error.  I'll fix it tonight.
> >
> >
> Not a merge error.   It was a "upgraded to mysql 4.1 without
> re-testing"  error.   The query worked fine with Mysql 4.0.
>
>
> -------------------------------------------------------
> 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://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> 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

Re: [Fofredux-devel] Unknown table 'fr_x_tag_item' in MULTI DELETE

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

Kevin wrote:
>> With the current CVS head branch of fofredux, when I try to delete
>> any feed by invoking delete.php, I get the error:
>>   Cannot query database. Have you run install.php? MySQL says:
>>   Unknown table 'fr_x_tag_item' in MULTI DELETE
>>
>>     
>
> Merge error.  I'll fix it tonight.
>
>   
Not a merge error.   It was a "upgraded to mysql 4.1 without 
re-testing"  error.   The query worked fine with Mysql 4.0.