> > 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 :-)
I understand the purpose, which is very important. I only question the content, whether we really want to push users in that direction. 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). Unfortunately I find the builtin-help very unpractical… I'd much rather look at actual code samples. In fact on Pharo Days this year Andrei did experiments with GTSpotter, and none of the participants (me included) looked at the builtin help, everyone was looking just at real samples of code. Most people do not seek understanding, only solving their problem… which is not bad of itself… but we should address both. 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. I don't see why it wouldn't. There were problems on Windows, but that's related to ProcessWrapper, not gitfiletree. OSSubprocess has maybe fixed that on Windows? Merging will be, unfortunately still a challenge, although GitFileTree-Merger works surprisingly well. But if we push for in-image git, then tools will slowly emerge (as they already do)… if we push users out of the image, then there would be much less incentive. Besides anything that's available to you with FileTree, you also have available with GitFileTree (but not vice versa). The objective is to have a single place with that information, accessible > without at looking at videos and browsing mailing list archive :-) That's why I mentioned centralized front-end for the help with nice search, formatting and everything. Currently achieving this in browser is trivial compared to the work necessary to do it in-image… > 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. It _is_. Present tense. > 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). I've been using gitfiletree for more then year and a half without any (major) issues on gitfiletree side. It may take years to have a really good integration, but even now it's much better than just plain filetree, because you are not losing in-image diffs and history, and because you don't need to use an external tool. In any case, I will use this Help for me, and will not try to push it. Btw. if you need a place to store your snippets, take a look at Torsten's QuickAccess https://www.youtube.com/watch?v=j-dTp6i_P3s . I'm using it a lot and it's super cool for snippets. :) On Sun, May 8, 2016 at 6:31 PM, Alexandre Bergel <[email protected]> wrote: > >> 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. > > +1 > > > > I do not want pharo to be bound to use external merging tools. > > Me neither. But the competition is really though. > > Anyway, let’s see what the future will bring :-) > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >
