Now that esmart is moving into libs, it makes sense to combine most of
the utility smart objects into a single lib. So xcomp has bravely
volunteered to combine estyle and etox into it. This will reduce the
perceived number of dependancies for EWL, and the total number of libs.
Along with bringing them into esmart, the API distinction between the
two will be going away. They will still be logically separated in the
code, but only one API will be exposed as esmart_text.

If you're using etox, the impact on your code will be negligible. A
simple search and replace for Etox/etox/ETOX to the Esmart_Text
equivalent should be sufficient. On the other hand, estyle's API will not
be exposed, so you will need to port to the Etox API. I will be doing
this in EWL once the move has been made.

Sorry for any inconvenience, but this should make more sense in the long
run.

-- 
------------------------------------------------------------------------
| Nathan Ingersoll          \\  Computer Systems & Network Coordinator |
| [EMAIL PROTECTED]   \\  http://www.ruralcenter.org            |
| http://ningerso.atmos.org/  \\  Rural Health Resource Center         |
------------------------------------------------------------------------

Attachment: signature.asc
Description: Digital signature

Reply via email to