INTERNSHIP PROJECT: Writing Coding in Different Languages for LBTCftCL about community HOT 25 CLOSED

@shannona I can take the lead to complete the Python section.

from community.

I can lead the completion of the NodeJS section. I can also help out with the Golang section.

from community.

Great. Tag me when you have a section complete & submit a PR. It'll sometimes take me a few days to get back. I'll offer some comments in the short-term, and will then do a full polish way down the road when I complete the big upgrade of the rest of the book.

Looking forward to seeing the material!

from community.

@shannona Take a look. I'm deepening in Create a transaction section.
https://github.com/javiervargas/Accesing_Bitcoind_with_Java/blob/master/18_2_Accessing_Bitcoind_with_Java.md

from community.

@shannona I can take the lead to complete the Python section.

Can help here.

from community.

Sure, I'll be submitting a PR soon for the Node.js and Go sections.

The usage code in the README for bcrpc didn't work so I fixed it and submitted a PR. This is my bcrpc fork with the fix: https://github.com/gg2001/bcrpc.

from community.

I can lead the completion of the Java section.

from community.

@javiervargas So you inherited a previously written section that could use your work. Definitely feel free to revise what's there as much as you see fit.

Here's some ways you could clean up the previous sections that you inherited:

1. I'm a bit confused at Maven vs gradle, and this might just be my personal inexperience with Java. But we show the package installation for Maven, and then it looks like gradle comes out of nowhere. Is that because it's a default (if so we should mention it) or is that because it's an alternative (if so, we should show how to get it)?

2. This isn't quite laid out in the organization I suggest (see the major and minor sections in the outline, with the major sections being what's missing), but that's easy enough to change.

3. I can't tell what's actually being done in "Look Up an Address". It seems to offer a function then set an address. Maybe we could show its usage and output?

4. Similarly, "Create a Transaction" shows a function but now how to use it, and not how that connects with the "Send a Transaction" in the next section. (I don't even know what the second argument in sendToAddress is, though my guess is BTCs.

[Generally, we can always add brief explanation about what's being done.]

The summary you created is fine. If you're able to help polish things up (or change them, as you see fit), above, we can have a fine chapter here.

from community.

So far I've heard:

Go @gg2001
Java @javiervargas
NodeJS @gg2001
Python @jodobear [help from @cprkrn ? ; you two should discuss]
Rust (unwritten)
Swift (unwritten)

Thanks folks!

from community.

@shannona I can take the lead to complete the Python section.

Can help here.

Cool! I've already starrted writing it, will share and let's take it from there

from community.

@javiervargas So you inherited a previously written section that could use your work. Definitely feel free to revise what's there as much as you see fit.

Here's some ways you could clean up the previous sections that you inherited:

1. I'm a bit confused at Maven vs gradle, and this might just be my personal inexperience with Java. But we show the package installation for Maven, and then it looks like gradle comes out of nowhere. Is that because it's a default (if so we should mention it) or is that because it's an alternative (if so, we should show how to get it)?
2. This isn't quite laid out in the organization I suggest (see the major and minor sections in the outline, with the major sections being what's missing), but that's easy enough to change.
3. I can't tell what's actually being done in "Look Up an Address". It seems to offer a function then set an address. Maybe we could show its usage and output?
4. Similarly, "Create a Transaction" shows a function but now how to use it, and not how that connects with the "Send a Transaction" in the next section. (I don't even know what the second argument in sendToAddress is, though my guess is BTCs.

[Generally, we can always add brief explanation about what's being done.]

The summary you created is fine. If you're able to help polish things up (or change them, as you see fit), above, we can have a fine chapter here.

1. In that case I should create a maven project and show results and outputs. You're right, I understand gradle it's an alternative.
2. OK,
3. Same as case 1, I'll create methods for lookup an address and create a raw.
4. I'll try to connect create and send tx and show output. Hope have it this weekend.

from community.

@shannona I've add more code and outputs to sections and completed others. Take a look and tell me if it's ready to merge.

https://github.com/javiervargas/Accesing_Bitcoind_with_Java/blob/master/18_2_Accessing_Bitcoind_with_Java.md

from community.

@shannona I've add more code and outputs to sections and completed others. Take a look and tell me if it's ready to merge.

https://github.com/javiervargas/Accesing_Bitcoind_with_Java/blob/master/18_2_Accessing_Bitcoind_with_Java.md

Looks great. I have one request:

You "List generatedBlocksHashes = rpcClient.generateToAddress(110, addr1);" but don't really explain what that's doing. If you can add some explanation of that, I think this is ready to PR.

Thanks!

from community.

Great!!

Ok, I’ll check it and add it.

from community.

Thanks, @javiervargas I've merged the Java content. Is "Javier Vargas" the correct credit for you?

from community.

And thanks to @jodobear I've merged in the Python section.

from community.

Thanks, @javiervargas I've merged the Java content. Is "Javier Vargas" the correct credit for you?

It's Ok!, thanks!.

from community.

A Note for is someone picks up the SWIFT section: we should consider basing it on (or referencing) the code in FullyNoded2.

from community.

@shannona I've completed the JavaScript section and I'm almost done with the Go section. I've submitted a pull request.

from community.

@gg2001, terrific, this was a very pleasant surprise!

I've looked it over and offered a general style suggestion that I think could help polish this up and make it an improved teaching piece.

from community.

Rust (unwritten)

I'll write this. Written.

from community.

@shannona I've completed last C section and I've submitted a PR.

from community.

Hey Folks,

Thanks for all the great work on this. Here's the current status:

Go: Drafted by @gg2001, revisions requested
Java: Updated by @javiervargas (DONE)
NodeJS: Drafted by @gg2001, revisions requested
Python: Written by @jodobear (DONE)
Rust: Written by @gorazdko (DONE)
Swift: Unwritten, but @Fonta1n3 has provided a basis at Issue #137

from community.

@shannona I just made some revisions to the Go and NodeJS sections.

from community.

We've got this fully completed as Chapter 17 (https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/17_0_Talking_to_Bitcoind_Other.md), which has been released under v2.0 of Learning Bitcoin.

Thanks for all intern updates to Learning Bitcoin: gg2001 (Go, Node.js sections), gorazdko (Rust section), Javier Vargas (C, Java, Lightning, Tor sections), jodobear (Appendix: Compiling Bitcoin, Python section). I wrote Swift, thanks to that code snipped supplied by Fonta1n3.

from community.