Re: [JIRA] Resolved: (NETREXX-35) NetRexx Should contain SIMPLE statements (NEW instructions) to produce a PRINTED Report

[ThSITC]

Hello You all there,

    1.) When the current behaviour of the NetRexx *group* is to change
*nothing* for NetRexx versions 4.00 : I'll be off at any and all NetRexx
Lists.

Sorry for me, but a great advantage for you:

  *Nothing has to be changed*,  *or* advanced, (bit fo rbit) ..

    2:) I'm totallly (personally) DIS-AGGREING that *when* I'm,
enterering *issues* there at www.kenai.com, project NetRexx, at my spare
time:

*and suddenly*

Those issues do DIS-Appear, because someone else did decide to do so.

When we do have an issue tracking at KENAI, please do NOT
DISTORT my suggestions ...

Otherwise my membership there will be USELESS at all :-)

...  as I am an unwanted member in many communities, any way :-)

I'm not sitting here to enter issues, when other people do decide:
NO Issue.

I DO have too much work to do to have too much spare time to take
my time to enter CLOSED issues (when they are NOT closed)...

Sorry to say ..

Massa Thomas.

Thomas Schneider
CEO
ThSITC IT Consulting KG
===============================================================
Am 26.09.2011 1:12, schrieb Kermit Kiser (JIRA):

>       [ http://kenai.com/jira/browse/NETREXX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Kermit Kiser resolved NETREXX-35.
> ---------------------------------
>
>      Resolution: Won't Fix
>
> This can be handled by library functions. No language change is needed.
>
>> NetRexx Should contain SIMPLE statements (NEW instructions) to produce  a PRINTED Report
>> ----------------------------------------------------------------------------------------
>>
>>                  Key: NETREXX-35
>>                  URL: http://kenai.com/jira/browse/NETREXX-35
>>              Project: netrexx
>>           Issue Type: Improvement
>>           Components: Translator
>>             Reporter: Thomas.Schneider.Wien
>>
>> NetRexx should add NEW instructions (Verbs) to be able to produce a simple, formatted, REPORT.
>> I'm proposing to add the NEW Verb:
>> PRINT a,b,c
>> for this purpose.
>> PRINT shall take the defined HEADER (the default should be the 'variables' and/or properies name,
>> and should PRODUCE a columnated output, well designed, as giben by the actual values, of the appropite COMLUMNS of the Printout.
>> To obtain a properly FORMATTED PRINTOUT, the follwong must be known:
>> a) Are all Values of the COLUMN in question NUMRIRIC? If yes: COLUMNS must be RIGHT aligned !
>> b) What is the maximum WIDTH of the column in question?
>> c) MAY the width, when the total PRINT LINE Length is TOO LONG, may the item BE WRAPPED ?
>> A Reference Implementationof this (still untested) new feature is in:
>> org.netrexx.thsitc.runtime.compatibilty  (class Reports)
>> My personal PP does and will produce whe approriate methoid invocations, BUT:
>> I'm suggesting to ADD this feature to the NetRexx Languqage.
>> Reletaed TOPICS: TITLE, FOOTING, HEADING, etc...

--
Thomas Schneider (Founder of www.thsitc.com) Member of the Rexx Languge
Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team
(www.netrexx.org)

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

[Kermit Kiser]

Thomas -

Please reconsider this. You have submitted issues that will improve
NetRexx when they are implemented. Your input is valuable and is always
carefully considered.

But you also need to be realistic. There are four developers for NetRexx
right now and I am pretty sure that Patric, David and René are quite
busy with commercial work just as you are and administrative matters or
project infrastructure items currently take most of their NetRexx time.
That leaves me as the primary person with time to handle NetRexx
language issues and I am splitting time with commercial projects also.
(I try to prioritize NetRexx because we are about 10 years behind on
maintenance!) Development resources are quite limited at the moment.

You have entered 17 issues at Kenai, 9 of which are still open, and
every single one of them is marked "major" priority even if it can
already be handled easily by other means. That makes the priority system
useless and forces me to decide what is important and what should be
closed. I have already told you the criteria for those decisions:

1) Don't break existing programs.
2) Don't change the language if there is an easier or better way to do
things already.
3) Don't destroy the simplicity and power of NetRexx.

Although you can always create your own version of NetRexx now that it
is open source, I suggest that you stick with us for a year or two and
see if there is any progress. Just don't expect to get everything you
ask for - I didn't get what I wanted for the LOOP OVER change (fast
no-snapshot loops) and I was the one who wrote the code!

-- Kermit


On 9/26/2011 12:02 PM, Thomas Schneider wrote:

> Hello You all there,
>
>    1.) When the current behaviour of the NetRexx *group* is to change
> *nothing* for NetRexx versions 4.00 : I'll be off at any and all
> NetRexx Lists.
>
> Sorry for me, but a great advantage for you:
>
>  *Nothing has to be changed*,  *or* advanced, (bit fo rbit) ..
>
>    2:) I'm totallly (personally) DIS-AGGREING that *when* I'm,
> enterering *issues* there at www.kenai.com, project NetRexx, at my
> spare time:
>
> *and suddenly*
>
> Those issues do DIS-Appear, because someone else did decide to do so.
>
> When we do have an issue tracking at KENAI, please do NOT
> DISTORT my suggestions ...
>
> Otherwise my membership there will be USELESS at all :-)
>
> ...  as I am an unwanted member in many communities, any way :-)
>
> I'm not sitting here to enter issues, when other people do decide:
> NO Issue.
>
> I DO have too much work to do to have too much spare time to take
> my time to enter CLOSED issues (when they are NOT closed)...
>
> Sorry to say ..
>
> Massa Thomas.
>
> Thomas Schneider
> CEO
> ThSITC IT Consulting KG
> ===============================================================
> Am 26.09.2011 1:12, schrieb Kermit Kiser (JIRA):
>>       [
>> http://kenai.com/jira/browse/NETREXX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>> ]
>>
>> Kermit Kiser resolved NETREXX-35.
>> ---------------------------------
>>
>>      Resolution: Won't Fix
>>
>> This can be handled by library functions. No language change is needed.
>>
>>> NetRexx Should contain SIMPLE statements (NEW instructions) to
>>> produce  a PRINTED Report
>>> ----------------------------------------------------------------------------------------
>>>
>>>
>>>                  Key: NETREXX-35
>>>                  URL: http://kenai.com/jira/browse/NETREXX-35
>>>              Project: netrexx
>>>           Issue Type: Improvement
>>>           Components: Translator
>>>             Reporter: Thomas.Schneider.Wien
>>>
>>> NetRexx should add NEW instructions (Verbs) to be able to produce a
>>> simple, formatted, REPORT.
>>> I'm proposing to add the NEW Verb:
>>> PRINT a,b,c
>>> for this purpose.
>>> PRINT shall take the defined HEADER (the default should be the
>>> 'variables' and/or properies name,
>>> and should PRODUCE a columnated output, well designed, as giben by
>>> the actual values, of the appropite COMLUMNS of the Printout.
>>> To obtain a properly FORMATTED PRINTOUT, the follwong must be known:
>>> a) Are all Values of the COLUMN in question NUMRIRIC? If yes:
>>> COLUMNS must be RIGHT aligned !
>>> b) What is the maximum WIDTH of the column in question?
>>> c) MAY the width, when the total PRINT LINE Length is TOO LONG, may
>>> the item BE WRAPPED ?
>>> A Reference Implementationof this (still untested) new feature is in:
>>> org.netrexx.thsitc.runtime.compatibilty  (class Reports)
>>> My personal PP does and will produce whe approriate methoid
>>> invocations, BUT:
>>> I'm suggesting to ADD this feature to the NetRexx Languqage.
>>> Reletaed TOPICS: TITLE, FOOTING, HEADING, etc...
>
>

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

[ThSITC]

Hello Kermit, *and all*,

I'm now nearly *though* with my own, never ending, story, of my my own
scanner, parser, transformer, and what so ever.

I did, by intent, and lack of time, actually never look at MFC's code up
to now.

*You*, and *others*, did sa, that I should enter my *proposals*,
*ideas*, *etc*

--- as ISSUES ---

there at KENAI, Poject NetRexx ..

Which I did ! (by he4 way)

When now, as currently happened, the approach is:

CLOSE The issue ....' when currently neither implemented NOR wanted

... then:

All of my efforts to enter those issues (according to you advise) have been:

*** LOST TIME ***

(for me, you and anybody else watching this dialog)

THEN, I will spend my time with other things ....

... needless to enter *ideas for improvements* when the language
does *not need any* !!!!   ::::: ((((

Massa Thomas.
==================================================:
Am 26.09.2011 22:56, schrieb Kermit Kiser:

> Thomas -
>
> Please reconsider this. You have submitted issues that will improve
> NetRexx when they are implemented. Your input is valuable and is
> always carefully considered.
>
> But you also need to be realistic. There are four developers for
> NetRexx right now and I am pretty sure that Patric, David and René are
> quite busy with commercial work just as you are and administrative
> matters or project infrastructure items currently take most of their
> NetRexx time. That leaves me as the primary person with time to handle
> NetRexx language issues and I am splitting time with commercial
> projects also. (I try to prioritize NetRexx because we are about 10
> years behind on maintenance!) Development resources are quite limited
> at the moment.
>
> You have entered 17 issues at Kenai, 9 of which are still open, and
> every single one of them is marked "major" priority even if it can
> already be handled easily by other means. That makes the priority
> system useless and forces me to decide what is important and what
> should be closed. I have already told you the criteria for those
> decisions:
>
> 1) Don't break existing programs.
> 2) Don't change the language if there is an easier or better way to do
> things already.
> 3) Don't destroy the simplicity and power of NetRexx.
>
> Although you can always create your own version of NetRexx now that it
> is open source, I suggest that you stick with us for a year or two and
> see if there is any progress. Just don't expect to get everything you
> ask for - I didn't get what I wanted for the LOOP OVER change (fast
> no-snapshot loops) and I was the one who wrote the code!
>
> -- Kermit
>
>
> On 9/26/2011 12:02 PM, Thomas Schneider wrote:
>> Hello You all there,
>>
>>    1.) When the current behaviour of the NetRexx *group* is to change
>> *nothing* for NetRexx versions 4.00 : I'll be off at any and all
>> NetRexx Lists.
>>
>> Sorry for me, but a great advantage for you:
>>
>>  *Nothing has to be changed*,  *or* advanced, (bit fo rbit) ..
>>
>>    2:) I'm totallly (personally) DIS-AGGREING that *when* I'm,
>> enterering *issues* there at www.kenai.com, project NetRexx, at my
>> spare time:
>>
>> *and suddenly*
>>
>> Those issues do DIS-Appear, because someone else did decide to do so.
>>
>> When we do have an issue tracking at KENAI, please do NOT
>> DISTORT my suggestions ...
>>
>> Otherwise my membership there will be USELESS at all :-)
>>
>> ...  as I am an unwanted member in many communities, any way :-)
>>
>> I'm not sitting here to enter issues, when other people do decide:
>> NO Issue.
>>
>> I DO have too much work to do to have too much spare time to take
>> my time to enter CLOSED issues (when they are NOT closed)...
>>
>> Sorry to say ..
>>
>> Massa Thomas.
>>
>> Thomas Schneider
>> CEO
>> ThSITC IT Consulting KG
>> ===============================================================
>> Am 26.09.2011 1:12, schrieb Kermit Kiser (JIRA):
>>>       [
>>> http://kenai.com/jira/browse/NETREXX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>>> ]
>>>
>>> Kermit Kiser resolved NETREXX-35.
>>> ---------------------------------
>>>
>>>      Resolution: Won't Fix
>>>
>>> This can be handled by library functions. No language change is needed.
>>>
>>>> NetRexx Should contain SIMPLE statements (NEW instructions) to
>>>> produce  a PRINTED Report
>>>> ----------------------------------------------------------------------------------------
>>>>
>>>>
>>>>                  Key: NETREXX-35
>>>>                  URL: http://kenai.com/jira/browse/NETREXX-35
>>>>              Project: netrexx
>>>>           Issue Type: Improvement
>>>>           Components: Translator
>>>>             Reporter: Thomas.Schneider.Wien
>>>>
>>>> NetRexx should add NEW instructions (Verbs) to be able to produce a
>>>> simple, formatted, REPORT.
>>>> I'm proposing to add the NEW Verb:
>>>> PRINT a,b,c
>>>> for this purpose.
>>>> PRINT shall take the defined HEADER (the default should be the
>>>> 'variables' and/or properies name,
>>>> and should PRODUCE a columnated output, well designed, as giben by
>>>> the actual values, of the appropite COMLUMNS of the Printout.
>>>> To obtain a properly FORMATTED PRINTOUT, the follwong must be known:
>>>> a) Are all Values of the COLUMN in question NUMRIRIC? If yes:
>>>> COLUMNS must be RIGHT aligned !
>>>> b) What is the maximum WIDTH of the column in question?
>>>> c) MAY the width, when the total PRINT LINE Length is TOO LONG, may
>>>> the item BE WRAPPED ?
>>>> A Reference Implementationof this (still untested) new feature is in:
>>>> org.netrexx.thsitc.runtime.compatibilty  (class Reports)
>>>> My personal PP does and will produce whe approriate methoid
>>>> invocations, BUT:
>>>> I'm suggesting to ADD this feature to the NetRexx Languqage.
>>>> Reletaed TOPICS: TITLE, FOOTING, HEADING, etc...
>>
>>
>

--
Thomas Schneider (Founder of www.thsitc.com) Member of the Rexx Languge
Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team
(www.netrexx.org)
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

[David Requena]

Thomas,

While closing an issue with a "Won't fix" might be seen as somewhat rude, you must understand that abusing the system cannot really be qualified as kind to your fellow developers.

1 - the issue tracker is not a forum for discussion of possible or desirable future enhancements. **THERE IS** such a forum: it's the developers mailing list. You have ibm-netrexx when a wider audience is desired.

2 - if you want to file an RFE, that might be acceptable for filing/reminding purposes but then:***YOU DON'T*** mark these as of utmost importance and **YOU DON'T** qualify them as of critical severity.

3 - if you want to comment on some issue, you *DO* by entering a comment on the issue itself. This way all info on an issue is archived together where it belongs, not lost in an ocean of issue notifications.

4 - Developers stay subscribed to this list just to stay on top of things. It is already a noisy list, try not to worsen it.

Try to envision Joe Dev willing to devote the little free time he has fixing one or two of the critical issues that are stoping the release of 3.01. It is out of politeness that we should not force poor Joe to hunt the really urgent issues among a flood of wishes for a 4.00 release.
 
Finally, everybody likes the nice (green) open to fixed ratio plots at the reporting area. *YOU ARE TURNING THEM ALL TO RED* by filing a deluge of critical issues which nobody can or will realistically fix in a short time.

Please, do not use the issue tracking tool as your personal wish list.

Best regards

-
Saludos / Kind regards,
David Requena

NOTE: The opinions expressed here represent the opinions
of the authors and do not necessarily represent the opinions
of those who hold other opinions.

-----Original Message-----
From: Thomas Schneider <[hidden email]>
Date: Mon, 26 Sep 2011 21:02:31
To: <[hidden email]>; IBM Netrexx<[hidden email]>
Reply-To: [hidden email]
Subject: Re: [JIRA] Resolved: (NETREXX-35) NetRexx Should contain SIMPLE statements
 (NEW instructions) to produce  a PRINTED Report

Hello You all there,

    1.) When the current behaviour of the NetRexx *group* is to change
*nothing* for NetRexx versions 4.00 : I'll be off at any and all NetRexx
Lists.

Sorry for me, but a great advantage for you:

  *Nothing has to be changed*,  *or* advanced, (bit fo rbit) ..

    2:) I'm totallly (personally) DIS-AGGREING that *when* I'm,
enterering *issues* there at www.kenai.com, project NetRexx, at my spare
time:

*and suddenly*

Those issues do DIS-Appear, because someone else did decide to do so.

When we do have an issue tracking at KENAI, please do NOT
DISTORT my suggestions ...

Otherwise my membership there will be USELESS at all :-)

...  as I am an unwanted member in many communities, any way :-)

I'm not sitting here to enter issues, when other people do decide:
NO Issue.

I DO have too much work to do to have too much spare time to take
my time to enter CLOSED issues (when they are NOT closed)...

Sorry to say ..

Massa Thomas.

Thomas Schneider
CEO
ThSITC IT Consulting KG
===============================================================
Am 26.09.2011 1:12, schrieb Kermit Kiser (JIRA):

>       [ http://kenai.com/jira/browse/NETREXX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Kermit Kiser resolved NETREXX-35.
> ---------------------------------
>
>      Resolution: Won't Fix
>
> This can be handled by library functions. No language change is needed.
>
>> NetRexx Should contain SIMPLE statements (NEW instructions) to produce  a PRINTED Report
>> ----------------------------------------------------------------------------------------
>>
>>                  Key: NETREXX-35
>>                  URL: http://kenai.com/jira/browse/NETREXX-35
>>              Project: netrexx
>>           Issue Type: Improvement
>>           Components: Translator
>>             Reporter: Thomas.Schneider.Wien
>>
>> NetRexx should add NEW instructions (Verbs) to be able to produce a simple, formatted, REPORT.
>> I'm proposing to add the NEW Verb:
>> PRINT a,b,c
>> for this purpose.
>> PRINT shall take the defined HEADER (the default should be the 'variables' and/or properies name,
>> and should PRODUCE a columnated output, well designed, as giben by the actual values, of the appropite COMLUMNS of the Printout.
>> To obtain a properly FORMATTED PRINTOUT, the follwong must be known:
>> a) Are all Values of the COLUMN in question NUMRIRIC? If yes: COLUMNS must be RIGHT aligned !
>> b) What is the maximum WIDTH of the column in question?
>> c) MAY the width, when the total PRINT LINE Length is TOO LONG, may the item BE WRAPPED ?
>> A Reference Implementationof this (still untested) new feature is in:
>> org.netrexx.thsitc.runtime.compatibilty  (class Reports)
>> My personal PP does and will produce whe approriate methoid invocations, BUT:
>> I'm suggesting to ADD this feature to the NetRexx Languqage.
>> Reletaed TOPICS: TITLE, FOOTING, HEADING, etc...

--
Thomas Schneider (Founder of www.thsitc.com) Member of the Rexx Languge
Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team
(www.netrexx.org)

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/