Hi Peter! Thanks for having looked at it. I have written it because I need a easy-accessible place with code snippet. My underlying question was wether some other may find it useful. It is okay if no :-)
The in-image help sucks hard⦠monospaced walls of text, no formatting, no styling, no images, and zero discoverability.
Some ideas â this is food for thought for moving forward, not something that I would expect anyone would do tomorrow:
I agree with you. But there are several use cases here. Any professional application has builtin-help. I usually use the built-in help for useful code snippets (e.g., how to add a gtInspector view for example).
### Simple-ish: online fronted ... ### Complex-ish â¦
Sure, would be great :-)
## 2. Comments for the git help (I've just skimmed through it briefly)
My impression is that it doesn't really describe git in Pharo, which is what we are pushing forâ¦
it is recommanded to tick the checkbox "Initialize this repository with a README". This will ease the initialization of the repository (you will be able to immediately clone your repo).
GitHub is lying, you can clone it regardless
Well.. I am okay living with this lie :-)
- From Pharo you can _only_ save and load your code frmo the harddisk (see the chapter Alternative for more options)
Partially true. It will always go through disk (obviously), but with remote git repo you don't care about the local repo.
Does remote git repo works well on OS X? And more importantly, merging is something that we are still miles away to do it within Pharo, sadly.
To sum it up: you've described how to use filetree:// with Git, which was possible years ago, so I am not entirely sure what's the objective.
The objective is to have a single place with that information, accessible without at looking at videos and browsing mailing list archive :-)
The push for git+pharo is to use git from within Pharo, which means gitfiletree, which allows you to commit, load, diff, push, pull directly from the image.
Yes, that would be great.
So my point is: if we want to provide help for people, we should push them in the correct direction⦠that is towards git IN pharo. If we push them to not actually use git in Pharo, then we will push them away from our objectives.
Yes, but that will take years before getting there. And I need to use it now⦠and this help actually does help me (creating a baseline and configuration are unfortunately still serious challenges). In any case, I will use this Help for me, and will not try to push it. Thanks for having a look at it :-) Cheers, Alexandre
On Sun, May 8, 2016 at 5:01 AM, Alexandre Bergel <alexandre.bergel@me.com> wrote: Hi!
I have written a help to use Git in Pharo. Execute the following:
Metacello new baseline: 'GitHelp'; repository: 'github://bergel/Git-Help:master'; load.
It will load a Help topic, available on the Help Browser. If you wish to contribute: https://github.com/bergel/Git-Help
One some point, I will propose an inclusion in the base image.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.