gaphu.js

Current release is version 0.0.9. Please consider this a beta release.

The Expression Editor has been developed and tested primarily with Firefox on a Mac.

Please report bugs and cross browser issues.

The following os/browsers have been superficially tested.

	Firefox	Safari	Opera	Chrome	IE6	IE7	IE8
OS X	v3.6.11	v5.0.1	v10.62	v7.0.517.41	v6.0.2800.11061	v7.0.5730.131	untested 2
Win XP	v3.6.11	v5.0.2	v10.63	v7.0.517.41	untested	v7.0.5730.13	untested
Linux	untested	untested	untested	untested	untested	untested	untested

working (minor bugs)
buggy (see issues)
not working
untested

1 tested in Wine 1.1.35

2 IE8 in Wine not stable enough to test

I have tried to make the code as unobtrusive as possible to the current layout and style of the html/css however there are several places in which this was not possible:

• Pages must be using strict mode in order for layout to be correct
• Blue "focus glow" is disabled in Safari and Firefox as it affects size calculations in a strange way
• If the textarea's own position is static (the default) then it is changed to relative
• The textarea's z-index is managed to allow the error highlighting to work
  (as this introduces a new div behind the existing textarea)
• It is advised that your textarea be in a positioned parent container (use position:relative) in the following circumstances:
  • If your editor is inside a scrollable div (make sure the container is also in the div)
  • If you have dynamic content that changes the position/size of your textareas
  You do not need to do this for window resizing which is managed automatically
• If you add body{position:relative} to your css then all the positioning gets screwed up in FF
  (I don't know why you'd do this).

• Cross browser check on linux
• Disable errors if no parser set
• Disable autocomplete if no autocomplete set
• User method for binding to all textedits satisfying a jQuery select
• option autocomplete: [off | onDemand | onChange]
• Investigate making the error highlighter wrap the editor for more robust positioning (although at the cost of greater DOM changes)
• Scalability testing
  • Delay while typing before parse request
  • More sophisticated caching to reduce server hits
  • Allow a max results to be specified for ac results (for large data sets)
• Improve demo
  • Autocomplete match on camel notation (eg wBo matches WineBody)
  • More convincing test parse function
  • Try to write a general service for XML that works against a schema using SAX exceptions
  • Try to write a general service that takes an (E)BNF gramma (HARD?)r
• OWL parser errors
  • ac should return [ etc if "hasVintageYear only (yearValue some xsd:int"
  • No autocomplete on "yearValue some ". (see OWLAPI bug)
• Text input support
  • error highlighter does not manage horizontal scrolling
  • error highlighter does not manage custom height (vertical-align does not work)