[Fwd: Re: [Fwd: Re: JEDIT PLUGINS]]

[Thomas.Schneider.Wien]

David requested I should bring this discussion to the list....
What herewith (when my english is correct :-( ?? :-) ) I'm doing...
Thomas......

-------------- next part --------------
An embedded message was scrubbed...
From: David Requena <[hidden email]>
Subject: Re: [Fwd: Re: JEDIT PLUGINS]
Date: Mon, 8 Feb 2010 22:43:14 +0100
Size: 28130
Url: http://ns.hursley.ibm.com/pipermail/ibm-netrexx/attachments/20100208/9c1439e8/JEDITPLUGINS-0001.eml

[David Requena]

ahemm.. obviously I meant "should try not to step on RexxLA's toe tips" :-)

2010/2/8 Thomas Schneider <[hidden email]>

> David requested I should bring this discussion to the list....
> What herewith (when my english is correct :-( ?? :-) ) I'm doing...
> Thomas......
>
>
> Thomas,
>
> I'm allready losing track of what mail goes were. And forgeting to click
> 'Reply to all' half of the time too...
> Could we bring these discussions to the list please?
>
> Anyway I think we should try to setp on RexxLA's toe tips. They -you- are
> doing their job right now and we should be doing ours.
> I doubt very much if MS was going to release an Office coded in NetRexx,
> they would post it to www.netrexx.org.
>
> That is no to say that a central point for all open source projects related
> to NetRexx isn't a great idea. It *is* indeed.
> That would help to raise general awareness of the language as well as
> in projects willing to join. It would certainly help growing
> a community of NetRexx developers.
>
> As stated before such a site could well be www.netrexxdev.org. Latter,
> when oss NetRexx and associated www.netrexx.org go live
> some kin of affiliation, or even integration, would be worked up between
> domains, should the RexxLA be interested.
>
> Open sourcing NetRexx is not our project, is RexxLA's. They will be
> deciding about de whys, hows and whens.
> 2010/2/8 Thomas Schneider <[hidden email]>
>
>> Hello there,
>>  from MY POINT of view, we will (*very quickly*) have to decide where
>> all those tools available *should reside*
>>
>>  *Otherwise we will get a total garbage of home-pages*
>>
>> Tom.
>>
>> PS: I am *asking you all*, to do NOT valid any new home-pages.
>> PPS: Rene, Master of the Open source release of NetRexx, how should we
>> proceed to *CONSOLIDATE* the efforts of Kermit and David underway.
>>
>> Any finally, Mike Cowlishaw.
>>
>> 1.) How did you handle this with 'classic Rexx' Development ??
>> 2.) What would you suggest (as a CONSULTANT) ??
>>
>> Yeah, well, even tv stand for some iso country code..
>> Original idea was to use NetRexxIDE but I seemed to me it was a bit of a
>> mouthfull given the product's current simplicity.
>>
>> I *really* do like your suggestion for a www.netrexxdev.org under which
>> would host any oss NetRexx projects.
>>
>> 2010/2/8 Thomas Schneider <[hidden email]>
>>
>>> Hi David,
>>>  the *suffix* 'DE' stands, at lest here in Austria, for *German* ...
>>>
>>> Hence, may I again propose you name the successor of NetRexxJe simply
>>> NetRexxDev (has nothing to
>>> do with dear Devil, but with (compiler Oriented) Development...
>>>
>>> Thomas.
>>> ==========================================================
>>> David Requena schrieb:
>>>
>>>> Thomas,
>>>>  Kermit went recently through the process with his NetRexxScript plugin.
>>>> He sent to the list some advice to me recently too.
>>>>  I'm planning submitting my own NetRexxDE as soon as I complete a couple
>>>> features I'm implementing right now.
>>>>  As for the sources, when you download
>>>> http://kenai.com/projects/netrexx-misc/downloads/download/NetRexxDE%252FNetRexxDE-1.0.2c.zipyou'll find them inside the zip archive.
>>>>
>>>> Cheers.
>>>>  2010/2/6 Thomas Schneider <[hidden email] <mailto:[hidden email]>>
>>>>
>>>>
>>>>    I need to know where I can find on the WEB:
>>>>
>>>>    1.) How can I become a member (PLUGIN Author) to Jedit ?
>>>>    2.) Where do I have to look what has do be done to get a PLUGIN
>>>>    validated by Slava Pestov & Crew.
>>>>    3.) Which FORUMS (or whatever) DO I have to subscribe to become a
>>>>    JEDIT PLUGIN
>>>>    Author.
>>>>
>>>>    Tom.
>>>>
>>>>    PS: When you could forward the souces of your current State of
>>>>    your PLUGINS (namely
>>>>    NetRexxScript and NetRexxDev) this would be of REAL HELP!
>>>>
>>>>    I could, looking at your code, probably very quickly adopt my
>>>>    PARSER Routines.
>>>>
>>>>    For your info, I am attaching the white-paper of PP (The Program
>>>>    Porting Machine).
>>>>
>>>>    Tom.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>    PP - the Program Porting Machine               Vienna, 22.08.2008
>>>>    ================================
>>>>
>>>>                                     Copyright Th. Schneider, 2002 - 2008
>>>>
>>>>    PP is a machine porting a Program from the source-language (e.g.
>>>>    PL/I, COBOL, Rexx,
>>>>    NetRexx, Java, C, C++, C#, ooRexx) to a target-language.
>>>>
>>>>    The source language is determined by the File-Type of the source
>>>>    program.
>>>>
>>>>    The target-language is usually defined in the respective
>>>>    Global-File (see below)
>>>>    It might be overwritten by the TARGET=language option in the
>>>>    invoking sequence.
>>>>
>>>>    PP, when not otherwise defined, performs the following STEPS on
>>>>    each source-program
>>>>
>>>>    PP SCAN source-file(s)      -- this step SCANS the files only, and
>>>>    produces the program METRICS
>>>>    PP DECL source-file(s)      -- this step parses all declarations only
>>>>    PP CODE source-file(s)      -- this step USES the declarations and
>>>>    parses the Code.
>>>>    PP ANALYSE source_file(s)   -- this step ANALYSES (semantically)
>>>>    the source code
>>>>    PP TRANSFORM source-file(s) -- this step finally TRANSFORMS the
>>>>    given source-file
>>>>                                  to the desired target-language
>>>>    PP DOCUMENT source-files(s) -- this step DOCUMENTS the source code
>>>>    (in HTML)
>>>>
>>>>    Invocation of the Program Porting Machine (PP)
>>>>    ==============================================
>>>>
>>>>    PP is invoked by
>>>>
>>>>    PP <action> <source-files> [TO <target-language>] <options>
>>>>
>>>>    The source files may be either a blank delimited list of Full
>>>>    file-names (including type)
>>>>    or a pattern selecting the file-names, e.g.
>>>>
>>>>    PP SCAN *.CBL
>>>>    PP DECL *.PLI
>>>>    PP ANALYSE *.COBOL
>>>>    PP TRANSFORM *.Rexx TO NetRexx
>>>>    PP TRANSFORM *.PLI to Java
>>>>    PP TRANSFORM *.COBOL to PLI
>>>>    PP SCAN *.PLI
>>>>    PP PARSE *.CBL
>>>>
>>>>    The valid options (and there are a lot of them) may be either:
>>>>
>>>>    a) prefixed by a hyphen (as usual in the Java and C world)
>>>>    b) enclosed in parenthesis (as usual on IBM CMS, etc)
>>>>
>>>>    When you are invoking PP without any parameter, a list of the
>>>>    valid actions, with a short
>>>>    description, is given. You then are asked interactively to enter
>>>>    the action(s),
>>>>    source-file name(s), and option(s).
>>>>
>>>>    Multiple actions have to be separated by a '+'-sign. But usually,
>>>>    PP checks, if the
>>>>    needed preceeding actions have been already performed for each
>>>>    source-file, and when not,
>>>>    performs those actions implicitely.
>>>>
>>>>    Please note, that PP has a BOTTOM UP Parsing algorithm, thus
>>>>    enabling you to
>>>>    translate program-pieces (like COBOL COPY books or PLI
>>>>    %INCLUDE-files) BOTTOM UP.
>>>>
>>>>    This also implies, that you can, for instance, TRANSFORM an IBM
>>>>    PL/I %INCLUDE-File,
>>>>    containing declarations only, to an equivalent Java ArtiFact, for
>>>>    instance. Detto
>>>>    for COBOL COPY-books, containing declarations only.
>>>>
>>>>    More-over, PIECES of CODE can be transformed without the necessary
>>>>    declarations to
>>>>    the INTERNAL CODE.
>>>>
>>>>    Hence, essentially, the PP Parsers are BOTTOM UP-Parsers,
>>>>    accepting nearly any
>>>>    type of CODE or CODE-fragment, in a couple of supported
>>>>    SOURCE-languages..
>>>>
>>>>    In fact, for each module, an internal Decl File (named *.__decl)
>>>>    and an internal
>>>>    Code file (named *.__code) are produced. Those files are loaded on
>>>>    demand by the
>>>>    different steps of PP into core.
>>>>
>>>>    A Documentation of those file-formats are contained in PP.doc (for
>>>>    the internal PP-Code),
>>>>    and PP_Decl.doc (for the internal Declaration attributes/Properties).
>>>>
>>>>
>>>>    The following PP actions are available:
>>>>    =======================================
>>>>
>>>>    PP SCAN *.PLI (for instance)
>>>>    ----------------------------
>>>>
>>>>    Scan scans the file (with the given source-language). Scan in this
>>>>    context means also,
>>>>    that the source-file is TOKENIZED. The used Tokenizer, however, is
>>>>    parametrized
>>>>    by the source-file-type in question.
>>>>
>>>>    PP DECL *.COBOL  or PP DECL *.PLI (for instance)
>>>>    ------------------------------------------------
>>>>
>>>>    The DECL step performs the SCAN, when not yet done, and parses all
>>>>    PreProcessor
>>>>    statements (for PL/I, for instance) and declarations. It also
>>>>    determines the
>>>>    SCOPE of each variable, function, or property, and determines all
>>>>    LABELS used
>>>>    in the program.
>>>>
>>>>    As a SIDE-effect, it captures the needed information to produce a
>>>>    GLOBAL Cross-Referece.
>>>>
>>>>    PP CODE *.Rexx (for instance)
>>>>    -----------------------------
>>>>
>>>>    The CODE step uses the already known Declarations, and transforms
>>>>    the actual code to
>>>>    the Internal PP Code format, which - by design - is essentially
>>>>    *Language Independent*.
>>>>
>>>>    Thus, the various DIALECTS of an IF-statement, for instance, are
>>>>    all translated to
>>>>    the same internal common format.
>>>>
>>>>    PP ANALYSE *.PLI (for instance)
>>>>    -------------------------------
>>>>
>>>>    The ANALYSER step performs a SEMANTIC analysis of the program(s)
>>>>    in question.
>>>>    Try the Rexx2Nrx converter (see www.Rexx2Nrx.com<http://www.rexx2nrx.com/>
>>>>    <http://www.rexx2nrx.com/>) to fully exploit the power of
>>>>
>>>>    the semantic analysis.
>>>>
>>>>    PP TRANSFORM *.PLI TO NetRexx (for instance)
>>>>    --------------------------------------------
>>>>
>>>>    Finally, the TRANSFORMER step of the Program Porting machine
>>>>    translates
>>>>    the given program modules TO the so-called TARGET-Language.
>>>>
>>>>    Currently, NetRexx is the major TARGET-Language supported. NetRexx
>>>>    has been
>>>>    designed and developed by M.F. Cowlishaw, IBM fellow, who has been
>>>>    also the
>>>>    original author of the REXX language.
>>>>
>>>>    GOOGLE NetRexx to get at the IBM home-pages describing the
>>>>    features of NetRexx.
>>>>
>>>>    You might also GOOGLE Rexx2Nrx for my 'classic Rexx to NetRexx
>>>>    converter', or look at
>>>>    www.Rexx2Nrx.com <http://www.rexx2nrx.com/> <
>>>> http://www.rexx2nrx.com/> for the current - more
>>>>
>>>>    formal- documentation available.
>>>>
>>>>    The principles developed for Rexx2Nrx are now expanded for other
>>>>    languages as well.
>>>>
>>>>    You can reach me via SKYPE at Thomas.Schneider.Wien or via e-mail
>>>>    at [hidden email] <mailto:[hidden email]>
>>>>
>>>>
>>>>
>>>>
>>>>    Document history:
>>>>    =================
>>>>
>>>>    .. spelling errors corrected, Th.S., 9.09.2008
>>>>    .. Documentation still to be completed. Th.S., 9.09.2008
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Saludos / Regards,
>>>> David Requena
>>>>
>>>>
>>>
>>
>>
>> --
>> Saludos / Regards,
>> David Requena
>>
>>
>>
>
>
> --
> Saludos / Regards,
> David Requena
>
>
> _______________________________________________
> Ibm-netrexx mailing list
> [hidden email]
>
>
>

--
Saludos / Regards,
David Requena
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns.hursley.ibm.com/pipermail/ibm-netrexx/attachments/20100208/137dfc12/attachment.html