ActiveBlog

Komodo 6.0 Beta 2: HTML 5, CSS 3, Python 3, Database Explorer, Publishing, ...
by Trent Mick

Trent Mick, July 14, 2010

We (ActiveState) released Komodo 6.0 beta 2 yesterday and we want your feedback, bugs and IDE dreams. While we've made nightlies available since almost the first builds of Komodo 6, we feel that Komodo 6 is getting stable enough that it is time to start talking about it more to get a wider audience trying it and giving us feedback on what we've done so far.

So if you are a current Komodo IDE or Komodo Edit user; in the market for a new Python, Perl, PHP, Ruby, JavaScript, Tcl, XML, HTML, CSS IDE or editor; interested in hacking on an open source editor; or just curious please

➊ download the beta:

➋ read some of the details below and

➌ tell us how you really feel:

What's New in Komodo 6?

A lot. HTML 5 autocomplete. CSS 3 autocomplete. Full Python 3 support (debugging, syntax checking, autocomplete, code browsing). A new Database Explorer tool for quickly exploring SQL databases (SQLite out of the box and extensions for MySQL and Oracle, with plans for Postgres). A new project system called Places that adds a file system browser (local and remote). New publishing support for syncing a directory with a remote machine. Additions to Komodo's Hyperlinks for quickly navigating to file references. Added support for PHP, Perl, Ruby and JavaScript regular expression debugging with Komodo's excellent Rx tool. See the Komodo 6.0 Features post for a full outline.

Your feedback please

Komodo 6 is still months (a few at least) away from a final release. We'd love to have your input on how we can polish and improve on the above work and how we can make Komodo IDE and Komodo Edit tools that help you get your coding work done faster. Please subscribe to this blog or follow @activestate on twitter for comings posts that go into detail on what's coming and new in Komodo 6. And please give us your feedback. Enjoy.

Subscribe to ActiveState Blogs by Email

Share this post:

Category: announcements
About the Author: RSS

Trent Mick is one of ActiveState's Python gurus and senior developer. He's a member of the Python Software Foundation and is the author of many popular Python modules. At ActiveState his primary focus is Komodo. Trent has a Bachelor of Engineering and B. Sc. in Computer Science Degrees from the University of Saskatchewan.

Comments

20 comments for Komodo 6.0 Beta 2: HTML 5, CSS 3, Python 3, Database Explorer, Publishing, ...
Permalink

Looking great.. but..
How can i put a file into the toolbox ? !
I had large collection of links to the local files, which, after opening new komodo are not present.Even more, I can't add any local file to the toolbox....

Is it a bug or I'm doing something wrong.

Permalink

Karol, there's no bug here, just a change in how we're
managing tools, projects, and files going forward.

We dropped files (and folders, etc.) from the toolbox.

We've also dropped directory shortcuts, but they get
replaced with a macro that looks and acts just like a
directory shortcut. You can see this macro in
[Sample Macros|Create Directory Shortcut], and it should
be easy to create a similar macro that gives you quick access
to files (although you'll lose the properties dialog).

We are planning on adding something like "Favorites" to
the Places sidebar, so you'll have the same kind of
quick access to commonly used files that the old toolbox
gave you.

Also, when Komodo converted the version 5 toolbox the
first time, it wrote out a list of all the tools that
it didn't convert to the pystderr.log file. You can
reproduce this process by removing the toolbox.sqlite
and tools/ directory from your profile directory,
removing the tools/ directory from your shared data
directory if you have one, and restarting Komodo.

Hope this helps,
Eric

Permalink

Thanks for great explanation.
Lookin forward to "Favorites" feature.
Best Regards,
Karol

Permalink

1. The Places' Name Button shows the pop-up menu of the files. Seems wrong to me!

2. Also that button seems a lot of waste of space only for having the name soring action in that full length.

3. The folder icon at the left of Places does nothing when clicked, so it is useless. Wait, I right clicked and pop-up menu appeared. User as to guess that he/she has to right-click, not good.

4. The sidebars continue to be very inflexible. I can not concentrate every sidebar at the same side.

Permalink

segiol, you're right in sync with where we're going.

The "Name" button has already disappeared in the
nightlies, and is replaced with a sort popup menu
in the gear popup menu.

The popup menu at the right of the places mini-toolbar
will be merged into the folder icon at the left.

It's possible that with the changes we've been making
to Komodo, we'll be able to make it easier to move
sidebars around, or even to allow them to show up as
standalone windows. I can't promise that'll happen,
or that it's reasonably easy to do. But they no
longer have code that assumes where they live in
the XUL tree, so it might be possible to do. Anyone
want to try writing an extension?

- Eric

Permalink

I would LOVE to see better dynamic language debugging. For example, inline notification for errors and warnings that are normally produced at run-time. Perhaps some static analysis can be performed (clearly not everything will be found - these are of course dynamic languages). Or perhaps the script could be executed in a sandbox and the run-time errors caught. This would really be a winning feature.

Permalink

@Brandon Siegel: Komodo *does* have background syntax checking for Perl, Python, PHP, Ruby, JavaScript, XML, HTML, & CSS. For each of these the native interpreter for the language (or the internal Mozilla build's HTML/JS/CSS tools for those languages) is being used to catch syntax errors. If you have PerlCritic installed (a static analysis checker for Perl), Komodo's syntax checking for Perl will show warnings/errors from it inline.

Komodo's run command system, macro system, and extension system can be used to integrate 3rd-party linting/checking tools that do basically what you are asking. For example, integrating Pylint and Pyflakes from the Python world would be interesting. Komodo should indeed always try to make these kinds of integrations easier or, if possible, just work out of the box. The fundamentals are there though.

Cheers,
Trent

Permalink

Tell us a bit more, if you would, about the database explorer functionality you mention... like, to start with, where we would find it to play with it a bit and what it might take to extend/provide that functionality to other DBMS (e.g., MS SQL Server).

Permalink

The DB explorer is in the left sidebar, with projects.

It currently supports Sqlite3, PostgreSQL, MySQL, and
Oracle, but you'll need to install extensions for the
latter two

MySQL: http://community.activestate.com/xpi/mysql-database-explorer

Oracle: http://community.activestate.com/xpi/oracle-database-explorer

The explorer is designed to allow plugging in of other
connectors -- each one is an extension, that automatically
registers itself with Komodo at startup. To build an extension
you need the database client library, a Python adaptor
that talks to the library, and a back-end XPCOM component
written in Python that mediates between the front-end
db explorer, and the Python library. You can see one
of the connectors we ship as an example.

If the demand shows up, we can write a connector
for SQL Server. But it's not in our current plans.

- Eric

Permalink

Very neat so far. Any plans to open the table editor/viewers in tabs like source files?

Permalink

Been trying out the beta of IDE 6.0, and I've run across a few problems. Short version: Can't have multiple projects open at once, and the code pane takes the same spot as the project pane. Both of these are showstoppers for me.

More detailed version here: http://www.danhulton.com/blog/2010/07/16/initial-impressions-of-komodo-6...

Permalink

Dan,

We've been actually planning this move since version 5, when we introduced multiple windows. People have wanted the project system to also work like a file manager, but it wasn't designed for that, and retrofitting it didn't make a lot of sense.

The new projects now reflect the current directory, and it made more sense to allow only one directory per window.

Thanks for the comments on your blog. The best way to accomplish that is by using multiple windows, with a different project open in each window. I'll add an "Open Project in New Window" command to make this easier to do.

- Eric

Permalink

Thanks for that!

Would it also be possible to add the currently-opened project to the titlebar? Something like "index.php - ClientDB (D:\Projects\ClientDB)" If I'm going to be switching between windows all the time so I can flip through projects, then having easily-identifiable windows will be critical.

Permalink

That's going on in the nightlies right now -- you can follow along at
http://downloads.activestate.com/Komodo/nightly/

Keep in mind that things are going to be in flux for
the next few weeks.

- Eric

Permalink

I forgot to mention dealing with the codebrowser -- please see the TweakUI extension at
http://community.activestate.com/xpi/tweak-ui

- Eric

Permalink

Sadly, TweakUI isn't compatible with v6 yet.

Are there any plans to enable this sort of functionality in-house, or will everyone have to download an add-on to move their windows around?

Permalink

There aren't immediate plans to make this happen, but it
is something we have talked about in the past.

I'll ask Todd if he can update TweakUI soon.

- Eric

Permalink

I installed K6 because it claimed to have fixed the pegging of the cpu to 100% caused by the code intellisense. It's not fixed. The following pattern cause it to happen:

(function(){
var d = document;

window.bv = {
query: function(q){
var r = d.getEle // dies!
}
}

})();

The key trigger there is using "window". Without that it didn't happen.

It looks that I have a workaround by using var bv = {...} and then at the end of my code adding: window.bv = bv;

cheers

Permalink

Stable and fast; looking forward to the final release.

I've discovered a performance issue with the sqlite3 explorer.

performance while working with a ~1,000,000 row
db was poor -- very slow/sluggish.

Not an issue with same db under V5.2.4 + Sqlite Manager.

Keep up the good work.

Permalink

Thanksss