<div dir="ltr"><div><div><div>Hi Chris,<br><br>Since you cannot figure out GitHub, you could instead zip up your code folder and send as an attachment for us to look at.<br><br></div>Regards,<br></div>Curtis<br><br></div>P.S. To fix any problems, we can fork your current GitHub project and push the code into our fork...<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 3, 2013 at 6:26 AM, Chris <span dir="ltr"><<a href="mailto:christopher.coulon@gmail.com" target="_blank">christopher.coulon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Curtis and Johannes,<br>
<br>
I have studied all the lessons suggested below and taken them as far as I could go with them. For example, in Working with repositories example, I can fork the Spoon-Knife project to my account, but I cannot clone it, because there is no "Clone on Mac" button anywhere on the page. There is a "Clone in Desktop" button, but that just takes me to the <a href="http://mac.github.com" target="_blank">mac.github.com</a> page for downloading GitHub for Mac, which I already have. So I cannot do the clone and therefore I cannot go any further with the tutorial. I can and have read the tutorials beyond, but I cannot do any of the examples beyond the cloning part.<br>
<br>
As a result, I am unable to work with my project. I have the errors that package org.jdesktop.layout does not exist, although I suspect swing-layout-1.0.4 (which contains org.jdesktop.layout) does exist because the project ran before I removed the APC_ dependency in my pom.<br>
<br>
I would love to be able to clone my project and resolve the errors, but the tutorials do not match what I see in my github page, and I don't have enough information to know why and resolve these issues.<br>
<span class="HOEnZb"><font color="#888888"><br>
Chris<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Jun 27, 2013, at 2:31 PM, Johannes Schindelin wrote:<br>
<br>
> Hi Chris,<br>
><br>
> On Thu, 27 Jun 2013, Chris wrote:<br>
><br>
>>>> I need instructions on how to do steps B through E.<br>
>>><br>
>>> You already have the clone on your workstation. You wouldn't have been<br>
>>> able to push the README otherwise. You probably ran "git init" which<br>
>>> actually *creates* the repository on your workstation, and then you<br>
>>> ran "git push" which mirrors it back to GitHub. So you don't need to<br>
>>> clone in that case; you already have a copy of the repo, since the<br>
>>> workstation is where you created it.<br>
>><br>
>> OK, but I created the README on the website<br>
>> (<a href="https://github.com/ad1054/Postcards" target="_blank">https://github.com/ad1054/Postcards</a>), not with a terminal command.<br>
><br>
> Yep, that was not exactly what that page said, was it? It can be fixed,<br>
> but it requires more effort on your side than if you had not created the<br>
> files on the website.<br>
><br>
>> When I then went through the instructions and tried to create the<br>
>> Hello-World README from the terminal, that's when I got the errors.<br>
><br>
> Multiple errors, because you had to understand the commands listed in the<br>
> article in order to adapt them to your particular case.<br>
><br>
> For one, your repository is not called Hello-World.<br>
><br>
> Another problem is that you did not know how to undo an already-run<br>
> command (git remote add ...).<br>
><br>
>> When I click the "clone in desktop" button on the <a href="http://github.com" target="_blank">github.com</a> site, it<br>
>> takes me to the <a href="http://mac.github.com/" target="_blank">http://mac.github.com/</a> site where my only option is to<br>
>> download Git for Mac -- which I already downloaded.<br>
><br>
> ... and which you could use as described on<br>
><br>
> <a href="https://help.github.com/articles/working-with-repositories#cloning" target="_blank">https://help.github.com/articles/working-with-repositories#cloning</a><br>
><br>
> to clone your own GitHub repository.<br>
><br>
>>> Step (D) is "git commit"<br>
><br>
> GitHub for Mac can help you do that, if you study the information conveyed in<br>
><br>
> <a href="https://help.github.com/articles/making-changes" target="_blank">https://help.github.com/articles/making-changes</a><br>
><br>
>>> Step (E) is "git push"<br>
><br>
> This page has the information which you need to learn in order to use<br>
> GitHub for Mac to "push" (which they call synchronize because it is more<br>
> convenient than the "push" concept of Git what they do: they have a<br>
> two-way synchronisation between the remote repository and the local one).<br>
><br>
> <a href="https://help.github.com/articles/making-changes#sync-your-changes-with-github" target="_blank">https://help.github.com/articles/making-changes#sync-your-changes-with-github</a><br>
><br>
>>> The book and other Git tutorials have more information.<br>
>>><br>
>>> You are already really close -- you have the code on your local<br>
>>> workstation, you have a GitHub repository already in existence, you<br>
>>> have a local Git repository linked to that remote repository, so all<br>
>>> you have to do is commit and push.<br>
>>><br>
>>> The errors you mentioned yesterday were because your local Git<br>
>>> repository had the wrong URL for the GitHub remote. That's why I asked<br>
>>> you to check the output of "git remote -v". It should say your origin<br>
>>> is "<a href="https://github.com/ad1054/Postcards" target="_blank">https://github.com/ad1054/Postcards</a>". If it says "Hello-World"<br>
>>> that is wrong. To fix, try this:<br>
>>><br>
>>> git remote rm origin<br>
>>> git remote add origin <a href="https://github.com/ad1054/Postcards" target="_blank">https://github.com/ad1054/Postcards</a><br>
><br>
> Of course it is best if you understand that these commands work *inside*<br>
> one working directory that has remote information.<br>
><br>
>> This is the result of those commands in my terminal:<br>
>><br>
>> ChrisGAIAG:~ chris$ git remote rm origin<br>
>> fatal: Not a git repository (or any of the parent directories): .git<br>
><br>
> Well, what do you expect if you remove the 'origin' remote in your home<br>
> directory, which is not the working directory of the repository you<br>
> initialized with "git init"?<br>
><br>
> I told you in an earlier mail that each local repository lives in a .git/<br>
> subdirectory of the working directory. You created a Hello-World directory<br>
> and made it the working directory of a newly-initialized repository by<br>
> calling<br>
><br>
> git init<br>
><br>
> *inside* Hello-World/. So that is where your Git information is: in<br>
> Hello-World/.git/.<br>
><br>
> Git will not try to guess what you mean if you are outside that directory.<br>
><br>
>> ChrisGAIAG:~ chris$ git remote add origin <a href="https://github.com/ad1054/Postcards" target="_blank">https://github.com/ad1054/Postcards</a><br>
>> fatal: Not a git repository (or any of the parent directories): .git<br>
><br>
> In general, it is a real bad idea to call the second command in any set of<br>
> instructions when the first one failed.<br>
><br>
>> So do I need to cd to some place first?<br>
><br>
> Actually, yes. As described above, Git has no chance of knowing what<br>
> project you want it to work on if you are outside the project's working<br>
> directory.<br>
><br>
> It is even what Git said:<br>
><br>
> fatal: Not a git repository (or any of the parent directories): .git<br>
><br>
> Which is true, because I am sure that there does not exist a .git/<br>
> directory in your home directory.<br>
><br>
>>> Or, as Johannes says: just reclone from your GitHub remote into a new<br>
>>> directory, and then copy your files into there, and then commit and<br>
>>> push using the GitHub for Mac GUI.<br>
>>><br>
>>> Don't worry about "screwing anything up" because you can always just<br>
>>> delete and recreate the repository. It's not like you're going to lose<br>
>>> hundreds of hours of work, here.<br>
>><br>
>> The GitHub for Mac is a complete mystery right now. There is a long<br>
>> list of my java classes and resources, followed at the end with a link<br>
>> to my NetBeans project folder, so I see there is a link to my computer.<br>
>> I guess I am in fact close. I just need to figure out how to commit and<br>
>> push.<br>
><br>
> Well, I think that understanding the information given in<br>
><br>
> <a href="https://help.github.com/articles/making-changes" target="_blank">https://help.github.com/articles/making-changes</a><br>
><br>
> should help.<br>
><br>
>> And of course, resolve the strange errors in my project that can't<br>
>> recognize the Swing components of my jFrames when I removed the APC_<br>
>> class from my pom dependencies. Now when I attempt to run it on my<br>
>> computer, I get this error:<br>
>><br>
>> Exception in thread "main" java.lang.NoClassDefFoundError: org/jdesktop/layout/GroupLayout$Group<br>
>> at A_Postcard.run(A_Postcard.java:25)<br>
>> at A_Postcard.main(A_Postcard.java:35)<br>
>> Caused by: java.lang.ClassNotFoundException: org.jdesktop.layout.GroupLayout$Group<br>
><br>
> Oh, that is a new piece of information. I was left under the impression<br>
> that you built and ran the project inside NetBeans. Apparently not so.<br>
><br>
>> Also, when I was able to run my project, I get an error that it could<br>
>> not find the class "Versatile Wand" which is in my project's<br>
>> target>classes.<br>
><br>
> So you *were* able to run your project in the meantime? I am sorry, but it<br>
> seems that I get incomplete information about the problems and the<br>
> progress on this side.<br>
><br>
> I fear that really, the only way forward that guarantees an efficient use<br>
> of your, Curtis' and my time, is to get familiar enough with Git or GitHub<br>
> for Mac so that you can publish exactly the files with which you have a<br>
> problem.<br>
><br>
> It is my failing that I do not understand from the descriptions what the<br>
> exact invocations and the exact error messages are, and therefore trying<br>
> to help you would only result in super-wild guesses that are unlikely to<br>
> assist you in fixing the issues.<br>
><br>
> The only way I could help effectively would be to be able to get at<br>
> exactly the same state where you are at, to be able to try to reproduce<br>
> your problem, and to fix it by way of a pull request (no need to fear, the<br>
> GitHub notification you receive will have detailed information that, when<br>
> read carefully, will equip you with everything you need to get back my<br>
> changes).<br>
><br>
> Ciao,<br>
> Johannes<br>
<br>
</div></div></blockquote></div><br></div>