Re: Re: [ jEdit-devel ] I want to write a HEX editor plugin,Could anyonekindly help me to build the hex edit area GUI

[Alan E. <ala...@gm...>]

You can get the existing source for the two plugins and look at them
as an example of a starting point, regardless of whether you can reach
the developers.  I've started hacking on plugins and making changes,
and I then send in my fixes to the developers when I'm done (or if I'm
stuck).

You want some help getting started? join #jedit on irc.freenode.net
and you can also ask questions there. Perhaps other people can give
you some good starting points.

What specifically is it about the Hex Editor that you do not like?
What would you change about it? Try to describe each thing as a
specific feature, perhaps you can open bug reports for them on
jedit-plugin-bugs tracker. Then start working on them. When you need
help, you can say "I'm working on bug# 1617421151" on HexEdit plugin.
Can someone help me? And when you get more information about them,
post comments to the tracker item that you opened.

Start out by checking out the plugin anonymously via CVS and working
in a CVS working directory. That will make it easier to submit patches
later.

On 12/31/05, ??? <la...@21...> wrote:
> Hi Vampire,
>
> Yes, I agree with "make a _third_ similar plugin which has more
> functionality is the wrong way".
>
> But How to and who should to "contact the current maintainers of the two =
plugins"?
> The two HEX plugin have not update for years.
>
> In my opinion, we can mark plugin that have not update for years as "obso=
lete" like "Deprecated" in Java API. So that user&developer can understand.