Expand my Community achievements bar.

SOLVED

Flex only?

Avatar

Level 1
Level 1
Unless I am mistaken it seems that Cocomo is targeted at Flex
developers only, but why? A lot of the provided functionality would
fit great in a lot of Flash Site designs, e.g. community sites,
which are typically build using the Flash authoring tool. May we
expect Cocomo support for Flash CS3/4 in the future too?
1 Accepted Solution

Avatar

Correct answer by
Former Community Member


Hi bvi,



We did choose to focus specifically on Flex for this release
- mostly, I think it was a matter of ease of development - it's
much harder to write these sorts of apps non-declaratively.



That said, we did spend some cycles trying to distance
ourselves from the Flex framework for the "base" classes in Cocomo
- you wouldn't get any UI for free, but the model classes are
largely Flex-independent. We still have a ways to go to be
completely independent (largely, this is around data classes such
as ArrayCollection, which are *so useful* that I hate to remove
them), but I think if there's a demand for it, a Flash-only version
is within reason.



thanks

nigel

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member


Hi bvi,



We did choose to focus specifically on Flex for this release
- mostly, I think it was a matter of ease of development - it's
much harder to write these sorts of apps non-declaratively.



That said, we did spend some cycles trying to distance
ourselves from the Flex framework for the "base" classes in Cocomo
- you wouldn't get any UI for free, but the model classes are
largely Flex-independent. We still have a ways to go to be
completely independent (largely, this is around data classes such
as ArrayCollection, which are *so useful* that I hate to remove
them), but I think if there's a demand for it, a Flash-only version
is within reason.



thanks

nigel

Avatar

Level 1
I personally would like to see you stick with Flex. As you
say, writing a layer for non-declarative apps will eat up your
resources that could be much better spent enhancing and extending
this very cool project.



I do flash work for flash stuff (animations and pretty
stuff). I do flex for applications (albeit, pretty too).

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----