Hi Dashamir!
> Sorry, but my aim was never to satisfy everybody
> or most of the people
What *is* your aim then?
Well, most projects are interested in discussing with their users. But I
did not mean to criticise you. I think as I explained: I have been
looking for something like DocbookWiki for years. I had quite a hard
time making in work on my server, but you have been so kind as to help
me with that. But when I thought I was done and wanted to start using it
to get my books created, edited and downloaded in plain text or PDF I
found out that my learning just started.
So maybe I should have written:
My understanding of the tools gets better every day.
In case you care, I would like to contribute some comments:
> People have also everyday problems to
> think about, and are not always quiet enough to
> think about science and similar things.
Sure. If you want to further discuss this, please give me your personal
email address. We should not take it here in public.
> I think that it *is* already clear that the web
> interface is secondary and it is not a substitute
> for the command line.
In my very personal opinion, the point in having a web interface is that
I can use the application from any web browser without having to install
anyting and without having shell access.
If you don't own the server, but you are just a user of the package, you
will not be given shell access typically. And even if you get it: It
required the user to understand the shell.
>>You mean: Alter the script?
>
> Sure, why not.
See above. Just it is one step further. It is not only that you have to
have shell access, you also have to understand shell programming and you
need to modify code which is part of the package to get content into the
app.
For me separating content, configuration and code has always been mandatory.
Again: It's your project and I am just a happy user of it. I thought
you'd like to receive feedback and discuss to maybe take the project
further and make it more usable for even more people.
Regards,
Torsten
Dashamir Hoxha schrieb:
Hi Torsten!
--- Torsten Schlabach <[EMAIL PROTECTED]> wrote:
Thank you for your explainations. I appreciate your
patience
I try to respect people, especially when they are
serious and they deserve it.
and I
really think DocbookWiki keeps improving every day.
Either you are not honest (sorry, this is what
I think), or you are wrong. It is not improving
everyday. People have also everyday problems to
think about, and are not always quiet enough to
think about science and similar things.
Sorry for this email being out of the thread,
SourceForge had some
problems obviously. I only read your answer on
www.mail-archive.com and
I cannot get the header needed to keep the thread
together from there.
Anyway:
> 1 - After importing a new book you should also
> add an entry for it in
> 'content/SVN/book_list.sh'
You mean: Alter the script?
Sure, why not.
> (maybe this should be done automatically by
> the system, I am not sure about it)
I think this is what most users would expect. Don't
you think so? I was
calling that script and wondering why my new books
don't show up there,
neither the imported nor the newly created ones.
Sorry, but my aim was never to satisfy everybody
or most of the people. I think that it is better
(it is right) to do it manually. I think that
most of the people are lost (are in a wrong path)
so I don't think that I have to fulfill everybody's
expectations.
Regarding documentation: I would personally suggest
that you should
either try to make everything work through the web
interface (which
would be most desireable) *or* make it very clear
that some operations
require using the command line.
I think that it *is* already clear that the web
interface is secondary and it is not a substitute
for the command line. But in case it is not so clear
and the people have to find out about it, I think
that this is still ok.
I would have contributed to the manual, but the site
was down,
unfortunately.
You can modify a local copy of the manual and
send me the patches.
> Creating a separate repository for each document
> is a design decision. If you think that it could
> have been done better, we can disscuss the
advantages
> and dissadvantages of it at:
I am not saying it's bad. I was just confused,
because what you
explained in your mail was not obvious to me. It
might still be
discussed if this is a good decision or not, but
first things first. I
think this is not the most imporant part to work on.
Regards,
Torsten
P.S.: I might have asked this before, but it might
have gotten lost in
SF list troubles: Which one is to be used to stay on
top of the latest
code changes? The SF *CVS* repository or the SF
*SVN* repository or are
they synced?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Doc-book-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doc-book-users
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Doc-book-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doc-book-users
