ActiveState Community Site - Creating custom editor tab - Comments

a better example

ToddW — Fri, 25 Apr 2008 10:44:46 -0700

It's probably best to extend the "views-editor" binding. Try out this example, I think this may help you along:

If you modify the diff view binding "views-diff.unprocessed.xml" as such:

-    extends="chrome://komodo/content/bindings/views-buffer.xml#view-buffer-base">
+    extends="chrome://komodo/content/bindings/views-editor.xml#view-editor">

Note: The "views-diff" binding is only currently used by the diff dialog (not for view diff in editor tab).

Then open up a diff view in a Komodo editor tab like so:
ko.open.URI("/path_to_a_patch_or_diff_file.txt", "diff");

You'll have close to the functionality you need (i.e. you have the additional diff button toolbar) plus an editable scintilla view.

Note that some functionality will be borked by this example (i.e. close buffer).

Cheers,
Todd

That info was very useful,

basil_brush — Fri, 25 Apr 2008 06:52:58 -0700

That info was very useful, thanks. It seems that, yes, I want to create my own view binding (e.g. views-myextension.xml) but opening it in a browser view gives an undesirable navigation toolbar at the top of the page. I notice that the view manager and view bindings have functions such as newView or doNewView which open a new view of the requested type. Ideally I like to use the same technique, but how can I get the view manager to know about the new view type offered by my extension?

I basically need something like views-diff.xml, but opening in a document tab rather than its own window - and also not read-only, which diff is.

On a side note I had managed to get a new scintilla view insome cases but the editing area only allowed a sinlge line of text because the return key was not recognised. I presume this is something to do with bindings and the way scintilla is embedded as a plugin.

re: custom Komodo tab

ToddW — Thu, 24 Apr 2008 17:23:21 -0700

You'll need to create a custom Komodo view, similar to the view-xxx.xml bindings in:
http://svn.openkomodo.com/openkomodo/browse/openkomodo/trunk/src/chrome/...

Once the view is defined and the bindings (xml and css) are properly setup, you can then create new instances of the view using "ko.open.URI(filepath, 'xxx')", where xxx would be the name of your binding, i.e. "ko.open.URI('foo.html', 'browser')".

The browser preview functionality will likely be the closest match to what you are after, as you can load chrome xul straight into this view by doing something like:

ko.open.URI('chrome://komodo/content/dialogs/authenticate.xul', 'browser');

Cheers,
Todd

Creating custom editor tab

basil_brush — Sat, 12 Apr 2008 13:47:27 -0700

Hello. I'd like my extension to be able to create a new document tab for editing C code, but this code will be processed by my extension and not written to a file. In addition I would like a few extra GUI elements in the page area just above the document itself, mostly for displaying info such as function details and parameters. The editor in the tab needs to be komodo's editor so that all komodo's editing functionality is still there, so not just a plain xul textarea.

If it was firefox I'd just make a xul page, with GUI elements at the top and an editor tag, and open it in a new tab using the "chrome://" address. But how to do this in komodo? I looked in komodo.xul and noticed that the document area is a view tag, which I guess is associated with the xml objects in bindings folder. But I don't know xul well enough to understand it well.

Is it possible to load xul into a view tab or will I have to hack komodo using script? Any commments on the best way to achieve this are greatly appreciated. Thanks.