- Academic
- AdaptiveDB
- Admin
- All
- Bailey
- CanMys
- Cascade
- ColDesp
- Depts
- DHSI
- FrancoToile
- HOPOL
- HumsSites
- IMT
- Lansdowne
- LondonMap
- Maint
- Mariage
- MoM
- Moses
- MyNDIR
- Pro-D
- Projects
- Properties
- RenMedics
- ScanCan
- Times-Col
- Transformer
- Vac/Hours
- Vesalius
- viHistory
Image Markup Tool blog
18/05/11
09:25:26 am, by mholmes, 21 words, 877 views 
Categories: Activity log, Announcements; Mins. worked: 60
IMT version 1.8.2.0 released
The Image Markup Tool version 1.8.2.0 has been released. This is a minor bugfix release. See the Update page for more details.
11/05/11
Fixed a bug in IMT 1.8.1.9
Working at home on a personal project, I've found a bug in the way IMT handles the content of annotation titles (which are <head> elements). When reading <head> elements which contain mixed content, a space character preceding an element node is eliminated. I pinned it down and fixed it, and I've created a new release, but I'll test it at home before I release it finally.
06/04/11
ImtLink and ImtLinkSet basically working
They can read and write themselves from a QDomDocument, and seem to be working well. Next, I need to polish up the test application so that it works as a demo of that module of the real app, which means installing some more filtering features (sorting works already, but filtering on any of the values in the fields would be great).
05/04/11
ImtLink and ImtLinkSet progress
Added transcriptional attribute, and tested sorting with QSortFilterProxyModel.
15/03/11
ImtLinkSet now functioning as a working model
...in that I can add a link and have it show up in the connected QTableView. We're moving forward. Must remember to add the link subtype field to ImtLink, though.
14/03/11
Progress with ImtLinkSet
Began fleshing out the ImtLinkSet class, after some trouble deciding whether to base it off QAbstractTableModel or QStandardItemModel, and whether to keep the links in a QMap or QHash (chose the former in both cases). It compiles, but doesn't have enough functionality for testing yet.
I'm still unsure about QMap; it may be that a simple QList with some lookup functions would be way better in the end.
11/03/11
Started again with links
After some experimentation, I realized my link setup was far too complicated, so I've thrown it away and started again, based on what I've learned from my home project. I've now rewritten ImtLink, and all links will be handled by a single ImtLinkSet class which will descend from QAbstractTableModel (not yet started). The end result should be much simpler, and easier to plug into the GUI.
04/03/11
Began converting ImtLinkGrpSet to descendant of QAbstractTableModel
One thing I've learned from my home project GVT is that your core data model really should descend from an QT abstract model, and not anything else, so I've started converting the top-level link-handling class, ImtLinkGrpSet, to a descendant of QAbstractTableModel. This involves re-implementing inherited functions from ImtElement, and implementing the core virtual functions from the table model. It's about half done, with one outstanding difficulty.
Wireframe planning meeting
Interview with MT to complete a questionnaire from which she'll build a wireframe model. This was useful, and helped me to clarify a couple of ideas I haven't been sure about. I'm going to detail them here while they're fresh in my mind:
- All main windows will be dockable.
- The three main windows will be:
- The Images window, looking much like our previous mockup.
- The Links window, which will provide an accessible list of all the links made so far, organized by category.
- The document browser, which will provide access by filterable xml:id to the ids already in the document, and also by means of a tree model of the document body.
- Other windows will be modal dialogs:
- The category manager (or should this tie into the links manager?).
- The XML editor (pops up from the document browser when you elect to edit an element).
- The Preferences window.
- The Output options window (could this simply be integrated into Preferences?).
- Still haven't decided how to handle translations -- presumably the easiest mechanism would be QT's built-in translation tools, but this might require separate compilation for each language -- check this out.
- One issue which came up was accessibility: is it going to be possible to allow users to define zones using only the keyboard? It's conceivable, but it might be really difficult to design and code.
18/02/11
11:28:50 am, by mholmes, 106 words, 878 views Categories: Activity log, Announcements; Mins. worked: 120
New release of the Image Markup Tool
A couple of bugfixes and enhancements have been made to the Image Markup Tool, resulting in the release of version 1.8.1.9. These are the changes:
- A Hungarian interface translation was contributed by Kóta Péter.
- Pressing the Delete key when an annotation zone was selected on the image didn't do anything; now it triggers a "Delete annotation(s)" action.
- When clicking in the Annotation Title field, if the default text is still there as a guide, it should be removed automatically. However, this wasn't happening when an alternative language interface was loaded. That bug is now fixed.
The new version is available from the IMT website.
:: Next Page >>
Image Markup Tool blog
The Image Markup Tool is a Windows application for annotating images, using TEI XML as its data format. Our aim is to produce a tool which creates conformant TEI P5 XML files, but which has a simple enough interface that it can be used by people with little or no experience in editing XML code.
Actions
Reports
Categories
- All
- Activity log (254)
- Announcements (9)
- Half-Baked Contributions (9)
- Tasks (35)
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | |||
XML Feeds