Flex as the frontend is a good choice. It's really a nice framework,
which lets you concentrate on the content. If you are a good
programmer, you'll be able to pick up speed with Flex very quickly. On
the other hand you are limiting your audience to Flash player 9.

As for the backend: I'd go with the knowledge & resources you have
available. Though Java environments like Eclipse JDT are very good, i
doubt that it will make the difference in a three month project,
esspecially if you have to learn it first.

Maybe haxe is another option? Looks like a promising technology to me
(see haxe.org).
Cheers,
Ralf.


On 7/2/06, João Saleiro <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hey guys,
>
>
>
> First, I want to thank everybody who helped us, and also those who made
> comments on our project. J
>
>
>
> I've delivered the report on my university so CastingOffice is closed for
> now as an academic project. In October, we will get back to work, and make
> it final for modeling agencies. Till then, I have a huge project, a fashion
> portal completely done in Flash. Imagine FTV.com … now imagine much better!
> That's the project. J
>
>
>
> There is a lot of responsibility on this project, and the problem is  that
> probably it will be referenced on TV from time to time, causing extremely
> high traffic periods.  That's one question I'm worried about: how can I know
> from the beginning that there won't be problems on these periods?
>
>
>
> I'll have two months and a half to finish it, and all the resources I need.
> J The only resource I'm lacking is qualified personal, experienced with
> Actionscript and used to design patterns (and this is something that it's
> not being easy to find K).
>
>
>
> On CastingOffice I used mysql+php +amfphp+actionscript2 over ARP, on a kind
> of a AMES workflow (we used flash ide for creating the library).
>
>
>
> I want to know what do you think on:
>
>
>
> 1-      Migrating Flash to Flex? On terms of cost, learning curve, changes
> on workflow, team work, efficiency, productivity, tools, good and bad
> points.
>
> 2-      Migrating PHP+AMFPHP to JAVA+OpenAMF? On terms of learning curve,
> changes on workflow, team work, efficiency, productivity, tools, good and
> bad points.
>
>
>
> Your opinion is extremely valuable to me. J
>
>
>
> Thank you all,
>
>
>
> João Saleiro
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to