Can't find the right message to reply to, so same thread, here we go.
Thanks for the link to the free promo version of delphi. It works
nicely, and I now have a fully registered version of delphi on my
system, and although it works well enough, I have trouble with too much
junk onscreen, but that's normal for visual editors, so I'm used to
that, and will find work arounds eventually. I've not tried the whole
lazarus ide yet, because I'm sure it wasn't designed with accessibility
in mind, and it's generally more frustrating than anything else for me
trying new environments that have little or no accessibility. Most
often, this is a result of the designers not being aware such
needs/processes exist), so there's no blame there. I've been an fpc
user for years, though for the last 10+ years I've been windows free, so
didn't care that lazarus probably didn't work with screen readers. :) I
think it's only fair to give it a fair shake though before I begin
complaining about it.
Since it's opensource, I may load it up, and attempt to fix said issues
so it will work for others who might want to use it. Generally, it's
just a matter of labeling buttons properly, and identifying areas that
may not be recognized by the screen readers as things like scroll areas,
pull downs, opening tabs, and the like. Once those items are properly
identified to windows, they generally work well. Of course, sometimes,
design issues (such as screen layout) prevent screen readers from
working well, but those are rare). Anyway, I've hijacked this thread
long enough. I just wanted to say thanks for the pointers.
On 10/31/2016 7:13 AM, Graeme Geldenhuys wrote:
On 2016-10-31 10:29, Mark Morgan Lloyd wrote:
have been pulled
in that are either no longer available or aren't going to work with
FPC/Lazarus.
In the case of XanaNews, the two primary components is use are Indy and
VirtualTreeview. Both are supported by FPC. I don't see the point of
using VirtualTreeview though, so if I do go ahead with the port, I'll
probably remove that dependency. There are other minor components in
use, but they are custom written and included with XanaNews source code
- easy to port of simply replaced with standard components. The other
obstacle is multiple Win32 API calls and RichEdit.dll usage. I can't
remember exactly for what usage the Win32 API call was used, but it
shouldn't be hard to de-tangle - maybe just time consuming. The
RichEdit.dll usage is easy to remove too.
There as already been some discussion regarding what is needed to port
XanaNews. You are welcome to read about them on my news server, where I
host the official XanaNews support newsgroup too.
server: geldenhuys.co.uk
port: 119
newsgroup: xananews.talk
Frankly, I've always found the standard Mozilla family of clients adequate.
I would normally agree, and indeed it is the longest standing clients I
have been using for many years. Thunderbird does come with its bugs
though, and I unfortunately often stumble over the same ones for the
last 8 years. eg: unable to save an attachment (randomly occurs), or
moving a message from one account to another account, I loose any
attachments.
Saying that, XanaNews has some excellent newsgroup features, very fast,
and light on memory.
Regards,
Graeme
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
fpc-other maillist - fpc-other@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other
