Hello, Code Styler 1.1 (beta) is available for download at: <http://euro.futurebasic.com/CodeStyler1.1.sea.hqx> This version is supposed to: - fix the mess with the file types on the very first launch; - fix the unexpected overwriting of literal strings and comments; - handle the saving of files differently. There are three operating modes: Single file mode: you will be prompted for a name and a location for the converted file. Batch mode: a whole folder will be scanned and the converted files will be stored in a new created folder. AppleEvent mode: with drag & drop, the files are handled the same way as in the previous version (my favorite and unsecured mode); - handle the conversion LEN(a$) to a$[0]; - allow extra lines between LOCAL FNs. As usual, use with caution. Now, Matt has suggested to me that I make the code open source. It looks like a good idea at first sight, well, actually I like very much the idea of a common effort to enhance and optimize the tool, but I'm a bit reluctant for the various reasons listed below: - The prog uses my Appearance override include file which is sometimes really handy but not a recommended way. I feel that my role is to promote the Appearance Runtime that will come very soon to FB. - Every now and then I use non recommended syntax too. Argh!!!! - A couple of features will be available with the Release 5 but not before. - The prog has started with a few experimental functions and has grown beyond my control in a certain way. This is indeed a poor design when it comes to serious programming. - Not a single line of code was commented (OK, this one is fixed by now). - On top of that, I've got only 18 users who paid their shareware fee of 10,000 dollars out of more than 22000 downloads during the first week. What a pity! All the above clearly show this is not an example to follow, the main problem being of course the Appearance override include file. I have not yet toyed with the Appearance Runtime therefore I don't know what it would take to streamline the code and it seems to me that this is required to make the prog open source. In a similar vein Michele, Jonathan and I also agree to give away the source of the ZSM plug-in. Remember that ZSM is strictly for adults only. OK, that's just for teasing, 'cos the plug-in started with the idea of a tool destined to replace the current script manager built in the FB^3 Editor. Currently, the project is stopped for different reasons, however Zippy Script Master is close to its beta stage, perhaps other programmers might have a mind to complete the task. ZSM is almost functional as it is, you can already store and retrieve snippets of code and even drag and drop them into your source code. Unfortunately again, that project also uses the Appearance override include file. So, I don't know what to do: make the code available right now, with the condition that the first change should be to make the prog Appearance Runtime savvy before it is uploaded to the drop box at futurebasic.org or wait until I possibly make the change myself provided I find time. That being said I'm perfectly willing to send privately the source code "as is" to whoever wants it. -- Cheers Alain ----------------------------------------------------- FB^3 in Europe: http://euro.futurebasic.com/ FB II Pouch: http://www.pixmix.com/FB/outils.html -----------------------------------------------------