eyegrade

I've just moved Eyegrade to a new Web location at eyegrade.org. These are the important links: Project homepage: http://eyegrade.org/ User manual: http://eyegrade.org/doc/user-manual/ Blog: http://eyegrade.org/blog/ RSS feed: ... [More] http://eyegrade.org/blog/rss.xml Requests for the old addresses will automatically be redirected to the new location. However, the old server may be down for some periods of August. In fact, the frequent downtimes of the old hosting are one of the main reasons for the change. During those downtime periods redirections won't work. However, the new addresses will work properly even in that case. The new website is hosted at the GitHub Pages service. My experience so far with this service has been very satisfactory. The availability of the website with the new hosting will definitely be much better. [Less]

I'm planning the next major release (0.3) of Eyegrade for September. There are some features I have in mind, but listening to the users from time to time does not harm ;) If there is a feature you are especially interested in, just let me know by ... [More] commenting on this post. Apart from some polishing here and there, these are things I'm thinking about: Right now, you can review and fix detection errors in an exam only at the moment you scan it. What if you discover an error later on? It think it would be great if the interface allowed you to open a grading session anytime later and use the same reviewing/fixing features. This feature would probably include a list of students and grades in the interface, so that you can quickly access the exam of a specific student. A user interface for entering the questions of an exam, creating the PDFs, etc. This would probably include dropping LaTeX in favor of something else (my main option is the ReportLab library). Using the current command-line interface and LaTeX would still be possible, but not the preferred method. Making life easier for users that only want to use Eyegrade for grading, but not for creating the exams. I include here features such as creating a .eye file through guided dialogues or creating the PDF of a personalized answer sheet in the user interface. It's about time to close issue 36. Adapting the user interface for multiple languages. I can start with an English, Spanish and Galician interface, and wait for volunteers to translate it to other tongues. I won't have time for all the features in the list, so you can help me to prioritize. Of course, you can also request features not in the list ;) [Less]

I'm planning the next major release (0.3) of Eyegrade for September. There are some features I have in mind, but listening to the users from time to time does not harm ;) If there is a feature you are especially interested in, just let me know by ... [More] commenting on this post. Apart from some polishing here and there, these are things I'm thinking about: Right now, you can review and fix detection errors in an exam only at the moment you scan it. What if you discover an error later on? It think it would be great if the interface allowed you to open a grading session anytime later and use the same reviewing/fixing features. This feature would probably include a list of students and grades in the interface, so that you can quickly access the exam of a specific student. A user interface for entering the questions of an exam, creating the PDFs, etc. This would probably include dropping LaTeX in favor of something else (my main option is the ReportLab library). Using the current command-line interface and LaTeX would still be possible, but not the preferred method. Making life easier for users that only want to use Eyegrade for grading, but not for creating the exams. I include here features such as creating a .eye file through guided dialogues or creating the PDF of a personalized answer sheet in the user interface. It's about time to close issue 36. Adapting the user interface for multiple languages. I can start with an English, Spanish and Galician interface, and wait for volunteers to translate it to other tongues. I won't have time for all the features in the list, so you can help me to prioritize. Of course, you can also request features not in the list ;) [Less]

Eyegrade 0.2 has been released! It features the shiny new PyQt-based user interface that I showed in previous posts. The Eyegrade User Manual contains up-to-date instructions for using the new interface. If you have Eyegrade 0.1.x installed, you need ... [More] to install PyQt and change the value of an environment variable. See the section about upgrading Eyegrade. This new user interface will facilitate other usability improvements in the future, such as the possibility of reviewing previously graded exams, editing the student list, writing grades to disk in several orders and formats, etc. If you experience problems with this new version, please let me know by commenting on this blog or posting an issue at GitHub. [Less]

Eyegrade 0.2 has been released! It features the shiny new PyQt-based user interface that I showed in previous posts. The Eyegrade User Manual contains up-to-date instructions for using the new interface. If you have Eyegrade 0.1.x installed, you need ... [More] to install PyQt and change the value of an environment variable. See the section about upgrading Eyegrade. This new user interface will facilitate other usability improvements in the future, such as the possibility of reviewing previously graded exams, editing the student list, writing grades to disk in several orders and formats, etc. If you experience problems with this new version, please let me know by commenting on this blog or posting an issue at GitHub. [Less]

I've been working on the new session dialog. Now it is a wizard with three pages. The main novelties are that: You can now select more than one student list. All of them are used when detecting the student id. You can now enter the scores for ... [More] correct and incorrect answers. If the exam configuration file already contains the scores, you'll see them as default values. In addition, you can let Eyegrade choose appropriate values for you, by just entering the maximum score of the exam and choosing whether incorrect answers should penalize or not. You can try the new dialog in the development branch at GitHub, and see it this screenshots gallery! This new dialog will appear in the 0.2 release. I have in mind for a future release the possibility of entering the exam configuration from the new session dialog, as an alternative to reading it from a file. This may be handy for users who do not create the exam with the command line tools that Eyegrade provides. Comments and suggestions are welcome. [Less]

I've been working on the new session dialog. Now it is a wizard with three pages. The main novelties are that: You can now select more than one student list. All of them are used when detecting the student id. You can now enter the scores for ... [More] correct and incorrect answers. If the exam configuration file already contains the scores, you'll see them as default values. In addition, you can let Eyegrade choose appropriate values for you, by just entering the maximum score of the exam and choosing whether incorrect answers should penalize or not. You can try the new dialog in the development branch at GitHub, and see it this screenshots gallery! This new dialog will appear in the 0.2 release. I have in mind for a future release the possibility of entering the exam configuration from the new session dialog, as an alternative to reading it from a file. This may be handy for users who do not create the exam with the command line tools that Eyegrade provides. Comments and suggestions are welcome. [Less]

I'm programming from scratch the graphical user interface of Eyegrade. The old user interface uses Pygame. It allowed me to build the first interface of the program very quickly, but its lack of graphical components (buttons, dialogues, menus, etc.) ... [More] was preventing me from programming a more user-friendly interface. I've decided to use PyQt for the new interface. Why PyQt? I programmed a game with Qt in C++ many years ago, and I liked the library a lot. With the python bindings, it is even easier to use. The new user interface will be released with Eyegrade 0.2 (hopefully, before the end of January). Check the first screenshots gallery! Right now the program does more or less the same as the old interface, but it will be easier to add new features in the future. The brave can give it a try before the release (it is available at the development branch of Eyegrade at GitHub). Suggestions are welcome (just post a comment here or write me an email.) I have tested it only in Linux, although it should work in Windows too. If you try it, notice that: You need PyQt (package python-qt4 in Debian and Ubuntu). There is no src directory anymore. Following the Python conventions, the Python files are now directly under the eyegrade subdirectory of the main directory of the project. The main program does not receive command line arguments. The .eye file and student list are selected at the new session dialog. [Less]

I'm programming from scratch the graphical user interface of Eyegrade. The old user interface uses Pygame. It allowed me to build the first interface of the program very quickly, but its lack of graphical components (buttons, dialogues, menus, etc.) ... [More] was preventing me from programming a more user-friendly interface. I've decided to use PyQt for the new interface. Why PyQt? I programmed a game with Qt in C++ many years ago, and I liked the library a lot. With the python bindings, it is even easier to use. The new user interface will be released with Eyegrade 0.2 (hopefully, before the end of January). Check the first screenshots gallery! Right now the program does more or less the same as the old interface, but it will be easier to add new features in the future. The brave can give it a try before the release (it is available at the development branch of Eyegrade at GitHub). Suggestions are welcome (just post a comment here or write me an email.) I have tested it only in Linux, although it should work in Windows too. If you try it, notice that: You need PyQt (package python-qt4 in Debian and Ubuntu). There is no src directory anymore. Following the Python conventions, the Python files are now directly under the eyegrade subdirectory of the main directory of the project. The main program does not receive command line arguments. The .eye file and student list are selected at the new session dialog. [Less]