Though the changes seem small, alpha, asthetics, etc they can amass to
something huge. Our project has experienced many upgrade pains and took much
longer than anticipated. There are benefits of course but you shouldn't
underestimate the time to upgrade.
Hmm one point. You can build your project with Flash Builder 4 using the SDK
of your choice, be it 3.5 or 4.0, etc. You don't have to use the latest SDK.
The issues mentioned above are from going from SDK 3 to SDK 4. Best wishes,
JP
On Wed, Jun 23, 2010 at 2:56 PM, flexnewbie06 <flexnewbi...@yahoo.ca> wrote:
>
>
> Thanks! I have resolved all my initial errors and compiled and re-deployed
> my App. Wow that was really painless! so surprised. Although, i had to set
> the compiler to use
>
> -theme=${flexlib}/themes/Halo/halo.swc
>
> so it would resolve half the issues, however it doesn't look anything like
> the Flex 2 version does. Alpha's are missing and other random aesthetics
> aren't supported. So I have some clean up to do.
>
> My main reason for the upgrade - DataGrid...works like CRAP in Flex 2.
> Random re-drawing of fonts, item rendered cell with checkboxes or images get
> placed anywhere in the grid when you scroll around. Lots of weird things
> (that my boss wants fixed and I can't fix them)...so I'm hoping this upgrade
> fixes some of those issues.
>
> I only have 9 days left on my trial though!! eek.
>
> :)
>
>
> --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, Brendan
> Meutzner <bmeutz...@...> wrote:
> >
> > Yeah, you don't want to have LiveCycle or BlazeDS checked... those both
> rely
> > on services which would be present on your backend server, and dictated
> in
> > the services-config.xml file. LiveCycle and BlazeDS would have nothing to
> > do with your web service calls.
> >
> > You should use the RemoteObject checkbox, and honestly, if you're using
> web
> > services, it shouldn't really affect it at all. Correct me if I'm wrong,
> > but your web services would have url endpoints defined within each call
> (ie.
> > the mxml tag) from Flex 2.0 right?
> >
> > The remaining errors you face if you choose RemoteObjects checkbox should
> be
> > fixable as Jeffry points out.
> >
> >
> > Brendan
> >
> >
> >
> > On Wed, Jun 23, 2010 at 2:15 PM, flexnewbie06 <flexnewbi...@...> wrote:
> >
> > >
> > >
> > > Yes Apologies...I think I typed before I thought about this some more.
> > >
> > > Flex 2.0.1 SDK To Flex 4 SDK(I guess I was stuck on the name change
> from
> > > flex builder 2 to Flash builder 4)...I dunno.
> > >
> > > Yes I downloaded Flash Builder 4 Trial. Tried to open my project in and
> I
> > > tried to update some build path properties. One option is to "Use
> remote
> > > object access services", in the Flex Server tab of project properties.
> Maybe
> > > I'm not supposed to be using that check box at all?
> > >
> > > So If I select Live Cycle - because my only other options BlazeDS
> (which
> > > I'm certain I'm not using)..."Only LiveCycle Data Services 2.6 and
> higher
> > > are supported" is the error I get. I suppose this wasn't introduced
> until a
> > > later SDK for web Services?
> > >
> > > So I just left it unchecked (not knowing if this will make my
> web-services
> > > unusable or not) and it let me proceed and compile...I have a few
> errors to
> > > sort out...
> > >
> > > However, as mixed up as I am, "relatively few problems" sounds like a
> good
> > > start.
> > >
> > > Thanks.
> > > Jenn
> > >
> > >
> > > --- In flexcoders@yahoogroups.com
> > > <flexcoders%40yahoogroups.com><flexcoders%
> 40yahoogroups.com>, Jeffry
>
> > > Houser <jeffry@> wrote:
> > > >
> > > >
> > > > Do you mean that you're moving from Flex 2 to Flex 4? Or from Flex 2
> > > > to Flash 4? They mean radically different things. I'm going to assume
> > > > you mean the former.
> > > >
> > > > Did you download a trial of Flash Builder 4? You said you hit a wall;
> > > > what wall did you hit?
> > > >
> > > > When you say that "Web Services Not Using Live cycle"; I'm not sure
> > > > what that means. But to me that sounds like it might be a problem
> with
> > > > your server side code.
> > > >
> > > > It would be my expectation that compiling a Flex 2 application
> against
> > > > the Flex 4 SDK would present relatively few problems.
> > > >
> > > > On 6/23/2010 2:19 PM, flexnewbie06 wrote:
> > > > >
> > > > > Hi all,
> > > > > I would like to see our current code base updated from Flex 2.0.1
> to
> > > > > Flash 4. We have many bugs inherent to the components in the SDK I
> > > > > would like to see resolved. The project is quite large...using web
> > > > > services and many many components(and States..I think these guys
> > > changed).
> > > > >
> > > > > I downloaded the trial for Flash 4 and tried to port some of our
> code
> > > > > over, but immediately hit a wall with the web services not using
> live
> > > > > cycle. So I am looking for some thoughts from you guys...aside from
> > > > > some of the web services being broken, am I looking at a whole of
> > > > > change? How much backwards compatibility does this migration
> support.
> > > > >
> > > > > Thanks so much for any suggestions.
> > > > >
> > > > > Jenn
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jeffry Houser, Technical Entrepreneur
> > > > Adobe Community Expert: http://tinyurl.com/684b5h
> > > > http://www.twitter.com/reboog711 | Phone: 203-379-0773
> > > > --
> > > > Easy to use Interface Components for Flex Developers
> > > > http://www.flextras.com?c=104
> > > > --
> > > > http://www.theflexshow.com
> > > > http://www.jeffryhouser.com
> > > > --
> > > > Part of the DotComIt Brain Trust
> > > >
> > >
> > >
> > >
> >
>
>
>
