back to the Classtab home page

progress on upgrading the site

2 February 2020 - A reminder: the original tabs page and the scrolling app should
work fine with Edge or Firefox. Many people prefer having all the tabs on one page,
so that option will remain. But for those using other browsers or accessing the site
using cell phones or tablets hopefully there will soon be a choice of other formats.
A search box has been added to the home page using Google's 'sitesearch' feature.

background

Praise for Classtab on Reddit varies from 'super low tech' to 'ugly as fuck'.
The size of the main page was causing loading problems with some browsers,
and it's not optimised for cell phones and tablets. A site upgrade looks inevitable.
But first, I'd like to acknowledge the many generous offers of help received over
the years, and give my excuses as to why most of them haven't been taken up.
(Though the main reason is that I prefer tabbing to upgrading web sites.)

some of the offers of help received for developing the website

(This list is not complete - any I've missed out, please let me know)

using framesets - Jim Cranwell - October 2004
- demo

tab printing utility - Curzio Vasapollo - September 2005
(no longer available)

graphics makeover - Tolobek - September 2006
(image files) - sample logo/title - sample intro

site redesign - ? - March 2007
(image file) - sample home page

CSS makeover - Vicktor S - December 2007
(demo no longer available)

android app - Ryan Guthrie - March 2010

site redesign - Miguel Jimenez - July 2012
(demo no longer available)

Android app - James - December 2012

classtab logo - Karl Duckett - March 2013
- current logo

pdf version of the site - Louc Guillaume - February 2014

site update - Arthur Canal - June 2014
offer to make the site searchable and categorized

scrolling app / utility - Maxime Bergeron - August 2014
- current page
possible updates - clean up code, maybe rewrite in Python, bug list on Discord (see below)

Android app - Marcus P - June 2016
- screenshot
- GitHub page

html code update - Marcus - July 2016

site redesign - Brandon Weaver - September 2016
- 'heavy beta' site
- GitHub page
- tools for extracting metadata from classtab

help with coding and developing features - Nicolas Calle - May 2017

Discord server - June 2017
server name - Classtab (invite on request)
still up, but not very active - 5 members

CSS makeover - Gerald Rivas - February 2018
- demo site

foreign language support offered - Luc R. Boel Linger - 2018

dark mode extension - Sean Alexander Free - December 2019
- Chrome web store

site redesign - Nate Brooks - December 2019

miscellaneous thoughts on developing the site

some people prefer the current page style, so a simplified (downloadable) version could still be available

possible meta data: LHF, RHF, key signature, tuning, time signature, tempo, difficulty level, tab author, style/era of music

option for random choice of tab?

different language versions?

options for discussing tabs (wiki? forum?)?

option for submitting new tabs and corrections online?

separate app for mobiles and tablets?

queries about a new site -
- will it still work with older (legacy) and text-only browsers?
- will it be machine-translatable and usable by non-English speakers? (eg using Google translate)
- will it be accessible for people with sight problems who use text to voice software?
- will it be easy to navigate by people with common types of colour blindness?
- will it have a global edit facility? (eg for changing a tabber's email address in multiple tabs)
- will it incorporate Google site verification?
- how will the site integrate with the scrolling app?
- is a search facility needed? (or maybe use Google site search?)
- will it work ok with mobiles and tablets?
- how easy will it be to move the site to a new web host if the designer is no longer involved?
- will the site come top of search engine results for the query term "classical guitar tablature"?
- will individual tabs be indexable directly by search engine robots? (most traffic comes via Google searches)
- but above all, will it be easy to maintain on an everyday basis?

is a maximum of 80 characters a line for tabs still optimal? if not, what is?
(do people still use fixed character width printers?)

why are the tabs in ASCII plain text format?
- small file size (not many bytes)
- plain text will probably be in use long after other tab formats have disappeared
- ASCII is an international non-proprietory standard and is readable by inbuilt commands on most operating systems
- can be viewed by any text editor, browser or word processor that uses a standard European character set
- isn't vulnerable to malware and viruses
- easy to edit and customise
- disadvantage: (strictly speaking) it only has standard characters (eg no accents)
- disadvantage: it's difficult to generate a MIDI file from the tab (and vice versa)
- disadvantage: it's difficult to generate a score from the tab (and vice versa)

further discussion

You are welcome to discuss this on the Facebook Group, or to email me your thoughts about it.



back to the Classtab home page

comments to weed@wussu.com
revised & validated (HTML 3.2) 3 February 2020
URL http://www.classtab.org/upgrade.htm