Jamie Balfour BSc

Welcome to my personal website!

Technology enthusiast

I am very interested in technology, particularly relating to computer science. I am most interested in web design and development.

My main hobby is programming. One of my most well known products from this is ZPE. I also am the sole creator of BalfBlog, BalfBar and BalfSlider.

A little bit about me

In 1997, when I was six years of age, I got my very first computer. I was always very interested in the ins and outs of it and dismantled it to see how it worked.

Years later, in 2016 I received my BSc (with honours) in Computer Science, obtaining a First class degree.

I'd like to welcome you to my website and hope you enjoy using it as much as I have enjoyed building it!

Google Plus
Me
Jamie Balfour BSc
Full stack developer

Personal Blog

Browsers

NPAPI or Netscape Plugin Application Programming Interface was the norm for a very long time in web browsers. It was a single standard that allowed all browsers to use plugins. But plugins have plauged the web for a long time too. One of the most well known plugins, Adobe Flash, had become pretty much everywhere, requiring users to download a plugin for the system. It used NPAPI. On top of this, plugins were cumbersome to develop and meant developers needed to know several in order to achieve the results they wanted. Now the web is finally moving away from a plugin interface to a much more standards based interface.

NPAPI was the interface (a set of methods which each plugin must implement) which all plugins complied with. This was originally developed by Netscape, one of the original companies to develop a web browser and Microsoft's competitor in the first browser war. Netscape developed many standards and one of them was this plugin interface that has left us in the messy situation we are in now.

NPAPI has been around for a long time, but last year was supposed to be the end of it. In 2015 Mozilla announced they had plans to drop NPAPI by the end of 2016. This was later brought back to March 2017. Chrome has already dropped NPAPI and did so in September of 2015, only after turning support off by default in April that same year. Google cited that it "has become a leading cause of hangs, crashes, security incidents, and code complexity" thus that the older architecture of it needs "to evolve the standards-based web platform". It's important to note that NPAPI is an architecture from the 90s when the web began to take shape and at that point we were using HTML 3.2 and lower. Since then HTML5, CSS3 and JavaScript have all brought huge improvements to the standards-based web. 

Many plugins already exist that take advantage of NPAPI including Flash and the Java applet plugin. But both of these can be replaced by much more modern solutions. 

By removing the NPAPI browser developers are encouraging standards. They are making it more difficult for those who develop these plugins to make them a part of the future. By doing this they are offering a safer web environment for everyone. They are also ensuring that there is no longer the complicated mess of choice that Netscape and Microsoft once supported through the NPAPI and that we live in a standards controlled environment where no one company owns the web.

A standards based website is the way to go and older websites need to update to catch up with standards. Nobody has time for these older websites that rely on these plugins now, they themselves are slow and ineffective and need to catch up. 

In the old days, before CSS, background colours were set using the bgcolor attribute as below:

HTML
<html bgcolor="rgb(255, 0, 0)">
</html>

But since this is quite an old way of doing things and not used often nowadays, you'll probably find it has a lack of support in some newer browsers like Google's Chrome. I came across this issue when I was trying to make the background red by using rgba(255, 0, 0) which would normally produce red and does in other browsers, but in Google's Chrome browser it produces a totally different colour. I believe this is because Google did not spend much time working on support for this older attribute that should be banished from HTML5 altogether. Below is a sample that may or may not do anything at all:

Hello world

Have you experienced this issue where the colour value represents different colours on different browsers? If so let me know by commenting below.

I'd like to mention my new software which is under development:

Hyper WEB

Hyper WEB (Hyper Wonderword-Extends-BlackRabbit) is a web editor. It is based on the same distinct feature set of the BlackRabbit Editor in that it uses a function machine editor where inputs are given and the editor produces the output based on those inputs. The editor uses the Internet Explorer's Trident engine with full support for Internet Explorer 10. Future plans are to bring WebKit to it. Pictures will be posted soon as progress begins to show. Currently the browser engine provided is based on Cobweb version 2.0, and it features the same page blocking technologies integrated into it. There are some very clever features being produced for it that will make creating sites easier.

BlackRabbit 2.0

Although I did announce this in the blog for BlackRabbit, version 2.0 is a total redesign on the scripting language. Integration in Cobweb will be much deeper, Hyper WEB will include ways to include sandboxed scripts into websites and Painter Pro and Wonderword will have better support. The current version of Elements will support version 2.0.

Cobweb

Recently, I stopped working on Cobweb because of a limitation of Windows preventing the use of the rendering engine of Internet Explorer 8 and above as part of any application apart from Internet Explorer itself. Due to a new feature brought to Cobweb, it is now possible to ensure that all versions of Trident can be used in Cobweb Internet Browser, and so version 2.0.1.319 has this feature. I will soon put the latest version up on the web. As Cobweb is my currently only finished product, feedback would be much appreciated.

Wonderword

The future for Wonderword stopped back in October 2012 because it was taking the place of nothing more than a web editor, script editor and more other things. Due to the fact that Hyper WEB and BlackRabbit do both of these, I have decided to revamp Wonderword. There is now the possibility of a full WYSIWYG word processing package, but this will need some investment. It cannot happen without support.

Painter Pro

Current betas on Painter Pro have expired. To obtain another beta, please contact me. Painter Pro 1.2.1.6000 was the latest release and the next release will be 1.2.2.0, currently known as it's codename Aberdeen.

VUEBB

Work on VUEBB has also been slowed, but it will resume as soon as the next file extension library is complete.

Site accessibility

A lot of the original functionalities that once existed here have been removed.

This page was generated in 0.31 seconds using 2097152 bytes. Slow? Let me know.

To use project mode, the window must be greater than 920 pixels in width.
Click here to disable Project Mode.
This site uses cookies to deliver its services, to personalise ads, to store preferences and to analyse traffic. Information about your use of this site is shared with other companies. By using this site, you agree to its use of cookies.
Contact me
Contact Jamie Balfour

Get in touch with me via this form.