[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Hex editor widget
From:       "Friedrich W. H.  Kossebau" <Friedrich.W.H () Kossebau ! de>
Date:       2003-06-21 10:52:19
[Download RAW message or body]

Am Samstag, 21. Juni 2003 00:45 schrieb Russell Miller:
> I would also be interested in such a widget - one of the apps that I have
> written, kbview, would benefit greatly from such a widget.  

Hehe, that is funny: At the very same time this year I started such a program 
like kbview myself, partly out of the same reason you mention on your page 
:))  (Perhaps we can cooperate in the future, though by now I will 
concentrate on the hex widget). Any actual code (since march 30th) or 
screenshot? 

And there arose my need for this hex edit widget, too. Well, I will deliver 
this part :)

> What I would like to see (not a list of demands, but a list of wishes):
>
> 1.  ability to work on an arbitrary pointer.
As much as I understand: Prepared.
(what is the meaning of arbitrary in this context? My dictionary didn't help 
me to get a feeling for it.)

> 2.  ability to set read-only or read-write
Prepared.

> 3.  ability to edit by changing the values directly in the view widget,
> OR by changing the characters in the ".... ...." to the right
Editing in the ASCII view as well as digit by digit in the hex view? Prepared.

> 4.  ability to delay committing changes without confirmation (ie, working
> in a separate variable)
Prepared: This should be left to each app IMHO. I made an abstraction layer to 
the data so you can implement this logic yourself. The widget does not buffer 
any data but operates directly on the data supplied by the data layer. So the 
buffering is to be done in your subclass of the layer.

> 5.  a kpart is nice, but I'd also like to use it as a compile-time widget.
Both prepared. Not sure about the API of the KPart (and what the KPart should 
do, help please ;)

> 6.  variable monitoring - ie, if the variable is modified externally, to
> update the widget in real-time (well as close as practicable, there are of
> course limits)
Has to be handled by the app (or do you expect the widget to scan the data 
over and over?;).  A slot "void updateRange( int index1, int index2);" should 
serve on the widget's side. 

Oh wait: Are you thinking not of a data range viewer but a simple one-byte 
edit widget? Hm. Might be usefull, to. Will put this on my TODO list. Should 
be doable. The basics are the same as for the range hex edit. Might be 
already implemented in today's KHexEdit.

> That's just my two cents.

Thanks :)

Friedrich
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]