[Oorexx-devel] Fwd: Re: Questions ad Allura ...
Hi there, enclosed FYI my postings to the Allura dev list, which caused me to create four tickets today, which are enclosed right at the top of the forwarded e-mail. Please consider to vote on them. ---rony Original Message Subject:Re: Questions ad Allura ... Date: Sat, 25 Aug 2012 12:47:35 +0200 From: Rony G. Flatscher (Apache) r...@apache.org Reply-To: allura-...@incubator.apache.org To: allura-...@incubator.apache.org Hi Dave, thank you for your feedback, which leaded to the creation of the following four tickets, hoping that their description and content can be understood out of context as well: * #4792 Please allow normal users to receive notification e-mails for all commits and patches: https://sourceforge.net/p/allura/tickets/4792/ * #4789 Please add links to the file's diffs for commits and patches in the notification e-mail : https://sourceforge.net/p/allura/tickets/4789/ * #4790 Allow additional fields to be shown on bug tracker: https://sourceforge.net/p/allura/tickets/4790/ * #4791 Please add a popup to determine sort (fields, sorting position and kind): https://sourceforge.net/p/allura/tickets/4791/ ---rony On 23.08.2012 23:58, Dave Brondsema wrote: Hi again Rony. Thanks for the feedback. On 8/23/12 5:09 AM, Rony G. Flatscher (Apache) wrote: Hi Dave, On 22.08.2012 20:00, Dave Brondsema wrote: Patches: Perhaps I am not understanding the problem clearly. Are you talking about a ticket in your Patches tracker? E.g. https://sourceforge.net/p/oorexx/patches/171/ On there I can see the attached patch file and can open it fine. If you are subscribed to a ticket, you should get an email when a file is attached. It'll have the attachment metadata, but not the whole file included. Emailing the attachments could be a problem if they are very large. Can you provide an example if I'm not on the right track here? Maybe the following helps understand the built attitude/expectation better: when following a project like ooRexx over the years as a former/potential developer it is important to learn about *all* supplied patches and *all* commits in general. Then, if patches, commits occur it used to be the case that an e-mail including the diffs got sent out via a relay-e-mail-list and anyone who subsribed to that e-mail list received it. Now, the diffs embedded in the e-mail would not be necessary, if the e-mail contained a list of files that got changed each with a link to get to its diff (and ultimately one link that would present all diffs at once). For study purposes or merely documentation printing out those diffs (either physically or as a pdf) is important, if an area got changed that one has special interest in. Following a specific tracker item needs the prerequisite, that one learns that a tracker item got created in the first place, which is quite cumbersome. [In the example https://sourceforge.net/p/oorexx/patches/171/; one would be able to get access to the patch attachment, but I have not found a way to display it inline with color highlighting.] So maybe the bottom line would be: allow for sending out any patch (and commit) via a relay e-mail-list, which can be subscribed by interested parties. This would allow for a push model, where one would be informed that a patch (commit) got submitted/applied. If that e-mail contained the aforementioned links to get to diffs (on each file or optionally having one big diff for all affected files), then this would be great! There is a setting that should get you most of the way there, I think. If you go to Admin, Tools and then click on Options for the tracker, there is a Email ticket notifications to: field. The remaining piece would be to easily get to the attached patches. Allura doesn't have that now, but a new ticket to make the attachment references include a direct link seems appropriate. Sorting bugs: There is a ticket https://sourceforge.net/p/allura/tickets/4596/ for making the sort order oldest-first by default. Several people have voted for it already, so we'll probably get to it soon. Of course, patches are welcome too :) After you do a search, there is a 'Help' button near the search box. That help box details the fields available for searching and sorting (near the bottom of that help box). Thank you, yes, I have studied the help box. (It seems that now the initial order of the bug tracker is newest first, oldest last, which is great! However, when doing a search on the bug tracker system, the order is oldest first, newest last.) Here there would be the following ideas/requests: allow for displaying the column reported_by_s and in addition allow/show a field/column reported on.and mod_date_dt. Also, in general a RFE (not sure whether I should open a ticket for it) for sorting: how about having a popup (like the field popup where one can determine which
Re: [Oorexx-devel] Ad sorting arrays: request for discussion/thoughts ...
Hi there, thank you very much for all of your feedback which encouraged me to create the following two RFEs: * feature-requests:479 Add a condense method to the Array class: https://sourceforge.net/p/oorexx/feature-requests/479/ and * feature-requests:480 Allow the sort/sortWith methods to sort sparse arrays as well: https://sourceforge.net/p/oorexx/feature-requests/480/ ---rony On 24.08.2012 12:01, Rony G. Flatscher wrote: Yesterday I stumbled over a surprising behaviour of Array's sort, which led me to open a bug report https://sourceforge.net/p/oorexx/bugs/1107/. Obviously the sorting is working as designed, hence the reported behaviour was not accepted as a bug. Having slept a night over this and thinking about my utmost surprise that sort would raise an error condition if it hits an empty array element (one without an entry) in between, I try to summarize my thoughts about the current behaviour, requesting a change of the design and implementation to get rid of the surprising factor and to remove undeterminable fragility from the Array sort. First, the current design and implementation: The single dimiensioned array that gets sorted must not have empty entries in between. If the sort tries to refer to an empty slot it raises Error 98.975: Missing array element at position xyz and the program is ended, if the condition does not get trapped. Thoughts about this: 1. Having worked for many years sorting arrays, I was *totally surprised* about this unexpected (because never experienced) behaviour! The surprise factor for me was at the maximum. 2. There is no documentation going with sorting arrays that would communicate that the arrays to be sorted must have no empty elements in between that I am aware of. Therefore one cannot expect this behaviour at all. 3. If one uses single dimensioned arrays that get changed in routines and methods (written by others) such that elements get removed in between, then sorting such an array all of a sudden (and totally unforseeable) raises the above mentioned error condition, which makes sort quite fragile for programmers IMHO. 1. To overcome this situation, one must advice every ooRexx programmer to do *always* a (potentially time-consuming) makearray before sorting an array just to make sure that the aforementioned error condition does not get raised. 4. Finally, I would have expected that an array with empty elements should be sortable without a problem, therefore my utmost surprise! :) 1. My expectations would be simply as follows: if a single dimensioned array contained empty elements, then sorting would work and all the empty elements are sorted to the end of the array, no matter what the comparison method returns. This way, after a sort, all empty elements are always at the end of the array. (The items and size messages would remain the same.) The questions I would have, before contemplating about filing a RFE: * am I the only one who is surprised about a failing sort on a single dimensioned array if in between there are empty elements? * Independent of this, would it be acceptable to change the current design and implementation of the sort such that empty elements are tolerated and put to the end of the array (what would be arguments, thoughts that speak against such a change)? ---rony -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] publican version of the error message files
David, I'm working on having the build generate the 4 error message files for you. I notice that the ones in the publican build don't have an xml declaration or a doctype declaration. Should those be there? I think I can get those added since I'm in the process of making changes. Rick -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Man Pages
On Sat, Aug 25, 2012 at 12:28 PM, CVBruce cvbr...@gmail.com wrote: Would it not make sense to either create a man page for ooRexx, or to create a link to the existing rexx man page. Hi Bruce, I'm not sure what you mean by or to create a link to the existing rexx man page Actually, I guess I'm just not sure what you mean at all. Are you saying you would rather have the man page named ooRexx than rexx? Or ... what? ;-) The rpm and deb installers correctly set up the man pages on Linux. The executable is named rexx. On Unix-like systems, you typically type man nameOfExecutable to get a hint as to what some executable is. So, on Linux, the installers do what is typically expected by a Linux user. I have no idea what that translates into on a Mac. For instance neither my mother nor by brother would have any concept typing 'man'. It seems to me, that most Mac users just use the GUI part of a Mac in a way similar to Windows users. What would make the most sense to me is to set up the ooRexx reference manuals in the way the typical Mac user expects to find documentation on the things they install. I probably know closely about 20 or 25 people who use a Mac. Not a one of them knows anything about 'man' and I doubt that any of them has every used a command prompt on their Macs -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] FYI ooDialog 4.2.0 release and ooRexx 4.1.2 release
Just a FYI on my plans. For ooDialog 4.2.0, I plan to do the official release this weekend. Probably tomorrow. For ooRexx 4.1.2, I'm currently planning on getting the official release started at the beginning of the week. I'll probably move the branch code to release the first part of the week and start building the release installers and doc. Have the doc and installers up on SourceForge and do the official announcement around Friday. I'll send out an e-mail when I move the branch code to the release directory. -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Man Pages
Yes the executable is rexx, how do you know that? I would expect that if I was installing ooRexx, the executable would be ooRexx. You grab the ooRexx installer off of source forge install it, and now what? I would think that the ooRexx man page would mention the other man pages, and possibly where stuff was installed, the class files, and the examples in /share. It might also mention that the documentation is available in a separate download from source forge. That you have to possibly setup both path and library environmental variables. The error message you get when rexx can't find its libraries. You know just general stuff that the first time user wouldn't know. Bruce On Aug 25, 2012, at 3:52 PM, Mark Miesfeld wrote: On Sat, Aug 25, 2012 at 12:28 PM, CVBruce cvbr...@gmail.com wrote: Would it not make sense to either create a man page for ooRexx, or to create a link to the existing rexx man page. Hi Bruce, I'm not sure what you mean by or to create a link to the existing rexx man page Actually, I guess I'm just not sure what you mean at all. Are you saying you would rather have the man page named ooRexx than rexx? Or ... what? ;-) The rpm and deb installers correctly set up the man pages on Linux. The executable is named rexx. On Unix-like systems, you typically type man nameOfExecutable to get a hint as to what some executable is. So, on Linux, the installers do what is typically expected by a Linux user. I have no idea what that translates into on a Mac. For instance neither my mother nor by brother would have any concept typing 'man'. It seems to me, that most Mac users just use the GUI part of a Mac in a way similar to Windows users. What would make the most sense to me is to set up the ooRexx reference manuals in the way the typical Mac user expects to find documentation on the things they install. I probably know closely about 20 or 25 people who use a Mac. Not a one of them knows anything about 'man' and I doubt that any of them has every used a command prompt on their Macs -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Man Pages
Bruce, I was going to say in my first post that I don't think much has been done with the man pages at all since we got the code from IBM. I did a very little clean up one time a few years ago to fix some completely wrong statements. So go for it. This area is just one of the many little details that could use some work. As far as creating an ooRexx man page and linking to the other man pages, I have no real objection to that. David is more of the expert on what is the norm on Linux and Unix. If you wanted to keep a common set of man page files, I'd see what he says. On the other hand, if you think the current pages are not what is done on OS X, then, since you are the OS X expert, I'd say set up the OS X installer with what you think is right. You can add stuff to the macosx subdirectory for OS X only stuff if needed. -- Mark Miesfeld On Sat, Aug 25, 2012 at 4:57 PM, CVBruce cvbr...@gmail.com wrote: Yes the executable is rexx, how do you know that? I would expect that if I was installing ooRexx, the executable would be ooRexx. You grab the ooRexx installer off of source forge install it, and now what? I would think that the ooRexx man page would mention the other man pages, and possibly where stuff was installed, the class files, and the examples in /share. It might also mention that the documentation is available in a separate download from source forge. That you have to possibly setup both path and library environmental variables. The error message you get when rexx can't find its libraries. You know just general stuff that the first time user wouldn't know. Bruce On Aug 25, 2012, at 3:52 PM, Mark Miesfeld wrote: On Sat, Aug 25, 2012 at 12:28 PM, CVBruce cvbr...@gmail.com wrote: Would it not make sense to either create a man page for ooRexx, or to create a link to the existing rexx man page. Hi Bruce, I'm not sure what you mean by or to create a link to the existing rexx man page Actually, I guess I'm just not sure what you mean at all. Are you saying you would rather have the man page named ooRexx than rexx? Or ... what? ;-) The rpm and deb installers correctly set up the man pages on Linux. The executable is named rexx. On Unix-like systems, you typically type man nameOfExecutable to get a hint as to what some executable is. So, on Linux, the installers do what is typically expected by a Linux user. I have no idea what that translates into on a Mac. For instance neither my mother nor by brother would have any concept typing 'man'. It seems to me, that most Mac users just use the GUI part of a Mac in a way similar to Windows users. What would make the most sense to me is to set up the ooRexx reference manuals in the way the typical Mac user expects to find documentation on the things they install. I probably know closely about 20 or 25 people who use a Mac. Not a one of them knows anything about 'man' and I doubt that any of them has every used a command prompt on their Macs -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
