André - NOW I understand! Thank you! I'm really very happy at the moment with your 3838 build so please don't go to any trouble on my account unless and until you think a fresh build is truly worthwhile.
Thanks also for your explanation of Clang. I'm feeling bowed over by all this so... I'm giving up for the day and going for supper! Cheers buddy! Tim. On 10 Nov 2009, at 18:50, andreb wrote: > @Tim > > Sure I can post binaries. But I don't really think in time frames. > When I develop in my sparetime it happens in spontaneous bursts. > There may even be longer periods where I can't do anything at all > until I am out of a freelance job. > Longest freelance job I had was half a year ;) And that was 18hr > double pressure half a year :) > > But let me say that there isn't much point in trying to build QS > merely to get a workable binary. I don't think that should be the job > of the users. > It makes more sense in my book to post binaries when we have fixed > another issue. Posting nightlies or regularly timed binaries is ok for > projects like Firefox where really a lot happens during one day. > For QS with its handful of devs this just places too much unneeded > strain on the devs. Unneeded because there may not even be that much > that has changed. > Most likely you won't feel difference if we would adopt nightlies. > > That said I will try to post a binary of the current state later on. > > Anyway about Clang. It's a compiler already integrated into Xcode. In > Xcode you can adjust certain settings to tell it which compiler to > use. > Clang is already the default compiler of the source code you > downloaded. > > Mastering compiler error messages and Xcode's tripple cascading build > settings system can be tough if you're just starting out. > I know the feeling :) > > > André > > > On 10 Nov., 19:16, Tim <[email protected]> wrote: >> Gotcha, André but I have just one outstanding query: I don't know how to go >> about compiling / building the app from the binaries I've downloaded. Is >> Clang a command line thing (at which point I don't want to go any further!) >> or is it a downloadable app with a nice, pretty GUI? If the latter, I don't >> mind trying to get my head around it. >> >> I have got XCode because I have it mind to try to write a simple (but >> useful) iPhone app one day when I get the time. I tried to build QS using >> your binaries with that but got loads of errors. >> >> All that said, if periodic (say, weekly or fortnightly) builds of the app >> itself could be made available on github, that would be great for the >> non-tech likes of me! >> >> Tim. >> >> On 10 Nov 2009, at 17:58, Andre Berg wrote: >> >> >> >>> @Tim >> >>> No need to be sorry mate :) >>> It is particularly easy to post binaries to GitHub but that is entirely up >>> to the repo owner. I would do the following: >> >>> Check tiennou/blacktree-alchemy Downloads tab and look at the date of the >>> last item posted. >>> Check andreberg/blacktree-alchemy Downloads tab look at the date of the >>> last item posted. >> >>> Download whichever is more recent. Probably goes without saying but >>> remember to always backup your data first. >>> Details are in the README.markdown about that. >> >>> Now this is important: >> >>> Development will happen distributed as this is the nature of Git. Etiennes >>> repository (tiennou/blacktree-alchemy) will be the main one from which all >>> other developers will download a repo copy ("fork" in git speak) and do >>> their changes on their own copy. When satisfied with their changes >>> developers will ask Etienne to pull from their fork which incorporates the >>> new changes into Etienne's repository. >>> Etiennes repository should always be (in the end) the one which has all >>> changes so this should be your first address to check. It can of course >>> happen that my fork or any other devs fork appears to be newer because I >>> haven't asked Etienne to pull from me yet. That's why I gave the order >>> above. >> >>> NOTE: This also means that effective immediatly >>> github.com/andreberg/Quicksilver-B5X is obsolete and I may delete this repo >>> in the future. >>> As said I will continue my development on my fork of Etienne's repo (where >>> he already was so kind to do the work I should have done and incorporated >>> my changes of github.com/andreberg/Quicksilver-B5X) at >>> github.com/andreberg/blacktree-alchemy. >> >>> This also means that issues should now be posted at >>> github.com/tiennou/blacktree-alchemy. I will post the issues I have >>> recieved at github.com/andreberg/Quicksilver-B5X over at Etienne's repo if >>> the Issue owners don't do it themselves. >> >>> I know this is a bit confusing but we will get behind this :) Took me quite >>> a while to figure out Git too. But once your on top of things it really is >>> so much better for exactly our kind of project. >> >>> André >> >>> 2009/11/10 Tim <[email protected]> >>> Yep - should have said, so very sorry. I removed the icon from the dock >>> (dragged it off the dock) and then went into the QS prefs pane (now that it >>> shows up in your 3838 build, André) where I noticed that the option to show >>> it in the dock was unchecked. Checking it returned the normal / expected >>> behaviour. >> >>> On an entirely different tack, can we expect new builds of the QS.app (the >>> app not the source code) to be made available on the github from time to >>> time as things progress? If so, at which location - 'andreberg' or >>> 'tiennou'? And how would notification of such builds be made? >> >>> Finally (for the moment at least) - I'd like to express my sincere and >>> heartfelt thanks to everyone who's going to such efforts to make QS >>> compatible with SL. It's an indispensable app. to me (I much prefer it to >>> LaunchBar). >> >>> Tim.
