Re: [Oorexx-devel] Advice on ooDialog ...
On Sun, Nov 21, 2010 at 1:49 PM, Rony G. Flatscher wrote: > skimming over ooDialog on 4.1.0 beta I was wondering what the best > "reading" path would be (also for newcomers) to get acquainted with > ooDialog, its logic, and the new ooDialog classes. E.g. which parts of > the ooDialog manual or Wikis on the net and the installed ooDialog > samples should be studied (and what sequence would you suggest)? Hi Rony, Really there is nothing new in ooDialog in 4.1.0. I added one simple example, added one method, and put in a couple of bug fixes. Everything else is the same as it was in 4.0.0. All the new stuff I've added is still in trunk. I've said this before, but it probably bears repeating. 4.1.0 does not come from trunk; it wasn't branched from trunk. It was branched from 4.0.1, primarily as a bug fix of 4.0.1. Back to your question. So, there are no new ooDialog classes. As to the best reading path for anyone needing to get acquainted with ooDialog and its logic, the answer is pretty much the same as it would have been for 3.2.0. There really isn't any good path. ;-( The problem is that the ooDialog doc, currently, is really a class and method *reference*, not a tutorial. It doesn't help much if you don't know how to get started. As a side note, I intend (maybe intended) for the next major release of ooDialog to be much better documented. But, the writing of the doc is basically what is holding up that release. It is very time consuming to write. At least for me. At this time, I think that the best path is to execute the example programs, get an idea for a simple dialog and write it. Then ask questions on either RexxLA, comp.os.rexx, or the SourceForge project. I try pretty hard to answer all ooDialog questions on those venues. Really the oorexx-users mailing list would be good for anyone not wishing to join RexxLA, but it is not widely used. Still, I watch it and would quickly answer any ooDialog questions, if they were asked. -- Mark Miesfeld -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problems with ooRexx 3.2 (sic!) on Windows 7 and a question about "ooRexx-WSH"
On Sat, Nov 20, 2010 at 11:34 AM, Rony G. Flatscher wrote: > due to some students who have Windows 7 installed I have been made aware of > that there are problems with ooRexx 3.2 on Windows 7: Hi Rony, I don't want to appear cold-hearted, but ooRexx 3.2.0 is not supported on Windows 7. At the time of the 3.2.0 release, October 2007, no one had a working build of Windows 7, or knew what the name of the release after Vista would be. > Problems: All the problems you list are simply a crash, which Microsoft seems to be adverse to stating in a clear, simple way. > These problems in effect inhibit the usage of "ooRexx-WSH" on W7 systems! ooRexx-WSH is not supported on Windows 7, that's for sure. ;-) > It may be the case that the problems could be fixed for ooRexx 3.2, so I > wonder whether anyone (maybe mostly addressed to Mark) would think it to be > worthwhile. I really doubt that it is a simple problem, but I may, sometime in the future, take a quick look to see if it is simple. But, it won't be any time soon. > If not, would it be possible to move the WSE (WindowsScript Engine a.k.a. > ActiveX) implementation for ooRexx 4.x up the waiting list, such that on > Windows 7 and later, "ooRexx-WSH" becomes operational/functional again? Just out of curiosity, have you run the same tests on Vista, to see what results you get? As for the waiting list, it's not so much as to where it is on the list as to a need to find a developer, or developers, with the time, interest in, and level of skill, needed to do the task. -- Mark Miesfeld -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx internal doc ?
Jean-Louis, I'm certainly in favor of a DocBook on how the internals of ooRexx work. -- Mark Miesfeld On Sun, Nov 14, 2010 at 9:37 AM, Jean-Louis Faucher wrote: > There is a skeleton "InternalClasses" in the wiki, currently empty. > Is there other sites I'm not aware of ? > > I have accumulated a few notes coming from : > - Q&R in the developper list, > - how some bugs have been fixed, > - notes taken on the fly, while debuging. > It's raw material and certainly not a technical documentation. > But instead of keeping it for me, I could put it somewhere for sharing. > > If no other doc already started somewhere, then I'm thinking to create a > directory 'internals' in my sandbox. And write some DocBook files with an > editor like XXE. > > > Jean-Louis > > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] [RexxLA] Announcing ooRexx 4.1.0 Beta 1
On Wed, Nov 10, 2010 at 6:39 AM, Mike Cowlishaw wrote: > FYI, using the first link below gives me 'access denied'. However search on > oorexx then All Filkes gets there... David inadvertently posted the link of his location when he was uploading the files. Access to the upload page is, not surprisingly, restricted to someone on the project with admin privileges. The correct link to the "Files" section of the project on SourceForge is: http://sourceforge.net/projects/oorexx/files/ Be sure to scroll past the first section "Newest Files" to the "All Files" section so you can see all the files available. I would think it would be rare that an individual would be able to pick the correct package by looking at the "newest" files. The current SourceForge user interface uses a directory layout for the packages available. The directory names have a triangle next to them. Click on triangle to open, or close up, the individual directories. Drill down to: oorexx -> 4.1.0.beta to see the current list of packages available for the 4.1.0 beta. -- Mark Miesfeld -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Ad Windows installer, dialogs, mimetype definition ... (Re: Beta 4.1: no fiel-association for ".rex" ?
On Sun, Nov 7, 2010 at 5:27 AM, Rony G. Flatscher
wrote:
> ...
> if possible, put the explaining text into a help popup or into a tooltip as
> this would allow for using more of the dialog's real-estate,
Hi Rony
I would like to put all the file association controls on one page.
The problems with that are these:
* There is no way to have tool tips.
* Popping up message boxes is against Microsoft's design guidelines
for Wizards and installation Wizards. Microsoft specifically says in
their guidelines to put the explanatory text on the pages. Presumably
Microsoft's user interface research is more comprehensive than mine.
* NSIS is a very limited environment to work in. There are no tool
tips. There is no WYISWYG dialog editor to lay out the controls.
Moving controls around involves guessing where to put them, compiling
the installer, doing an uninstall / install cycle to see where the
controls actually, repeat endlessly.
To get all the controls on one page, I suspect is either not possible,
or only possible with minimal labeling, or only possible by having a
very cramped looking page that is not aesthetic to *my* eyes. In
other words, I suspect that if I spent the considerable amount of time
doing it, I would end up going back to two pages.
The bottom line is, although I would prefer all the controls on one
page, it would be hard to do. "Being hard to do" is in my mind no
excuse for not doing something.But in this case I don't
think I have the time to do it for this release.
> in the case that an upgrade is possible, because the new installer is used,
> then by default that option should be checked (check-box "Perform an upgrade
> type of install") as probably most people who merely wish to upgrade the
> ooRexx interpreter would want to leave all setup options the same.
I would also prefer it to be checked. I would like to get some feed
back from others that use the installer during the beta. I'll solicit
opinions if they are not offered up during the beta period. It is an
easy change to make.
> in the case that an installation was done without having (all) file
> associations created, then, if on a new install the "Create Windows file
> associations" is checked, then the unchecked file-associations ("rexx.exe",
> "rexxhide.exe", "rexxpaws.exe") having empty/missing "Extension" and "File
> type name" entries should have the original values filled-in as defaults
> that can be overriden by the user. Alternatively the help/tooltip could
> inform the user what the ooRexx developer's default values would be, such
> that the user can use those.
The defaults values are listed on the applicable page for each of the
executables. I listed them for exactly this reason, so that people
would know what the suggested defaults are.
> Finally a question ad mimetype definition for Rexx programs: shouldn't the
> installer also set up a mimetype for Rexx programs? Either
> "application/x-rexx" or "text/x-rexx" or the like?
This is something I'm not much interested in. You should bring this
up separately. You need to either get a consensus from the
developers, or the users, that this is something that *should* be
done. I have no objection to it, and would implement it, if I felt
it was something the users, or the developers, really wanted.
--
Mark Miesfeld
--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Beta 4.1: no fiel-association for ".rex" ?
On Sat, Nov 6, 2010 at 10:40 AM, Rony G. Flatscher wrote: > The point that I tried to make (and failed) is: if one checks the > "Create Windows file associations", then one (in any case: I) would > expect that the file associations get created. Therefore, I would > suggest in that particular case to make sure that the check-box a few > pages later is set as well, The point I was trying to make (and apparently failed at ,) was that this is what *is* done. However, the user is free to uncheck *any* of the check boxes specifying which associations to create, including the association to rexx.exe. Once a check box is unchecked, it stays unchecked until the user re-checks it. If you run the install with no ooRexx installed, you will see that the check box is checked. If you run the install with any ooRexx 4.0.1 or earlier installed, you will see that the check box is checked. If you run the install with any ooRexx 4.1.0 or later installed, and if that previously installed ooRexx *did* do the rexx.exe association, you will see the check box checked. But, if you run the install with any ooRexx 4.1.0 or later installed, and if that previously installed ooRexx did *not* do the rexx.exe association, you will see the check box unchecked. All of the above is the *intended* behaviour. If it does not happen, then that is a bug and should be fixed. And of course it should be said that if people do not think the behaviour I implemented is optimal, and want to change the intended behaviour, then that can be done. -- Mark Miesfeld -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Beta 4.1: no fiel-association for ".rex" ?
On Sat, Nov 6, 2010 at 10:40 AM, Rony G. Flatscher wrote: > ... cut ... > In your case, once 4.1.0 got installed one time without the .rex >> associations, then the next time you did the uninstall / install cycle >> the check box would be set to unchecked. Because that is what was >> done during the previous install. >> > What would be the key in the registry that is used for remembering > previous installation options, such that one can delete them in a case > like this (and become able to test in a "plain-vanilla" state)? The thing to do would be to uninstall the current version of ooRexx. Not by running the install program, but by running just the uninstall program. The "plain-vanilla" state is always "no ooRexx installed." The uninstall program cleans up every registry setting made by the install. Only the uninstall program knows exactly what those settings are, since those settings can (and do) change. The uninstall is written as part of the install. It is at that point, and only at that point, that you can be sure of what the installer is doing. -- Mark Miesfeld -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Beta 4.1: no fiel-association for ".rex" ?
On Sat, Nov 6, 2010 at 8:29 AM, Rony G. Flatscher wrote: > On 06.11.2010 16:09, Mark Miesfeld wrote: > > send me the file as an attachment. Just send it to my g-mail account, > or open a bug and attach the file to the bug. > > Unfortunately, that is not possible. One can mark a single line, but > pressing ctl-c would not copy the marked line to the clipboard. Trying to > select all (ctl-a) does not work, nor a section (select first line + > scrolling to the end, pressing shift-click). Well, that's a NSIS thing that can't be changed. If you right click on the details window you get a context menu with only one item. Which is: Copy Details to Clipboard. If you select that menu item, then the entire contents of the details window is copied. You can paste into a file. I think it is meant to be a convenience. You don't have to first do a select all and then do a copy. > The "Create rexx.exe file association" check box *must* be checked. > If it is not checked, no file association will be created. This could > be your problem, the check box has to be checked. > > Oh, this was not clear to me at all! Well, it's hard to write text that takes into account every conceivable scenario. If the text is too long, 95% of the people reading it, tune it out. (As will happen with this e-mail. ) On the "Associate file extensions with ooRexx ..." page it says: Check the check box to have the installer create file associations. The following pages will allow you to *specify* which associations are created. Then in the next pages you specify which associations you want. It seems entirely conceivable to me that someone would want to associate rexxpaws with all their programs. Therefore, if the "Create rexx.exe file association is unchecked, that association is not created. By leaving the "Create rexx.exe file association" check box unchecked, you are specifying that you do not want the association created. That is the standard Windows interface behaviour. Checking a check box means do what the check box label says, unchecking the box means do not do what the label says If someone goes through the pages and leaves every check box unchecked, then no associations are created. In your case, once 4.1.0 got installed one time without the .rex associations, then the next time you did the uninstall / install cycle the check box would be set to unchecked. Because that is what was done during the previous install. How 4.1.0 got installed the first time without associating .rex is the only question here. Once that happened, then what you describe happening on every install past that, makes sense. > If there is a connex between the > "Create Windows file-extensions" and this option, then maybe you could have > this option checked by default and filling in the default "Extension:" and > "File type name:" ? Well, it does. But - once you do an install of 4.1.0 and later, then these are filled in with what you did during the previous install > Running the install another time, this time checking "Create rexx.exe file > association" shows an empty field for "Extension:" and an empty filed for > "File type name:". Yes, because that is what was done during the previous install. > Supplying an extension is not really clear (with leading dot or not? Entered > ".rex"), If you do not enter the dot, when you leave the page, it will prompt you for the dot. > also it is probably not clear what to enter for "File type name:" > (I entered "RexxProgram" instead of "RexxScript"). > Maybe you could supply > defaults in the input fields as a guidance to the users? It says in the sentence above the check box: By default in Open Object Rexx .. the Rexx interpreter, rexx.exe, is associated with the .rex extension using the file type name of RexxScript. The edit controls are labeled "Extension" and "File type name" I don't really know what could be more clear than that. Although, I do realize that it may not be clear to some people, I don't know how to be more explicit. I, literally, have run the restructured installer hundreds of times, and could not break it. If you have the time to play with the install a little bit and can come up with a repeatable scenario that shows a problem, I'd love to have you open up a bug. 1.) Rerun the install program now that things are set the way you want. Do not check the "Upgrade type" of install check box. You will (should) see the file associations options pre-set to what you already have. 2.) Uninstall your current ooRexx through the Control panel or through the uninstall menu item in the start menu, first, before you run the install program. Then when you run the install of 4.1.0, you will (should) see
Re: [Oorexx-devel] Beta 4.1: no fiel-association for ".rex" ?
On Sat, Nov 6, 2010 at 7:44 AM, Rony G. Flatscher wrote: > Sorry, if I have not been clear enough: the file association for ".rex" does > not get set up, although I checked that check-box. Can you run the installation again and send me the output of the install. There is the details window that shows the output of the install. After clicking the "Install" button, on the next page, all the files are installed. When that finishes, before clicking the next button, copy all the text in details window, paste it into a file, and send me the file as an attachment. Just send it to my g-mail account, or open a bug and attach the file to the bug. > In addition "PATHEXT" does not show ".rex" as one of the extensions Windows > should probe when searching for executable files. If the file association is not going to be created, then .rex is not added to PATHEXT. > Just did it once more: > > Installing (the already installed ooRexx) > > agreeing to uninstall existing ooRexx > > do not remove the directory > uninstalls completes without errors/warnings; > > Now installing ooRexx > > Checking "Create Windows file associations" check-box > Leave "Create 'Send To' ..." as is, ie. 'Send To' for Rexx Hide and Rexx > Pause are checked, > On the next screen entering the full path to the vs-editor, but *not* > changing "File Association for rexx.exe" (not wanting to override) check box > which is also dubbed "Create rexx.exe file assocation", which then seems to > allow for entering an arbitrary extension; The "Create rexx.exe file association" check box *must* be checked. If it is not checked, no file association will be created. This could be your problem, the check box has to be checked. If the current installed ooRexx is 4.1.0 or later, the default settings will be whatever the last install was. I.e., if in the previous install, no file association was created, this check box will not be checked, and you would need to check the check box to create the file association in the current install. > On the next screen (Associate a file extension with rexxhide.exe and /or > rexxpaws.exe), leaving everything alone (unchecked boxes) > install completes without errors/warnings. If you finish the install, with none of the check boxes checked, no file association will be created and the editor setting is of course not done. (Setting the editor requires at least one file association.) -- Mark Miesfeld -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Beta 4.1: no fiel-association for ".rex" ?
Hi Rony, On Sat, Nov 6, 2010 at 6:36 AM, Rony G. Flatscher wrote: > on my Win XP SP3 installation, the ooRexx file associations are not > set-up although that option gets set on the new ooRexx installation > screen (great work!). > (Also the editor is not set up for that file-extension.) I don't follow what you mean. Maybe because I haven't had my coffee yet. Are you saying there is a bug, the file associations did not get set up, ever though you set the option? > The installation of the beta will run the uninstall (without deletion of > the existing directory itself), if that makes a difference. Do you mean by this that you have run the uninstall / install mulitiple times with the same results? -- Mark Miesfeld -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Ready for 4.1.0 beta
On Tue, Nov 2, 2010 at 1:17 PM, David Ashley wrote: > I'm ok with putting things on SF. I will start adding things after tonight's > builds. Good, that's the plan then. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Ready for 4.1.0 beta
I finished the doc update I was planning on doing. I know Jean-Louis may still have some stuff he is doing for the File class. I'm going to be out of town and won't have access to my Windows systems. So, I need to build the first Windows beta release today. I'm going to use the 4.1.0 docs as they are now. David - I could either create the beta folder on SourceForge this evening and put the Windows builds up on SourceForge. Or I could scp them to the build machine and you could start things on SourceForge tomorrow, or when you are ready. I would prefer to just get things going and put the builds on SourceForge tonight. It's a beta after all and really things are at least 99.9% ready. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx installation directory
On Tue, Nov 2, 2010 at 7:15 AM, David Ashley wrote: > No firm release date yet. But we are trying to get out a beta ASAP (this > week?) Yes, this week. I'm finishing up the ReadMe.pdf today. We should start the beta tomorrow, I think. I'll post later today when I'm done. > and certainly a final release before the Christmas holidays. Definitely, barring any unforseen events. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] current ooRexx 4.1 on AIX 64 bit
On Tue, Nov 2, 2010 at 7:12 AM, Rainer Tammer wrote: > this is the result for the test suit on AIX 5.3 / 64 bit. > The test suite does show 3 (unexpected?) failures: Rainer, Be sure you are using the 4.0.1 test suite: https://oorexx.svn.sourceforge.net/svnroot/oorexx/test/releases/4.0.1 NOT the test suite in trunk: https://oorexx.svn.sourceforge.net/svnroot/oorexx/test/trunk I think some people may be forgetting 4.1.0 is branched from the 4.0.1 release, not branched from trunk. If you still get the errors using the 4.0.1 test suite, then let us know. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
On Sun, Oct 31, 2010 at 12:48 PM, Jean-Louis Faucher wrote: > > I did not yet study the implementation of the File class, but the methods > look very similar to the Java "File" class. > http://download.oracle.com/javase/6/docs/api/java/io/File.html > > If this is it the case, then I'm inclined to copy-paste some portions of the > Java "File" documentation... I'm not native english writer so this doc is > far better than the doc I could invent myself. > No objection ? Jean-Louis, I agree with Rony. Go ahead and write it it in your own words. If the english is a little off, I'll rephrase some things for you. Really, getting the doc started is half the battle. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
On Sat, Oct 30, 2010 at 1:37 PM, Jean-Louis Faucher wrote: > I finished the review of changes for 4.1.0. > Feel free to fix any error/omission I may have done. Jean-Louis, Good job on the release notes. > CHANGES : > Section Patches is empty, to remove ? Yes, I would suggest removing any empty section in either CHANGES or the ReleaseNotes. > The doc for the new "File" class is missing (or I didn't find it). We might have to write that. Rick has usually been adding doc when he added things, but he might not have done it with the File class. I suggest we start the beta without the doc and add a skeleton chapter on it when someone has the time and / or inclination. It might even be something you want to do Jean-Louis, you seem to have an interest in xsl processing. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Start 4.1.0 beta soon
That sounds good David. I'm thinking Monday, or whenever after that you have time. I'm hoping to have the last updates done by Sunday. -- Mark Miesfeld On Fri, Oct 29, 2010 at 11:17 AM, David Ashley wrote: > All - > > Just let me know when you are ready and I will produce the beta docs as well > as > all the rpms and debs. I will rely on you guys to produce the Win installs, > > David Ashley > > On 10/29/2010 11:55 AM, Mark Miesfeld wrote: >> All, >> >> I'd like to get the 4.1.0 beta started in a couple of days. We're in >> pretty good shape now. If the beta goes smoothly we can hopefully do >> the release at the end of November. >> >> I think everything is done in the interpreter source, except for >> updating the CHANGES and ReleaseNotes files. They are both started, >> just need to be finished up. The ReadMe.pdf doc still needs some >> work. I started that, will try to finish up over the weekend. >> >> -- >> Mark Miesfeld >> >> -- >> Nokia and AT&T present the 2010 Calling All Innovators-North America contest >> Create new apps& games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > > -- > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Start 4.1.0 beta soon
All, I'd like to get the 4.1.0 beta started in a couple of days. We're in pretty good shape now. If the beta goes smoothly we can hopefully do the release at the end of November. I think everything is done in the interpreter source, except for updating the CHANGES and ReleaseNotes files. They are both started, just need to be finished up. The ReadMe.pdf doc still needs some work. I started that, will try to finish up over the weekend. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
On Mon, Oct 25, 2010 at 3:01 PM, Jean-Louis Faucher wrote: > >> I placed the Draft 2 docs here. >> >> http://build.oorexx.org/builds/release-candidates/ >> > Not part of the doc, but I don't see a CHANGES file for 4.1.0. > If no one is on the subject, then I can initialize the file from the > trackers (in this case, remind me the procedure...) Jean-Louis, the CHANGES doc is maintained the interpreter souce tree. It is started for 4.1.0, but not complete. Just update it and commit like you would any other file in the source tree. https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/branches/4.1.0/trunk/CHANGES We have always just listed the tracker item numbers and titles that are fixed in the current release. You can see the format by what is already in the file. I believe I have the bug, documentation, RFE, and patches tracker database items pretty cleaned up. Every thing going in the 4.1.0 release is marked as 'pending' and 'next release.' If you do a filter on those, you should see all the relevant items. Feel free to update the CHANGES file. Anything you can add to the ReleaseNotes file is also good. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
On Sun, Oct 24, 2010 at 10:49 AM, Jean-Louis Faucher wrote: > ok, I started the work. > But while doing that, I had some doubts for the left position of the > table... And I discovered a problem that I didn't see at first sight in > winextensions.pdf : > With pgwide="1", the table 4.2 is left-aligned on the column of the > varlistentry "Event Log Record". > Without pgwide, the table is left-aligned on the column of the text column > (so more on the right). Yes, that's what the Doc Book documentation for the attribute said it would do. I like it better that way in the PDF, and in the html, I like it a lot better. So, I'm glad you went ahead and committed the changes. -- Mark Miesfeld. -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
Jean-Louis, I just did a quick test, and I agree with David. I'm all for the change. I'd never looked at the html docs before. It seems all the tables look bad. -- Mark Miesfeld On Sun, Oct 24, 2010 at 6:07 AM, Jean-Louis Faucher wrote: > >> * This bug: 3028787 Online Ref ::options formatted wrong still >> exists in the HTML version. > > According to my tests, the browser (IE, Firefox) does not use 100% of the > display area when displaying tables whose colum width is relative like > width="1*". The whole table width is shrinked. > If you add the attribute pgwide="1" to the DocBook element, then the > result looks good in HTML (and PDF is still ok). > Tested with winextensions because faster to rebuild (two tables in section > 4.1). > > When searching for XML files which contain *'> or *">, I get this list : > oodialog\buttoncontrols.xml > oodialog\windowExtensions.xml > rexxpg\api.xml > rexxpg\classicapi.xml > rexxpg\tour.xml > rexxref\classes.xml > rexxref\dire.xml > rexxref\fundclasses.xml > rexxref\intro.xml > rexxref\rexutil.xml > rexxref\utilityclasses.xml > winextensions\wineventlog.xml > > I did not verify each file, but if the proposed change is ok for you, then I > can verify if the HTML of these files is not good, and add pgwide="1" where > appropriate. > > > Jean-Louis > > -- > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
Hi David, * Inisde the zip file, within both the pdf all and the html all, the winextensions reference is missing. * This bug: 3028787 Online Ref ::options formatted wrong still exists in the HTML version. You can see it by putting: x5242.htm in a browser. It is fine in the PDF. This looks to be a problem with jade maybe. SlickEdit reports no end tag for colspec. The online Doc book reference shows colspec like this: in the xml we have: But, if I add the / making it: Then jade reporst an error. So, I'm guessing that's why things don't work in the HTML version. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
On Fri, Oct 22, 2010 at 8:36 AM, David Ashley wrote: > The old scheme. There is some work to do to convert the docs which I don't > want to tackle until after the 4.1.0 release. Okay, that sounds the most reasonable. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.1.0 Draft Documents
Is this still using the old doc build process, or RenderX? -- Mark Miesfeld On Fri, Oct 22, 2010 at 7:11 AM, David Ashley wrote: > All - > > This morning I build the first draft documentation for ooRexx 4.1.0. You can > fin > it here > > http://build.oorexx.org/builds/release-candidates/ > > Please take a look at them and let me know if you discover any problems. > > David Ashley > > -- > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] New Processing for ooRexx Documents
On Thu, Oct 21, 2010 at 9:56 AM, Mark Miesfeld wrote: > On Thu, Oct 21, 2010 at 9:35 AM, David Ashley > wrote: > >> After much frustration, I finally have a potential replacement for the DSSSL ... > > In addition, after I read the RenderX license, I was not convinced > that the license was geared to Open Source developers as Jean-Louis > thought. I think the licensing would need to be looked at closely. Well, I found this for the personal edition license: The RenderX XEP Personal Edition is for non-commercial applications. PDF and Postscript files generated from the application can be distributed, posted to the web or used within internal working groups. The output contains a small, non-obtrusive stamp at the bottom of the page. So, it says the PDF files generated can be distributed and posted to the web, so I think that is an acceptable license. Another advantage of going this route is that it looks like you can use it on Windows also. I'd like that as if I'm working on a Windows box and need to keep switching to a Linux system to compile the docs. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] New Processing for ooRexx Documents
On Thu, Oct 21, 2010 at 9:35 AM, David Ashley wrote: > After much frustration, I finally have a potential replacement for the DSSSL > processing we currently use to produce our PDF documentation. The product is > know as RenderX and, although not open source, is completely free for > non-commercial use. It is Java -base and really easy to use. The PDFs it > produces are pretty good. Hi David, RenderX is the product that Jean-Louis wanted us to try. Check out the oorexx-devel e-mail thread of 6-22-09 titled: About doc defect 2808222 and call to volunteers. That said, your example looks okay to me. Maybe you could do one of the bigger PDFs as an example? We never seem to have come to a consensus in the previous discussion. Jean-Louis has done a fair amount of work concerning this, and has some stuff in the incubator. In addition, after I read the RenderX license, I was not convinced that the license was geared to Open Source developers as Jean-Louis thought. I think the licensing would need to be looked at closely. But, I have no objection to moving to this if others think we should. It's no secret that I don't like certain things about our current process. -- Mark Miesfeld -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] More authoritative discussion on new rpms
On Wed, Oct 20, 2010 at 6:35 AM, David Ashley
wrote:
> Is there any reason to provide symlinks for any libraries other that
> librexx.so and librexxapi.so? I can't think of any reason why the other
> libraries need to be available to developers or dlopen. But I might be missing
> something.
It doesn't seem like it. I can't think of any reason either.
While we are on the subject, remember for both the 4.0.0 and 4.0.1 we
had people open bugs about the "backwards compatibility" symlinks.
I.e.:
# allow backwards compatibility to Object REXX 2.x
ln -sf %{_prefix}/lib/ooRexx/librexxapi.so.%{orx_libversion}
/usr/lib/librexxapi.so.2
--
Mark Miesfeld
>
> David Ashley
>
> On 10/19/2010 10:15 PM, Mark Miesfeld wrote:
>> On Tue, Oct 19, 2010 at 6:06 PM, Mark Miesfeld wrote:
>>
>>> 1.) The dlopen test fails under 4.1.0 from trunk and works with the
>>> released 4.0.1, on Fedora Core 13 64-bit
>>>
>>> 2.) Building the external binaries for the test suite fails under
>>> 4.1.0 from trunk and works with the released 4.0.1
>> Both of these problems are fixed by creating symlinks in /usr/lib64 to
>> the the libraries in /usr/lib64/ooRexx.
>>
>> Creating the file: /etc/ld.so.conf.d/ooRexx.conf with contents of:
>> /usr/lib64/ooRexx fixes the dlopen problem, but not the build problem
>> in the test suite.
>>
>> --
>> Mark Miesfeld
>>
>> --
>> Download new Adobe(R) Flash(R) Builder(TM) 4
>> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
>> Flex(R) Builder(TM)) enable the development of rich applications that run
>> across multiple browsers and platforms. Download your free trials today!
>> http://p.sf.net/sfu/adobe-dev2dev
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
>
> --
> Download new Adobe(R) Flash(R) Builder(TM) 4
> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
> Flex(R) Builder(TM)) enable the development of rich applications that run
> across multiple browsers and platforms. Download your free trials today!
> http://p.sf.net/sfu/adobe-dev2dev
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Debian and /usr/lib64
FYI On my 64-bit Kubuntu, /usr/lib64 is just a symlink back to /usr/lib. I found this statement: "Fedora (and possibly some other distros) patched their libtool 1.5 packages so that on 64 bit Linux platforms it calculates the list of directories ld.so searches as /lib64 and /usr/lib64 plus anything in ld.so.conf (rather than /lib and /usr/lib plus anything in ld.so.conf which is what vanilla upstream libtool does). Debian use /lib and /usr/lib on all architectures" So I think on Debian 64-bit we should just put the libraries in /usr/lib/ooRexx. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] More authoritative discussion on new rpms
On Tue, Oct 19, 2010 at 6:06 PM, Mark Miesfeld wrote: > 1.) The dlopen test fails under 4.1.0 from trunk and works with the > released 4.0.1, on Fedora Core 13 64-bit > > 2.) Building the external binaries for the test suite fails under > 4.1.0 from trunk and works with the released 4.0.1 Both of these problems are fixed by creating symlinks in /usr/lib64 to the the libraries in /usr/lib64/ooRexx. Creating the file: /etc/ld.so.conf.d/ooRexx.conf with contents of: /usr/lib64/ooRexx fixes the dlopen problem, but not the build problem in the test suite. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] More authoritative discussion on new rpms
Hi David, So, I was at a disadvantage in the earlier discussion because I didn't have access to a Fedora system, and hadn't had a chance yet to test thoroughly. Because of that I couldn't be sure of my facts. But, now I've had a chance to look at this more closely, and the same two problems I listed on a Debian system exist on Fedora Core 13 64-bit. 1.) The dlopen test fails under 4.1.0 from trunk and works with the released 4.0.1, on Fedora Core 13 64-bit 2.) Building the external binaries for the test suite fails under 4.1.0 from trunk and works with the released 4.0.1 I just think we need to fix these two things, and it is not that hard, before we release. It's the type of thing the average use won't notice because they aren't building C / C++ programs, but will have some people screaming about backwards compatibility. It's easy enough to test for yourself. I committed the dlopen source code to the test suite, it's under the misc/ directory and the gcc command line to compile is given in the header of the file. The test suite test is simple with this command line: ./testOORexx.rex -B -n Under a build from trunk after you committed the fix (6308): [miesf...@eagle 4.x]$ rpm -q ooRexx ooRexx-4.1.0-6308.fedora13.x86_64 [miesf...@eagle 4.x]$ ./dlOpenTest librexx.so: cannot open shared object file: No such file or directory[miesf...@eagle 4.x]$ [miesf...@eagle 4.x]$ ./testOORexx.rex -B -n ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter: REXX-ooRexx_4.1.0(MT) 6.03 19 Oct 2010 Addressing Mode: 64 ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0 Tests ran: 0 Assertions: 0 Failures:0 Errors: 1 Skipped files: 0 [Framework exception] [20101019 17:58:16.098098] Type: External Command Failure Severity: Severe File: /home/miesfeld/work/wc/ooTest/4.x/building.frm Line: 222 Failed to build external binaries Issuing make failed Command line: make -f Makefile.linux Return code: 2 Location: /home/miesfeld/work/wc/ooTest/4.x/external/API/Makefile.linux Total time: 00:00:00.396555 [miesf...@eagle 4.x]$ Under the 4.0.1 release: [miesf...@eagle 4.x]$ rpm -q ooRexx ooRexx-4.0.1-5867.x86_64 [miesf...@eagle 4.x]$ ./dlOpenTest dlopen worked for librexx.so, handle=0x1d07030 dlopen worked for librexxapi.so, handle=0x1d09150 dlsy worked for RexxGetVersionInformation, function pointer=0x7f46c5f093d0 ooRexx Version Information: Open Object Rexx Version 4.0.1 Build date: May 2 2010 Addressing Mode: 64 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html [miesf...@eagle 4.x]$ ./testOORexx.rex -B -n ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter: REXX-ooRexx_4.0.1(MT) 6.03 2 May 2010 Addressing Mode: 64 ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0 Tests ran: 0 Assertions: 0 Failures:0 Errors: 0 Skipped files: 0 Total time: 00:00:03.131003 [miesf...@eagle 4.x]$ -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 1:13 PM, David Ashley wrote: > On looking back at my changes I see I did make a change that could impact the > debian build. The following was changed: > > AC_PREFIX_DEFAULT(/usr) Yes, that is the change that effected the debian build. What the deb target does is build the interpreter as normal and then do an install into a subdirectory of the build directory. Once that is done it simply packages that subdirectory up into the .deb installation package. But, that's okay. I think the installed files on a debian system should be the same as we are doing on Fedora, SuSE, etc.. Don't you? I'll get that fixed up. But the basic question is, should the installed files go in the same place, /usr/lib/ooRexx etc.? -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 12:31 PM, David Ashley wrote: > That new location for the library files is reflected in the oorexx.spec file. > I did not attempt to make any changes to the debian build locations. There > have > been NO CHANGES to the Makefile.am so far other than a small header file > search > that was added. Hmm, okay. I just looked at the commits. You did make 4 or 5 changes to Makefile.am, that I didn't look at closely at the time. When I saw that the debian files were not getting installed in /opt/ooRexx, I had assumed it came from your changes. But apparently not. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 11:50 AM, David Ashley wrote: > Ok, hard stop. > > I made NO CHANGES to the debian build! I only made changes to the RPM > build. > So something is now broken in the debian build. I know you made no changes to the debian build, but you did make changes to the build itself, in where the the interpreter files are placed in the file system during an install. In particular, the library files are now going to /usr/lib/ooRexx, not /opt/ooRexx/lib/ooRexx. On a debian system, at least, simply doing ldconfig doesn't seem sufficient. And, my experience on Fedora leads me to suspect that it may not be sufficient on other Linux distributions. I'll fix the debian build, but that's why I started this conversation, to see if symbolic links, or adding a file to /etc/ld.so.conf.d, was the "correct" thing to do. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 10:52 AM, David Ashley
wrote:
...
>
> BTW - it bothers me that no one seems to have done any testing of the rpm
> builds
> I have been doing except me. It make me wonder why I am going to all this
> work.
Well, I've been out of town and haven't had access to my Linux
systems. But, testing your builds this weekend is why I started this
thread.
1.) On a debian system, trying to build the external binaries in the
test suite fails for me. Before you made the Linux build changes, it
worked fine.
2.) On a debian system, I have a small program to test dynamically
loading the rexx and rxapi libraries. After the change to the
location of the libraries, it stopped working. It works for the 4.0.1
release.
3.) Then, to try and see if this was a debian only problem, I
installed the Fedora Core 13 64-bit rpm on my Fedora system, and rexx
wouldn't even run. I don't have the message output here, but it
basically said that librexx.so couldn't be located.
#1 can be fixed by changing the make file. But, that shouldn't be
necessary. To test, use this command line for the test suite:
./testOORexx.rex -B -n -V 6
#2 can be fixed either by creating the symbolic links, or by adding a
file to /etc/ld.so.conf.d as outlined by Erico.
#3 As I mentioned, I was in a hurry when I had access to the Fedora
Core 13 machine. I simply did an install of the rpm and tried rexx
-v. It could be the problem is not related to the library location.
But, then there is some other problem. A simple install should have
worked.
# 2 here is the dlopen test code:
/**
* Test to see if librexx.so and librexxapi.so can be dynamically loaded and
* used.
*
* To compile use
*
* gcc -o dlOpenTest dlOpenTest.c -ldl
*/
#include
#include
#include
#include
int main(int argc, char **argv) {
void *hRexx, *hRxapi;
char *str;
char *rexxLibName = "librexx.so";
char *rexxapiLibName = "librexxapi.so";
PFNGETVERSIONINFORMATION getVer;
hRexx = dlopen(rexxLibName, RTLD_LAZY);
if ( !hRexx ) {
fputs(dlerror(), stderr);
exit(1);
}
printf("dlopen worked for %s, handle=%p\n", rexxLibName, hRexx);
hRxapi = dlopen(rexxapiLibName, RTLD_LAZY);
if ( !hRxapi ) {
fputs (dlerror(), stderr);
dlclose(hRexx);
exit(1);
}
printf("dlopen worked for %s, handle=%p\n", rexxapiLibName, hRxapi);
getVer = dlsym(hRexx, "RexxGetVersionInformation");
str = dlerror();
if ( !getVer ) {
printf("dlsym getVer=%p error=%s\n", getVer, str);
exit(1);
}
printf("dlsy worked for RexxGetVersionInformation, function
pointer=%p\n", getVer);
str = (getVer)();
printf("\nooRexx Version Information:\n\n%s\n\n", str);
dlclose(hRexx);
dlclose(hRxapi);
return 0;
}
#1 Here is the complete output from the test suite test:
:~/work/tools/wc/ooTest/4.x$ . setTestEnv.sh
Setting env for Linux
:~/work/tools/wc/ooTest/4.x$ ./testOORexx.rex -B -n -V 6
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.1.0(MT) 6.03 15 Oct 2010
Addressing Mode: 32
ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0
Tests ran: 0
Assertions: 0
Failures:0
(Known failures:) 0
Errors: 0
Exceptions: 1
Skipped files: 0
Messages:0
Logs:1
[Framework exception] [20101019 11:07:19.776849]
Type: External Command Failure Severity: Severe
File: /home/miesfeld/work/tools/wc/ooTest/4.x/building.frm
Line: 222
Failed to build external binaries
Issuing make failed
Command line: make -f Makefile.linux
Return code: 2
Location: /home/miesfeld/work/tools/wc/ooTest/4.x/external/API/Makefile.linux
gcc -c -fPIC -I /home/miesfeld/work/tools/wc/ooTest/4.x/api -I
/home/miesfeld/work/tools/wc/ooTest/4.x/api/platform/unix
orxfunction.cpp
gcc --export-dynamic -shared -nostartfiles
-L/home/miesfeld/work/tools/wc/ooTest/4.x/.libs -lrexx -lrexxapi -o
liborxfunction.so orxfunction.o
/usr/bin/ld: cannot find -lrexx
collect2: ld returned 1 exit status
make: *** [liborxfunction.so] Error 1
Interpreter: REXX-ooRexx_4.1.0(MT) 6.03 15 Oct 2010
Addressing Mode: 32
ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0
Tests ran: 0
Assertions: 0
Failures:0
(Known failures:) 0
Errors: 0
Exceptions: 1
Skipped files: 0
Messages:0
Logs:1
Total time: 00:00:01.777142
:~/work/tools/wc/ooTest/4.x$
So, see, someone is testing your builds. They just are getting
different results than you are.
--
Mark Miesfeld
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R)
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 10:15 AM, Erico Mendonca wrote: > I don't have a Fedora machine at hand, but the behaviour should be the same > on all modern Linuxes. > > The problem is, you still need to tell ldconfig the "extra paths" to scan. It > only scans /usr/lib and /lib by default. Just create a file at > /etc/ld.so.conf.d containing the extra path. > > For example, create "/etc/ld.so.conf.d/oorexx" containing the following line: > > /usr/lib/ooRexx Yes that would work. My point was that currently what is being done, doesn't seem to work. > run "ldconfig" to re-create the library cache and you're done. You can check > if it worked by issuing "ldconfig -p | grep rexx". > > There should be no need to create symlinks manually. Well, that was why I was doing a Google search, to try and see which approach you were "supposed" to use. On my Kubuntu system, there is only one file in /etc/ld.so.conf.d, so I was thinking that adding a file to that directory was not used. Creating symlinks is easy enough in the script and was what we did before. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem with Linux rpm installs
On Tue, Oct 19, 2010 at 8:08 AM, David Ashley wrote: > No, they do not. In the postinstall section of the RPM spec file we run > ldconfig after all the files have been installed. ldconfig is smart enough to > look in all the subdirs of /usr/lib and put them in the library search path as > well. That doesn't seem to be the case though. I thought that ldconfig might do that, but it doesn't seem to do that. Fedora Core 13 64-bit specifically didn't work. But, I only did a quick test, maybe there was some other reason the interpreter wouldn't run. Doing a Google search also seemed to point to the conclusion that symbolic links needed to be created. I started with debian documentation though, where the writers seem to be adverse to stating things simply. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Enhanced Windows installation program
On Sun, Sep 19, 2010 at 6:28 AM, Rony G. Flatscher wrote: > just a very brief/quick feedback, Hi Rony, Thanks for the feedback. I'm not going to address the points individually, just giving an update here. The 'Send To' idea is good, I've added that. The user can choose to create a Send To item, or not, for each of the 3 Rexx executables. The main driving factors for update to the installer comes from the comments entered in the RFE, which I perceived to be: 1.) Don't change people's customized settings when they are doing what is basically an update installation. 2.) People requested that they could have different file types for rexxhide and rexxpaws. 3.) People didn't like the editor being changed back to notepad. So, that's basically what I focused on. People don't have to add extra file types if they don't want to. The point is they have the option of doing that, and they can specify whatever they want. You and I woud never use rexxpaws, Gary wants *all* his Rexx programs to be executed by rexxpaws, *not* by rexx. With the old version of the installer, the user had absolutely no say in what or how the file extensions were set up. Now they can do whatever they want. As to assigning a lot of different extensions to a ftype, well I'd prefer to leave that up to the user. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Enhanced Windows installation program
On Fri, Sep 24, 2010 at 8:29 AM, Brandon Cherry wrote: > I thought about rewriting bits of it as I am accustom to if statements > rather than what amounts to gotos. For me it helps in readability to > have the logic library available. From the new installer, it looks like > you agree. Yes, using the logic library difinetly makes it easier to understand what is going on. I basically rewrote a lot of the script simply so I could comprehend what the script was doing. > One question quickly comes to mind. Why would you want to associate > different editors for each extension? That's a great comment. I rewrote the screens so that you only need to enter the editor once. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Problem with Linux rpm installs
Hi David, In your new rpm scheme, you've changed the install location for the libraries to /usr/lib/ooRexx. Without creating symbolic links for the libraries, things don't seem to work. I've only had limited access lately to some Linux machines, so I haven't tested throughly. But a quck install of the Fedora core 13 rpm showed that rexx would not even run. It couldn't find librexx.so. On an Ubuntu system, for the test suite, the external API executables wouldn't build because they couldn't link to rexx and rexxapi. Which would mean that people with existing make files would need to redo them. You're the expert here, but don't the symbolic links still need to be created in /usr/lib? -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Updated Windows Installer / Windows build(s) on Build machine
All, I updated the Windows Installer using the feedback I got, and also placed some Windows builds on the build machine: http://build.oorexx.org/builds/interpreter-main/6304/ There are 32-bit and 64-bt builds of both 4.1.0 (which will be the next release) and what is now labeled 4.2.0 which is the tip of tree. For the Windows installer, from Brandon's comment "which would you assign a different editor to the different program file types," I changed the screens around and have only one place to enter the editor. This is then used for all the file types, if the user elects to create different file types. >From Ronny's comments, I added a screen that allows the user to select to create 'Send To' items, or not. The 4.1.0 build seems pretty stable to me. It is pretty much what the release will be, so if people were to start testing it - that would be good. The build machine has the Linux builds on it already. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx Docs RPM
On Mon, Oct 18, 2010 at 2:38 PM, David Ashley wrote: > I need opinions and I know this group has no shortage of those :-) > > I am going to create an RPM for the ooRexx documentation. What I need o know > is > what to put in the RPM - just PDFs, just HTML, or both? Since this is Linux I > am > leaning toward PDFs since almost all Linux distributions have pretty good PDF > viewers and AcroReader is widely available as well. But I am open to other > opinions. I'd say PDF for sure. I personally don't like the HTML format very much, the one good use for it is what you have done, putting it up on a web page. On a sort of contrary note, I'm not sure I'd bother with downloading a rpm, I'd probably just download the zipped PDF docs. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] If we were to install the PDF doc on Linux ... ?
On Fri, Oct 15, 2010 at 8:47 AM, Mark Miesfeld wrote: > A completely un-related question. > > It seems to me in older installations, you could launch rexxtry from > the command line on Linux. I just noticed in 4.1.0 you can't if you > install from a deb package. Not sure what happens using a rpm > package, I only have access to a Kubuntu system at present. > > Since you are now putting the executables in /usr/bin, I think you > should either put rexxtry there also, or link to it. Which ever is > appropriate. Okay, I just took a look at the rpm spec and see that it does link rexxtry to /usr/bin. I'll add that to the deb package. -- Mark Miesfeld > > -- > Mark Miesfeld > -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] If we were to install the PDF doc on Linux ... ?
David, mostly directed towards you. If we were to install the PDF doc along with the interpreter on Linux, is there a standard place it would go? The reason I ask is I want to close this bug: 'RexxTry using wrong path for Documentation.' I plan to add a check if the doc is in a specific location and a PDF reader can be found, then launch it, otherwise say no online documentation. A completely un-related question. It seems to me in older installations, you could launch rexxtry from the command line on Linux. I just noticed in 4.1.0 you can't if you install from a deb package. Not sure what happens using a rpm package, I only have access to a Kubuntu system at present. Since you are now putting the executables in /usr/bin, I think you should either put rexxtry there also, or link to it. Which ever is appropriate. -- Mark Miesfeld -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Test failures concerning stems
On Sun, Oct 10, 2010 at 3:12 PM, Rick McGuire wrote: > Yep, I see the problem. I forgot that the default value is that > determined by the NOVALUE handler, which uses the provided name. > Needed to tweak things a little. Thanks. -- Mark Miesfeld -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] 4.1.0 doc branch created
David / Rick In case you miss the svn message, I've branched the 4.1.0 docs from trunk. -- Mark Miesfeld -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Test failures concerning stems
Rick,
In trunk (and in the 4.1.0 branch) there are the below 2 test
failures. Really the same error I'm sure. Since you just did that
bug fix for NOVALUE condition can report wrong compound variable name,
I thought maybe you would know the problem right off the bat:
C:\work\ooTest\4.x>testOORexx.rex -p FUNCTION -p METHOD
Searching for test containers..
Executing automated test suite..
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.2.0(MT) 6.04 10 Oct 2010
Addressing Mode: 32
ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0
Tests ran: 398
Assertions: 1485
Failures:2
Errors: 0
Skipped files: 0
[failure] [20101010 14:23:11.321000]
svn:r4248 Change date: 2009-03-02 16:17:10 -0800
Test: TESTSETVARIABLE01
Class: FUNCTION.testGroup
File: C:\work\ooTest\4.x\ooRexx\API\oo\FUNCTION.testGroup
Line: 812
Failed: assertSame
Expected: [[FOOBAR.1], identityHash="266583864"]
Actual: [[SETSTEM.1], identityHash="266709002"]
[failure] [20101010 14:23:11.368000]
svn:r4248 Change date: 2009-03-02 16:17:10 -0800
Test: TESTSETOBJECTVARIABLE01
Class: METHOD.testGroup
File: C:\work\ooTest\4.x\ooRexx\API\oo\METHOD.testGroup
Line: 1045
Failed: assertSame
Expected: [[FOOBAR.1], identityHash="266773381"]
Actual: [[SETSTEM.1], identityHash="266469998"]
File search:00:00:00.344000
Suite construction: 00:00:00.032000
Test execution: 00:00:00.109000
Total time: 00:00:01.032000
The FUNCTION.testGroup looks like:
x = TestSetContextVariable('setStem.', .stem~new("FOOBAR."))
self~assertSame("FOOBAR.", setStem.[])
self~assertSame("FOOBAR.1", setStem.1)
and the METHOD.testGroup looks like:
self~TestSetObjectVariable('setStem.', .stem~new("FOOBAR."))
testGroup~assertSame("FOOBAR.", setStem.[])
testGroup~assertSame("FOOBAR.1", setStem.1)
--
Mark Miesfeld
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Need to branch docs for 4.1.0
David / Rick We need to branch the docs for 4.1.0. I would do it, but I'm not sure which would be the best way to do it. We either need to branch from the 4.0.1 docs or branch from trunk. For ooDialog, the docs in trunk are incorrect for 4.1.0. They need to remain the same as the docs for 4.0.1, with maybe some doc bugs fixed. But, I'm not sure about some of the stuff you guys have done. I haven't been paying strict attention to it, but I think Rick has done the doc for things like the File class in trunk, and some other things. Same for some of the stuff David has done, it may be already doc'd in trunk. Not sure though if there is some doc in trunk for stuff that will not be in 4.1.0? If we branch from trunk, it is easy enough for me to fix the ooDialog doc. David if you feel like doing the branch, go for it. -- Mark Miesfeld -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Broken download link from
It looks to me that the link needs to be: https://sourceforge.net/projects/oorexx/files/oorexx/3.2.0/ooRexx320-1.exe/download or http://sourceforge.net/projects/oorexx/files/oorexx/3.2.0/ooRexx320-1.exe/download to work. However, isn't www.oorexx.org a RexxLA thing? Maybe it should be reported to the RexxLA webmaster. -- Mark Miesfeld On Sat, Oct 9, 2010 at 11:13 AM, Rony G. Flatscher wrote: > Hi there, > > The download link from <http://www.oorexx.org/download.html> is broken, > if choosing download Windows 3.2.0, which points to > <http://sourceforge.net/projects/oorexx/files/oorexx/ooRexx320-1.exe/download>. > However the user is led to page > <http://sourceforge.net/projects/oorexx/files/> instead. > > ---rony > > > > > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Build Machine - Windows builds
David, That sounds good. As I recall, when you first posted the problem with the Windows, you said that the build worked fine when you ran it manually. That you only got the error when you ran it automated. Is that still the case? -- Mark Miesfeld On Wed, Oct 6, 2010 at 9:33 AM, David Ashley wrote: > All - > > I am in the process of changing the process by which the Build Machine creates > ooRexx Windows builds. This may take a little time to create and debug but > when > finished the entire process will be driven as a set of Windows batch files > instead of a single ooRexx script. There will still be some ooRexx scripts > involved but they will all be small and they will never control the build > process, just set/check variables and copy files. This should fix the build > problem by eliminating the single ooRexx script we were using. > > I will keep you updated on my progress. > > BTW, as you can probably tell, the nightly build scripts are running smoothly > now. I am sometimes seeing a problem with SVN checkouts, but this only happens > about once a week and usually only to a single build process. I think we can > live with that :-) There are now 14 builds happening every night and 4 more > will > be added when I get the Windows builds working again. > > David Ashley > > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Win 7 64 bit ooRexx Builds
On Sun, Oct 3, 2010 at 7:56 AM, David Ashley wrote: > 1. Can Win 7 64 bit run 32 bit binariaes and DLLs? > 2. Are there any different steps or additional items that need to be performed > for 64 bit? All 64-bit Windows OSes can run 32 bit binaries. (You can't of course install both a 32-bit and 64-bit ooRexx on the same machine because rxapi will have conflicts.) What controls if a 64-bit or 32-bit version is built is the Windows SDK or VC++ environment set up. So for a 64-bit build (on a 64-bit Windows) I use this setup: call "C:\Tools\Visual.Studio2008\VC\vcvarsall.bat" amd64 call "C:\Tools\MsSDK.v6.0\bin\SetEnv.cmd" /Release /x64 /XP and for a 32-bit build (on a 32-bit Windows): call "C:\Tools\Visual.Studio.2008\VC\vcvarsall.bat" x86 call "C:\Tools\MsSDK.v6.0\bin\SetEnv.cmd" /Release /x86 /XP Note that the exact parameters vary a little bit with the version of the SDK (and I think with the compiler also.) You can get the parameters by doing: C:\Tools\Visual.Studio.2008\VC\vcvarsall.bat or C:\Tools\MsSDK.v6.0\bin\SetEnv.cmd /? using the correct path to the installaion of course. You only need to quote the path if you installed into a directory with spaces in it. You can also cross-compile, compile the 64-bit version in a 32-bit Windows, etc.. But I usually have a 32-bit system right next to a 64-bit system so I never bothered to try it. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Enhanced Windows installation program
All, I placed Windows installation packages on the build machine: http://build.oorexx.org/builds/interpreter-main/6209/windows/ There are 32-bit and 64-bit builds of 4.1.0 and 4.2.0, both debug and non-debug versions. -- Mark Miesfeld On Tue, Sep 21, 2010 at 9:56 AM, Brandon Cherry wrote: > Seeing how the build server is down for windows builds for the time > being, is there an alternative location for at least a 32 bit build? > -- > Brandon Cherry > > On 9/18/2010 3:08 PM, Mark Miesfeld wrote: >> All, >> >> I've committed a rewritten NSIS script to trunk and 4.1.0. This >> script is what creates the Windows installation program, so >> essentially it is an updated installation program. I'm planning on >> using it for 4.1.0, so I'd like to explain the changes and start to >> get feed back now. >> >> There are 2 major changes. (Well really 3 major changes. The whole >> script has been rewritten so that it is much more readable and >> understandable. At least it is to me. But, users won't see >> that.) >> >> Major changes >> === >> >> 1.) There is a new 'type' of install, which I'm calling an 'upgrade' >> type of install. The upgrade installation is only active if there is >> a previous version of ooRexx installed. >> >> An upgrade removes only the files from the previous version and >> installs the files for the current version. It does not change any of >> the existing registry or environment settings. They stay exactly the >> same. >> >> Since the uninstaller is written at the time of installation, the >> upgrade install is only available if the version of the uninstaller is >> 4.1.0 or later. What this means in practice is, the first time you >> install a 4.1.0 ooRexx, the upgrade install will not be available >> because the previous installation wrote an uninstaller that does not >> understand the upgrade type. >> >> When you do an upgrade install you can not change any of the settings >> from the previous install. I.e., if you installed in >> C:\MyCrummyDirectory\ooRexx then the upgrade also installs in that >> directory. If you installed rxapi as a service in the previous >> install, then it remains installed as a service. Etc., etc.. >> >> 2.) The installation lets the user pick their own file associations, >> or not do any file associations at all. In addition you can create >> file associations for rexxhide and rexxpaws, if you want. >> >> For each executable the user can specify the extension, the ftype, and >> the editor for the edit context menu. The user can choose to create a >> file association or to not create a file association for each >> executable. >> >> There needs to be default values for the file associations and these >> are what I picked. Speak up if you have any other ideas. >> >> Extension ftype (File type) Editor >> === >> .rex RexxScript C:\Windows\system32\NotePad.exe >> .rexg RexxHide C:\Wndows\system32\NotePad.exe >> .rexp RexxPaws C:\Wndows\system32\NotePad.exe >> >> If you can build from trunk or the 4.1.0 branch give it a try and let >> me know what you think. >> >> Minor changes >> === >> >> 1.) Rather than put up a message box about stopping rxapi, I made that >> a page. That way there is more room to explain why rxapi needs to be >> stopped. If the user elects to not stop rxapi, the installer quits. >> >> The reason for this is simple, there is no way on Windows to replace >> the old rxapi with the new rxapi if it is running. What I could do is >> use the delayed mechanism in Windows where the user has to reboot and >> the new rxapi is copied over before the system comes all the way back >> up. Since this process stops rxapi, it is no different than stopping >> rxapi during the installation, just more tedious. >> >> 2.) The message box popup with the question about uninstalling the >> previous version is turned into a page. This makes it easier to >> insist that the user uninstall the previous version and explain that >> if she chooses not to uninstall the previous version it is likely to >> cause problems and that we won't support that. It is made more >> difficult for the user to not uninstall a previous version, there is a >> second check box that has to be manually checked. >> >> 3.) During the uninstall, the user is given the option of uninstalling >> by simply deleting
Re: [Oorexx-devel] ooRexx RPM Naming
On Thu, Sep 23, 2010 at 1:53 PM, David Ashley wrote: > Although not yet commited, I am playing around with the RPM spec file for > ooRexx. I have added some new macros to the file that create additional > information in the name of the RPM. A typical RPM name produced by these > macros > looks like this: > > ooRexx-4.2.0-6212.fedora13.x86_64.rpm > > The format is: > > ooRexx--...rpm This is pretty close to what we have done for 4.0.0 and 4.0.1. I would like to: 1.) Keep the format the same for all OSes, for what goes up on SourceForge for the releases. 2.) Avoid having to build a zillion different Linux variations. What I mean by that is, I'd rather avoid putting up all these different packagaes: ooRexx-4.2.0-6212.fedora11.x86_64.rpm ooRexx-4.2.0-6212.fedora13.x86_64.rpm ooRexx-4.2.0-6212.fedora14.x86_64.rpm ooRexx-4.2.0-6212.kubuntu87.x86_64.deb ooRexx-4.2.0-6212.ubuntu87.x86_64.deb ooRexx-4.2.0-6212.kubuntu90.x86_64.deb ooRexx-4.2.0-6212.ubuntu91.x86_64.deb And have people asking us: I using Fedora 12 and there is no RPM for me. What should I do? When any one of the rpms listed above will work on Fedora 12. -- Mark Miesfeld > > I think this gives a lot more information about the RPM and its intended > target > operating system. I can potentially add additional information if you think it > is needed, but this seems pretty complete. Let me know what you think. > > David Ashley > > -- > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Enhanced Windows installation program
On Tue, Sep 21, 2010 at 9:56 AM, Brandon Cherry wrote: > Seeing how the build server is down for windows builds for the time > being, is there an alternative location for at least a 32 bit build? If David sends me the details on to access the build machine, I could drop a Windows 32-bit and 64 bit build in the current build directory, and then post which directory it was. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Enhanced Windows installation program
All, I've committed a rewritten NSIS script to trunk and 4.1.0. This script is what creates the Windows installation program, so essentially it is an updated installation program. I'm planning on using it for 4.1.0, so I'd like to explain the changes and start to get feed back now. There are 2 major changes. (Well really 3 major changes. The whole script has been rewritten so that it is much more readable and understandable. At least it is to me.But, users won't see that.) Major changes === 1.) There is a new 'type' of install, which I'm calling an 'upgrade' type of install. The upgrade installation is only active if there is a previous version of ooRexx installed. An upgrade removes only the files from the previous version and installs the files for the current version. It does not change any of the existing registry or environment settings. They stay exactly the same. Since the uninstaller is written at the time of installation, the upgrade install is only available if the version of the uninstaller is 4.1.0 or later. What this means in practice is, the first time you install a 4.1.0 ooRexx, the upgrade install will not be available because the previous installation wrote an uninstaller that does not understand the upgrade type. When you do an upgrade install you can not change any of the settings from the previous install. I.e., if you installed in C:\MyCrummyDirectory\ooRexx then the upgrade also installs in that directory. If you installed rxapi as a service in the previous install, then it remains installed as a service. Etc., etc.. 2.) The installation lets the user pick their own file associations, or not do any file associations at all. In addition you can create file associations for rexxhide and rexxpaws, if you want. For each executable the user can specify the extension, the ftype, and the editor for the edit context menu. The user can choose to create a file association or to not create a file association for each executable. There needs to be default values for the file associations and these are what I picked. Speak up if you have any other ideas. Extension ftype (File type) Editor === .rexRexxScriptC:\Windows\system32\NotePad.exe .rexg RexxHide C:\Wndows\system32\NotePad.exe .rexp RexxPaws C:\Wndows\system32\NotePad.exe If you can build from trunk or the 4.1.0 branch give it a try and let me know what you think. Minor changes === 1.) Rather than put up a message box about stopping rxapi, I made that a page. That way there is more room to explain why rxapi needs to be stopped. If the user elects to not stop rxapi, the installer quits. The reason for this is simple, there is no way on Windows to replace the old rxapi with the new rxapi if it is running. What I could do is use the delayed mechanism in Windows where the user has to reboot and the new rxapi is copied over before the system comes all the way back up. Since this process stops rxapi, it is no different than stopping rxapi during the installation, just more tedious. 2.) The message box popup with the question about uninstalling the previous version is turned into a page. This makes it easier to insist that the user uninstall the previous version and explain that if she chooses not to uninstall the previous version it is likely to cause problems and that we won't support that. It is made more difficult for the user to not uninstall a previous version, there is a second check box that has to be manually checked. 3.) During the uninstall, the user is given the option of uninstalling by simply deleting the installation directory or only deleting the files placed there by the installer using the log file. Using the log file is the default. On my 64-bit XP system, uninstalling by deleting the whole installation directory is about 10 times faster than using the install log. 4.) The installation user interface is meant to be more modern, meant to explain better to some one new to the install of ooRexx on Windows what they should do and why, and meant to allow some one used to installing a quicker uninstall / install cycle. I'm hoping to get good feedback on the user interface during the beta of 4.1.0, but again if you can build from source now and want to give feedback that'd be great. I've tested this heavily in the last two weeks, but as always some second eyes are sure to pick up things I don't see. In particular I haven't yet tested much as a regular user on Vista or Windows 7. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _
Re: [Oorexx-devel] z/Linux Access Found
On Fri, Sep 17, 2010 at 7:48 AM, Erico Mendonca wrote: > >>> On 9/17/2010 at 10:52 AM, in message <4c93728e.8040...@gmail.com>, David > Ashley > wrote: >> On both the i386 and x86_64 versions on SLES 11 the problem is with the >> version >> of gcc used (4.5?). None of the other Linux distributions are using that >> version >> of gcc yet so that is why we only see the error on it. The 3.x versions of >> gcc >> work fine against our source code. The error on the 4.x version of gcc has >> something to do with the definition of a C++ method. Unfortunately this kind >> of >> definition happens throughout our code base and will be a real pain to fix >> according to Rick. > > Are you sure? I just checked my VMs here, and SLES 11 uses 4.3.2. SLES 11sp1 > uses 4.3.4. This bug report gives details on the problem I think David is referring to: https://sourceforge.net/tracker/?func=detail&aid=2991134&group_id=119701&atid=684730 4.0.1 rev. 5804, 5766 don't build with gcc 4.5-5.2 It is gcc 4.5-5.2 that is giving us problems. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
On Fri, Sep 17, 2010 at 6:41 AM, David Ashley wrote: > Sorry, AC_PROG_YACC should not have been removed from the autoconf.ac file. > But > the Makefile.am is still messed up. It needs some cleanup to adjust for the > source files we just removed. I will work on that today. David, do you intend to include hostemu, cvsStream, mime.cls, smtp.cls, and streamsocket.cls in 4.1.0? I think you should, but I wasn't sure if you just hadn't gotten around to adding the files to 4.1.0, or if you didn't intend them to be in 4.1.0. Don't struggle with the Windows build if you do add them, I'll fix it up. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] RPM Spec File Changes
David, I'm not to up on what is standard and not standard in Linux, so I think whatever you want to do is fine. The one thing I do know is, you can't rely on the user. > Depend on the user to make the install prefix choice correctly? Since I install and uninstall different Linxu OSes, a lot, I've installed rpm packages hundresds, probably thousands of time. I've never once used: rpm --prefix= -- Mark Miesfeld On Thu, Sep 16, 2010 at 8:59 AM, David Ashley wrote: > All - > > I have been looking at making some changes to the RPM spec file and I am now > having second/third thought about one issue in the current spec file. > > Currently, we build the RPM so that ooRexx is installed into /opt/ooRexx > unless > the user adds a prefix=xxx clause on the rpm command line i.e. rpm > --prefix=/usr > -ivh ooRexx-4.xxx.rpm. This is so that we meet the Linux Standard Base > specification that says that all packages that are not distributed with the > Linux distribution should be installed in /opt. Essentially we are forcing > that > to be the case by default. > > I am now having second/third thoughts on that decision. The normal prefix is > /usr for an RPM so that the files are installed to meet the standard for Linux > distributions. So unless you override with the --prefix option on the rpm > command line that is where most RPMs are installed. > > The reason I am having second thoughts is that because of the way we do it now > it makes the spec file more complex than it needs to be if we used the default > prefix. And if we used the default mechanisms in the spec file there are a lot > more spec file macros that would just work without any fuss (we have to doa > lot > of work to ensure the macros will work as designed currently). > > So the bottom line is this. Whiich do we think is more necessary: > Ensure that we meet the Linux Standards Base by default? > Depend on the user to make the install prefix choice correctly? > > Another item to consider is that the Fedora distribution essentually throws > away > our spec file and creates a far more standard file. If we fell into line with > the spec standard then they might be more inclined to use our spec file as-is. > > Please let me know what you think. > > -- > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
Rainer, I don't think you have a clean 4.1.0 source tree, or your compile is somehow picking up stuff from another source tree. > +AC_PROG_YACC There is no AC_PROG_YACC line in configure.ac in the 4.1.0 branch. You can see that using svn browse on SourceForge. But, Makefile.am is not correct. I think it got messed up during this commit: 6150: Merge rxunixsys into the trunk and branch. This builds cleanly on Fedora 13. - libhostemu.so > -# > -# Sources for libhostemu.so > -# > -libhostemu_la_SOURCES = $(extensions_hostemu_unix_dir)/hostemu.cpp \ > -$(build_extensions_hostemu_dir)/hostemu.h \ > -$(build_extensions_hostemu_dir)/cmdparse.ypp > -# > -# Preprocessor flags for libhostemu.so > -# > The hostemu are not in the 4.1.0 branch at all. > cp ./extensions/rxsock/streamsocket.cls ./ > cp: ./extensions/rxsock/streamsocket.cls: A file or directory in the Those class files are not in 4.1.0. Same with cvsStream, that extension is not in 4.1.0. Maybe David didn't finish merging everything he meant to. -- Mark Miesfeld On Thu, Sep 16, 2010 at 1:52 AM, Rainer Tammer wrote: > Hello, > I just tried to compiler the 4.1 branch on AIX, but there are some > problems with the code: > > 1. YACC > > Index: configure.ac > === > --- configure.ac (revision 6196) > +++ configure.ac (working copy) > @@ -59,7 +59,7 @@ > AC_PROG_INSTALL > AC_PROG_MAKE_SET > AC_PROG_RANLIB > - > +AC_PROG_YACC > AC_LIBTOOL_DLOPEN > AC_PROG_LIBTOOL > > 2. Source files > > Some source files are no longer there ans some are renamed: > > Index: Makefile.am > === > --- Makefile.am (revision 6196) > +++ Makefile.am (working copy) > @@ -87,7 +87,6 @@ > build_extensions_rxmath_dir = $(build_extensions_dir)/rxmath > build_extensions_rxregexp_dir = $(build_extensions_dir)/rxregexp > build_extensions_rxsock_dir = $(build_extensions_dir)/rxsock > -build_extensions_hostemu_dir = $(build_extensions_dir)/hostemu > build_utilities_dir = $(top_srcdir)/utilities > build_utilities_rexximage_dir = $(build_utilities_dir)/rexximage > build_api_dir = $(top_srcdir)/api > @@ -102,7 +101,6 @@ > interpreter_unix_dir = $(build_interpreter_dir)/platform/unix > extensions_unix_dir = $(build_extensions_dir)/platform/unix > extensions_rexutils_unix_dir = > $(build_extensions_rexutils_dir)/platform/unix > -extensions_hostemu_unix_dir = $(build_extensions_hostemu_dir)/platform/unix > utilities_rexx_unix_dir = $(build_utilities_dir)/rexx/platform/unix > utilities_rexxc_unix_dir = $(build_utilities_dir)/rexxc/platform/unix > utilities_rxqueue_unix_dir = $(build_utilities_dir)/rxqueue/platform/unix > @@ -202,8 +200,7 @@ > $(build_classes_dir)/SupplierClass.hpp \ > $(build_classes_dir)/TableClass.hpp \ > $(build_classes_dir)/WeakReferenceClass.hpp \ > - $(build_classes_dir)/StackFrameClass.hpp \ > - $(build_classes_dir)/ExceptionClass.hpp > + $(build_classes_dir)/StackClass.hpp > classesSupportHeaders = $(build_classes_support_dir)/ProgramMetaData.hpp \ > $(build_classes_support_dir)/RexxCollection.hpp \ > > $(build_classes_support_dir)/RexxCompoundElement.hpp \ > @@ -214,7 +211,6 @@ > $(build_classes_support_dir)/RexxListTable.hpp \ > $(build_classes_support_dir)/StringUtil.hpp > concurrencyHeaders = $(build_concurrency_dir)/ActivationApiContexts.hpp \ > - $(build_concurrency_dir)/ActivationFrame.hpp \ > $(build_concurrency_dir)/ActivityDispatcher.hpp \ > $(build_concurrency_dir)/ActivityManager.hpp \ > $(build_concurrency_dir)/CallbackDispatcher.hpp \ > @@ -357,7 +353,6 @@ > $(build_extensions_rxregexp_dir)/dblqueue.hpp \ > $(build_extensions_rxregexp_dir)/regexp.hpp > rxsockHeaders = $(build_extensions_rxsock_dir)/rxsock.h > -hostemuHeaders = $(build_extensions_hostemu_dir)/hostemu.h > # Platform specific files > windowsMiscFiles = > unixMiscFiles = $(interpreter_unix_dir)/*.cat \ > @@ -376,11 +371,8 @@ > $(top_srcdir)/unix-like-build.txt \ > $(top_srcdir)/windows-build.txt \ > $(top_srcdir)/oorexx.ver \ > - $(build_extensions_csvstream_dir)/csvStream.cls \ > $(build_extensions_rxftp_dir)/rxftp.cls \ > - $(build_extensions_csvs
[Oorexx-devel] 4.1.0 stuff
Just wanted to note this before I forgot. David had said: "I want to include my Unix functions and some other smaller items." Which I'm all for. I just noticed that hostemu is not in the 4.1.0 branch, only in trunk. I think if you include the Unix functions it would be good to include hostemu also. We know at least one person is using it because he opened a bug.And, he had to go to the trouble of compiling from trunk himself. Docs == The ooDialog docs in trunk can't go into 4.1.0. Originally, I thought just branch the 4.0.1 docs. But, maybe it is less work to branch the docs from trunk, and I could just replace the ooDialog files in the branch with the ones from 4.0.1. Whatever any one else thinks, I'm fine with. -- Mark Miesfeld -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] My bug merge strategy for 4.1.0
All, Just to spell out the bug status and the strategy I am taking. * I went though all the pending bugs and closed all of them that were included in the 4.0.1 release. * I then looked at the pending bugs left and put all the ones I knew for sure I wanted merged to 4.1.0 in the v4.0.2 group. * As I merge the pending bugs in the v4.0.2 group, I changed the group to 'Next Release.' I did that becasue there are a handful of bugs that are pending and already in group v4.1.0, that I'm not sure if Rick or David want to merge. Currently there are only two bugs that are both 'pending' and in the 'Next Release' group. Those bugs have been merged to the 4.1.0 branch. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx:[6153] main/branches/4.1.0/trunk
On Wed, Sep 8, 2010 at 12:27 PM, Rick McGuire wrote: > I'd like it changed so we don't get confused :-) Yeah, that's why I wanted to change it, I get easily confused. Right now when I do: C:\work\>rexx -v Open Object Rexx Version 4.1.0 - Internal Test Version I can't remember if it is the branch version I built this moring, or the trunk version, I also built this morning. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx:[6153] main/branches/4.1.0/trunk
Rick and David,
Thanks for getting this started.
Can we also update the version numbers in trunk to be some number
higher than 4.1.0?
--
Mark Miesfeld
-- Forwarded message --
From:
Date: Wed, Sep 8, 2010 at 11:59 AM
Subject: [Oorexx-svn] SF.net SVN: oorexx:[6153] main/branches/4.1.0/trunk
To: oorexx-...@lists.sourceforge.net
Revision: 6153
http://oorexx.svn.sourceforge.net/oorexx/?rev=6153&view=rev
Author: wdashley
Date: 2010-09-08 18:59:35 + (Wed, 08 Sep 2010)
Log Message:
---
Update the version numbers in the branch.
Modified Paths:
--
main/branches/4.1.0/trunk/CHANGES
main/branches/4.1.0/trunk/INSTALL
main/branches/4.1.0/trunk/configure.ac
main/branches/4.1.0/trunk/extensions/rxftp/rxftp.cls
main/branches/4.1.0/trunk/oorexx.ver
main/branches/4.1.0/trunk/platform/unix/oorexx-config.1
main/branches/4.1.0/trunk/platform/unix/oorexx.spec.in
main/branches/4.1.0/trunk/platform/unix/rexx.1
main/branches/4.1.0/trunk/platform/unix/rexxc.1
main/branches/4.1.0/trunk/platform/unix/rxqueue.1
main/branches/4.1.0/trunk/platform/unix/rxsubcom.1
main/branches/4.1.0/trunk/readme.version
main/branches/4.1.0/trunk/unix-like-build.txt
main/branches/4.1.0/trunk/windows-build.txt
Modified: main/branches/4.1.0/trunk/CHANGES
===
--- main/branches/4.1.0/trunk/CHANGES 2010-09-08 07:20:15 UTC (rev 6152)
+++ main/branches/4.1.0/trunk/CHANGES 2010-09-08 18:59:35 UTC (rev 6153)
@@ -1,131 +1,15 @@
- Fixes in Open Object Rexx 4.0.1
+ Fixes in Open Object Rexx 4.1.0
-The following is the list of bug fixes added to ooRexx since the 4.0.0 release.
+The following is the list of bug fixes added to ooRexx since the 4.0.1 release.
All Bugs
=
- * 2958746 - addListEntry() won't accept 'DATA' for an entry
-
- * 2958172 - RPM Does Not Use lib64 on a 64 bit Install
-
- * 2958165 - Update Dates and Version numbers
-
- * 2956787 - User string methods can cause problems if returning a number
-
- * 2949539 - DIRECTORY function returns not null
-
- * 2949175 - USE not mandating comma to delimit variables to assign to
-
- * 2935183 - REX0372E: Error 40.1: External routine "SYSSTEMINSERT" fail
-
- * 2934013 - Linux : rxqueue("create") returns an invalid queuename
-
- * 2933583 - routine and method reset address to system instead of defaul
-
- * 2926003 - Typo in socket.cls
-
- * 2898248 - rxapi : assert error with terminatedThreads
-
- * 2897421 - No Large File Support on 32 bit Linux
-
- * 2894336 - possible bug in rxfuncdrop()
-
- * 2893307 - LISTCHOICE list truncated
-
- * 2892639 - Bug in Time BIF
-
- * 2891974 - rxapid init script is missing LSB tags
-
- * 2883908 - disablemenuitem doesn't
-
- * 2883064 - Deviant behaviour changestr-function regarding "00"X, ooRexx
-
- * 2878683 - SysFromUnicode does not work well again in the release 4.0.0
-
- * 2877234 - RxWinExec fails on long commands
-
- * 2876047 - MS Access sample
-
- * 2875360 - 4.0 Linux install missing symlinks
-
- * 2873359 - .DateTime~fromISOUTCDate fails
-
- * 2871956 - Crash when GC happens during tracing
-
- * 2870816 - Memory leaks in ooRexx4.0 due to retainMessageData flag
-
- * 2869039 - ooDialog may fail under certain versions of XP
-
- * 2866554 - Multithreading problems, 3 ("run_90_testgroup.cmd")
-
- * 2865707 - Multithreading problems, 2
-
- * 2864958 - ::Routines cannot be called in mixed/lower case
-
- * 2863643 - Multithreading problems with ooRexx
-
- * 2862333 - Incorrect comment box in RXMATH.CPP
-
- * 2859404 - sample.rex Improvements
-
- * 2857264 - ooRexx may crash on exit when RegularExpression class is use
-
- * 2853119 - Error in oostdfct
-
- * 2851871 - oodtree pseudo-parent?
-
- * 2850208 - Quoted command name parsing error
-
- * 2848529 - Bug in CheckList class (ooDialog)
-
- * 2848293 - Incorrect file overlay
-
- * 2846895 - oograph improvement
-
- * 2846075 - Syntax error crashes Rexx
-
- * 2846065 - Calculator
-
- * 2843451 - Incorrect indention during trace
-
- * 2842161 - OOdialog pixel calculation wrong
-
- * 2841530 - bootstrap problems on Mac OS X Leopard
-
- * 2841071 - Trace string empty for Address w/expr
-
- * 2840637 - format(small,,2) cause error 93.941
-
- * 2840151 - SysAddRexxMacro Segmentation Fault
-
- * 2838700 - novalue(?) in asynch(?) uninit method(?) aborts Rexx.exe
-
- * 2303747 - CPU LOAD 100%
-
- * 1842856 - CPU 100% when ooDialog program started through explorer
-
- * 1346379 - RexxHide pegs the CPU
-
- * 1118328 - sysfiletree problem
-
Documentation
=
- * 2977049 - circularqueue new class method requires size
- * 2930620 - Progress bar method setpos not working
-
- * 2859410 - Play Routine description
-
- * 2856496 - 5.2.4.2 new
-
- * 2853785 - Ellipses
-
- * 2849618 - 5.2.4.13. linein
Re: [Oorexx-devel] oodialog : question about initPropSheetHeader and caption
On Mon, Sep 6, 2010 at 2:49 PM, Jean-Louis Faucher wrote: > I need your help to understand initPropSheetHeader... Jean-Louis, I should probably go review the code, but off of the top of my head: > The PROPSHEETHEADER structure contains LPCTSTR strings, so when built in > byte char mode, the strings are made of byte char. > But I see that you do a conversion ansi --> unicode and store the result in > pcpsd->caption and psh->pszCaption, which are both byte char strings. Well, really both of those are just pointers. The unicode strings are not converted back to multi-byte just by setting the pointer. > I assume that Window will convert the pszCaption to wide char (again) when > calling Who knows what Windows does under the covers. If we had the source code like we do in Linux, then we could say for sure what Windows does. > INT_PTR ret = PropertySheet((PROPSHEETHEADER *)wParam) > since the "A" function is called. > > Do I miss something here ? It is a work around for observed behavior. If I don't do the conversion, then on Vista and Windows 7 the caption comes out as garbage. Ah, now I went back and looked at the code. The conversion is only done if the PropertySheetDialog is a wzard dialog, and only if it is the new Aero wizard. There are a number of places in using dialogs where the strings have to be unicode, even if the whole application is compiled using ansi strings. This appears to be one of them, although I could not find it documented. The Aero wizard is only available on Vista or later. There could be some other problems with the new code I've added on Vista or later, because I have not done a lot of testing on Vista. If there is, it should only be with methods or other things (like the Aero wizard) that are only available on Vista or later. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Missing commit e-mails
On Sat, Sep 4, 2010 at 9:03 AM, CVBruce wrote: > As someone requested I did go in and subscribe to the svn list. After > I subscribed, I still got a message saying my post had been rejected. Yeah, there is a special set up for that list I think. Anyone that subscribes can not post to the list. You have to be explicity added, I think by David. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Rexx On A Stick (was ooRexx as portable App)
On Sat, Sep 4, 2010 at 9:20 AM, Gil Barmwater wrote: > See comments below (sorry for the format but I never received this; only > found it in the archives :-( ) Actually, I like this format. I was taught to never top-post and always use plain text for e-mail. > > 2.) For 3.2.0 open up a command prompt with the runas admin option, > > then work from there. I think that will work. > > Indeed, this was the answer! Funny that this works but a "real" admin > ID fails (didn't try 'run as admin' on the admin ID). >From Vista on, an admin ID does not run as an Administrator. When an admin ID logs on, their privilege level is set to a regular user. Any time something requires admin privileges, the process has to be elevated to a privilege level for an Administrator. In Vista, you almost always had to supply the password. In Windows 7 this has been eased off a bit and you just get a message box asking if you want to continue. > > 3.) If you have an admin ID, you can give yourself the DEBUG > > privilege, which should also work. Let me know if you want details on > > that, I'd have to look it up. > > As above, strange that one would need an additional privilege on an > admin ID. Again, it is because you are not really running as an admin, you are running as a regular user. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Missing commit e-mails
I'm still not seeing commits from Bruce, and as it turns out Brandon, from the svn list. Looking at the archive of the list, I don't see any archive mail for either Bruce or Brandon. Is there some way of fixing that? Brandon made a commit yesterday, that I only stumbled across by accident. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Rexx On A Stick (was ooRexx as portable App)
If I remember correctly, 3.2.0 uses shared memory for rxapi. The Vista and later security won't let a user open a shared memory handle. This is why for Vista, we recommend always installing rxapi as a service. 1.) You shouldn't have this problem if you try it with 4.0.0 and later. 2.) For 3.2.0 open up a command prompt with the runas admin option, then work from there. I think that will work. 3.) If you have an admin ID, you can give yourself the DEBUG privilege, which should also work. Let me know if you want details on that, I'd have to look it up. If course, you can not have 3.2.0 run from the memory stick if you already have another verison of ooRexx installed on the system. That will never work. -- Mark Miesfeld On Thu, Sep 2, 2010 at 10:39 AM, Gil Barmwater wrote: > Well, it wasn't so good for me :-( I copied my old (2007) ooRexx 3.2 > from my laptop to my stick, put it into my desktop - HP 64-bit, VISTA - > did the path thing and typed 'rexx rexxtry.rex'. Rexxtry starts (yeah!) > but then I get a dialog box with "Open Object Rexx API Manager > (RXAPI.EXE) could not be started or conflicts!" I am able to type rexx > statements at the rexxtry prompt and get results with another prompt but > I get more dialog boxes with a slightly different message - "Open Object > Rexx API Manager (RXAPI.EXE) could not be started. This could be due to > a version conflict!" > > I tried it with the ooRexx folder first in the path as well as at the > end and on the Admin ID as well as a user ID, all with the same result. > Any ideas? > > Walter Pachl wrote: >> Rexx on the stick >> Works for me >> CMD Window >> >>>set path=%PATH%;e: >>>rexx whatever... >> >> Didn't find where to set the user path on Vista (but never mind) >> Thanks y'all >> Walter >> >> -- >> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program >> Be part of this innovative community and reach millions of netbook users >> worldwide. Take advantage of special opportunities to increase revenue and >> speed time-to-market. Join now, and jumpstart your future. >> http://p.sf.net/sfu/intel-atom-d2d >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > -- > Gil Barmwater > > -- > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Compile Error
On Thu, Sep 2, 2010 at 8:10 AM, Rick McGuire wrote: > Hmm, for some reason I never say the response from my second patch. > This could be a nasty one to clean up, since this likely effects all > of the ooRexx classes. Each one will require the same sorts of > changes as I had in my patch. > > When researching this, I found an update to gcc that seemed to > acknowledge that the change that was causing this error to be issued > was not totally correct. I wonder if upgrading to a newer version of > gcc might make this go away. Or going back to a previous version. When I looked at the bug a couple of weeks ago, I had a hard time trying to put a specific version of gcc on the debian-based system I was on. Eventually I gave up. ;-( Maybe David with his better Linux skills can do that. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Compile Error
This looks to be exactly the bug already in tracker: 2991134 4.0.1 rev. 5804, 5766 don't build with gcc 4.5-5.2 On Thu, Sep 2, 2010 at 7:49 AM, David Ashley wrote: > I set up a new virtual machine last night (Open SUSE 11.3 i386) and tried to > build ooRexx on it. The compile generates an error that I have not seen before > and that no other Linux OS/GCC combination generates. You can see the error > here: > > http://build.oorexx.org/builds/interpreter-main/6141/opensuse113-i386/opensuse113-i386.buildrpt.txt > > I have not opened a defect on this but I will if necessary. > > David Ashley > > -- > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
On Wed, Sep 1, 2010 at 2:44 PM, Rick McGuire wrote: > I'm even thinking we might want to include the new File class, if we > can get some more tests written and the docs completed in time. This sounds good to me also. The File class is a great enhancement, there were also a couple (or one) new method you added to the DateTime class. If we included those and a couple of small enhancements from David, I think it would make a good release. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
On Wed, Sep 1, 2010 at 12:29 PM, Rick McGuire wrote: > That would work too, although I think if there are new APIs included, > then the version number should be 4.1.0, not 4.0.2. Oh, yeah. I'm not set on a version number. 4.1.0 would be fine. -- Mark Miesfeld > Rick > > On Wed, Sep 1, 2010 at 3:22 PM, Mark Miesfeld wrote: >> On Wed, Sep 1, 2010 at 11:32 AM, Rick McGuire wrote: >> >>> I wonder if we could include your new ooDialog work in the new release >>> and make it the 4.1.0 version? There are a couple of new APIs that we >>> added to support that, but I suspect it would not be difficult to >>> back-port those changes to a 4.0.1 base. It would be nice to get all >>> of that work out if you think it's ready for primetime. >> >> The problem is, I'm not sure that it is ready for prime time. In >> particular, the new documentation that I started, will take me some >> time to finish. And I'm worried about backwards compatiblity. My >> tests look good, but I constantly find things that other people's >> programs do that I never imagined people would do. For instance, >> invoking methods on a subclass object in init() before the superclass >> is initialized. >> >> What I would really like to do, , is back-port the couple of new >> APIs to a 4.0.1 base, release it as 4.0.2, and add a separate beta >> ooDialog that could be downloaded from SourceForge. >> >> The beta ooDialog could replace the 4.0.2 release ooDialog by swapping >> the oodialog.dll and ood*cls files. (I was thinking of writing a >> simple installer that would do the swapping for the user and allow >> swapping back.) >> >> Your objection to back-porting those couple of new APIs to 4.0.1 was >> that they weren't documented. So, I was going to try and overcome >> that objection by doing the documentation myself. >> >> My motivation for this was the, perhaps forlorn, hope that enough >> users would work with the beta ooDialog to give feedback on the new >> classes and new methods before they were set in stone. And find >> backwards compatibility issues, that could maybe be worked out. >> >> -- >> Mark Miesfeld >> >> -- >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > -- > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
On Wed, Sep 1, 2010 at 11:32 AM, Rick McGuire wrote: > I wonder if we could include your new ooDialog work in the new release > and make it the 4.1.0 version? There are a couple of new APIs that we > added to support that, but I suspect it would not be difficult to > back-port those changes to a 4.0.1 base. It would be nice to get all > of that work out if you think it's ready for primetime. The problem is, I'm not sure that it is ready for prime time. In particular, the new documentation that I started, will take me some time to finish. And I'm worried about backwards compatiblity. My tests look good, but I constantly find things that other people's programs do that I never imagined people would do. For instance, invoking methods on a subclass object in init() before the superclass is initialized. What I would really like to do, , is back-port the couple of new APIs to a 4.0.1 base, release it as 4.0.2, and add a separate beta ooDialog that could be downloaded from SourceForge. The beta ooDialog could replace the 4.0.2 release ooDialog by swapping the oodialog.dll and ood*cls files. (I was thinking of writing a simple installer that would do the swapping for the user and allow swapping back.) Your objection to back-porting those couple of new APIs to 4.0.1 was that they weren't documented. So, I was going to try and overcome that objection by doing the documentation myself. My motivation for this was the, perhaps forlorn, hope that enough users would work with the beta ooDialog to give feedback on the new classes and new methods before they were set in stone. And find backwards compatibility issues, that could maybe be worked out. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Timeline for V4.1
On Wed, Sep 1, 2010 at 6:38 AM, Rick McGuire wrote: > There's no target date currently. The work I was doing to implement a > try/catch/throw exception model still requires a bit more work, and > lately, I've had little time to work on it. I'd also like the next > release to include the new regex classes I've been working on, but > that also requires a bit more work. I would like to do a 4.0.2, a bug fix release. Been meaning to bring this up for a week. I would like to target it for release around November 2 which would put it at 6 months from 4.0.1. We could do it the same as we did for 4.0.1, just branch from 4.0.1 and apply the bug fix patches we think appropriate for the release. The read-only file bug that Mike found was a bit of a shocker. In addition there are some other bugs I fixed that had really just been sitting there for too long. I think it must be discouraging to users to report a legitimate bug and not see it get fixed. Doing periodic bug fix releases serves the users better, I believe. We really have no idea when the next major release will be ready. So, I think periodic bug fix releases are needed. In addition, I can probably do most of the work myself, so it is not much of a burden for the other developers if they are too busy. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] #ifdef __APPLE__ & __MACH
This is the only other place in the code that is similar, in SysFile.cpp: #if defined(__APPLE__) && defined(__MACH__) so you should have copied that. -- Mark Miesfeld On Wed, Sep 1, 2010 at 6:06 AM, CVBruce wrote: > I'll go check. To tell you the truth, I just copied it from someplace > else in the code. Perhaps is should be && instead of &? > > Thanks, > > Bruce > On Aug 31, 2010, at 11:16 PM, Jean-Louis Faucher wrote: > >> Hi Bruce >> >> In unix/rexxutil.cpp : >> #ifdef __APPLE__ & __MACH >> generates this warning under Linux >> ./extensions/rexxutil/platform/unix/rexxutil.cpp:170:18: warning: >> extra tokens at end of #ifdef directive >> >> Don't know if this expression is allowed by your compiler, so I >> forward for verification :-) >> >> Jean-Louis >> -- >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > -- > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Tue, Aug 31, 2010 at 7:41 AM, David Ashley wrote: > As far as I can tell neither of those 2 files is created. The makeorx.bat > file > crashes right away before even compiling the first file. David, One thing you could try, although at this point I don't have much hope it will work, is this: In your script where you set SRC_DRV and SRC_DIR, set NO_BUILD_LOG to 1 set NO_BUILD_LOG=1 and change your command: 'makeorx.bat BOTH PACKAGE' to: 'makeorx.bat BOTH PACKAGE >> myBuildReport.txt' That will put the the build output for both the release and debug builds in one file. You could name it anything and put it where ever you want. It should work fine. (Of course what you are currently doing *should* also work fine.) -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Tue, Aug 31, 2010 at 7:41 AM, David Ashley wrote: > As far as I can tell neither of those 2 files is created. The makeorx.bat > file > crashes right away before even compiling the first file. Hi David, I think what the problem might be is some statement like this: if %USELOGFILE% EQU 1 (echo readme.pdf is missing >>%OR_ERRLOG%) else (echo readme.pdf is missing) in makeorx.bat. It could be happening because some error path is taken that I haven't tested. But, I've looked at all the places where the redirection symbol is used, and they all look correct to me. And, I've tried introducing different errors to see if I could get the message you've gotten. No luck. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Mon, Aug 30, 2010 at 8:10 AM, Mark Miesfeld wrote: > On Mon, Aug 30, 2010 at 7:33 AM, David Ashley > wrote: >> This is very strange. I can perform builds by hand, just not with my build >> script. It always chokes on the invocation of the makeorx.bat command. And >> the >> characters '>>' do not appear anywhere in my build script. David, I took a quick look and couldn't see the problem. I wrapped makeorx.bat in a Rexx program and it still ran okay. When makeorx.bat is invoked do you get anything written to either Win32Rel.log or Win32Dbg.log at all? If some lines are written it might narrow things down. -- Mark Miesfeld -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Mon, Aug 30, 2010 at 7:33 AM, David Ashley wrote: > This is very strange. I can perform builds by hand, just not with my build > script. It always chokes on the invocation of the makeorx.bat command. And the > characters '>>' do not appear anywhere in my build script. Okay, then it is a problem in makeorx.bat, or, more accurately, a problem introduced by running makeorx.bat from the Rexx program. makeorx.bat does use >> to redirect the output to the log file. > You can look at the script. It is on the build server at > \builds\scripts\orxbuildwin.rex. I'll take a look at it. If you are redireting output from orxbuildwin.rex, it might be that the second redirection in makeorx.bat is not ... something. Not valid, no longer has a stdout handle ... -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Sun, Aug 29, 2010 at 3:44 PM, David Ashley wrote: > It seems to be working now, at least some of the time. But I have a new > problem. > > The Windows build script is now aborting. The error message looks like this: > > A C:\buildtemp\utilities\rxqueue\platform\windows > A C:\buildtemp\utilities\rxqueue\platform\windows\rxqueue.cpp > A C:\buildtemp\utilities\rxqueue\platform\windows\rxqueue.mak > A C:\buildtemp\bootstrap > U C:\buildtemp > Checked out revision 6136. > Checking for > p:\www\build\docroot\builds\interpreter-main\6136\winxpsp3-i386\ooRexx*.exe > File Not Found > 20100829 17:36:48 Building SVN revision 6136. > >> was unexpected at this time. David, The "was unexpected at this time" message most likely comes from the command interpreter, cmd.exe. I see it all the time when I'm trying to write a batch file and have some error in the syntax. I think you are using Rexx scripts for most everything, so I suspect you have an error in something you are passing out to the OS. I would check where you are using the redirection >> and see if you have a syntax error in the command. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Experimental : Start working on support for encoded strings (m17n).
On Mon, Aug 30, 2010 at 6:02 AM, Rick McGuire wrote: > I've looked at the past at adding better character set support, and my > personal preference would be to make the interpreter do everything > internally using unicode so that it is not necessary to convert > strings to a common format to perform language operations. ooRexx > performance is very much tied to string object performance, so changes > here should be handled with care. I'd like to see Unicode support added, and having the interpreter do everything internally sounds best. Unfortunately, I don't think I have the skill set to design a good implementation. I was hoping Rick would add to the discussion, because I know he could design a clean implementation. Both the transition to 64-bit and the C++ native APIs have demonstrated that. So, I'd like to see Unicode support added, it would be great if it was something that could interest Rick. I'd like to see it done with his guidance. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Sat, Aug 28, 2010 at 6:01 PM, David Ashley wrote: > I am still Having problems checking out the ooRexx source code from the SVN > repository even after installing a new version of Slik Subversion. Does anyone > have any suggestions? Can you show us the last few lines of the check out so we can see where it fails and the exact message? I haven't had any problems and I check out on a number of different machines. C:\work.ooRexx\wc\main>cd \ C:\>svn checkout https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk main.temp Amain.temp\oorexx.ver Amain.temp\unix-like-build.txt Amain.temp\rexxapi Amain.temp\rexxapi\server Amain.temp\rexxapi\server\QueueManager.cpp Amain.temp\rexxapi\server\APIServer.cpp ... Amain.temp\utilities\rxqueue\platform\windows\rxqueue.cpp Amain.temp\utilities\rxqueue\platform\windows\rxqueue.mak Amain.temp\bootstrap U main.temp Checked out revision 6136. C:\> C:\>svn --version svn, version 1.6.5 (SlikSvn:tag/1@38906) X64 compiled Aug 21 2009, 23:02:21 Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ This product includes software developed by CollabNet (http://www.Collab.Net/). The following repository access (RA) modules are available: * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. - handles 'http' scheme - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - handles 'http' scheme - handles 'https' scheme C:\> -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] build.oorexx.org reachable ?
On Wed, Aug 25, 2010 at 8:53 AM, Rony G. Flatscher wrote: > Just wondering, whether the build-machine is already up and reachable or > not yet ready (getting timeouts trying to use it from over here). It's not up. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx as portable App
On Tue, Aug 24, 2010 at 7:20 PM, Chip Davis wrote: > As an alternative, would it be possible to simply copy all of the > files in the installed ooRexx directory structure to the USB memory > stick, plug it into a non-ooRexx computer, update the PATH to include > the memory stick, and run from the stick? Chip, Yes that should work just the same. If you used it on the same computer, where the USB stick always came up with the same drive letter you could write a simple batch file to set the path. Or have the drive letter be input to the batch file. Or copy a simple Rexx program to the root ooRexx directory and be a little creative with the setup. You could have the Rexx program figure out what the path should be, then write it out to a batch file and invoke it. You just need to cd into the ooRexx root directory to invoke the Rexx program from the command line. Using a USB stick was really what I had in mind, it was just simpler to do a quick demo with a zip file. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx as portable App
On Tue, Aug 24, 2010 at 11:31 AM, CVBruce wrote: > What about the rxapi service? Won't that require somesort of admin > auth? rxapi does not have to be installed as a service. When the interpreter starts up, if rxapi is not running, it is started. Once started it, it does not terminate until it is killed. On Windows, (admittedly I'm more familiar with this on Windows,) if rxapi is installed as a service, it gets started when the system boots up and is available to all users. If the service process is halted for some reason, the next time the interpreter starts, it attempts to restart the service. If that fails, it starts rxapi as a regular process. If rxapi is not installed as a service, the first time the interpreter starts, it starts rxapi as a regular process. This implies that the process is user specific. It ends when the user logs out, (or the user manually halts it by some means, task manager, pskill, killer, etc..) On Windows, rxapi is best installed as a service. For Windows Vista (and I assume for Windows 7) there are a number of problems caused by UAC that can be avoided if rxapi is started as a service instead of as a regular process. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx as portable App
On Tue, Aug 24, 2010 at 11:07 AM, Mark Miesfeld wrote: > On Tue, Aug 24, 2010 at 10:29 AM, Walter Pachl wrote: > >> Sitting at my office computer w/o Admin rights I dearly miss ooRexx. >> Is it possible to use it as portable app without installing it? >> Would be nice! > > Walter, it is certainly possible on Windows. Here is a quick transcript of the procedure: On my home computer where I already have ooRexx installed: C:\home\Interpreters\Rexx>zip -X9r my_ooRexx ooRexx adding: ooRexx/ (stored 0%) adding: ooRexx/api/ (stored 0%) adding: ooRexx/api/oorexxapi.h (deflated 92%) ... Move the zip file to my office computer where there is no ooRexx installed: C:\office.work>rexx -v 'rexx' is not recognized as an internal or external command, operable program or batch file. C:\office.work>copy \file.transfer\my_ooRexx.zip . 1 file(s) copied. C:\office.work>unzip my_ooRexx.zip Archive: my_ooRexx.zip creating: ooRexx/ creating: ooRexx/api/ inflating: ooRexx/api/oorexxapi.h ... C:\office.work>dir Volume in drive C has no label. Volume Serial Number is 4C7E-4254 Directory of C:\office.work 08/24/2010 11:14 AM . 08/24/2010 11:14 AM .. 08/23/2010 08:13 AM ooRexx 08/24/2010 11:09 AM 4,784,884 my_ooRexx.zip 1 File(s) 4,784,884 bytes 3 Dir(s) 67,166,003,200 bytes free C:\office.work>set PATH=C:\office.work\ooRexx;%PATH% C:\office.work>rexx -v Open Object Rexx Version 4.1.0 - Internal Test Version Build date: Aug 23 2010 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\office.work>cd ooRexx\samples C:\office.work\ooRexx\samples>factor.rex -- Nothing happened, got a popup saying Windows can not open this file. C:\office.work\ooRexx\samples>rexx factor.rex Enter a number 12 12 factorial is 479001600 C:\office.work\ooRexx\samples> You could do more to set up things and use some, but not all, of the features added by a regular install. I just don't have the time to spell things out. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx as portable App
On Tue, Aug 24, 2010 at 10:29 AM, Walter Pachl wrote: > Sitting at my office computer w/o Admin rights I dearly miss ooRexx. > Is it possible to use it as portable app without installing it? > Would be nice! Walter, it is certainly possible on Windows. If you already have ooRexx installed on one of you own computers, simply copy the entire directory structure to a usb stick. Or zip it up. On a machine where you want to use it, plug in the usb drive, or unzip the zip file into a directory of your choice. Then you can add the top level ooRexx directory to you path, and things would work. I don't have time to spell out the exact directions, but: If you are running from a console window you could add it to the path directly using: set PATH=;%PATH% Otherwise set it in the Control Panel ->System->Advanced. Even if you don't have Admin privileges you can set your individual path, which is appended to the system path for everything you do. rxapi will start automatically when you run a Rexx program and will keep running until you log off. It will just run as a regular process rather than as a service. Which is just fine. -- Mark Miesfeld -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problems creating a deb package on a German 32-bit Ubuntu ... (Re: Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it
It looks like that machine doesn't have the debhelper package installed.
sudo apt-get install debhelper
Should do it, if not try a Google search for debhelper install
--
Mark Miesfeld
On Mon, Aug 23, 2010 at 11:31 AM, Rony G. Flatscher
wrote:
> Hi there,
>
> while creating a 32-bit ooRexx for a German 32-bit Ubuntu and doing the step
> to create a deb package ("make deb"), the process stops with the error
> (translated from German to English):
>
> fakeroot dh_clean -k
> /sr/bin/fakeroot line 176: dh_clean: command not found
>
> Any ideas what could be wrong?
>
> ---rony
>
> P.S.: For testing purposes it is still great that "sudo make install" works,
> although the installation from the package is the preferred way.
>
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Strange Windows SVN Bug
On Mon, Aug 23, 2010 at 6:59 AM, David Ashley wrote: > You may have noticed that there have been no builds of the Win XP version of > ooRexx on the build machine for two weeks. I finally got around to trying to > debug the problem. I thought it was a file access problem since I have been > moving things around for the last two weeks. Turns out, that was not the > problem. > > The problem is that when an svn checkout is performed on the Windows virtual > machine the checkout fails. It gets about 90% through the checkout and fails > with a message that a response record from the svn server is not correct. It > always fails in the same spot. David, I've seen that message a few times, it was always when I had a bad connection to the Internet. But, it never even get 0%. It would take awhile for it to come back with the message. And, it would take me a bit to figure out the problem because the message is not that intuitive as to what the real problem is. Could it be that ethernet connection is not stable in the virtual machine? -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] oorexx.nsi and ooRexxProcess.dll
All
I've committed some big changes to oorexx.nsi, which I've tested well.
But, if anyone finds a problem let me know.
As I explained in an earlier post, the script now requires the
ooRexxProcess.dll pluging. The script header explains what plugins
are required and where to get them:
; This script requires 2 plugins added to your NISI installation. They need to
; be put into ${NSISDIR}\Plugins directory:
; services.dll -> http://nsis.sourceforge.net/File:Services.zip
; ooRexxProcess.dll ->
http://sourceforge.net/projects/oorexx/files/ under oorexx-buildutils
--
Mark Miesfeld
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] V4.1
On Sat, Aug 21, 2010 at 4:23 PM, CVBruce wrote: > It looks like I should create the symlinks, since the current install > process, symlinks everything else into /usr/bin. Bruce, What I would suggest doing is looking at platform/unix/oorexx.spec.in and doing what is done in the post script. You can locate it by looking for the line starting with: %post The post script is kept up to date and the rpm install is undeniably the best tested of all the Unixes. -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problems compiling 64-bit ooRexx for 64-bit Linux (Ubuntu) and installing it
On Sat, Aug 21, 2010 at 1:04 PM, Rony G. Flatscher wrote: > in the need of a 64-bit ooRexx from trunk, I checked out ooRexx from > Sourceforge. > > Changed into "main/trunk", created a subdir "tmp", > ran from main/trunk/tmp the command "../conifugre --disable-static" followed > by "make" > then issuing a "make install" (to have it installed into /opt/ooRexx), but > receive the following output with errors at the end: *Don't* do make install. *Don't* do sudo make. If you are on a Debian based system, Ubuntu, etc., build the the deb package. If you are on some other Linux, build the rpm package. I just built on 2 different 64-bit Debian systems a couple of days ago. It worked fine. Plus Jean-Louis is is sort of right, why are you creating tmp and trying to configure from there? Here is how you should build on a 64-bit Ubuntu, assuming a fresh check out and no ooRexx yet installed: # whomami miesfeld # svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk main # cd main # ./bootstrap # ./configure --disable-static # make # make deb # cd .. # su root # dpkg -i oorexx_4.1.0-6128_amd64.deb I just did that, it worked fine on Kubuntu 10.04 64-bit. Took less than 10 minutes, including the time spent rebooting in the Kubuntu partition. If, there is already an ooRexx installed, the last two step should be these 3: # su root # dpkg -P ooRexx # dpgk -i ooRexx If you already have trunk checked out, and want to be sure you have a good build, the first step(s) should be: # cd main # make maintainer-clean # svn update # ./bootstrap # ... I just redid the build using the steps directly above, worked fine, took less than 4 minutes. -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Interesting Build Action
On Fri, Aug 20, 2010 at 8:01 AM, David Ashley wrote: > I am not really sure you can at install time. This version information is > maintained by hand. But, you can when you're building, which is what I think / thought Bruce was concerned with. In general: Any of the beta or release branches will have oorexx.ver updated for sure. (Manually by David.) Often, when we first branch from trunk, the manual update in trunk isn't done right away, but David usually does the manual update pretty soon after we branch. A couple of weeks or a month. -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Interesting Build Action
On Fri, Aug 20, 2010 at 6:52 AM, CVBruce wrote: > Ok, I didn't know that. It complicates the install - uninstall > process a bit. Where can I determine the current release version > numbers for the libraries? You could read it from oorexx.ver: # This defines the oorexx library version. For ooRexx this should always be the # same as the ORX_MAJOR number. ORX_CURRENT=$(ORX_MAJOR) # Each public release of ooRexx should increment this number by one except # when the ORX_MINOR goes back to zero. If that is the case then this entry # should also be set to zero. ORX_REVISION=2 # For ooRexx, this number should ALWAYS be zero. This will force the linker to # utilize all previous releases for linking. ORX_AGE=0 -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] New building / packaging details on Windows
All, Synopsis: === This is only of concern if you plan on running the packaging step of the Windows build: Download: ooRexx-build-utils-1.2.0-windows.zip from SourceForge. Its under oorexx-buildutils. Unpack it. Put ooRexxProcess.dll in the Plugins directory of your NSIS installation Replace your existing killer.exe with the one from ooRexx-build-utils-1.2.0-windows.zip Details: == On Windows we use NSIS to create the installation package. NSIS supports 'plugins' and oorexx.nsi uses a number of plugins for various tasks. None of the existing plugins I've looked at do a good job of determining if rxapi is running and / or killing it. So, I wrote our own plugin. ooRexxProcess.dll Source code is in: https://oorexx.svn.sourceforge.net/svnroot/oorexx/build-utilities/trunk I put a new release of oorexx-buildutils up on SourceForge that has the prebuilt ooRexxProcess.dll in it. ooRexx-build-utils-1.2.0-windows.zip ooRexx-build-utils-1.2.0-windows.exe (self-extracting zip file.) I have changes to oorexx.nsi that, once I commit, will require ooRexxProcess.dll to package ooRexx. It is simply a matter of putting ooRexxProcess.dll in the Plugins directory of your NSIS installation: Directory of C:\tools\NSIS\Plugins 08/18/2010 02:29 PM 4,096 ooRexxProcess.dll killer.exe === When I rebuilt killer.exe, it started working again on my system. Without any code changes, I just rebuilt it. On the system where it stopped working for me, I had moved up to Visual Studio 2008. It's probably some stupid library thing. It may be that it needs to be statically linked to the libraries ... not really sure. David - If for some reason either killer or the ooRexxProcess plugin do not work on the build machine, I think just building from source will fix it for you. svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/build-utilities/trunk build-utils cd build-utils edit Nmake.inc - Put in the directory path to your NSIS installation NSIS_API_DIR = C:\Tools\NSIS nMake /F Makefile.win <- builds killer nMake /F Makefile.win ooRexxProcess_Plugin <- builds ooRexxProcess.dll ooRexxProcess.dll is not in the 'all' build because it requires NSIS to be installed. -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Request for help on (Ubuntu) Linux (32- and 64-bit)
Hi Rony, I know how frustrating these types of things can be. (But, it is very satisfying if you solve them.) I might take a look at this, this weekend, if I have time. Unfortunately, the set up required is a deterrring factor. Until then: I would try with a build from trunk. David has the build machine working well and you could easily pick up a pre-built deb package with all the latest fixes. I would try putting all the required files in the same diretory you are executing your script from, just to see what happens. Of course, you may have already tried these things. -- Mark Miesfeld On Mon, Aug 16, 2010 at 9:31 AM, Rony G. Flatscher wrote: > Hi there, > > after experimenting the whole day, I have not yet come to a conclusion about > the cause of a runtime problem I have been experiencing with ooRexx 4.0.1 on > 32- and 64-bit Ubuntu: > > when requiring "UNO.CLS" which requires other Rexx packages itself, an error > along the following lines occurs: > > r...@ronylinux:/opt/BSF4ooRexx/install$ rexx /usr/bin/UNO.CLS > 318 *-* ::requires UNO_XINTERFACES.RXO-- get the list of all of UNO > XInterface classes > EX0003E: Error 3 running /usr/bin/UNO.CLS line 318: Failure during > initialization > EX0200E: Error 3.1: Failure during initialization: File > "/usr/bin/UNO_XINTERFACES.RXO" is unreadable > r...@ronylinux:/opt/BSF4ooRexx/install$ > > > it seems to be positional, i.e. if changing the requires statement to > "::requires "rgf_utli2.rex" then the same error occurs but now relating to > "rgf_util2.rex" ! > this error occurs whenever Rexx programs requiring UNO.CLS are invoked from > the command line using the "rexx" executable. Running programs requiring > UNO.CLS via the OpenOffice macro menu works! > all rights on the scripts are set to 755 (rwxr-xr-x), they reside in > "/usr/bin" (as a matter of fact, it does not matter where they reside and > whether they are owned by root or by the user who executes the scripts). > > I have not been able to create a standalone test-set which would exhibit > this behaviour on Linux, unfortunately. :( > > Therefore a request for help/ideas to solve this puzzling problem! > > This would be needed to recreate the problem as I have been facing it: > > get Ubuntu, > uninstall the Ubuntu-OOo via synaptic manager (they tamper with the genuine > OpenOffice, unfortunately, harming the Java interface to OOo, which is > exploited by BSF4ooRexx), > get the matching genuine OOo package by pointing your browser (from within > Linux) to: <http://download.openoffice.org/index.html>, this will place the > genuine OOo installation package that matches your installation on top, > download it, unpack and install it (to install change into the DEB directory > and issue: "" > get the installation package of BSF4ooRexx from this particular location: > <http://wi.wu-wien.ac.at/rgf/rexx/bsf4oorexx/archive/2010/2010-08-16/BSF4ooRexx%5finstall%2ezip> > > unzip it, change into "bsf4oorexx/install" and run "install.sh"; this will > copy the entire package to "/opt/BSF4ooRexx" and proceed from > "/opt/BSF4ooRexx/install/" where the installation and uninstall scripts get > created > after the installation BSF4ooRexx got installed, and now you need to install > the OOo support by running "/opt/BSF4ooRexx/install/reinstall.sh" > > currently it is possible that "unopkg" is not successfully carried out, due > to a leftover lock file in "~/.openoffice/3/.lock" > locate and delete that lock-file, then run "sudo > /opt/BSF4ooRexx/install/installOOo.sh" > check by starting the OOo writer, go to "Tools -> Macros -> Run" and pick > the "HelloWorld" example from the "OpenOffice/ooRexxExamples" macro folder. > > best logoff and logon again (this makes sure that from that point on > "/etc/profile" is honored which sets up the environment for BSF4ooRexx; this > allows one to start BSF4ooRexx scripts also by double-clicking via the > desktop interface of Linux). > > Now, if you open a command line window and go into "/opt/BSF4ooRexx/install" > and run "rexx testOOo.rxo" you should get the above mentioned error! > > Hopefully, you can find a workaround or the cause of this error, which is a > showstopper right now for the Linux platform. > > TIA, > > ---rony > > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev
Re: [Oorexx-devel] A question related to 64-bit ooRexx on Linux ...
Are you sure it works on 32 bit? -- Mark Miesfeld On Sat, Aug 14, 2010 at 12:36 PM, Rony G. Flatscher wrote: > Hi there, > > while working on the 64-Bit-Ubuntu-Linux platform, I have been hit with the > following error from ooRexx: > > o...@ronylinux:/opt/BSF4ooRexx/install$ rexx /usr/bin/UNO.CLS > 318 *-* ::requires UNO_XINTERFACES.RXO-- get the list of all of UNO > XInterface classes > EX0003E: Error 3 running /usr/bin/UNO.CLS line 318: Failure during > initialization > EX0200E: Error 3.1: Failure during initialization: File > "/usr/bin/UNO_XINTERFACES.RXO" is unreadable > o...@ronylinux:/opt/BSF4ooRexx/install$ > > > The file "/usr/bin/UNO_XINTERFACES.RXO" is readable (set to 755, i.e. > "-rwxr-xr-x") and can be called successfully on its own. > > As one can see from the error message "UNO.CLS" uses a > "::REQUIRES"-directive to get access to "UNO_XINTERFACES.RXO". > > Is it possible that 64-bit ooRexx 4.0.1 would have such a problem on a > 64-bit Linux system? > > ---rony > > P.S.: The reason for this question is, that this corner of BSF4ooRexx > addresses OpenOffice.org. Usually, OOo installations from the Linux > distributions repackage OOo and many times ruin/break some of the OOo > interfaces (especially the Java part). So it may be the case that there is a > problem in that corner, except UNO_XINTERFACES.RXO does not attempt to touch > any of these APIs (it creates an ooRexx directory storing all known UNO > interfaces by name, serving like a sort of a cache). > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] WSH bugs in tracker - new proposal
Based on feedback from Rick and Rony, I propose that we (I'll actually do it) do this with the bugs * Create a new category: WSH Change the WSH bugs to: Category: WSH Resolution: Postponed Status: Pending That way the bugs are still easily retrievable, they are no longer in the open state, and the resolution indicates that they are not just discarded. I'll do that tomorrow unless there are more objections. -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] SysFileTree > 4 GB files
Rick, I remember (thought I remembered) you saying at one time that SysFileTree would not be altered to correctly report file size greater than 4 GB because of backward compatibility with the formatted output. Or something similar. But, my searching skills are either too poor, or my memory is too poor. What were you comments here, or do I really not remember correctly? -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] bug fix in sandbox
On Thu, Aug 12, 2010 at 11:59 AM, Mark Miesfeld wrote: > On Thu, Aug 12, 2010 at 11:17 AM, Jean-Louis Faucher > wrote: > >> Some weeks ago, I fixed two crashes I had in my sandbox, and maybe those >> fixes are candidate to go in trunk... >> Let me know... >> > ... > > Of course, I'll have to look it up anyway. I'm *pretty* sure I it > doesn't have the bug. buf = (char *)LocalAlloc(LPTR, ++count); The buffer is allocated zerored with a size big enough for the line + 1 In other cases, GetWindowText() is used, which does copy the terminating null. -- Mark Miesfeld -- Mark Miesfeld -- Mark Miesfeld -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] bug fix in sandbox
On Thu, Aug 12, 2010 at 11:17 AM, Jean-Louis Faucher wrote: > Some weeks ago, I fixed two crashes I had in my sandbox, and maybe those > fixes are candidate to go in trunk... > Let me know... > ... > 6027 > sandbox\jlf\trunk\extensions\platform\windows\oodialog\oodBasicControls.cpp > Fix a bug in relation with EM_GETLINE : Must add a \0 explicitely (From > MSDN, the copied line does not contain a terminating null character). > In theory, the byte char version of oodialog has the same bug, but it seems > that the copied line has always a final \0, maybe thanks to the conversion > made by the "A" API ? No, the byte char version does not have this bug. It is not because of the "A" API, it is because of some other reason that I forget right now. I think it is because the buffer is zeroed and the buffer is big enough for the copy. (I'll have to look it up, I forget right now.) Of course, I'll have to look it up anyway. I'm *pretty* sure I it doesn't have the bug. -- Mark Miesfeld > > > Jean Louis > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
