SourceNav release ...

Khamis Abuelkomboz
Mon Jan 7 12:04:00 GMT 2002

Hi Ralf,

I find your input great. we need an "open" way to add work into SN, I 
had the idea
about taking the current redhat SN and provide my own SN release, basicly
to rework the GUI and extend the existing parsers.
As example I would like
- to integrate the symbol browser into the main window,
- add more functionality to the browser, like add/remove files, history, 
- making it possible to open more than one editor pane in a window.
- list the symbols of current edited file on the right (OLD SN 
functionality reenabled)
- etc.

Actually I already started to do this work, see
and welcome your input.

But the problem is, where to keep the whole SN? My own web space is too 

However I find puting SN into an open CVS is a first step to achieve 
this gool.


Ralf Corsepius wrote:

>Am Son, 2002-01-06 um 04.54 schrieb Mo DeJong:
>>On Sun, 6 Jan 2002 02:25:59 -0600 
>>"Simonovsky, Pavel" <> wrote:
>>>		So - you mean , that in fact SN is dead , and there is no
>>>any development team behind it? It is very important info - I suggested this
>>>tool to 2-3 teems in our company ... I have to warn them - that it dose no
>>>worth a waste of time...
>>Well, that might be a bit too strong. I don't speak for Red Hat, but as a former member of the development team I feel safe in stating that they are no longer allocating resources to SN. Basically, it comes down to $$. If you have paying customers then you can pay the engineers and managers. This might just be my impression, but it seemed that being able to download the code for free gave people the impression that they should not have to chip in for any new development. Also, the dot crunch did not help.
>>I know for a fact that Ian has been doing some great work on his own
>time to get the development version that uses Tcl/Tk 8.3 available via
>CVS. It is quite an improvement over the 5.0 release. That said, what is
>lacking is time and resources to put out a 5.1 release. What is the
>solution? I am not sure. I would like to hear ideas from people on this
>OK, here is mine:
>IMHO, the basic problem is to render SN into an active project.
>As RH apparently is not developing actively anymore, one solution would
>be to convert SN into a real OpenSource community project.
>AFAIS, there would be 2 approaches to such an attempt:
>1.) Apply the existing RH-infrastructure and run it
>This would require RH to provide minimal assistance and support (ML,
>CVS, ftp etc) + generally OK-ing into such undertaking.
>Given the existing SN-related infrastructure at RH, I fail to see why
>this should not work. At that lacks are active maintainers (RH or Non-RH
>person) willing to accept and apply patches + to guide people though
>>From my POV, it's only the lack of active maintainers which currently
>lets appear SN as "dumped dead code junk".
>2.) To lunch a GPL'ed non-RH related project somewhere else, using RH's
>SN-code as basis. IMHO, nobody actually would be interested in doing so
>and I also doubt it would actually work out.
>>I would think the right solution would provide a stable 5.1 release,
>>but also provide a plan for 5.2 and future releases.
>I fully agree.
>But the only way to achieve something of this kind IMHO would be
>somebody (the maintainer - who is it? Ian, you?) to show some visible
>initiative - Currently, SN appears not only to be dead, but to

More information about the Sourcenav mailing list