I'm with Klass on this one, Rony. And you really should avoid case-sensitivity as well.
There are only three pieces of information that the extension must convey: 'Rexx', 'BSF4Rexx(Java)', and 'OpenOffice'. It's not necessary to specify that it is "Open Object" Rexx, since that's the only "Rexx" that is applicable. By the same token, "BSF4Rexx" is a tad more obscure than "Java", so "Java" would be a more valuable identifier. One suggestion would be simply '.jro', except that there is too great a possibility that it will collide with another extension in the Java namespace. In fact, the proliferation of Java application files is making it difficult to assign with confidence any extension that starts with '.j'. Besides, I feel that the beginning of the extension should indicate the source language of the file. For that reason, I would suggest that all BSF4Rexx ooRexx programs use a '.rxj*' extension. After all, the whole point is that the code is written in Rexx, not Java, for the Java environment. The 'j' identifies the file as input to the BSF4Rexx Java interface, and further suffixes would identify the application environment to which the program communicates. Thus, an ooRexx program that simply interfaces the Java virtual machine would have an extension of '.rxj'. This extension is not likely to be used by anything else. (Fortunately, NetRexx uses '.nrx'. ;-) An ooRexx program that uses the BSF4Rexx Java framework to access OpenOffice would have an extension of '.rxjo' (or '.rxjoo' if you're concerned about application namespace collisions with only one letter). One which accesses SQL would be '.rxjs', '.rxjsq', or even '.rxjsql'. The suffix characters are where you want to have the ability to disambiguate a multitude of target applications. Orthographically yours, -Chip- On 10/11/09 17:57 Klaas. said: > Op 10-oct-09 schreef Rony G. Flatscher: > >> Hi there, > >> in preparation of packaging BSF4Rexx 4.0 for the beta-test I would like >> to take advantage of those new icons that Gray Wilson has kindly created >> for BSF4Rexx and OOo (OpenOffice support via BSF4Rexx). In order to be >> able to utilize these icons, there need to be distinguished filetypes >> with which the icons can get associated. > >> For this reason I will rename all BSF4Rexx-Rexx-programs to the file >> extension ".jrexx" (Java-Rexx), which is the filetype in use on the MacOS. > >> My problem currently: what filetype should Rexx programs have that are >> written for scripting OpenOffice.org (or StarOffice for that matter)? >> One idea, as this support builds upon BSF4Rexx was ".jrexxOOo". But it >> may be the case that this name is too long, too cumbersome, too error >> prone (because of "OOo", which is the official acronym for >> "OpenOffice.org"). So I would request alternative ideas for a filetype >> that denotes Rexx programs that script OOo. Any ideas would be most welcome! > > My idea would be to avoid this .jrexxOO.. at all cost. > Is there a reason to not use the usual .rexx or maybe .jrexx? > I would say that as long as the OpenOffice macro's etc are > placed in the correct library where the system could find > them everything is fine. > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
