Implement hex editor into QSciTE

[GoogleCodeExporter]

We already have a HexView widget that works nicely, but we need to extend
it to also edit files.  I'd really like this to be a major new feature for
the 0.5 release.

Original issue reported on code.google.com by jpsut...@gmail.com on 22 Mar 2008 at 9:28

[GoogleCodeExporter]

Having some second thoughts about what we gain by having the hex editor and the 
text
editor in one application.
I would personally prefer that the hex editor be a separate application (with a
straightforward, customizable menu in QSciTE for launching external tools) 
unless we
can come up with a compelling use case for integration.
Advantages of separating are:
 * cleaner code
 * launching external tools is a feature I want to do by 0.6 anyway
 * people who already have a favorite hex editor don't end up second class citizens.
Disadvantages?

Original comment by bfrobin...@gmail.com on 30 Dec 2008 at 5:57

[GoogleCodeExporter]

The biggest advantage to me would be the ability to tweak files that may have
non-printable characters in them.  I've run into a file every now and then that 
has a
strange character that's causing problems (especially bash scripts...they don't 
like
strange characters at all).

Other than that, I suppose it could be a separate component application.  If 
this is
the only milestone issue holding 0.5 back, I say we release and discuss it 
further
with Dave (who is developing the hex component).

Original comment by jpsut...@gmail.com on 1 Jan 2009 at 3:50

[GoogleCodeExporter]

The only issues marked 0.5 are this and #18 (application icon). I'm removing the
milestone tag until we know what we want and when.

Original comment by bfrobin...@gmail.com on 6 Jan 2009 at 8:24

• Removed labels: Milestone-Release0.5

[GoogleCodeExporter]

I don't have any plans to implement this soon, so closing this.

Original comment by jpsut...@gmail.com on 6 Nov 2010 at 1:29

• Changed state: WontFix