Only for snippets of code. For included files it reports the line correctly.

https://github.com/caolan/kanso/issues/39 ;)

one possibility is using a git hook

#1

use more types, e.g.

    val exec_js_r : string -> string -> JSON.T list list -> string

should be

    val exec_js_r : fptr -> string -> arg list -> string

#2

The getter

    val exec_js_get : string -> string -> JSON.T list list -> string

should be

    val exec_js_get : fptr -> string -> string

Resize browser so that a horizontal scrollbar appears. When scrolling, the navigation goes on top of the content.

The simplest fix would be setting navigation's background:white.

<script type="application/x-polyml" src="no_such_ml_file.sml"></script>

Gives lots of spurious errors if the file "no_such_ml_file.sml" does not exist. We should detect if the file doesn't exist (404 messages), and give a sensible error.

Setting the custom ML path does not work (in settings)

TODO

• better editing of multiline commands
• Autocomplete
• a separate thread for console?

SOME PROGRESS

• styling and coloring of the messages (chrome style)

COMPLETE

• adjusting height of the logArea when change the size of the console
• tab and window madness (e.g. when two windows are opened the console breaks) (see https://developer.mozilla.org/en/Code_snippets/Tabbed_browser) (except the dragging of the tabs)
• Always on / Always off settings
• History of entered commands
• Style of the disable button

Won't be needed if #4 solved

try entering
2+2
it produces an output
try entering
2+
now whatever you enter won't have any effect :(

Multiple clicks on the polychrome icon (at the bottom-right), to start a polyml console, opens up multiple-pop-up windows asking if you want to open the console. We should only open up one however many times that icon is clicked.

Would be nice to have a complete JSON library. Could be reused in many other projects. It's not that big so it shouldn't be hard to fully implement it.

It could then be used in parsing messages from Firefox and event data. Also for example for jQuery function parameters (e.g. jQuery.ajax({type:GET, url:www});

Now the same code is used in Socket1 and Socket2 prototypes. Should have done this in the very beginning, but I can't seem to get this prototype inheritance right.

This would be a more direct way of executing PolyML script tags. Firefox would ask our XPCOM component to execute the code every time it finds a script tag. This way you wouldn't need to reread the page after it has loaded.

On the other hand, this is also too Firefox specific and it might actually slow down the rendering of the page.

The way JavaScript functions are executed in JSFFI.js allows only for certain types of functions to be called. I think, because of the way "this" is handled when doing obj[field].apply(obj, args);

For example, currently, all values sent to Poly as part of a foreign function call are strings. Every function using jsffi.exec_js... has to convert those strings into appropriate types. Which is also not that nice, because currently there is no guarantee that for example a string received from JavaScript can always be parsed into an Integer etc.
Additional dirty bit is a similar function Memory.convertArgsToPoly, which is used in Poly callbacks, where strings like "some_function arg1 arg2 arg3" are formed from javascript variables. Similarly to before, there is currently no guarantee that the number of arguments to the functions is going to be the same all the time or that those times are always gonna be the same. For example, if function "some_function" is of type int -> int -> string -> unit, we can't guarantee that the first argument in javascript function call will be smth that can be parsed into int.

This way all of the output produced by PolyML (like compilation information of the extension) will be printed to console.
Currently, you can't see extension compilation errors if you don't open firefox from the terminal

the extension has been reviewed. And remove the scary looking Warning header

when included like this: <script type="application/x-polyml" src="empty.sml"></script>

different elements, like htmlelement, formelement.... fptrs.. libraries.. shapes.. etc..., datatypes, signatures, structures...

Currently, to enable callback handlers, one has to define a table to store the handlers and then define special handling functions that can call functions from that table. Try to implement this in jsffi in a more universal way, to allow for adding callbacks like this:
exec_js ojb "drag" [args.callback f, args.callback b]

It should only display single alert.

a workaround is to create a wrapper function in the html doc like
fun newSomething() {
return new Someting();
}
and calling this wrapper function from sml
exec_js_call "newSomething"