eFTE/2 text editor & FTE text editor

Versione: 
1.0.0 & 0.5.01
Data rilascio: 
Giovedì, 4 Dicembre, 2003

Licenza:

Interfaccia:

Editor di testi avanzato che evidenzia parole chiave dei principali linguaggi di programmazione: c/pascal/asm/perl/java/HTML e molti altri.

Questo software è distribuito come pacchetto compresso, da scaricare e installare manualmente; se ci sono prerequisiti da soddisfare, andranno anch'essi scaricati e installati manualmente.

Installazione manuale

Disponibile sia in formato ZIP che WarpIN:

  • scaricare il pacchetto ZIP in una cartella temporanea e scompattarlo nella cartella di destinazione;
  • il pacchetto WarpIN è autoinstallante.

Vedi sotto per il(i) link di download.

Qui di seguito trovi i link di download per l'installazione manuale del software:

FTE configuration for HTML / CSS / IPF edition modes (25/9/2017, Alfredo Fernández Díaz) Readme/What's new
FTE is an advanced multiplatform text editor, and this is an updated configuration for some edition modes: -HTML: Completely rewritten, automated add/delete of tags and many other tasks, fixed mistakes in previous versions, more logically organized menus, support for common modern HTML constructions (DTDs, CSS, CC...). -IPF: Completely rewritten with real syntax parsing, added some text handling tools. -CSS: New mode for easy edition/writing of Style Sheets. -NLV-ready, Spanish support is included.
 hobbes.nmsu.edu/download/pub/os2/apps/editors/fte_cfg_20170925.zip  local copy
eFTE/2 v. 1.0.0 (31/5/2016, Marko Macek, Gregg Young) Readme/What's new
eFTE/2, Version 1.0 Copyright 2009-2016 by Gregg Young Copyright 2008-2009 by eFTE SF Group. Copyright 1994-1998 by Marko Macek. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version, or b) the "Artistic License" which comes with this Kit. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details. You should have received a copy of the Artistic License with this Kit, in the file named "Artistic". If not, I'll be glad to provide one. You should also have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. ----------------------------------------------------------------------- WWW http://svn.netlabs.org/efte This is the first version of eFTE/2. It is based on eFTE (see README.efte) which in turn is based on FTE (Folding Text Editor). The configuration now compiles on the fly. You should be able to use it with the configuration files of an existing FTE install simply by creating a mymain.fte file in the same directory as your old main.fte. The file must include the line #include 'main.fte'. You could also use the mymain.fte and sysmain.fte files from the package. Simply copy them to the directory main.fte is in. You will need to edit mymain to set the UI and color scheme as it will override the settings in main.fte. Another alternative is to rename your main.fte mymain.fte or use -Cmain.fte on the command line. If eFTE/2 can't find your configuration SET EFTEDIR in config.sys to point to the directory your main.fte is in. If you want to install it directly over an FTE/eFTE install and not lose your custom configuration changes you can achieve that by installing only packages 1 and 3 to your current install directory. I have structured the configuration files to make it easier to translate the menus. I lack the language skills to do the translations. If you have an opportunity to do one or more of the translations please send them to me at ygk@qwest.net. The menu files are located in the menu_xx (where xx is the language code) subdirectories of the config directory. You may add any language with a 2 letter code. Simple create a menu_xx subdirectory using the code and place the menus in it. To test them copy the direcctory menu_xx to the config directory of an eFTE/2 install and start eFTE/2 with -Lxx (xx = language code) on the command line. The edefault.fte also could be translated. If you are interested in translating the documentation (help file etc) please contact me. Known Issues: 1. Occasionally, eFTE/2 will trap when starting an external program. The problem appears to be an estyler issue. If this is a significant problem for you try adding eFTEPM.exe to estyler's exclusion list. 2. Opening some help files with certain keywords will trap newview. This is an issue either with newview or with the help file as it occurs when newview searches the same term. (e.g. open the Open Watcom 2.0 C Library Reference and search for return). 3. Anything placed on the command-line after --debug<clean> is ignored. If you wish to use other parameters and or load files with --debug<clean> place them before it. See HISTORY file for a list of recent changes. See AUTHORS file for a list of contributors
 hobbes.nmsu.edu/download/pub/os2/apps/editors/eFTE2-1-0-0.wpi  local copy
FTE v. 0.5.01+ (3/3/2008, Gregg Young) Readme/What's new
02 Mar 2008 This package combines Alfredo Fernandez Diaz's IPF/HTML configuration updates and Spanish language support with Michael Greene's change including open watcom support (see below). In addition it now uses wrc.exe which was updated by Steven Levine and should be part of Open Watcom 1.8 It can currently be found here http://svn.netlabs.org/fm2/ticket/131. In addition the latest code from the CVS has been incorporated. I have made some minor changes to the menu structure. I also fixed several problems with search and replace in the PM version. It was built with open watcom 1.7a It now has the Norton color scheme as the default (blue backgraoud). 26 Jan 2006 Other than a couple small changes, the major reason for this version is the release of OpenWatcom 1.4 GA which I use to compile. So, this upload includes binary and source. To build: cd into SRC directory wmake [owos2 or owclean] the owos2 option will build console and pm version Oh, if you use the console version of NT/XP you can build it with OW14GA on a Win machine - sorry OS/2 only peoples. Also... sorry about the white background Doodle. Changes: 1. Still doing little changes in dialogs 2. Patched with Sergey Pinigin's svn changes, guess this works the same as FTE cvs, but I don't know - feedback?
 hobbes.nmsu.edu/download/pub/os2/apps/editors/fte-03-02-08.zip  local copy
PHP mode for FTE (16/7/2001, Timo Maier)
 hobbes.nmsu.edu/download/pub/os2/apps/editors/phpfte.zip  local copy
REXX editing mode for FTE (19/3/2001, Michael DeBusk) Readme/What's new
Menus, Keybindings, and Macros for FTE REXX Mode March 19, 2001 DISCLAIMER Using this stuff is completely up to you. I'm not responsible for any problems your use of these files may create, no matter how great or small those problems may prove to be. INTRODUCTION Even though FTE is still a beta, it's an excellent text editor. I won't bother with a commercial for it here, though. You can get it on Hobbes or visit the FTE website hosted on SourceForge. http://fte.sourceforge.net One of the challenges to using FTE is the fact that the menus, keybindings, and macros for the various modes it supports are unfinished. Another challenge is that the documentation for these is barely there. I wanted better support for REXX in FTE, and in the spirit of the open source movement I opened the source and put together what I wanted... more or less. I am not a programmer; I can barely program in REXX. What I've done works, but it is probably ungainly. I welcome your improvements and suggestions. WHAT IT IS * Key combinations which automatically create complete loop constructs; * Extensive menu for REXX keywords, contructs, functions, and libraries; * Ability to recognize REXX files with the extension REX and REXX. INSTALLATION It is very important that you back up your FTE configuration files. 1. Add the following line to your UI file (default is fte\config\ui_fte.fte): include 'menu/m_rexx.fte'; 2. Add the following line to your MAIN.FTE in the appropriate place (there are similar lines in the default file): include 'ab_rexx.fte'; 3. Back up the following files, in case you'd prefer to go back to the old configuration some time: fte/config/kbd/k_rexx.fte fte/config/M_REXX.FTE 4. Place the enclosed FTERXMNU.ZIP in the same directory as FTE.EXE and unzip FTERXMNU.ZIP, assuring that directories are recreated. InfoZip's UNZIP will re-create directories by default; PKUnzip requires a command-line parameter which slips my mind at the moment. 5. If you want REXXUtil, RxFTP, and/or RxSock libraries available on your pull-down menus, open fte/config/menu/m_rexx.fte (in the FTE editor, of course <g>) and uncomment the appropriate lines in the beginning of the file. REXXUtil is already uncommented because I like it that way on my setup. 6. Compile the new CNF file by executing CFTE CONFIG\MAIN.FTE and rename the resulting FTE-NEW.CNF to FTE.CNF or FTEPM.CNF, depending on the executable you prefer to use. 7. Set an environment variable named USER denoting your name or an alias, using your perferred method under your operating environment. I use "SET USER=Michael DeBusk" (without the quotes, of course) in my OS/2 CONFIG.SYS and in Windows/DOS AUTOEXEC.BAT. This environment variable is used in the macro that creates your REXX header comment; the contents of the variable are inserted after the word "Author:". HISTORY March 19, 2001 Added an abbrev file and eliminated many of the Ctrl-E keystroke combinations at the suggestion of developer Darin McBride. I like it better and it's easier to use. Type a short string followed by a space and whole constructs appear. The abbreviations are as follows: headx : REXX program header comment utilx : Adds RexxUtil support sockx : Adds RexxSock support ftpx : Adds RxFTP support dox : Constructs a DO loop dux : Constructs a DO UNTIL loop dwx : Constructs a DO WHILE loop dfx : Constructs a DO FOREVER loop ifx : Constructs an IF-THEN-ELSE structure selx : Constructs a SELECT-WHEN structure I simply commented out the key combinations in case someone out there actually prefers them. Delete the "#" to uncomment. March 2, 2001 Added syntax highlighting for Object Rexx keywords and expanded the existing NetRexx highlighting; I haven't added menu selections for them yet. Also realized that not everybody would want all libraries in their menus, so added conditional statements there. Haven't figured out how to make macros and keybindings conditional, but they aren't that big. February 15, 2001 Corrected two bugs that should have never made it out of initial testing. I had neglected to put the necessary "InsertString" command before two statements in the CALL menu. February 9, 2001 I've made some minor improvements, including correction of a mistake in this document. I also decided to include the keyboard file instead of asking the user to edit it; no sense making it more complex than it has to be, right? STILL TO DO I would like feedback of any type before submitting these to the maintainers of FTE. I know it can be better. If you improve it, please send me your changes so I can distribute them in the next "version" and so I can enjoy them as well. Send messages to debu4335@eclipsetel.com with the subject "REXX FTE". Thanks.
 hobbes.nmsu.edu/download/pub/os2/apps/editors/fterx.zip  local copy
SQL mode for FTE (12/2/2001)
 hobbes.nmsu.edu/download/pub/os2/apps/editors/sqlfte.zip  local copy
BAT, BTM and CONFIG.SYS modes for FTE (10/2/2001) Readme/What's new
Included are mode files for FTE Text Editor to edit CONFIG.* in either OS/2 or DOS and to edit batch files under DOS COMMAND.COM or any JP Software command processor (4DOS, 4OS2, Take Command, and so on.) Since last distribution: fixed a typo in M_CNFGS.FTE and updated it to include new keywords for CONFIG.SYS of MS-DOS 7 for Windows 95. Note that if anything happens as a result of your use of these files, you bear total responsibility for it. M_CNFGS.FTE will recognize any file with the name CONFIG, regardless of extension. (How did I get 33 CONFIG.* files in C:\ anyway?) M_BATCH.FTE will recognize files with the extension BAT or BTM. To use these files: 1. Place the enclosed CNFGBAT.ZIP in the same directory as your FTE executable file(s) and unzip it in a way that re-creates directories (Info-Zip's UNZIP does this by default, PKUnzip does not); 2. Edit CONFIG/MAIN.FTE to add the following lines (examination of the file should tell you the appropriate place): include 'm_batch.fte'; include 'm_cnfgs.fte'; 3. Recompile your FTE configuration file. 4. E-mail me at debu4335@eclipsetel.com and let me know how you like them. If you improve these files, please send me your changes so I can enjoy them as well as add them to a subsequent upload. If everyone is pleased, I'll send these to the maintainers of FTE for their evaluation and possible inclusion in an FTE distribution. Thank you.
 hobbes.nmsu.edu/download/pub/os2/apps/editors/cnfgfte.zip  local copy
Scheda aggiornata l'ultima volta il: 05/02/2022 - 14:34

Aggiungi un commento