Re: [Epiphany] Bookmarks



On Sat, Oct 25, 2003 at 08:06:37PM -0400, Marco Pesenti Gritti wrote:

 > I'm going to avoid to reply to your previous mail because it's
 > nothing more than an heated reaction to something you dislike.

 Pity, because the one you did reply to is the one that was a heated
 reaction to a post of yours :-)

 > You are quoting (and maybe reading) only a part of what I said.

 Rest assured that I read everything you write.  And no, I don't like
 overquoting emails, tons of bandwidth is still a luxury in some parts
 of the world.

 > That said I know I have a limited experience and knowledge about
 > usability and I'd be ready to accept the decisions of the team that
 > is supposed to know more about GNOME usability.

 Well, *I* have a problem with some of the design decisions made by this
 team, too, it's not only you I disagree with :-)  But that doesn't mean
 I don't think GNOME is, from a purely technical point of view, the
 alternative that's in best shape at the moment.  I think the same of
 Epiphany.

 > The point anyway isnt really what users believe is more usable, but
 > what is actually more usable for the majority of the users I target.

 I won't argue with that kind of reasoning because it's a good one, but
 I did get the impression that one of the goals is to make Epiphany the
 default GNOME browser, which means Epiphany's users are GNOME's users,
 and I really get the feeling the former is only a subset of the later.

 > >  Separating the bookmark manager from epiphany is not only a good
 > >  idea from a programming point of view *and* a Unix point of view
 > >  (this *is* Unix, no matter how hard people try to deny it), but it
 > >  is also a good idea from a usability point of view.  There is no
 > >  single solution that can satisfy every user out there.  Not even
 > >  90% of them.  Aim for 50%, and you might be on the right track.
 > 
 > Being Unix or not is completely irrelevant ..

 On the contrary: "GNU Network Object Model Environment".  GNU's Not
 Unix, but it certainly feels *a lot* like it.  And one of Unix's
 building blocks is the idea that components should do one job and do it
 damn well.  Another one is that these blocks should be able to
 communicate with each other.

 > I already agreed with the original poster that a separate bookmark
 > manager would be good from architectural pov.

 You agreeing with the OP doesn't mean you agree to actually implement
 the current bookmark system as a separate component.  I'm sorry if I'm
 misunderstanding you and that is in fact what you wanted to say.

 I guess you could use CORBA to communicate with the bookmark manager,
 but I'd have to look into that.

 Marcelo



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]