ak19. Friday, May 9th, 2014
It’s been a very long period since we blogged our progress. Rest assured we’ve been working hard to improve Greenstone 2 and 3, and it’s only the blogging about it that fell by the wayside. Here’s some of the things that I’ve been working on in the last few months:
- Securing Greenstone 2 pages: this involved significant changes to both the code and the macros files
- Updating the GTI Greenstone installation. Owing to the security changes for Greenstone 2, the Greenstone Translation Interface on nzdl needed to have the latest Greenstone2 to work again
- Fixing up a Remote Greenstone 3 authentication issue
- The FormatConversion wizard dialog. This completes the process of opening a Greenstone 2 collection in Greenstone 3. The format conversion dialog automatically generates Greenstone 3 equivalents for Greenstone 2 format statements behind-the-scenes, before presenting these to you. You can then interact with the wizard to improve any of the Greenstone 3 format statements that have been generated.
sjm84. Friday, May 25th, 2012
This week we’ve been hard at work testing Greenstone 3. We’ve managed to discover a few bugs and have fixed several of them already. While we’re at it we’ve also added horizontal classifiers into Greenstone 3 (frequent Greenstone 2 users may find this a very welcome addition). A horizontal classifier has the top level of the classifier (e.g. ‘A’ ‘B-C’ ‘D-F’ etc.) displayed in a row along the top of the browsing area instead of vertically down the page.
There’s not much more to report about my week as it has mostly involved testing and bug fixing, which is not particularly interesting to write about.
sjm84. Friday, May 18th, 2012
This week I have been testing and have fixed several minor bugs in Greenstone 3. I have also started working on a new feature (to be included in 3.06 most likely), which will theoretically allow much more advanced collection editing than what we’ve ever had before. At the moment a single page in a collection can be made up of many different files and if you want to edit something then you have to know which file it came from. For example, the basic file used for a document view is document.xsl (stored in the interfaces directory), but if someone wants to modify part of it then they could add their own template to their collectionConfig.xml file or they could create their own interface file and put it into the transform directory of their collection. This new feature will keep track of what file each change has come from and (probably) allow you to edit the file via your web browser.
While I am working on this feature Anu will be taking over testing for the release.
sjm84. Monday, May 14th, 2012
Sorry that I haven’t posted an update in a while, I keep forgetting to do it. Good news though, we are now in the final testing stages of Greenstone 3 and should hopefully have a 3.05 release candidate ready before the end of the week. We’ve also got some exciting things planned for 3.06 as well so we’re wanting to get 3.05 out as soon as possible.
There is not a lot to report other than that. Testing seems to be going well and assuming we don’t find any major bugs then keep an eye out for a release candidate in the near future.
ak19. Saturday, May 12th, 2012
Over the week, have been working on the activate.pl script (and things that it needs). The details are at http://trac.greenstone.org/ticket/825
For the latest changes made today, need to retest these changes against GS3 on Windows.
Still need to test the entire process on Linux.
ak19. Thursday, April 5th, 2012
The very start of last week still required more work on the scripts that would handle translations made in Google’s Translator Toolkit. A couple of additional scripts were written.
Thereafter and until yesterday, the work has been mostly centred on GS3’s usersDB:
- getting the output of txt2usersDB to work as input to usersDB2txt and viceversa as well as allowing txt2usersDB to run in append mode,
- creating a new program to modify a user’s details in the DB which then gets called by the new targets config-user and config-admin (for setting the admin password) in build.xml
- getting the releasekit to update the admin password where the user provides this
Instead, I decided to write some handy instructions into the Wiki’s Greenstone 2 FAQ which will help explain how to do some common tasks. The questions added to the FAQ are on how to manually build collections, how to get better error reporting in GLI, how to run GLI in debug mode, how to launch, use and copy from the DOS prompt, how to launch Windows Explorer and where to find the Windows key. From experience, these instructions will be particularly helpful when answering Mailing List questions, as Greenstone users can be referred to these new FAQ items, armed with which they will then be better equipped to help us in the debugging process.
sjm84. Thursday, April 5th, 2012
I’m writing this a day early this week because I will not be working tomorrow due to Easter, I still have a bit to report however.
This week I decided to re-think one of the previous decisions we made in regards to viewing documents in Greenstone 3. In Greenstone 2 you can normally only view one section at a time and therefore it is difficult to get a grasp of where you are in the document and also how big the document is. For this version of Greenstone 3 we decided that we would take the opposite approach and that, by default, viewing the document would always show the whole document instead of just a section. This approach works find for small- to medium-sized documents, but for larger documents the page begins to get too long. To resolve this problem I have decided to implement a mixture of the two approaches. Now, by default, when you view a page it will only show the section you asked for, but it will also give you a full table of contents and links on the page that allow you to view other parts of the document without needing to go to a new page. New sections are dynamically loaded when they are needed and there is also an option to expand all the sections if you do want to see the whole document at once.
sjm84. Friday, March 30th, 2012
Just a short entry today to say that this week has mostly consisted of working on minor features and fixes. All of the major new features are mostly done now and we are nearing the final testing stage before we can release Greenstone 3.