[horde] Re: Comments and thoughts on Horde Framework

[Francisco Reyes]

On Wed, 24 Apr 2002 13:09:05 -0400, Chuck Hagenbuch wrote:

>Quoting Hermit <klowther at cisnet.com>:
>
>> I had to bounce from directory to directory to different config files to
>> get set up.  Horde, Imp and Turba.  Many of the files have areas to
>> customize or simply uncomment the appropriate lines.  One was for the
>> different installed modules.

>My reaction is mainly from a software engineering standpoint; I am open to 
>feedback that it really should/can be easier. But it seems like what 
>you're giving up - mostly self-contained apps, the ability to override 
>individual settings for different applications,

There could be defaults which one could use, or choose to over-ride the defaults.


>the scoping of the preferences system - isn't worth it.

Installation currently is probably a big source of questions. This takes time away from many other 
things you probably would rather be doing.

isn't that good enough a reason to seek to improve installation?


>And if you're talking about writing an installer program,

I won't speak for others.. but right now I find installation very confusing. I am yet to be able to get 
Nag working. :-(

How about the following
Instead of having the user have to change/uncomment many different areas, how about something like:

(pseudo code.. don't be too critical of the syntax)

app_var = true;
app_var2=false;
....
app_varn=true/false;

if (app_var)
  all definition and settings for app_var

if (app_var2)
  all definition and settings for app_var2

....

if (app_varn)
  all definition and settings for app_varn

This way all a user would have to do to get any given module configured in horde is to set a variable 
to true or false.


>dealing with one file versus multiple files is just 
>a programming problem, and a solvable one - wanting an easier way like 
>that shouldn't be a reason for sloppier engineering. Ease of use is 
>another matter, of course.
>-chuck

Perhaps some of the suggestions are totally crazy.. or undoable.. but the most important thing may be 
to listen to what we are trying to achieve. New users tend to be an excellent source of good feedback. 
Many times those who have been using something don't see problems because in their minds "it isn't a 
problem".. it is just the way this "xyz" gadget/program/language/framework works.