[Potlatch-dev] Setting up Adobe Flex project

[Steve Bennett]

On Mon, Dec 13, 2010 at 10:16 PM, Andy Allan <gravitystorm at gmail.com> wrote:
> Same here - the standalone debug player both pops up errors and shows
> them in the terminal window that I launch it from, and there's plenty
> of interesting stuff goes on with trace() calls. I use Kate as my
> editor.

Ah, thanks, will investigate.

>
> While we're talking about coding, I've written down some of the
> conventions we've been using up until now. Descriptive, not
> prescriptive - I'm more interested in consistency than any kind of
> correctness, so I stick to whatever seems most prevalent in the
> file/function that I'm working on.
>
> http://trac.openstreetmap.org/browser/applications/editors/potlatch2/CODING.txt

Seems reasonable*. I once had the luxury of working with a language
that didn't store its source code: instead, it compiled to p-code, and
then de-compiled it the next time you wanted to edit the file. Result:
no more arguments over whitespace, because it effectively enforced a
certain convention. I've often wondered why no one ever got into the
habit of introducing a beautify routine into version control systems -
get rid of all the arguments, enforce a per-project standard on every
checkin. (And if you really care, implement your preferred standard on
checkout.)

> Bugfixes like http://trac.openstreetmap.org/changeset/24708 are great
> but we need to avoid making lots of whitespace changes in commits that
> hide the actual code changes.

Whoops. Would you believe I only just figured out how to change the
tab settings in my editor?

Steve
* The 2-character tabs in functions are a bit quirky, but ok. :)