Need help putting my Pharo package under source control

I read the section in 2018-09-29-UPDATEDPHAROBYEXAMPLE:

"Monticello packages” just after Figure 3-27

I have a smalltalkhub account and created a repository:
MCHttpRepository
        location: 'http://smalltalkhub.com/mc/MichaelKentBurns/FredsLunch/main'
        user: ''
        password: ‘'

In Pharo I registered this as a new smalltalkhub repository:
'http://smalltalkhub.com/mc/MichaelKentBurns/FredsLunch/main’

And it shows up in the repository list for my package.

Then I think I’m supposed to poke ‘Save’.
It was kind of sketchy and popped up exception dialogs while I was typing my comment, but eventually it worked.

I was able to download the resultant .mcz file and unzip it, then change the ^M to newlines to get a readable source.

I’m not really happy about this process.

I would like to actually save this into my GitHub repository.
The document mentioned at the top mentions using git, but just says:

        There is a chapter in preparation on how to use Git with Pharo. Request it on the Pharo mailing list.

Question 1: Is there such a document?   If so, can you point me to it?

Question 2: Is there a way to fileOut a class, or a package?  

Hi,

Your document is definitely out of date!  The current version of PBE for
version 5, 6, and 7 can be found here:
https://github.com/SquareBracketAssociates/UpdatedPharoByExample/releases

If you're using Pharo 8 or 9, you'll want the updated version, PBE8, which
can be found here:
https://github.com/SquareBracketAssociates/PharoByExample80/releases

Yes, you can FileOut and FileIn.  If you right-click on an item in the
System Browser (which was 'Nautilus' until version 7, when it was replaced
with 'Calypso'), the last fly-out menu has 'FileOut' listed.  (I think you
need to send a message in the Playground to use 'FileIn'; I'm not sure, as,
like most, I don't use it.)

Note that you can no longer (or "shouldn't") use SmalltalkHub; it's
deprecated, and if it's not already locked for modifications, it will be
shortly.  (Then it becomes read-only until late in the year, when the site
will be shut down.)

So you *should* use GitHub.  Since version 7, it's the default repository
for Pharo code.  There is now a native Git client in Pharo called "Iceberg".
It works with GitHub, GitLab, BitBucket, local git repos, and remote git
repos.  You can create git repos, commit/push/pull, submit PRs, etc. from
Iceberg while remaining in the Pharo IDE.

You can read more about Iceberg and managing code here:
https://github.com/SquareBracketAssociates/Booklet-ManagingCode/releases

Have fun!
-Ted






--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Also, regarding keeping your images under control, if you haven't downloaded
and started using Pharo Launcher, you should!  It's a fabulous tool...

http://pharo.org/download



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Thank you for your answer.
The links provided lead me to the project which is nice, but I was not able
to find a fully rendered document. Can you point me at it?



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sorry about that... You should end up on a GitHub "Releases" page for each
document.

In the section for the top-most release, you should see an "> Assets (3)"
control.  Click the arrow to open it.

It should then list a PDF, a ZIP, and a '.tar.gz' document.  You probably
want the PDF, which you can read on the screen and/or print out.

Download the document to your system by clicking on its link.

-t




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

This is the way to get the latest version of any of the booklets, their "work
in progress" (WIP) versions.

https://books.pharo.org/ lists most of the books on a splashy page that
shows cover art, etc., but their versions can be behind the WIP versions.

My experience has been that the WIP versions are preferable.  (Note that not
all booklets that are "in progress" have been submitted to the build process
and resulted in a WIP document  In these cases, you have the option of
cloning the repository and examining each chapter file.)

-t



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

I'm reading the Managing Code booklet.

I'm on page 51 figure 5-6.
I put in my details for my repository (
https://github.com/MichaelKentBurns/FredsLunch-Pharo-iceberg.git ).
when I poke OK I get an exception window.
see image below...

Is there an easier way to capture the exception than a screenshot?

<http://forum.world.st/file/t372658/Screen_Shot_2020-05-12_at_2.png>




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Well, you can capture the stack to the clipboard, and you can save it as a
'Fuel' file.  That allows examination (including by others, within a
different image).

If you look at the image you posted, of the debugger window, on the far
right of "Proceed Restart Into Over Through" there's a small drop-down menu
(with an icon of horizontal bars).  Click on that and you should see options
for 'Fuel out Stack' and 'Copy Stack to Clipboard'.

As far as how to make the best use of this... That's over my head!  (But
others on this forum know.)

-t




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

I should go over it because I was working on the mooc and now I should remove all the discussion about Monticello