No. My policy has always been not to participate in link exchanges. Content should stand on it's own two feet. Link exchanges lower the value of content for the reader. And I care more about that than some perceived change in search engine ranking.
Can you bundle our software in your installers?
No. Users of my software will only ever get MY software. I feel the practice of bundling anything unrelated in the installer reduces user trust in the software industry. And I will not contribute to that ever.
When will you do 'X' feature or fix 'Y' bug?
I work on my software in my free time, so I get around to stuff when I can, and my life is busy enough with work, family and friends. Fitting coding in is a acheivement in itself. So patience is required.
Why doesn't i.Scribe support multiple accounts?
Because InScribe does, and who'd buy software if they could get it for free? Jeez it's not like it's expensive or anything.
What language do you program in?
I use C++ for executable code, and python for scripting. On windows I use Visual Studio 2013, on Linux I use the the latest default gcc + LgiIde, and on the Mac; the most recent XCode it lets me install.
What versions of Windows do you support?
My applications are targetted to run on Windows XP, Vista, 7 and 8. I don't support anything earlier than that. I personally run Windows 7 so that will have the best support.
Is there a Scribe FAQ?
Your 'xyz' application crashed! Can I help you fix it?
I do release debug builds, which you can use to help me fix crashes. If you want to run a debug build read this information to get started. If there is no current debug build for the application in question then ask me and I will provide one. You'll find them at the top of the history on the application's page.
What are all the "stable", "unstable" tags next to releases?
These are my hints at what sort of quality I expect a release to have. They aren't garentees of anything and if I receive feedback to the contary I'll often change the tag on a release to reflect my current feeling.
- Stable is obviously where I consider a release mature for everyday use without any nasty pitfalls.
- Unstable is a release that I know has unfixed bugs or I suspect has problems. Generally you'd only download this to help with testing or if you want to try out some brand new feature not available in a Stable build.
- Alpha releases are incomplete and buggy, and are only for the really adventurous. They require lots of patience and coxing to do anything really useful and a more than likely to crash just when you least want them to. Alpha is a bit like Unstable but only more so.
- Next is the just information about where I'm up to with the next version. People find it helpful to know where things are at so they don't bug me about something I've already implemented or fixed. If there is a release marked Next then it's generally whatever is building on my machine at the time and is completely untested. Usually it's a test fix for an individual user.
- Finally Legacy releases are old software that I no longer will support or improve, but I provide for those who may find some utility in using.