We updated Styled HTML Field today to version 2.0.10. The StyledHTMLField is a set of classes for Xojo that allow you to export HTML from StyledText in a native TextArea control. The classes also allow you to create HTML emails.
This maintenance release has the following changes:
- Added ConnectionType for secure connections with ability to choose SSL2, SSL23, SSL3, TLSv1 and TLSv11, TLSV12 for R3 when it’s released.
- Added Paragraph Alignment to the demo application
- Removed PWEmbedImageSMTP. Now uses TCPSecureSocket but secure set to false for non-secure connections.
- Fixed deprecated items with current Xojo replacements.
- Fixed items found in project check
- Fixed old BKeeney URL’s in the demo app
Demo, pricing, downloads, and other details at http://www.bkeeney.com/styled-html-field/
I apologize. Blog posts have been slow lately. Acquiring products from another company is an interesting process and figuring out the StyledHTMLField and Simple Help Editor was no exception. First, you have to get in the mind of the original developer and figure out what they were trying to do and then determine if you wish to change the code and then test, test, test. I can say I am very thankful for source code control because I’ve broken a few (too many) things and had to revert to older code!
One of the things we’re doing with Simple Help Editor is changing the licensing scheme to fit most of BKeeney Software’s other commercial products. That led me down the proverbial rabbit hole because we discovered that the eSellerate plugin works fine in Carbon and Cocoa (after contacting tech support to get the Cocoa update) but fails in Windows (go figure). Of course this only happens in Real Studio 2012 R1 and higher so I’m sure it’s simply a plugin compatibility issue and hopefully we can get an update soon (because we’re waiting to release!)
The other thing we decided to do was move to our standard preferences system. The reasoning was twofold: First, it now works just like every other of our products so my and my team won’t have to think about what the preferences system does because we know it (and use it everywhere). The second reason, which was kind of by accident but fortuitous anyway, was that we got to touch code everywhere. Just by replacing the preferences we go to see a LOT of code we wouldn’t have normally touched.
Just by doing these two seemingly minor items I now have a whole laundry list of items I want to change in Simple Help Editor. Some of it is personal preference and some of it is features I want for my own products. It’s also a strong possibility that we’ll integrate the Formatted Text Control into Simple Help Editor to not have to rely upon the RTF to HTML conversion routines and the built-in TextArea control which doesn’t allow any graphics to be shown. This should make the Simple Help Editor text editors to be a bit more intuitive. If you are are user of Simple Help Editor and have a feature request then please let me know. I
Speaking of the Formatted Text Control we’re also working on it too and getting it ready for new features in version 3. Among the planned features are Retina display support, HTML Export, Hyperlink support, and adding a number of simpler examples that developers can (hopefully) use out of the box without any plugins.
Sometimes I am amazed at how long some things seem to take. I guess I shouldn’t at this point as I come up with estimates for clients all the time. When it’s my own stuff it seems to take FOREVER to get done.
Anyway, that’s the current update. Thanks for you patronage and continued support!