Skip to main content

Marauder File Viewer

Download


I've been talking about rewriting the File Viewer application I developed at Communisis back in the early naughties for some time now. It took a while for me to find a solution for opening very large files (>20GB) that I liked and a virtual grid that would allow me to view them.

After being (almost) forced to learn Java I thought it might hold the key. It can certainly handle the large files easily enough and JTable is certainly virtual enough to view them. I got quite a long way down the Java route before I decided Swing didn't give me the most aesthetic of GUIs and layout managers were too much like hard work (I've since got to grips with layout managers and changed my mind about them to some extent).

I started looking around for a virtual grid for C#. I already knew that C# could handle the file sizes without any problem from the testing I'd done a few years back. It was pointed out to me that the DataGrid has a virtual mode and a little bit of playing about soon showed me that it was ideal for the task. Moving to C# would loose some of the platform independence I've always strived for, but the better looking GUI and the interest shown by some people who might actually use it in a C# version were overwhelming.

I ported my MVC design directly to C# from Java taking advantage of some of the better features in C#, such as properties and events and I now have a working prototype that allows the user to open and view fixed length record files using an xml layout to describe the fields:
<layout>
<field name="Id" length="20">
<field name="Number" length="20">
<field name="Add1" length="20">
<field name="Add2" length="20">
<field name="Add3" length="20">
<field name="Postcode" length="20">
<field name="CR" length="1">
</field>

This is the current limit of the features. There is no way of saving or reloading projects (a project consists of a layout and datafile), no search or reporting and no way of creating or modifying layouts. This is strictly a prototype to prove the concept.

Marauder File Viewer can be download here (You'll need .Net 2 if you don't already have it). After unzipping double click FileViewer.Exe to run file viewer. To test it:
  1. Go to the Help menu and select Create Test Files to create a set of three test files and a layout file in the same location as the exe.
  2. Go to the File menu and select New Project.
  3. Double click the Fixed Length icon from the New Project dialog.
  4. Click the first browse button and navigate to test1.txt to set the file.
  5. Click the second browse button and navigate to lay.xml to set the layout.
  6. Click create to load the file and layout.
  7. Repeat steps 2 to 6 for test2.txt and test3.txt.

Marauder File Viewer

You can now use the tabs to switch between the test files and the vertical scroll bars to scroll through their content. The Marauder File Viewer will work with any fixed length record text file and any xml layout that uses the format shown above.

The next steps in development will be:
  1. Support for RDF layouts
  2. Allow the saving and opening of projects.
  3. Searching
  4. Fixed length record file layout creator and modifier
  5. Further development plugin facility to allow other file types to be viewed

Comments

  1. Works quite nicely with Mono, so the platform independence issue is not so much of a biggy!

    ReplyDelete
  2. That's good to know, thanks! I assume you tried it on a Mac? I'm hoping to try it on Linux soon.

    ReplyDelete
  3. Any chance you may release the source code?

    ReplyDelete
  4. It is highly unlikely that I'll be releasing the source code, but let's talk about the application you have in mind (paul.grenyer@gmail.com).

    I now have the plugin architecture working and have nearly got the the project interface complete, so you could start writing your own plugins.

    Like I said, let's talk...

    ReplyDelete

Post a Comment

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...