> Okay, I am NOT buying the manual. Sorry, but I don't believe you
> should have to pay for basic docu for free software. However, you
> might be able to get me ot help contribute to making it.
Firstly, no one expects you to buy the manual. There is the
WriterToolsUserGuide.html file supplied with the extension which
covers all the basics. Secondly, the extension is distributed under an
open source license. Open source software is *not* freeware. Thirdly,
what do you believe? I give you an extension that I spend hundreds of
hours developing free of charge. The basic documentation is free of
charge, too. I answer your questions that you could have answered
yourself if you'd paid attention -- and, hey, you are not paying for
this either. In return I offer a manual for users who want to get the
most out the extension at a fair price. Do you believe that I should
give it away for free as well?
> I probably screwed up my path to browser (only wrote Firefox) but the
> path in the FAQ doesn't exist.
Yes, it does, you just have to read the reply to the second answer
carefully. Navigate to
c:\users\username\appdata\roaming\openoffice.org\3\user\ Then delete
the writertools folder.
>
> So if I try to use the microblogger to post to twitter, it says
> "Connection to the database failed. Make sure that WriterDB is
> registered in OpenOffice.org. Read Writer's Tools documentation for
> further info."
>
> I can find an FAQ and an expensive manual. Nothing in between where I
> can find basic directions. Feel free to direct me to them if I am
> just blind.
Once again, check the supplied WriterToolsUserGuide.html file if
paying for the manual contradicts your principles.
Kind regards,
Dmitri
---
Writer's Tools: tr.im/writertools | writertools.googlecode.com
I have no problems with an extra manual provided at cost, but I was unable
to find the original file. It might help if a reminded of it were included
in the FAQ. Something as simple as "For basic install and use guidelines,
refer to the HTML file included in the tool package <or have it on the web
site too>. For more detailed information, refer to <url> at LuLu to
purchase the extended guide."
I could not find the path referred to in the FAQ on my computer. Otherwise
I'd have deleted it by now. But I may have failed to extract the tools
properly and instead just installed the compressed one. I will try again
and study the html file. I will let you know if I have more problems.
Thank you for the quick response.
------------
Personal blog: http://balancingboard.blogspot.com
Dog training blog: http://bexandmolly.blogspot.com
It turns out that I can only find this file IF I use the search function
from the start menu. Windows once again thinks it is smarter than the user
so hides it otherwise. You may want to mention this in the FAQ. I had
tried lots of other things to find it first.
Also note that the folder I found was called "writetools" not "writertools"
as specificed in the faq. This explains why searching for "writertools"
also hadn't found the file.
I _think_ I now have done everything required by the file. However, I am
still unable to use the microblogging feature. Did I miss a step s
omewhere? The error says:
BASIC runtime error.
An exception occurred
Type: com.sun.star.sdbc.SQLException
Message: Attempt to insert null into a non-nullable column: column: ID
table: microblog.
(I really iwhs I could copy and paste from error messages)
The Lookup feature is definitely working. I haven't tested others yet.
> BASIC runtime error.
> An exception occurred
> Type: com.sun.star.sdbc.SQLException
> Message: Attempt to insert null into a non-nullable column: column: ID
> table: microblog.
I was trying to post to Twitter and I am sure my username and password info
were correct.
If there is anything else I can do to help debug this, please let me know.
What is the comment mrker for OOo in macros?
I will just have to live without that feature until some other users
experience problems so you have a wider base for debugging.
Thank you fo rmaking these tools and trying to help me!
THANK YOU!
I guess I am finding those guide bugs for you. ;-)