We’re excited to announce that the second Flex 4 SDK beta 2 is now available for download! Check out the Labs page and the Flex 4 Open Source page for more details. Also, be sure to check out Matt Chotin’s updated What’s new in the Flex 4 Beta and Joan Lafferty’s Differences between Flex 3 and Flex 4 articles. This beta release also coincides with the beta 2 releases of both Flash Builder and Flash Catalyst.
We received great feedback on beta 1, which we incorporated into beta 2. We hope you’ll keep the discussion going on the Labs forums.
Due to significant recent performance and reliability issues with our JIRA bug database, we will be making a series of changes over the next several weeks. So far, the changes we’ve made include disabling the following functionality:
- Remote API calls
- XML search requests
- Anonymous browsing
As a result, this may affect some existing apps and public wiki pages using xml search requests. We apologize for the inconvenience, however, we would like to keep this disabled until we can dive deeper in the cause and possible solutions. Thanks for your patience as we try to resolve these issues.
Note: This is a mirror of Adobe Evangelist Anirudh Sasikumar’s post http://anirudhs.chaosnet.org/blog/2009.09.01.html which has been down due to too much traffic.
September 1, 2009 10:36 PM
I spend a lot of time reading articles on the web. Somehow, I miss the lack of typesetting and pagination especially when the article is captivating as well as long. This is my attempt at making reading content on the web (and the computer to a certain extent) more beautiful. With a lot of help from Flex 4, Readefine beautifies text, RSS and HTML content for easier reading. Text is laid out in multiple columns, sanitized of stray newlines and paragraphs and a nice font is applied.
What is it?
Readefine is a Flex 4 web application (a desktop one is coming soon) that beautifies RSS, text and HTML content by laying text in multiple columns for easier reading. Take a look at the screenshots below:
It can load content from the web, a file on your computer or via copy-and-paste. Readefine supports content in RSS, HTML or plain text format.
Text settings like justification, ligatures, column width / count, etc. can be fully customized and saved.
Some nice things about it:
- Removes stray newlines, empty p, br tags.
- Newspaper like layout for RSS – my aim was for RSS files to look like a newspaper1.
- Paginates rather than supporting scrolling. I hate scrolling while reading a lot of text.
- Makes long plain text files beautiful and also sections them for performance.
- Copy paste or load a file from your computer (load, not upload)
- Gives a new look to those valuable Gutenberg text files
- Remembers the last 30 URLs you have visited.
- Re-flows text according to the available size.
- Resizes images to fit within the columns.
- Tries to compute the absolute URL from a relative link.
Some not so nice things:
- HTML support is experimental. Certain HTML (even from popular sites like the Wall Street Journal) will make it go crazy. Plain text and RSS work best.
For the Flex Community
This is my first full-fledged Flex 4 application. Flex 4 rocks!
The components used in this extend the existing Flex 4 and Text Layout Framework classes to add pagination, HTML cleanup and tolerant HTML import. I’ve also built a Scroller like component for the overflow of articles from top DataGroup to the one on the left side. I will be open sourcing these components shortly for the benefit of the developers out there.
Try it out and let me know. Any feedback is welcome.
There have been some questions over the last few days on the status of the Flex data visualization components and I wanted to make sure everyone knows our intentions.
First of all, you may notice that the 3.4 downloads page has an updated copy of the data visualization components (charts and the Advanced DataGrid and OLAPDataGrid). While we have made it easier to view the source (you don’t have to run the DMV-source.jar anymore), we still consider these components to be under the Flex Builder license, and the source to be considered “Professional Component Source Files” as described in the Flex 3 SDK EULA. So I hope that clears up the licensing question.
The other concern I’ve heard raised is that Flex 4 is not seeing many changes to the data visualization components, and therefore folks are worried that Adobe is not investing in them. Data visualization remains a “core competency” of Flex, and we absolutely plan on further development of these components along with supporting partners who have expanded upon them like the ILOG team at IBM. In the Flex 4 time frame we plan on making some improvements to the GroupingCollection, a fundamental piece of the ADG in the hopes of addressing one of the larger performance bottlenecks. However, we chose to take on 2 significant agendas that preempted doing significant work in the data visualization components.
The first is the data connectivity features in Flash Builder; the way we’re making it even easier to connect your data from the back end into the data visualization components in the front. We hope that this will make the data visualization components even more accessible for developers, making it simple to get up and running and build powerful data-driven applications.
The other agenda is the introduction of the Spark architecture. As everyone knows, this is a significant improvement to the fundamental component architecture in Flex, but it is too much to bring every component forward into the new model in a single release. While the charting components do not need to be modified significantly to fit well with Spark, the DataGrid (and therefore the AdvancedDataGrid) will take significant effort, and that is work we intend to do in the following release. Knowing that a fundamental re-architecture of the DataGrid is coming, we decided not to make significant investment in the current one for this release other than addressing the most important bugs.
So that’s the status and we hope you’ll understand and agree with our prioritization. If you’ve got any questions, feel free to comment here or post to the forums!
Adobe is conducting a User Research study to learn more about the work flows of Flex Developers. If you are currently working with Flex in a professional capacity we would really like to hear from you.
If you are interested in providing Adobe with feedback about your use of Flex and other Adobe products, please click on the link below and complete our survey. Adobe will be in contact with you if you align with our target characteristics.
When: Tuesday, August 18th at 10am – 11am PDT (Find your time zone here)
As mentioned in our previous post, we’ve had a lot of developments as a result of the beta feedback we received from many of you. We’re taking additional time to improve the experience when using Spark (the new component set introduced in Flex 4) and Halo together. We’ll be hosting another Open Iteration Meeting next week to discuss these updates. Post a comment here if there are particular questions you’d like addressed in this meeting and please continue to post to the forums if you have additional feedback or questions. Look forward to see you next week and if you’re unable to attend the OIM recordings will be posted to the Flex Open Source site.
The Flex 4 and Flash Builder 4 betas have now been out for a few weeks and we’re very excited to see so many folks playing with them, asking questions on the forums, and posting examples of what they’ve done. From the time we first started showing Gumbo we’ve been monitoring feedback, especially around the experience of using the Spark and Halo components together. While we know that in general using both models together is possible, we’ve decided that there are a number of smaller things that we can do (many suggested by you) to make the experience that much better for both new and existing users.
We’ve therefore decided that we need some more time to take your feedback into account, and are going to release a second public beta this fall. This will give us an opportunity to make the enhancements required, and get additional feedback from the community. Given the second beta, we anticipate the release of Flex 4 and Flash Builder 4 to move from late 2009 to early 2010.
On the Open Source Flex SDK side, we’re planning to host another open iteration meeting in the next few weeks to discuss all of the changes that we’re considering. We’ll also be looking for feedback on things we can do in our docs and messaging to make sure that users from all backgrounds are successful in adopting Flex 4. Stay tuned here for the announcement of that meeting. And keep using the beta, filing bugs, and communicating with us via the forums!
If you’ve had a chance to play around with the Flex and Flash Builder betas, we’d greatly appreciate getting your feedback on your experience. Please take 15 minutes to fill out our survey. Thanks for your help!
Flash Builder 4 beta extension serial numbers are available for all licensed Flex Builder 3 customers. This includes all commercial and education serial numbers. To request a beta extension serial number, you will need to enter your Flex Builder 3 serial number. Please go to the extension request site to obtain a serial to extend FB4 beta.
The latest official Flex SDK, now at version 3.3 has been released. You can download it from our main downloads page. We are not releasing a new version of Flex Builder, and therefore have made the updated Data Visualization components available from the same downloads page as well.
These releases are entirely bug fixes, along with the inclusion of the updated Flash Player and AIR bits.
You can see the SDK bug fixes here. The Data Visualization bug fixes are:
FLEXDMV-963: Complete chart area not used when day(s) are disabled
FLEXDMV-1882: Changing ColumnSeries itemRenderer at runtime doesn’t remove previous itemRenderer. All previous itemRenderers still get called.
FLEXDMV-1695: RTE for Chart display when using labels, 100% height and ViewStates.
The Flex SDK is also available from the Open Source site.
Instructions for extracting the source for the data visualization components can be found in the release notes.
The workaround below is not necessary if you’ve downloaded since 3/07.
NOTE: If you are on a Mac and using AIR you may need to run the script found attached to the bug SDK-19707 as we screwed up the symlinks pointing to the runtimes. This will hopefully be fixed in the downloadable version in the next day or two.