Download Intype 0.2.1.328

Warnings & Announces

• WARNING! Backup your changed files in bundles and themes folders and Uninstall previous release

Features

• Right-Click Popup Menu
• Horizontal Scrollbar
• Horizontal Scrolling with Ctrl+Alt+Wheel and Ctrl+Alt+Left/Right
• Select Lines now rounds selection to lines if selection is active. If selection is already rounded, next line is selected
• Select Indent Level selects lines with the same level (or empty lines). Empty lines at top and bottom of the selection are cropped.
• Select Paragraph selects sequence of non-empty lines above and below caret
• Full Path in Title
• Snippets with empty scope are launched in any scopes, but with lowest priority (good for general snippets like lorem_ipsum.itSnippet)
• Indentation Auto-detection also with support for Emacs style (see below)

Indentation Auto-Detection Plugin Description (codename metacrawler)

Indentation Auto-Detector consists of two detecting mechanisms: examining leading whitespace for lines in document and Emacs-style meta info. Detector is able to choose the best indentation values from both mechanisms.

Soft/Hard tabs detector:

• Detecting soft/hard tabs mode by leading whitespace on the lines
• Is able to detect size of soft tabs. Hard tabs size cannot be detected and defaults to user preferences.

Emacs-style detector:

• Detects soft/hard tabs ands it’s size by emacs-style meta information embedded to document
• Supported properties are:
  • indent-tabs-mode: nil to set soft tabs (spaces), or
  • indent-tabs-mode: t to set hard tabs (tab characters)
  • tab-width-value: value to set size of the identation

Examples for Emacs-style detector:
// -*- indent-tabs-mode:t; tab-width:4 -*-
or
// -*- indent-tabs-mode:nil; tab-width:4 -*-

Bug Fixes

Whats the new Plugins folder for?

rep bug:
1. write a long line (until the horizontal scrollbar has apeared)
2. delete that line
3. the horizontal scrollbar is still there even if there is no text

Albertus: I’m happy to see this new release! Unfortunately Intype does not remember settings about soft tabs: I have to set “Use spaces” each time I open a file..

You can just set the defaults in the preferences file. :) This issue is related to this

semioticmonkey: bug report: the ‘recent file’ list is not up to date. it ‘forget’ some files on his way (the most recent most of the time – WinXP SP2)

Already been highlighted in this thread ;)

shinuza: Wise stuff to create a drop down menu for the meta trigger in html mode ;-)
But I’ve noticed that link trigger include a link stylesheet with “print” as a default “media” value.

Hello, welcome to the forums! :) I’m Josh, the guy who messed with the HTML bundle snippets.. :P

Mm.. the dropdowns are automatic when you have more that one snippet with the same trigger. About the link snippet, I usually have “print” as the value in the “media” attribute, or omit it completely if its the page stylesheet. You can easily remove it by editing the link.itSnippet file :)

In fact, I had a little problem while editing in HTML, when I called the snippet for head I had both head and meta coming, but it didn’t occur in XHTML mode.

Btw it seems xhtml mode doesn’t work at all now (when selecting by the bottom menu), but it works with the keyboard shortcut.
In fact I’ve three choices in the drowndrop menu, and the first one doesn’t work, it might be the same one in the bottom menu.

(It’s not a fresh installation, maybe I should erase everything and try back)

For the link snippet, I was mistaken sorry, you have a drop down menu, one includes screen as default media value, the other includes print. :-)

For the link snippet, no, you’re right :) I didn’t make one that has “screen” as the value for “media”, I just made one with “print” as the value… the reason is because “screen” is the default value, so if the stylesheet’s meant for screen display, you just omit the entire “media” attribute. :P

After I’ve installed, re-installed Intype, the double XHTML mode bug has has disappeared. So as the drop down menu for link snippet :-D

Beside that, it is true, the dev is not as fast as E, but we can’t complain, I’m sure they are doing the best they can actualy.
I also think that they are aware about their competitor from a long time now :-)

The annoying thing, for me at least, is that we don’t have any update on the planning.
We could understand delay for a reason or another,
but having no news scares us that the project would fall into oblivion.

Ben

I agree with Ben, having no news makes us worry and fret (and again about the S&R :P its annoying to have to launch another app just to do S&R while I’m doing minor refactoring in Intype)... I don’t wanna have to use E for the rest of my life!!

Perhaps because of that, some forum members seem to have moved on to better places already…

Sorry or the double post but that IS good news ;)

tstrokes: Idyllrain does this mean that you are moving on and to where?

Nah… I’m still here (posting less as project deadlines approach…). I meant some of the other members who haven’t been logging on for quite some time. :)

I’m glad to see that progress was being made all the while (as opposed to my thoughts that things had stalled due to no news from the blog feed). Sorry I haven’t been around! I’ve been working on finishing up a couple projects at work, going through the stages of a partial (more than half) website overhaul and redesign; and trying to learn some more stuff during my free time.

Anyway, hopefully I won’t be as much of a stranger as I have been in the past couple months. Sorry, guys! Glad to be back. ;) ...oh, and the updates look great! I have yet to try it out though — just got back.

The main reason is that we have finished the roadmap. The current tasks for me is to revitalize and update the editing component to fullfil all our needs until 1.0, this is a huge task to accomplish and is the main reason for being so silent about the next release. Another big update is planned for application due to Juraj’s task with multi-documents and scripting support.

Completing these tasks will move us to 0.2.9 milestone due to merge of many smaller tasks to bigger ones. Next already mentioned update in the release philosophy is to release unstable branches that will be available since we get current branch to working state. We will skip internal testing phase for the future, that is the main cause of the delays between public releases, and we found it much less effective in recent releases.

Another big changes are planned in Juraj’s move to full-time development of Intype, and some other commercial negotiations with our employers to free our hands for Intype development. The development rate however haven’t slow down, there are many new updates to the whole application that are, however not visible to the public.

I will post the new feature list that will be available in the unstable branch as long as we manage some other things around the project.

:D

martin: Great news. thanks!

Take the opportunity to promote yourselves and your hard work a bit more. Maybe schedule a little bit of time each day – even if it’s only 10 mins to write a tiny blog entry – to keep people up to date on what you’re doing.

Little and often is much better than large but infrequent. This will really help to keep the community feeling involved, happy and growing – and to hopefully convert them to customers at a later date.

dflock:
Take the opportunity to promote yourselves and your hard work a bit more. Maybe schedule a little bit of time each day – even if it’s only 10 mins to write a tiny blog entry – to keep people up to date on what you’re doing.

This is a great idea… I really hope the devs can take just a couple of minutes every few days or so, for tiny updates along the way.

Regardless of the communications, I’m very excited for the future, it seems like development will speed up considerably in the next few months.

what do you mean “LTR as well as RTL” intype is not rtl-able

Seriously – more communication and inclusiveness is always a good way to foster community.

Thanks!

:)