Hi Mark,

The standalone version of Flex Builder on Windows is based on 3.1.2 
but the plugin version will work on 3.1.2 or 3.2 so you should be 
good to go. Let me know if you run into any issues.

-Heidi
Flex Builder Dev Manager

--- In [email protected], "Mark R. Jonkman" 
<[EMAIL PROTECTED]> wrote:
>
> Hi David
>  
> While I'm not the original poster and realize (via the other posts 
on this
> thread) that the changes are documented, they aren't immediately 
available
> from where you would expect to find them on the website. For 
example:
>  
> http://www.adobe.com/support/flex/
>  
> The top line says Current English Version: Flex 2.0.1... updaters 
available
>  
> Click on the link and wind up at:
>  
> http://www.adobe.com/support/flex/downloads_updaters.html
>  
> You get the release notes for 2.0.1 if you click Release Notes 
under Flex
> Builder 2.0.1 but if you click the Flex 2.0.1 SDK Release Notes, 
you get the
> release notes from Flex 2.0 unless somehow the 2.0.1 stuff is 
interspersed
> (but that wasn't evident if it was). So if you clicked on the 
correct Flex
> Builder 2.0.1 link you got what you wanted but one would expect 
the SDK link
> to list out updates to the compilers as well (ie. what changes 
affect more
> then just the Flex Builder such as new components or 
functionality). 
>  
> One thing I wanted to know and still can't figure out without 
installing the
> Flex 2.0.1 updater is whether or not the underlying version of 
Eclipse has
> been updated from Eclipse 3.1.2 to 3.2.x. Might not be meaningful 
to others
> but I really need Flex to run well under Eclipse 3.2.x so that I 
can use
> Castillo only plugins with Flex. I'm currently running the 2.0 as 
a plugin
> so that I can use Eclipse 3.2 but then I keep getting exceptions 
and issues
> about can't retrieve labels, thread exceptions when running Flex 
Debugger
> Perspective under Eclipse 3.2 (if anyone out there knows a 
solution please
> let me know). Up until mid December, Subclipse plugin for the newer
> Subversion client was only available for Castillo (subclipse 1.0.4 
for
> Eclipse 3.1 was released in December) so that caused other issues. 
I still
> don't know whether 2.0.1 upgrades Eclipse or not.. I'd love to 
know that. My
> guess is it won't.
>  
> Second, if one is running Flex Data Services, the same page lists 
release
> notes for Flex Data Services 2.0.1 but I can't seem to find the 
link to
> download the Flex Data Services 2.0.1. Unless they are a). 
Contained within
> the Flex Builder 2.0.1 installer or b) are located somewhere else 
on the
> site. I think I found link last night from some other page to 
download said
> version of the data services but I can't seem to find it today and 
the link
> last night wound up with a broken link page. Not sure if Flex 
Charting has
> similar issues as I believe they install as part of Flex Builder 2 
but if so
> I'd suggest a link on the update page along with the release 
notes. One
> should never have to search high and low and read between the 
lines to know
> what is included and what isn't and where one should search to 
find the rest
> of the parts one needs to update their install.
>  
> So while the stuff information and associated files may very well 
be there
> on your site somewhere, the site lacks cohesiveness in presenting 
the
> updaters and information properly. While I didn't start the thread 
nor do I
> necessarily agree fully with the title of the thread, I do see a 
lack of
> cohesiveness to the information presented on the site. 
>  
> I'd also like to point out that the main Flex Product page doesn't 
indicate
> in any way that an update to Flex has been made available. 
Depending on my
> reason for visiting Adobe's site, I'd be inclined to visit either 
the
> product page or the support site, both should have links to the 
updaters and
> both should be clear that an update has occurred. Currently one 
only finds
> out about the update from the support site.
>  
> Finally, more in response to those who are saying RTM, I'd say 
that the
> information needs to be posted clearly and in detail outside of 
the product
> documentation when it involves and updater like this. For example, 
if I'm in
> the middle of a major project that might benefit from said new 
feature but
> also could be completed without said new feature and the timeline 
of the
> project is rather "tight". I would want to read enough detailed 
information
> and find it quickly without the need to install the update to 
determine if
> the risk of installing the update is less the the amount of effort 
to
> continue developing without the update (at least for said 
project). It might
> be just a link to a pdf that comprises the pages that were added 
to the full
> documentation: list of changes, and the docs on the new features. 
The sheer
> volume of the documentation for Flex can be overwhelming. 
>  
> On the subject of the documentation, having only worked with Flex 
for about
> a couple of months in my free time, I still have mixed feelings 
over its
> completeness in terms of at least examples and finding the right 
stuff
> quickly. I've often had to "give up" on the documentation and 
search the
> Internet for examples that meet my particular need. Interestingly 
enough at
> times a Google search pinpoints what I need in the LiveDocs that 
the
> straight search in the documentation failed to find. The other 
issue I find
> is that the examples often utilize the simpliest of cases. An 
example this
> week I wanted an example on using a checkbox within a data grid 
but not one
> of the examples in the datagrid documentation showed doing 
anything other
> then using a datagrid with the standard item renders. A set of 
examples for
> a datagrid (or other components) would be to show the simple 
example and a
> more complex example that exercises the bulk of the functionality: 
using
> different item renderers etc. Often mxml examples will be shown, 
but a
> similar example using ActionScript only is omitted. It took me 
forever to
> figure out how to bind data without using ActionScript vs MXML. 
>  
> I'm not trying to flame anyone or create a bigger issue but there 
are some
> things about this updater and the documenation and downloads page 
that can
> or could definitely invoke emotions similar to the subject line 
especially
> if someone is in a hurry and wants the information to be there 
readily at
> their fingertips.
>  
> Sincerely
> Mark R. Jonkman
> 
> 
>   _____  
> 
> From: [email protected] 
[mailto:[EMAIL PROTECTED] On
> Behalf Of David Mendels
> Sent: Saturday, January 06, 2007 6:37 AM
> To: [email protected]
> Subject: RE: [flexcoders] Re: and I thought Adobe was a 
professional
> company. Whats going on with the upgrade
> 
> 
> Hello,
>  
> Have you tried the help system?  The new functionality is 
documented.
>  
> Regards
> David
>


Reply via email to