[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] logos for pim-apps
From:       Klaus =?ISO-8859-1?Q?St=E4rk?= <klaus.staerk () gmx ! net>
Date:       2001-09-25 12:37:54
[Download RAW message or body]

Hi Adriaan,
Hi Cornelius,

> On Tuesday 25 September 2001 12:02, Adriaan de Groot wrote:
> > > Okay, I rescaled the logo up to 48x48 and did a little bit what one
> > > could call artwork ;-)

> > OK, that looks just as ugly as the other icons so it should be fine.

Hehe ;-) I think it's okay for the moment - maybe there will be another icon
in future ...

> > As for content for the site, you can pull a lot of kpilot-stuff from
> >
> > 	http://www.cs.kun.nl/~adridg/kpilot/

I'll only set a link to that page ...

> > Have we got anything "live" yet? I still see the "old" korganizer and
> > kandy stuff on devel-home.

Take a look at devel-home/kdepim/pimpage for a first impression. 

I wonder if I should use the standard-KDE-colors (blue, violet, white) or if
I should do it like this (orange, grey, white) :-? What's your opinion on
this ? In case of a vote for blue-violet-white, it would be changed in a few
minutes ...

> I don't think we should replace the web pages for the applications by a 
> common kdepim one. It's good to have indivdual stand-alone pim-apps and
> the web pages should reflect that.

That's exactly what I do:

Part 1: Short decription of the pim-apps (as I said: *short* description)
and then a link to the webpage of the apps (that's also the part I need the
icons for :-))

Part 2: developper Part (detailed, common devel-desciption, roadmaps,
app-individual descriptions ...)

> My idea of the kdepim pages was that it should focus on the development 
> issues common to the different kdepim apps, i.e. mainly infrastructure
> like communication between kdepim apps, conduits, syncing, calendar or
> addressbook libs.
> In addition to that it would be nice to have some pages for users with
> links to the individual apps, but moving all the pages to a 
> common website is, at least in my opinion, not worth the effort.

... again: that's exactly the way I do it. But when non-developpers come to
that page, they also should know, what the KDE-PIM-suite consists of and
where they can learn more about it (=> on the webpage of the individual pim-app).
And developpers have "their" part, as I mentioned above as "Part 2".

Maybe in some future time - when the pim-apps start some kind of merging -
we can think different about the pimpage and then reorganize it ...

Bye, Klaus :-)

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

_______________________________________________
Kde-pim mailing list
Kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim

[prev in list] [next in list] [prev in thread] [next in thread]