All new Okteta features for KDE 4.2 in a pic

Time has passed quickly since the first official release of Okteta, the KDE 4 hex editor, and the release of the second version, 0.2, is again just two more month away. The scope of new features has been frozen some time ago. Now the codebase is getting some cleanup, which means removing bugs left and adding more unit tests. Update: Yes, bugs like that previously visible (after one night of sleep) in the picture below, the source code encoder always taking data starting at offset 0, not the selection. Fixed.

Adding unit tests afterward might look strange for people used to test-driven development. But I have found that I often want to simply sketch a possible solution directly in code and see if it works out from a structuring POV. Only then I see the time usefully spent for the hardening of a code module’s interface with unit tests. Is this called use-driven development? So far this hasn’t bitten me too much, at least I cannot remember nightlong searches for little, but complicated bugs. And still reports zero bugs for Okteta (Yes, I have heard people are using it ๐Ÿ™‚ ). Perhaps because I favor light classes with simple functions, separated by concern. But this pays in a large number of classes, just see the endless logs of a complete Okteta compile, which make me always wonder if I overengineer ๐Ÿ˜‰ Makes it easy to loose the overview. Needs to be matched with another technique, as someone teached me, which is reduceable design. I still feel I have the overview. But do others?

Back to Okteta, from a user’s POV. See here for an overview of all features new for Okteta with version 0.2, to be part of KDE 4.2:
All new features of Okteta 0.2 in one picture

The new, additional view modus Rows is of course also supported by the format “View in Plain Text” of the “Export”/”Copy as” commands, in the WYSIWYG-style of Okteta. See yourself and compare with the selection in the screenshot above:

0000:0090 |                           CC D1 13 00  CC D1 13 00
          |                           รŒ  ร‘  .  .   รŒ  ร‘  .  . 
0000:00A0 | CC D1 13 00  B0 27 00 00  84 54 00 00  06 00 00 00
          | รŒ  ร‘  .  .   ยฐ  '  .  .   .  T  .  .   .  .  .  . 
0000:00B0 | 00 10 00 00  02 00 00 00  7C ED 13 00  7C ED 13 00
          | .  .  .  .   .  .  .  .   |  รญ  .  .   |  รญ  .  . 
0000:00C0 | 7C                                                
          | |                                                 

Let’s see if I find the time next year to finally add to 0.3 what I really wanted to do with Okteta ๐Ÿ™‚


10 thoughts on “All new Okteta features for KDE 4.2 in a pic

  1. Nice! I tried it yesterday to debug a document and it worked like a charm, Is it possible to add an intel/x86 assembly view in the future? I can’t beleve that no one ever wrote a dissasembly library. This feature would be very usefull for student, security analyst and to reverse ingeneer propriatary content/file type.

  2. Riese, Mark, thanks for your comments ๐Ÿ™‚

    Emmanuel, of course there are FLOSS disassembly libraries and programs. E.g. have a look at BIEW (! And of course it is possible to add something like that to Okteta, it just needs someone to do it. Okteta is written in a very modular and layered style, so 3-party plugins should be easy and are welcome. Next year I hope to provide some tutorials how to do that best.

    Martin, yes, lazy-testing sounds better. Lazy as in resource-economically ๐Ÿ˜‰

  3. […] KDE utils ื™ืฉ ื™ื™ืฉื•ื ื‘ืฉื octeta, ื•ื”ื•ื ืขื•ืจืš ื”ืงืกืื“ืฆื™ืžืืœื™ ืขื‘ื•ืจ KDE. ืฉื•ื‘, ื›ืœื™ ืžืจืฉื™ื ืžืื•ื“ ืฉื›ื‘ืจ ื–ืžื™ืŸ ื‘ืชื•ืจ ื—ืœืง ืž-KDE […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.