On Tuesday 11 January 2005 19:13, Eric Laffoon wrote:
> On Tuesday 11 January 2005 10:55 am, Andras Mantia wrote:
> > On Tuesday 11 January 2005 20:34, Rick Hobson wrote:
> > > As someone who struggles with some of this I find the various
> > > dependencies difficult to get a handle on and also the various names
> > > that keep cropping up. OK, I've got the hang of Kate, Quanta and
> > > kdewebdev (I think although I'm not absolutely sure what it contains)
> > I think it's pretty clear if you look at the package, especially that
> > kdewebdev/README has the following lines:
> I love that you still think people are reading the README files, especially
> give that most users are loading a binary package. It looks like these are
> the first place to look for FAQ material.
> > Kommander: a GUI script builder and executor tool. Needed for some
> > Quanta functionality.
> > KFileReplace: powerful search and replace in multiple files
> > KXSLDbg: XSL debugger
> > KImageMapEditor: image map editor
> > KLinkStatus: link validity checker
> > > but:
> > >
> > > Cervisia?
> > About requirements, dependencies, read kdewebdev/PACKAGING.
> > And I extended Quanta now so on startup will warn you about all the
> > missing (possible) extensions telling you also what they are used for.
> > Cervisia is needed for the CVS operations.
> > > Qt?
> > Hm, explaining what kdelibs and qt is is something is not Quanta
> > specific at all, but we can do it. ;-) But maybe we need to explain
> > what is libc and the kernel then...
> Wow, and I thought you were the reasonable one and I was the wild man. ;-)
> I think libc is a little more transparent to the desktop than Qt. A brief
> sentence or two one what Qt and KDE are could be quite useful to a lot of
> windoze newbies.
> > > I'm sure there are others.
> > >
> > > Does an update of kdewebdev update all I need?
> > It depends what do you need. It will not update Cervisia, nor Kompare,
> > but will update all the applications that are in kdewebdev (logically).
> > > Does KDE need updating at the same time? (presumably).
> > Depends. Usually Quanta is compatible with the previous version of KDE,
> > so Quanta 3.3 runs on KDE 3.2 as well, but does not run on 3.1. Now
> > with 3.4 the situation is a little bit different as, altough untested,
> > I see no reason why Quanta 3.4 wouldn't run on KDE 3.2.
> > > This list of FAQs could be pretty long.
> > Well, let's gather the questions and we will filter out what is
> > important and frequently asked.
> Yes, and none of those questions about "what's wrong with the project
> manager or developers?" ;-)
> > > What I would love is a detailed HowTo which took me though the steps
> > > needed to update/install kdewebdev with information about
> > > dependencies and details (or links) on how to update those packages
> > > and libraries.
> > All we can give is information about how to do this from source. I think
> > we need such a section on the new site, be it in the FAQ or in a HOWTO.
> One critical element we need is an "Alerts" page. For instance when there
I wouldn't put an "Alerts" page in per-se but when there are alerts put them
big and loud on the front page. the trouble with an alerts page is that it
could sit there for ages with nothing to say. And in that circumstance it
would become unvisited and therefore almost useless. Instead put a noticeable
link in the home page to alerts as they become current. And of course remove
it when not current.
> were configure errors in the first packaging of version 3.3.0. What we need
> is a place to put this information as well as a category for RSS so that
> people can subscribe to this information, but that is a discussion for the
> other list so let's adjust accordingly.
> > So I propose: you (users) write the questions and what do you think
> > would be useful, we (the developers) will try to answer them and create
> > howtos.
> Or... and I'm just tossing out ideas here... we could do it the other way
> around and quiz the users? Free copy to the most right answers? ;-)
> > Andras
> > > Not much to ask :-).
I have sent Eric a further update just now it would be nice to see it up
because then we can get:
a, some small facility there
b, some feedback on what's useful and what's not
c, hopefully some suggestions and requests from users
d, find out what's working and what's not before creating a whole application
to deal with it then find out it isn't what was wanted or effective in the
e, get something seen on the kdewebdev site. massive amounts of constructive
effort may well be about to be brought to bear but regardless of that the
full site will take some considerable time. at least with something actually
appearing we may get some enthusiasm for a project which has had no movement
at all for some considerable time.
Expanding the flat site a little while the real construction goes on behind
the scenes can I think do nothing but good. As it gives us a chance to see
what people think. Gather information and have it available and useful.
Dave Reddish:- Web Site Lead
Quanta mailing list