Le 10 nov. 2009 à 10:56, andreb a écrit :
@Etienne That is good news indeed. I was getting nowhere with a commit (I must have been doing something wrong in the process up to then or it is because I didnt fork directly but added a remote and fetch) and had to put it on the backburner because I have been booked for a freelance job. So, sure if you already have all my commits on top of yours there's no point in me doing the same. I can fork or pull from you then. If you don't mind, can you include my README.markdown for GitHub? I think having some more explanation about building in there helps new devs such as myself. Throw the legal bit out if clashes with QS' existing paradigm.
Done. Had a hard time with cherry-picking though ;-). There's two commits I didn't include : bc7e2f323d5eae6162a1f43ac97d18b2e51547c5 and 9a56476e6dbe6d5fe48bdf35914fd6a005dcac8b, since GitHub is now our common repo. No problem with the License, we're under Apache License v2 anyway (if you ignore the old headers in source files ;-)).
We are still at around 125 warnings though. Most are still deprecation stuff and stuff from the NTViewLocalizer which would confuse any compiler.
Quick note about NTViewLocalizer: ...which is utterly useless, as far as I can remember. It's used for on-the-fly translation of the interface (as in, no need to duplicate every NIB file for every localization), but it's not used since it's main entry point is currently disabled.
@ Rob I guess the preferred way of posting issues may now be over at github.com/tiennou/blacktree-alchemy under the Issues tab. Or we just continue the issues tracker over at Google Code. It's really Etienne's decision as Etiennie's repo now will be the main one once again. Personally I wouldn't mind continuing at GC but I wouldn't underestimate having the code and the issue tracker in one place.
The GC issue tracker is a pain for me. People add reports but nothing tells you they just did, so they sit along, waiting for me to batch- assign them to me. People can't change the state of issues. Multiply all this with the fact that non-developer _love_ duplicate reports... I'm pretty sure I'll love the GitHub tracker, though I haven't used it yet.
Etienne
