RELEASE-NOTES.txt 5.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139
  1. ionCube PHP Encoder 7.0 Release Notes
  2. -------------------------------------
  3. Unless marked otherwise, changes refer to the Encoder products within
  4. this release; GUI refers to the Windows GUI supplied with the Windows
  5. version.
  6. Version 7.0.0.3 - 13 Dec 2010
  7. -----------------------------
  8. * GUI: New feature added to support legacy encoding (6.5) as a user
  9. preference. This brand new feature is a compatibility maximiser,
  10. giving access to new features of the version 7 GUI while allowing
  11. generation of legacy encoded files. Using the version 7 Encoder is
  12. recommended and is the default, but simply switch to legacy encoding
  13. using version 6.5 Encoders via the preferences dialog if needing to
  14. use encoded files to servers running old Loaders (pre version 4).
  15. Note that as this feature uses version 6.5 Encoders, new features
  16. of the version 7 Encoder (such as the @ syntax) are not available
  17. when legacy encoding is selected.
  18. * Legacy Encoders (6.5) are now included in the legacy directory with
  19. the Unix platforms for compatibility maximisation.
  20. Version 7.0.0 - 24 Nov 2010
  21. ---------------------------
  22. * The Encoder for the PHP 5.3 language is included in this release,
  23. plus the Encoders for PHP 5 < 5.3 and PHP 4.
  24. * Source directory substitution in wildcard patterns using @
  25. A leading @/ or @\ in the values for --keep, --ignore, --encode,
  26. --copy and --encrypt is interpreted as being to the first source
  27. item specified.
  28. * Option --ignore-deprecated-warnings added to ignore deprecated
  29. warnings.
  30. * Option --ignore-strict-warnings added to ignore strict language
  31. usage warnings.
  32. * GUI: (File menu) The recent files and directories history now
  33. indicates if an item is missing, and gives an option to remove that
  34. item from the history.
  35. * GUI: Accessibility enhancements.
  36. * GUI: (Project menu) New options added to quick-build and clean the
  37. current project. The build option will process as per the project
  38. settings with respect to whether an existing target is replaced,
  39. updated or merged. Quick-build will perform an update operation
  40. and only process files that are new or modified more recently than
  41. the corresponding item in the target folder. Note that a
  42. quick-build will not remove items in the target folder that do not
  43. appear in the source folder, so a clean or full build is
  44. recommended after changing the structure of the source folder.
  45. * GUI: Preferences dialog added for project defaults and other
  46. settings.
  47. * GUI: New toolbar icons added for moving to the next/previous parse
  48. error within the associated file. When used, the document
  49. containing the error is opened, and if supported by the editor set
  50. via the preferences dialog, the cursor will be positioned at the
  51. line containing the error.
  52. * GUI (user preference): The last open project can be automatically
  53. opened at startup.
  54. * GUI: The PHP language used (4, 5, 5.3) is added as a visual check
  55. to the title bar information.
  56. * GUI: Various bug fixes.
  57. * GUI: Event log entries optimised to show shorter paths, and
  58. date/time display is available as a user preference.
  59. * GUI: Source file edit/view. Source files can now be opened in a
  60. choice of editors both from the source files tree in project
  61. settings and in the relevant nodes of the event tree.
  62. The preferred editor is selected as a user preference from a list
  63. that currently includes: EditPlus 3, Notepad++, GVim, PSPad,
  64. Programmer's Notepad, PHP Edit or PHP Designer 2007. This list can
  65. be extended if required by editing an XML document located in the
  66. installation folder, using the exising entries as examples.
  67. If an editor supports opening of a file at a particular position,
  68. double clicking a parse error message in the event log will open
  69. the source file with the cursor positioned at the line containing
  70. the error.
  71. * GUI: The export batch file option is replaced with an Export
  72. Project feature. This allows a project to be exported as a Windows
  73. batch file, a command line Encoder project file, or a Unix shell
  74. script. The exported project script can optionally be updated
  75. automatically when a project is saved.
  76. Functional changes from previous versions
  77. -----------------------------------------
  78. * Encoded files produced by Encoder 7.0 require a minimum of Loader
  79. version 4.0 to function.
  80. * Encoding with strict language rules is now the default, and does
  81. not need to be enabled with --strict-php. Deprecated warnings
  82. (new from PHP 5.3) are also enabled by default.
  83. * New options --ignore-strict-warnings and
  84. --ignore-deprecated-warnings can be used to suppress strict and
  85. deprecated warnings.
  86. * PHP 5 Encoder: Code with var instead of public/private/protected
  87. will no longer give a strict warning if strict warnings are
  88. enabled.
  89. * GUI: New projects have strict language usage and deprecated
  90. warnings enabled by default in the project settings (miscellaneous
  91. tab).
  92. * GUI: Menu and toolbar "Encode" options renamed as "Build" options.
  93. * GUI: The "New Project" Wizard is removed for 7.0.0 and a new
  94. version will be added in a future revision.
  95. * GUI: Loaders for Windows and Linux are no longer included with the
  96. product installation to reduce initial download size and to reduce
  97. the chance of obtaining out of date Loaders. If Loaders are
  98. required and/or the Loader bundling feature is desired to be used,
  99. the exact Loaders required can be easily downloaded and made
  100. available to the GUI after installation. An "Add Loaders" link on
  101. the Target tab in project settings now provides a quick way to
  102. navigate to the relevant Loaders page on the ionCube website.
  103. Copyright (c) 2002-2010 ionCube Ltd.