Re: [flexcoders] Re: Best practices for the naming of item renderers ?
João wrote: I'm talking about some kind of coding conventions. In a team environment it's a good practice to make everyone follow the same coding conventions. Different programmers give more or less the same names to classes/methods/properties, etc since all of them follow the same rules. Unfortunately we do not have rules for naming Item Renderer classes so I'm researching if there are any coding conventions for this files - else, we need to create our own conventions. I'm not aware of any official convention, but I've always found descriptive names to be the most helpful. If you are creating am item renderer for a users list, something like UsersListItemRenderer in the proper namespace will work. I like to use this in general so a given class is as descriptive as possible: UserRegisterEvent, UserRegisterCommand, etc. -Ricky
Re: [flexcoders] Re: Is Flex the wrong technology for widgets? SWF file sizes are too big...
Josh McDonald wrote: I definitely agree with you Gabriel, you wouldn't catch me doing a non-Flex Flash project at all- I was under the impression the OP was *very* concerned about size, although that could just've been my (often lax) comprehension skills :) Strictly my opinion, but I'd do widgets in AS before I'd touch any mx imports. -Ricky
Re: [flexcoders] Flex dates and time zones.
Dale Fraser wrote: That whole milliseconds past 1970 is a Java thing and has bitten me before, one of many reasons we ditched Java. It's actually a Unix thing: http://en.wikipedia.org/wiki/Unix_time The standard has been around for almost 40 years. -Ricky
[flexcoders] HTTPService and response headers
This topic has probably been beaten to death, but I want to make sure I'm not missing something before writing a new service. Looking through the API docs and Google it seems the only way to access response headers is to use a proxy. Is this still the case? thanks -Ricky
Re: [flexcoders] Creating a Chart With 50,000 Data Points
Mark Easton wrote: It appears that Flex Charts cannot handle generating charts with large DataSets. We tried with 50,000 data points and it thrashed away without producing a result after 6 minutes. It was able to plot 2,000 points in about 25 seconds. What is the recommended approach for creating charts from large data sets. The best I can think of is to write some code that will reduce the data set in size yet still provide enough data to represent the graph accurately. Thoughts? LoD. Large scale datasets can work the same way computer graphics do. Users don't normally need to see every data point when a summary will do. Provide the user with the minimal amount of information necessary to understand what the data is saying and let them use the interface to drill down into specific areas. This works really well if you pre-calculate and cache the results on the backend (and predictive caching on the front doesn't hurt either). -Ricky
