enridaga / gapvis Goto Github PK

Text and Image should be visible only if there is some content in the respective areas

As the summary says. Discussed in ekansa/gap2#23

We need also to separate app configuration from the built js, so people can then deploy the distribution without the need of the sources.

As the summary says

It should include at least:

• how to install/use it
• specification of the data API to implement

This linked URL is 404 now, maybe Simile widgets were relocated?
http://static.simile.mit.edu/timeline/api/images/copyright-vertical.png

See discussion at ekansa/gap2#29

Don't know why, this single test does not pass even if I can test it correctly on the live page:

    test.assertEval(function() { 
        return gv.app.currentView.slots['.right-panel'].slots['.top-slot'].markers[0].map.getZoom() > 0
    }, "Map isn't screwed up");

We need to pack a customized version for the hestia project.
Todo list:

• Use Hestia Brand
• Top links to point to the Hestia project
• Remove the "published date" note
• Remove the section "Book references" if empty on the place page
• Place page, rename "Ch. (?):" to "Bk (?) Chapters:"

Is there an easy way of getting the map window to automatically zoom in on the places mentioned in the text in the "reading view"? At the moment, the automatic zoom is for the entire world, which is obviously irrelevant

This project has a lot of dependencies. None of them are documented properly.

For every book, the timeline never show any annotations.

Reproduction :
http://gap.alexandriaarchive.org/gapvis/index.html#book/12/read/509/991376

As you can see, Alone, Asia and Europe are annotated, but nothing is shown on timeline.

It's worth trying to implement awld.js (http://isaw.nyu.edu/members/sebastian.heath-40nyu.edu/awld-js) in HestiaVis to see what happens. I don't know if it's worth it -- it seems to have been removed from several of the sites that were originally using it -- but one potential that could be useful here is a gateway to wikipedia.

As described in ekansa/gap2#2

I was certain I'd seen a version of HestiaVis where the text chunks were linked to the appropriate Perseus sections. The scripting has clearly been adapted -- in Eric's version, the link is just to the Perseus text citation, but I can see that the current Perseus link includes both book and chapter. But now, in both the OU version and the version on your repo, we're back to all links leading to the first section of the first book in Perseus, which is not that useful. It would be much better to go directly to the same section -- and if this scripting was already done, not too difficult, right? Or am I misremembering?

The production build does not work.

I had comments from both high-school and college-level students this semester that they couldn't figure out how to deal with zooming in and out on the map without the aid of a +/- zoom button of the familiar sort. Double-left-clicking in and double-right-clicking out was not intuitive for them. Would it be possible to add zoom +/- buttons at one corner, even if it costs a little real estate on the map?

Implement support for alternative texts

Link should point to the first page of the bar/set
Highlight always go to the next bar after clicking (?!)

As the summary says.
It could point to a page in the database of places or to a feature to notify administrators about the problem (similarly to the popup form in the reading view).

Actually the production build is placed in the root project.
It would be nice to have it in a separate folder, ready to be zipped and pushed as release

It may be a configuration issue, or it is due to incompatibilities with the new version of casper.js.

Message is:

run-tests:
[echo] Running tests
[exec] CasperError: casper.test property is only available using the casperjs test command
[exec] /Users/Shared/casperjs/modules/casper.js:172

The map dosn't load right in any of the pages with Hestia data. It is misplaced at the bottom, out of the frame.

This suggests changes in the usage policies of the G api.
Need to add a G API key to index.html and detail this change in the documentation ...

When building with output compression, the app does not start!

To support the use case described here
ekansa/gap2#19

This might be related to the wrong link to pelagios

As the summary says

This is detailed at ekansa/gap2#17

For example, in case of Hestia the link should be to Perseus (where we got the Herodotus text from), not to Google books (in this instance).

This means that we need it to be part of the customization.

When the user has a window smaller then the given fixed height, half of the UI is unreachable. At first sight, there is some fixed height + absolute positioning which is not really needed. Removing them and adjusting the related css properties should do the job.

This is discussed at ekansa/gap2#8

Alternative index template for hestia

I notice that the slim number of images that are coming in from the Flickr stream may be related to a narrow interpretation of the machine tags. In Argos (http://enridaga.github.io/gapvis/gap2/#book/1/place/336), for example, only 5 of 18 available images are coming in, because only those tagged with pleiades:place are pulled. But the set of Pleiades machine tags in use includes pleiades:depicts and pleiades:findspot and several others that you can find here: https://www.flickr.com/photos/tags/pleiades:*=570106. All of them use the same URI ID number. Could the search be changed from pleiades:place= to pleiades:*=? to capture all the available tagged images? Among other things, this would bring in objects that the Open Learn team seems to be very interested in.

The histogram in Firefox:

• does not show number of instances at the end
• looks cropped on the right

This has been discussed in ekansa/gap2#26

While we're fixing the histogram, can we push it to the right if there's space? Right now several of the longer place names disappear under the map window on the left, but I see a lot of white space to the right of the numerical reference count along the right border.

A separate and even more minor issue: the link to "View on Perseus" (which we're updating to jump to the book/chapter, right?) currently reads "View on View on Perseus".

The current code base relies on bootstrap 2.* as basic css framework, and has a dependency with the less sources. These do not compile with the last lessc (now 1.5.0) . It is quite hard to stay with bootstrap 2 for this reason.
In general I think it is a good idea to upgrade dependencies to the latest versions.

@enridaga @ekansa: I found it really useful to have Eric's token-correction page, and I think there's more work to be done here (for example, to associate Olbia with elliptical spatial phrases like "city of the Borysthenites": http://gap2.alexandriaarchive.org/report/token-issues/117172). I can see that the Pleiades associations I updated are reflected in Enrico's version, which will be the one that moves to the production server. Is there a way to preserve the token-correction interface that Eric built, so that I can continue to use that? Right now the call-out for a site in Enrico's version takes the user directly to Eric's token page, but presumably we either want this behind a login or we want to kill the issue-reporting button and just maintain Eric's correction page (as long as it's feeding corrections back into the main tokenized text).

I'm going to cross-post this issue in Eric's repo as well. I don't understand the dynamics well enough to know how hard or how easy this is -- and if I haven't explained it well, please don't hesitate to ask for clarification.