Vanilla 1.1.1 is a product of Lussumo. More Information: Documentation, Community Support.
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:
Emacs-style detector:
Examples for Emacs-style detector:
// -*- indent-tabs-mode:t; tab-width:4 -*-
or
// -*- indent-tabs-mode:nil; tab-width:4 -*-
| Critical | GDI leak fixed |
| Editing | Indenting with soft tabs (spaces) is now working properly |
| Rendering | Changed rendering process, updated performance |
| Editing | No line length limit (EXPERIMENTAL) |
| Cosmetic | Removed square character from status bar |
| Rendering | Caret positioning and hiding now works as expected |
| Cosmetic | Charset drop-down now checks UTF-8 Plain properly |
| Performance | Major rendering, scrolling and caret movement performance upgrade |
| Rendering | Status bar now updates section widths properly |
| Snippets | Fixed bug with disabling nested placeholders |
| Files | Open/Save As file dialogs are now defaults to current doc’s folder |
| Files | Creating a new snippet with Intype now does not fail to save |
| Critical | Modifying preferences.itConfig now does not cause deadlock |
| Files | Intype initialization now sets defaults from preferences.itConfig properly |
whoo!
Whats the new Plugins folder for?
The plugins folder now contains first plugin — metacrawler that is used for detecting auto-indentation as described in release notes.
WOW looking great! thanks!
Yahoo!
the Crtl+Shift+P is used twice (bundels and select paragraph), is that a bug?
and- the Horizontal Scrollbar is over showing on the doc (or just the line numbers)
yarden: a screenshot?
Ctrl+Shift+P is used for grammars, this will change in 0.2.2
well, i guss i was worng about that…
but, the horizontal scrollbar is not updated if i delete the text that is ‘horizontal bigger’ then the window-
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
yarden: this is not a bug. Horizontal scrollbar would be too expensive feature when it will be reacting on deleting text (all lines has to be scanned to find next longest line). Therefore we decided to implement it the Scintilla-way, where horizontal scrollbar is only increasing. This method is making no extra overhead. However, we are planning to reimplement this in further versions.
jbeduya: For 0.2.2 we are refactoring many UI parts of Intype to be platform-independent so later it will be easier to move to other platforms. We have started with editing component, that will bring many new features. Wine is just a nice side-effect, but we will work on the compatibility as well.
chainy: Yeah, that is what we are working on now.
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..
When you open a file, the detector is being used to detect indentation in the file you are opening. Stored settings are used only if you are creating a new file (Ctrl+N).
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 :)
Hello, thanks for the welcoming ;-)
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. :-)
Haha, well, the HTML and XHTML bundles have been merged. :P So there should only be one HTML.itBundle folder in the Bundles folder and no XHTML.itBundle folder.
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
Ok so :-)
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
I’m not sure that this is really a bug. AFAIK it is this way in alot of editors (notepad++, scite). However it would be nice if it did.
.Dani: one thing I don’t realy understand is that you state that the core of a good editor is multitab, project support, and auto-indentation…
Your are not the only one who complain about intype not have those features,
but for me I found it really more crucial to first have a search and replace (even without regexp) than having multitab and project support.
At least that’s my opinion…
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
The other way around is… “good news is no news”? :P :))
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…
Idyllrain does this mean that you are moving on and to where?
Just have a look at the blog : Hvge is going to work full time on Intype as of june
http://intype.info/blog/success-intype-on-linux/#comment-3054
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. :)
Sure… I get a little busy, set the blog’s feed to alert me to updates, and the only updates are announced in the forum instead. That just figures!
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.
Ok, I’ll try to explain to you all what is going on in Intype project. Currently we have frozen the 0.2.1 branch and started with huge updates in the editor and application to reach our milestones faster. This made Intype unusable for some time until we get it back to work.
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.
Well confirmed
bq. ollu: “No news is good news”...
:D
LOL
martin: Great news. thanks!
Excellent – more communication in future about what’s going on would be very useful.
From the outside, a dead project with nothing going on and you guys working really hard – but not posting or updating the blog – looks exactly the same.
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.
Thanks to Thomas Bell, we will be updating actual development status on the blog each week (I hope). I’ve added one more feature to the editor to make it all done at once: the word wrapping. Currently it supports LTR as well as RTL wrapping and is quite fast. Thank you guys for staying with us. It’s really helpful.
sounds great!
what do you mean “LTR as well as RTL” intype is not rtl-able
Intype is not RTL-able, but is able to work with RTL text. The alignment of lines is always LTR, but this is going to change. There is planned a lot of testing and tuning for making Intype support RTL fully, but the rendering core is working with RTL, as well as word-wrap.
Hey Martin, glad to hear about you again ;)
Can you just give us a clue on the next release date ? I know you’re all working hard on Intype core and that you plan to release the final version during summer but what about the 0.3.0 and unstable releases ?
Can we expect to get them soon ?
Thanks Martin – sounds good. As you’ve planned out a provisional roadmap to one-point-oh, any chance you could copy and paste it into a blog entry? We promise we won’t hold you to it!
Seriously – more communication and inclusiveness is always a good way to foster community.
Thanks!
:)