Search

Saturday 6 August 2016

well well well - look what i've been doing

could this possibly hold a clue to what's comming next?

I've been recording a short snippit of what I'm up to and used a really cool program called asciinema to do so. It basically records any terminal session and let's you upload it to the web, which is what i've done. Watch closely. There is something interesting in there that might let you know what I'm up too.

enjoy

Mikey

Tuesday 3 May 2016

I need your help with a pygtk project

my project

over the last few months, i've been working ona project that, at least in my oppinion, is quite hard to maintain as only one developer. That's not the point however. I recently restarted the project from scratch to clean up the really messy code and have also submitted the git repository to github.

my problem

I've sorted out the main sidebar code, but, as the github page states, I need an api for people to develop widgets with. In my original code, I would just add them in to the main file, however, this means that anybody who wants to add a widget will have to modify my code. I would rather a system such as the one used by your favourite desktop environment's panel uses, where each plugin is a separate file that get's loaded on startup. The question I have is, how do I go about doing this? I've considered using the imp module and have started work on implementing that solution, however, this seems like a verry messy way of doing things. Do any of you have a way I can fix this problem?

what you can do

if you click here, you'll be taken to the github project page. If you can help me in any way, not just implementing the api, then please feel free to branch my repository and submit a pull request. That would be much apriciated!.
thanks for reading this and please help if you can
mikey

Monday 25 April 2016

ubuntu mate 16.04 review + channel update

hi guys. I've just uploaded a video to my youtube channel about ubuntu 16.04 and what I think. The video also contains a few channel updates, such as future content in the form of the HP-dc-5700 overview and my thoughts on my new laptop, the dell latitude d810. Hope you enjoy.


Saturday 9 April 2016

the state of linux accessability

****** The state of accessability under linux ******
I am writing this article because there is barely any documentation or even reviews like this about linux accessability. 
I spent ages going through forum posts and old documentation that didn't really apply anymore and came up with this. 
Now, before I start, I don't mean to bash the linux community in any way because of the lack of documentation, mainly because I can see exactly why there isn't much documentation online about this. First of all, how many developers are blind or visually impared? and secondly, How many people who are blind or visually impaired run linux?

I myself have had blindness from birth, as well as light sensitivity all my life, so when I got interested in computers, I was quickly dissapointed in the level of accessability that they provided. 

I played with computers for years without a screen reader or zoom, just high contrast, although given my age, I didn't really need a computer yet. Later I descovered narrator and how bad it was, but at least it gave me a starting point. I also later found NVDA and how much better it was, but ultimately, I wasn't really happy with windows itself. 
So, like I think most geeks would do, I decided to get a mac. Voiceover, the built-in screen reader on the mac, was very good, but again, the mac desktop still didn't seem customizable enough.
But then I found linux...
Linux, as far as I could tell by using my iPad to watch youtube videos, was what I had always dreamed of and, as I got older, I also started to really respect everybody making all open source projects possible. 
I loved-and still do love-the idea of opensource. The only thing holding me back was: 
A: my old pentium 4 IBM thinkcenter with 1GB ram  
B the seeming lack of accessability software, more spicifically, screen readers out there for linux. 
I was going off barely documented ways of getting ORCA (what I say is the number 1 screen reader for linux) to work on desktops other than GNOME. 
I was doing this because gnome 3 had just been released and my old computer just couldn't handle it properly.. Not only that, but I had another problem. It was pretty hard to get linux installed because there was no accessable installer. 
Well, after about 4 years of trying, I had to say that my situation, as well as, I can emagine, the situations of varios other people, has changed.

***** debian - the ideal solution *****

Yes. Somewhat surprisingly to me, debian was the best option for me. For a start, debian has a command line speach installer accessable at least for the net install cd image. 
By pressing S at the boot menu for the cd, it will load the tty and start a completely accessable speach installer.
 This enabled me to install linux, but I originally thought I would still have to use gnome, or modify an XFCE or mate installation for it to work. Amazingly though, that was not the case. I tried XFCE with a debian base, got it installed, rebooted, pressed enter on the grub screen waited, saw the log in screen come up and then, shockingly to me, heard espeak say "screen reader on". Lets just say I was very happy at that. Most of the XFCE desktop is fully accessable out of the box on debian (if you use the command line installer) and I am actually using it to write this article.

I also tried mate, thinking that the gnome 2 fork would be lighter on resources than gnome 3, but also accessable because of it's roots and it worked flawlessly. I would really like to thank debian, as well as the creators of the XFCE, mate and not forgetting gnome desk tops for making linux completely usable for me as a main operating system.
***** ubuntu mate *****
After using debian for ages, I decided to buy another used computer (HP dc-5700, 2007). This shipped with windows xp, but I replaced it with ubuntu mate, just to see if I could make it accessable. 
I was glad to descover that, not only were the accessability settings set correctly out of the box, but orca was also pre-installed and fully working. 
I love this distro, as well as the team who made it and clearly they know what the're doing. I have since reloaded standard ubuntu unity on to it, but will be switching back as unity, while accessable, is just not my thing.
****** added usability - compiz ******
I originally thought that compiz would be more of a pain than a benefit, because of my older hardware, but actually, especially on the ubuntu-mate machine, it ran really well and gave me access to one of the most needed features for me, “negative”. 
I used invert colours on my mac so much, I began to miss it on linux. When I found out about the negative plug-in for compiz, I gave it a try. Not only can you invert the whole screen, but the plug-in is even better than the mac's version, because you can choose to invert only the corrent window as well. I also tried to play around with the "enhanced zoom desktop" function, but because it wasn't esential, I didn't get very far with it.
One of the reasons why I probably didn't get very far and this is a minor gripe I have, is that the compizconfig settings manager is not very accessable, in that orca doesn't speak the labels of text boxes and key selection fields. While I can live with this, it's a major pain setting compiz up, as I have to basically guess what entry does what.
****** the tradeoff - qt application support ******
Because I use orca as my screen reader, which is based on gnome, it works best with gtk applications, I have had some quite major problems with qt  application support. Before anyone tells me, yes i've heard of jovie for kde, but I honestly can't wrap my head around how to set it up properly. I have qt accessability enabled and that gives me some support, but if I try to run, say, kdenlive, I get no output from orca. I would love to see someone work on this more, as it is the only thing holding me back right now.
***** conclusion *****
To some up, I honestly think that linux is more accessable than windows. I can't, as far as I know, install windows with a screen reader. Also, the gtk standard is pretty common, so I think that most applications are accessable, whereas on windows or mac, some software providers (microsoft office for mac) decide to use a none standard way of laying out widgets. Therefor, I have more of a chance of either getting accessability support out of the box with linux apps, or somehow being able to modify settings to get it to work. 

I hope you enjoyed reading this, but that's all for now. I may publish more articles about this subject in the future, especially how to get things working articles, but you'll just have to wait and see.


_mikey_