I partly agree with Jakub. I think F-Spot should monitor ~/Photos by default, but on the first "Import" action, note the user that files are going to be copied into ~/Photos, and put a "Change..." button.
This way we won't interrupt users on the first start-up with question he doesn't know the answer for, and we also keep him aware for what's going on. Yo'av. On 12/9/05, David Moore <[EMAIL PROTECTED]> wrote: > On Fri, 2005-12-09 at 13:08 -0500, John Stoffel wrote: > > I guess this is how I see it: > > - f-spot starts up. > > - looks for ~/Photos/ > > - if it exists, look for ~/Photos/.f-spotrc > > - if it exists, then f-spot owns this directory. > > - if .f-spotrc doesn't exist in ~/Photos, then ASK if you want > > this directory should be managed. > > I agree 100% with John's logic here. An application should never start > modifying an existing file structure without a) specifically informing > the user and allowing them to abort or b) responding to a direct user > action that would logically cause the modification. > > Starting the application for the first time does not count as (b). > > If popping up a "wizard" upon first launching f-spot is frowned upon by > the developers, then I believe the correct action is to _not add any_ > directory to the catalog. The user would be required to edit the > preferences and specifically add one. > > Just my 2cents, > > David > > _______________________________________________ > F-spot-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/f-spot-list > -- Yo'av Moshe http://www.PlaceOnEarth.org _______________________________________________ F-spot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/f-spot-list
