I am really excited about this library and I am curious when TLF support will be available. Soon... not soon? We are working on some interesting things but its all TFL or Flex 4 based. We can build our own interface, but that seem excessive if this is on the horizon.
Thanks for your positive feedback. Yes, this is a high priority, but to set realistic expectations, we will not be coming out with an update for this anytime super soon. We will definitely address it before the production release of Flex 4 TLF. Most likely it would be late fall or early winter.
Hope this helps,
- Bruce, Adobe Product Management
It would be great if someone from Adobe can let know when a TLF compatible version of Squiggly is planned for release. We are working on a large AIR application which extensively uses TLF for which we are in need of Spell Checking functionality. If it helps, the planned release date for the application which we are working on is mid December.
Unfortunatley, we don't have a firm date on Squiggly Support for TLF. We are working on TLF support along with other features but at this point all I can say is that the December timeframe is unlikely for us. We are expecting to be able to deliver it in the first quarter of next year.
Thanks for your patience,
Thanks for the prompt response Noela. We have already started writing wrappers which uses Sqiggly API's and would enable spell checking within our AIR application. Look forward to the official support soon !
" Thanks for the prompt response Noela. We have already started writing wrappers which uses Sqiggly API's and would enable spell checking within our AIR application. Look forward to the official support soon ! "
We're just about to start doing the same thing. Any pointers for us before we start (i know this is a big ask but thought it worth a try)
Bear in mind we've not even started looking yet, is planned for this week. All ouu components at the moment use TFL
tinylion development & design
At the moment we are taking this (route; but with two improvements:
1) Using underline (preferrable dotted) to mark the misspelled words.
2) To use the context menu for word suggestions instead of having a seperate panel.
Note that the example there doesn't compile directly due to changes in the SDK but you should be able to get that working with a few minor API tweaks.
I will report back once we are successful porting it.
I'm waiting with anticipation for TLF support in Squiggly - I just wanted to register my interest here.
KP, great work. It looks like you may come up with a solution before Adobe does. Does your algorithm work well for large documents? (Only need to check parts of the textflow that have been changed since the the document was last checked.)
I'm developing a Flash (AIR) based word-processor/publishing application.
The first public prototype (warts-n-all) is here...
A video introduction can be found here...
Just to reinforce a ponit made by Noela.
The TLF support we will be releaseing in the upcoming release is for Flex 4 Spark components, which are based on TLF. It will not include direct support for TLF outside of Flex 4.
- Bruce, Adobe
That's not ideal for a Pure Actionscript development. In fact I find it hard to imagine doing anything very special with the TLF using Flex components and framework. But then, I've never been a fan of Flex (despite it being my job).
In that case, I'll probably end up writing something myself along the lines of what KP described.
We do understand the need for pure TLF support and it is in our roadmap but we believe that support for Flex and in particular Spark components is of higher priority. That does not mean pure TLF support is not crucial also and we will be working on it in the near future. We would also be interested in hearing about your views on Flex.
Noela - Adobe
@Noela @Bruce: Thanks for the update and it's good to know that Squiggly support for Spark components is on the cards.
I understand that including support for Squiggly in Spark components might be the most strategic direction from a product standpoint and I am glad that there is plan to include pure AS support in the near future. Having said that, Daniel has a point here, having dealt with TLF in quite some depth I can say for sure that pure ActionScript support is what would be much needed. The components themselves may restrict users from creating complex applications using TLF and one would eventually prefer using a pure ActionScript approach to gain maximum control over the application.
@Daniel: I had a look at e2publish and it looks quite promising. I specifically liked the way you dealt with inline images. Good job overall.
And for updates from my side, I managed to hack into this and now I have the Squiggly underline, the right click context menu suggestions and the real time spell checking working much like how the Grant Skinner's and Adobe's Squiggly works. Had to go through a lot of pain to get this working but yeah it works like a charm. There are still minor glitches like the current sentence's squiggly going off when an edit is made (and recovered when a new word is typed) and the need to click on a word before it is right clicked to get the suggestions but then this was good enough for our client. It's completely done in ActionScript and it uses some code from the Adobe's Squiggly examples by itself.
As far as the speed goes, I would say it is pretty descent and may be takes approximately 1 sec per page. Since we are on an NDA I am not able to showcase the application in public but you can see a screenshot of the squiggly and right click working in TLF here. I will try and do a blog post on our site with some pointers when I am little free.
Thanks Bruce ! You guys have done a fabulous job with Squiggly. Many of us couldn't afford buying the commercial version of these libraries at the kind of price tags they came with.
Europe, Middle East and Africa