From: Katie B. <ka...@ho...> - 2005-12-30 23:18:57
|
Kevin commented under Feature Request 1375553 ("customizable appearance"): It wouldn't be a bad idea to have the ability to store global config options in the db. Then, config.php could be pared down to just the db connection info and table names. I think that's a good idea. Is that something you're working on, Kevin? Once we have a page for user configuration, I could work on input and storage of user login info for digest authentication. And we could move forward with allowing the user to customize fofredux's appearance. -- Katie Bechtold http://hoteldetective.org/ |
From: Evan B <ev...@at...> - 2005-12-30 23:44:44
|
I take issue with this. The problem with that is that all the config data gets wiped if the db crashes. As it stands, the only thing you have to lose is your feed entries, which (to a certain extent) can be rebuilt rather easily if you have an OPML backup of your feeds. e Katie Bechtold wrote: >Kevin commented under Feature Request 1375553 ("customizable >appearance"): > > It wouldn't be a bad idea to have the ability to store > global config options in the db. Then, config.php could be > pared down to just the db connection info and table names. > >I think that's a good idea. Is that something you're working on, >Kevin? Once we have a page for user configuration, I could work on >input and storage of user login info for digest authentication. And >we could move forward with allowing the user to customize fofredux's >appearance. > > > |
From: Andrew T. <ajt...@hi...> - 2005-12-31 04:44:26
|
That is a good point. Also a config file allows for easy install multiple with similar or diff't configs but the same feeds. Having all the 'extra' (non-db) config in another file is probably a good idea. What about using the built-in PHP config file format for storing the info? The api should extract the actual storage away as key-value pairings. config.ini: [NUM_VIEW_ITEMS] =3D 50 num_items =3D fof_get_config('NUM_VIEW_ITEMS'); Andy On 12/30/05, Evan B <ev...@at...> wrote: > I take issue with this. The problem with that is that all the config > data gets wiped if the db crashes. As it stands, the only thing you have > to lose is your feed entries, which (to a certain extent) can be rebuilt > rather easily if you have an OPML backup of your feeds. > > e > > Katie Bechtold wrote: > > >Kevin commented under Feature Request 1375553 ("customizable > >appearance"): > > > > It wouldn't be a bad idea to have the ability to store > > global config options in the db. Then, config.php could be > > pared down to just the db connection info and table names. > > > >I think that's a good idea. Is that something you're working on, > >Kevin? Once we have a page for user configuration, I could work on > >input and storage of user login info for digest authentication. And > >we could move forward with allowing the user to customize fofredux's > >appearance. > > > > > > > > > > ------------------------------------------------------- > 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 |
From: Katie B. <ka...@ho...> - 2006-01-11 16:44:47
|
On Fri, Dec 30, 2005 at 11:44:23PM -0500, Andrew Turner wrote: > Also a config file allows for easy install > multiple with similar or diff't configs but the same feeds. I think a database could offer the same flexibility; I'm imagining a config table where each column is an attribute (e.g., show_images, background_color) and each row is a "configuration". I'd be fine with using either the database or PHP's Config (file) class to start out with (as Kevin wrote, ideally the storage method will be abstracted so it could work either way). I'd just like to see some resolution to this issue so we can work toward getting these features implemented. -- Katie Bechtold http://hoteldetective.org/ |
From: Andrew T. <ajt...@hi...> - 2006-01-11 17:02:26
|
Good points. I think probably using a DB table for config and then the option to have the config file backed up whenever a config change is made would fulfill the niceness of a DB table with the user concerns of lost settings. I am doing the same for the OPML export. Any takers on who wants to implement the config API? I've added feature requests 1403106 and 1403108. Here is what I believe are the current breakdown of work for current devs: Kevin - tags, pgsql support, Andy - geomap, saved searches (waiting on tags), CSS Layout Katie - authentication/digest Benji - keyboard navigation Carlos - Andy On 1/11/06, Katie Bechtold <ka...@ho...> wrote: > On Fri, Dec 30, 2005 at 11:44:23PM -0500, Andrew Turner wrote: > > Also a config file allows for easy install > > multiple with similar or diff't configs but the same feeds. > > I think a database could offer the same flexibility; I'm imagining a > config table where each column is an attribute (e.g., show_images, > background_color) and each row is a "configuration". > > I'd be fine with using either the database or PHP's Config (file) > class to start out with (as Kevin wrote, ideally the storage method > will be abstracted so it could work either way). I'd just like to > see some resolution to this issue so we can work toward getting > these features implemented. > > -- > 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://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 |
From: Benjamin S. <bs...@cr...> - 2006-01-11 18:54:24
|
I'm not dead! I'll check out the keyboard nav stuff either Saturday or next week. I'm still swamped with post-travels cleanup at least through then. --Benjy On Wed, Jan 11, 2006 at 12:02:12PM -0500, Andrew Turner wrote: > Good points. I think probably using a DB table for config and then the > option to have the config file backed up whenever a config change is > made would fulfill the niceness of a DB table with the user concerns > of lost settings. I am doing the same for the OPML export. >=20 > Any takers on who wants to implement the config API? I've added > feature requests 1403106 and 1403108. >=20 > Here is what I believe are the current breakdown of work for current devs: >=20 > Kevin - tags, pgsql support, > Andy - geomap, saved searches (waiting on tags), CSS Layout > Katie - authentication/digest > Benji - keyboard navigation > Carlos - >=20 > Andy >=20 > On 1/11/06, Katie Bechtold <ka...@ho...> wrote: > > On Fri, Dec 30, 2005 at 11:44:23PM -0500, Andrew Turner wrote: > > > Also a config file allows for easy install > > > multiple with similar or diff't configs but the same feeds. > > > > I think a database could offer the same flexibility; I'm imagining a > > config table where each column is an attribute (e.g., show_images, > > background_color) and each row is a "configuration". > > > > I'd be fine with using either the database or PHP's Config (file) > > class to start out with (as Kevin wrote, ideally the storage method > > will be abstracted so it could work either way). I'd just like to > > see some resolution to this issue so we can work toward getting > > these features implemented. > > > > -- > > 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://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 > > >=20 >=20 > -- > Andrew Turner > ajt...@hi... 42.4266N x 83.4931W > http://highearthorbit.com Northville, Michigan, USA >=20 >=20 > ------------------------------------------------------- > 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_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel |
From: Kevin <ke...@dr...> - 2005-12-31 06:34:21
|
Evan B wrote: > I take issue with this. The problem with that is that all the config > data gets wiped if the db crashes. As it stands, the only thing you > have to lose is your feed entries, which (to a certain extent) can be > rebuilt rather easily if you have an OPML backup of your feeds. > > e > DB crash, hard drive crash, virtual host goes out of business, what's the difference? Any way you look at it, the data's gone. You should have backups of everything important to you. If you don't, that's your problem. Sorry to be so blunt, but it feels like the wrong approach to be designing the app to compensate for a poorly adminstered database server. With decent abstraction we could offer both config storage methods. (flat file or db table) But for now, I'm leaning toward using the DB. > Katie Bechtold wrote: > >> Kevin commented under Feature Request 1375553 ("customizable >> appearance"): >> >> It wouldn't be a bad idea to have the ability to store >> global config options in the db. Then, config.php could be >> pared down to just the db connection info and table names. >> >> I think that's a good idea. Is that something you're working on, >> Kevin? Once we have a page for user configuration, I could work on >> input and storage of user login info for digest authentication. And >> we could move forward with allowing the user to customize fofredux's >> appearance. >> >> >> > > > > ------------------------------------------------------- > 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel |
From: Katie B. <ka...@ho...> - 2006-01-12 18:12:12
|
On Wed, Jan 11, 2006 at 12:02:12PM -0500, Andrew Turner wrote: > Any takers on who wants to implement the config API? I've added > feature requests 1403106 and 1403108. I'll take a stab at it. -- Katie Bechtold http://hoteldetective.org/ |
From: Andrew T. (nilspace) <nil...@us...> - 2006-01-12 20:51:27
|
Awesome, thanks. The requests have been assigned. :) Andy On 1/12/06, Katie Bechtold <ka...@ho...> wrote: > On Wed, Jan 11, 2006 at 12:02:12PM -0500, Andrew Turner wrote: > > Any takers on who wants to implement the config API? I've added > > feature requests 1403106 and 1403108. > > I'll take a stab at it. > > -- > 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://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 |