editors - open source - written in ADA?

editors - open source - written in ADA?

[tony]

I'm wondering if anyone cn help me,
I'm looking for an open source editor written in Ada 
which I can attach in my code with out changing the license 
of the overall code
any ideas
 

-- 
************************************************************
Everybody is given the same amount of hormones, at birth, and
if you want to use yours for growing hair, that's fine with me.

Re: editors - open source - written in ADA?

[Robert Dewar]

tony <tonygair@btinternet.com> wrote in message news:<20011115154401.6637e73f.tonygair@btinternet.com>...
> I'm wondering if anyone cn help me,
> I'm looking for an open source editor written in Ada 
> which I can attach in my code with out changing the license 
> of the overall code
> any ideas


Well to start with, you need to say what the licensing
and copyright status is for "my code". For example, if
that code prohibits making derived works, then you can't
add anything. Presumably the status is less restrictive ..

Re: editors - open source - written in ADA?

[David Botton]

I think that you will find that most (I only know of one or two exceptions)
open source developers for Ada are quick (Ok, there have been some bumps
along the way, but they are now smooth) to make Ada libraries available
under the very unrestrictive lic. of the GMGPL (ie. GPL, but if you include
the code it doesn't cause your code to become GPL'd) in order that their
code should help to be advocates of Ada use even in non-GPL settings (such
as in proprietary products ;-)

In principle most of those developers, self included, wished Ada was already
firm in the heart of the worlds programmers and would rather release under
the true GPL, but see that being Ada advocates is more important in the
current climate and that we would contribute just about zippo to the FSF and
other like minded movements with our code (for now .....)

Typically an editor and other tool would be released under the GPL since
these are end products. Take a look at the FSF site for the "why"s on the
GPL.

Most people like to get paid for their work. There are of course many ways
to pay some one (money isn't everything). Putting new code under the GPL by
leveraging other's GPL code is very gratifying and rewarding to the GPL
author and part of why many release their code under the GPL.

If you can not pay the developers in GPL code, perhaps consider cash :-)

David Botton




"tony" <tonygair@btinternet.com> wrote in message
news:20011115154401.6637e73f.tonygair@btinternet.com...
>
> I'm wondering if anyone cn help me,
> I'm looking for an open source editor written in Ada
> which I can attach in my code with out changing the license
> of the overall code
> any ideas

Re: editors - open source - written in ADA?

[Larry Kilgallen]

In article <tve5qcrhhqd78c@corp.supernews.com>, "David Botton" <David@Botton.com> writes:

> Typically an editor and other tool would be released under the GPL since
> these are end products. Take a look at the FSF site for the "why"s on the
> GPL.

On VMS the standard for editors is to make them "callable", so they
can be activated in a uniform fashion by either the (minimal) EDIT
program or any other application that needs an editor.  So the user
gets their choice of editor with their choice of program.

From what I have read here, neither GPL nor other "open source"
licenses place any restrictions on interactions between components
in this sort of situation, since they are in separate images.

Re: editors - open source - written in ADA?

[Marin David Condic]

What about making a subprogram that takes an Unbounded_String as a parameter
and allows the user to edit the content of that string? A system dependent
or user selectable editor could underly it - or perhaps some
semi-standardized editor could be built under it and made in flavors that
would work on popular platforms? Would this be a useful thing to have as a
standard component?

I could imagine two useful versions: One that just dealt with standard
character data and one that dealt with XML. THere might need to be some
other options as well with respect to how the editor is displayed &
interacted with, but it seems like as nice utility to have around in some
standard context.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message
news:1fLkmUwU74fK@eisner.encompasserve.org...
>
> On VMS the standard for editors is to make them "callable", so they
> can be activated in a uniform fashion by either the (minimal) EDIT
> program or any other application that needs an editor.  So the user
> gets their choice of editor with their choice of program.
>

Re: editors - open source - written in ADA?

[Nick Roberts]

"Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> wrote in
message news:9tbdvi$4cv$1@nh.pace.co.uk...
> What about making a subprogram that takes an Unbounded_String as a
parameter
> and allows the user to edit the content of that string? A system dependent
> or user selectable editor could underly it - or perhaps some
> semi-standardized editor could be built under it and made in flavors that
> would work on popular platforms? Would this be a useful thing to have as a
> standard component?
>
> I could imagine two useful versions: One that just dealt with standard
> character data and one that dealt with XML. THere might need to be some
> other options as well with respect to how the editor is displayed &
> interacted with, but it seems like as nice utility to have around in some
> standard context.

In a GUI environment, this would be a widget?

What might be pretty handy would be for Ada implementations to add something
like:

   procedure Text_IO.Edit_Line (
      File : in     File_Type;
      Item : in out String;
      Last : in out Natural);

If File is an interactive terminal (or equivalent), this procedure would
initialise the line to Item(first..Last) and then allow the user a
reasonable set of editing facilities (e.g. cursor left/right, insert,
delete), before returning the result in Last and Item(first..Last). If File
is not interactive, the procedure would simply behave as
Get_Line(File,Item,Last). I don't suppose this is a new idea.

Are there any open-source 'screen' packages (which allow at least clear
screen, cursor addressing, and restricted-field data entry), written in Ada?

--
Best wishes,
Nick Roberts