Le 21/10/2015 22:03, Thierry Goubier a écrit :
> > Just use the ConfigurationOfGitFileTree available in your > Configuration browser in the image ;) > > Or > > Metacello new > configuration: 'GitFileTree'; > repository: > 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main'; > load > > Thierry Okay, thanks. Not sure I can handle it right now, there are a lot of know-how about git and fossil implicated. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
2015-10-22 10:40 GMT+02:00 Hilaire <[hidden email]>: Le 21/10/2015 22:03, Thierry Goubier a écrit : Yes, I guess so. Still, with all the people interested by Fossil, I think the motivation is there. And it would be nice to see a bit of refactoring to decouple the format from the specific commands used for the specific VCS. Thierry
|
Le 22/10/2015 10:47, Thierry Goubier a écrit :
> Still, with all the people interested by Fossil, I think the > motivation is there. And it would be nice to see a bit of refactoring > to decouple the format from the specific commands used for the > specific VCS. > Decoupling was my first though looking at the code. So it makes it bigger than a small hack as initially though ;) Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
2015-10-22 11:16 GMT+02:00 Hilaire <[hidden email]>: Le 22/10/2015 10:47, Thierry Goubier a écrit : Of course ;) It started as a small hack and has grown a bit since... Thierry |
In reply to this post by HilaireFernandes
Hilaire, if you are interested in contributing, I would be willing to
add you to the FileTree project up on GitHub ... Oops, unless you don't want to be:) Dale On 10/22/2015 01:40 AM, Hilaire wrote: > Le 21/10/2015 22:03, Thierry Goubier a écrit : >> Just use the ConfigurationOfGitFileTree available in your >> Configuration browser in the image ;) >> >> Or >> >> Metacello new >> configuration: 'GitFileTree'; >> repository: >> 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main'; >> load >> >> Thierry > Okay, thanks. > Not sure I can handle it right now, there are a lot of know-how about > git and fossil implicated. > > Hilaire > |
I will write you if needed, I am not there yet.
Hilaire Le 22/10/2015 22:51, Dale Henrichs a écrit : > Hilaire, if you are interested in contributing, I would be willing to > add you to the FileTree project up on GitHub ... Oops, unless you > don't want to be:) > > Dale > > On 10/22/2015 01:40 AM, Hilaire wrote: >> Le 21/10/2015 22:03, Thierry Goubier a écrit : >>> Just use the ConfigurationOfGitFileTree available in your >>> Configuration browser in the image ;) >>> >>> Or >>> >>> Metacello new >>> configuration: 'GitFileTree'; >>> repository: >>> 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main'; >>> load >>> >>> Thierry >> Okay, thanks. >> Not sure I can handle it right now, there are a lot of know-how about >> git and fossil implicated. >> >> Hilaire >> > > > -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
In reply to this post by Thierry Goubier
Le 22/10/2015 10:47, Thierry Goubier a écrit :
> Yes, I guess so. > > Still, with all the people interested by Fossil, I think the > motivation is there. And it would be nice to see a bit of refactoring > to decouple the format from the specific commands used for the > specific VCS. > > Thierry I started to look at it creating abstracted super classes. But RB (refactoring tool I guess) bumped on the middle, try again, then went fine, ouf! Any sandbox where to commit? Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
Thierry and Hilaire,
If you want to work together up on the github repo, that's up to you and Hilaire, if you have a github id, let me know and I will add you as a contributor on the project so that you two can work together ... Dale On 10/24/15 6:55 AM, Hilaire wrote: > Le 22/10/2015 10:47, Thierry Goubier a écrit : >> Yes, I guess so. >> >> Still, with all the people interested by Fossil, I think the >> motivation is there. And it would be nice to see a bit of refactoring >> to decouple the format from the specific commands used for the >> specific VCS. >> >> Thierry > I started to look at it creating abstracted super classes. But RB > (refactoring tool I guess) bumped on the middle, try again, then went > fine, ouf! > Any sandbox where to commit? > > Hilaire > |
Hilaire, Dale,
the easiest would be to make a fork of filetree on github, and try from there. But a branch in the main filetree would work just as well, with the added benefit of the travis CI integration (and gitfiletree has tests in there). Running tests locally is often necessary, but setting it up is a bit more involved (but I should have that in a Makefile somewhere). Hilaire, if you prefer a Smalltalkhub project, just do so and I'll make regular merges back into filetree. Thierry Le 24/10/2015 18:04, Dale Henrichs a écrit : > Thierry and Hilaire, > > If you want to work together up on the github repo, that's up to you and > Hilaire, if you have a github id, let me know and I will add you as a > contributor on the project so that you two can work together ... > > Dale > > On 10/24/15 6:55 AM, Hilaire wrote: >> Le 22/10/2015 10:47, Thierry Goubier a écrit : >>> Yes, I guess so. >>> >>> Still, with all the people interested by Fossil, I think the >>> motivation is there. And it would be nice to see a bit of refactoring >>> to decouple the format from the specific commands used for the >>> specific VCS. >>> >>> Thierry >> I started to look at it creating abstracted super classes. But RB >> (refactoring tool I guess) bumped on the middle, try again, then went >> fine, ouf! >> Any sandbox where to commit? >> >> Hilaire >> > > > |
I was not aware filetree need to be modified as well? But wait, I can
use it right now with Fossil, so I am bit lost. Hilaire Le 24/10/2015 18:44, Thierry Goubier a écrit : > Hilaire, Dale, > > the easiest would be to make a fork of filetree on github, and try > from there. But a branch in the main filetree would work just as well, > with the added benefit of the travis CI integration (and gitfiletree > has tests in there). Running tests locally is often necessary, but > setting it up is a bit more involved (but I should have that in a > Makefile somewhere). > > Hilaire, if you prefer a Smalltalkhub project, just do so and I'll > make regular merges back into filetree. > > Thierry -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
Le 24/10/2015 18:56, Hilaire a écrit :
> I was not aware filetree need to be modified as well? But wait, I can > use it right now with Fossil, so I am bit lost. No, no. This is just the development of GitFileTree is integrated inside the main FileTree repository. If you look at https://github.com/dalehenrich/filetree/tree/pharo4.0/repository, you'll find both MonticelloFileTree-Core and MonticelloFileTree-Git (as well as the Tests and the GitTests). Thierry > > Hilaire > > Le 24/10/2015 18:44, Thierry Goubier a écrit : >> Hilaire, Dale, >> >> the easiest would be to make a fork of filetree on github, and try >> from there. But a branch in the main filetree would work just as well, >> with the added benefit of the travis CI integration (and gitfiletree >> has tests in there). Running tests locally is often necessary, but >> setting it up is a bit more involved (but I should have that in a >> Makefile somewhere). >> >> Hilaire, if you prefer a Smalltalkhub project, just do so and I'll >> make regular merges back into filetree. >> >> Thierry > > |
At the end of the day, I would assume that it would be possible to run
travis-ci tests against a fossil repository which would be very useful to have ... but like I said, I'm fine with whatever you guys decide... Dale On 10/24/15 10:12 AM, Thierry Goubier wrote: > Le 24/10/2015 18:56, Hilaire a écrit : >> I was not aware filetree need to be modified as well? But wait, I can >> use it right now with Fossil, so I am bit lost. > > No, no. This is just the development of GitFileTree is integrated > inside the main FileTree repository. > > If you look at > https://github.com/dalehenrich/filetree/tree/pharo4.0/repository, > you'll find both MonticelloFileTree-Core and MonticelloFileTree-Git > (as well as the Tests and the GitTests). > > Thierry > >> >> Hilaire >> >> Le 24/10/2015 18:44, Thierry Goubier a écrit : >>> Hilaire, Dale, >>> >>> the easiest would be to make a fork of filetree on github, and try >>> from there. But a branch in the main filetree would work just as well, >>> with the added benefit of the travis CI integration (and gitfiletree >>> has tests in there). Running tests locally is often necessary, but >>> setting it up is a bit more involved (but I should have that in a >>> Makefile somewhere). >>> >>> Hilaire, if you prefer a Smalltalkhub project, just do so and I'll >>> make regular merges back into filetree. >>> >>> Thierry >> >> > > |
In reply to this post by Thierry Goubier
Le 24/10/2015 18:44, Thierry Goubier a écrit :
> Hilaire, if you prefer a Smalltalkhub project, just do so and I'll > make regular merges back into filetree. I commited to SqueakSource a few abstractions WIP http://ss3.gemstone.com/ss/istoa/ I more or less randomly abstracted the classes but can't test, I don't know much GIT. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
2015-10-29 10:26 GMT+01:00 Hilaire <[hidden email]>: Le 24/10/2015 18:44, Thierry Goubier a écrit : Thanks. I'll have a look, make an issue on github, a branch, merge your changes and travis will test for us ;) Thierry |
In reply to this post by HilaireFernandes
> Stef, > > There is no problem. > I just *lack time* to keep moving on DrGeo features and migrate to > Pharo4.0 at the same time. > > I quickly try Dr. Geo code on Pharo4 and realize it will need some work > and lot of user testing to get DrGeo as robust as it is now. We will > conduct end user experiment in primary school, so I don't think > migrating now will be a good idea. > > I will very likely skip directly to Pharo 5.0, as I did from 1.4 to > Pharo 3.0 directly. I understand :) > > Hilaire > > Le 20/10/2015 16:02, stepharo a écrit : >> Hilaire >> >> what is the problem that you encounter to still be in Pharo3.0? >> >> Stef >> >> >> Le 20/10/15 12:13, Hilaire a écrit : >>> Le 20/10/2015 11:20, Thierry Goubier a écrit : >>>> So it looks very similar to a filetree + git workflow ? >>>> >>>> Any taker on adding a fossil interface to filetree with the same >>>> approach as GitFileTree ? >>>> >>>> Thierry >>> Which version of GitFileTree should I take for Pharo3? >>> >>> Hilaire >>> >> >> > |
In reply to this post by HilaireFernandes
On Uto, 2015-10-20 at 11:09 +0200, Hilaire wrote:
Hello, potential Pharo user here who just installed 5.0 image on his Debian Sid and researching whether Smalltalk (Pharo) can be used as language for writing some multi-platform opens-source apps...tried/evaluated several languages, but, considering I abandon idea to use {C(++), Java}, the the most pragmatical option so far is to use Object Pascal and FPC/Lazarus(fpGUI), but someone recommended to inspect Smalltalk (I was tinkering with Digitalk looooooong ago while using OS2)... > I have been trying Fossil with Filetree, and I was rather please by > the mutuals use of these tools. So I may share a few feedbacks. > Fossil[1] itself is a software to manage source code development. It > is very simple to install and data is saved in a single sqlite > database. It comes with source code management, bug tracker, web > interface, wiki and timeline tools. so I'm delighted to see the talk about using Fossil for VCS tool with Pharo. > So all in all, it is pretty nice if one want to move to a private > souce code management system with very little requirement. For those Git-lovers, there is plan by Dr Richard Hipp (author of Fossil) to provide support which "would allow you to "clone" repos off of GitHub. Or to automatically sync your Fossil repositories on GitHub." (http://article.gmane.org/gmane.comp.version-control.fossil-scm .devel/580) Where can I find more about using Fossil with Pharo? Sincerely, Gour -- He who is regulated in his habits of eating, sleeping, recreation and work can mitigate all material pains by practicing the yoga system. |
Hello,
As for now, you have to use filetree, over fossil repo, but from Pharo you can only save to the repo, no way to fetch back I think. The GIT integration is more advanced with dedicated GIT package for Pharo. As a first iteration, I did some code modifications -- blindly I have to admit -- of the GIT package to decouple it from GIT, to later add fossil capability. Thierry was looking at integrating it in Jenkins job, to see if it is working or not. But if you are potential Pharo users, you should not waste your time on the CVS question but discover first the Pharo language and environment. There are other CVS options for Pharo you can use out of the box. Hilaire >> So all in all, it is pretty nice if one want to move to a private >> souce code management system with very little requirement. > > Where can I find more about using Fossil with Pharo? > > Sincerely, > Gour > -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
In reply to this post by Gour
Le 22/12/15 11:39, Saša Janiška a écrit : > On Uto, 2015-10-20 at 11:09 +0200, Hilaire wrote: > > Hello, > > potential Pharo user here who just installed 5.0 image on his Debian Sid > and researching whether Smalltalk (Pharo) can be used as language for > writing some multi-platform opens-source apps... Yes it does > tried/evaluated several > languages, but, considering I abandon idea to use {C(++), Java}, the the > most pragmatical option so far is to use Object Pascal and > FPC/Lazarus(fpGUI), Pharo is really working on multi-platforms for real. > but someone recommended to inspect Smalltalk (I was > tinkering with Digitalk looooooong ago while using OS2)... Pay attention Pharo 50 is alpha. >> I have been trying Fossil with Filetree, and I was rather please by >> the mutuals use of these tools. So I may share a few feedbacks. >> Fossil[1] itself is a software to manage source code development. It >> is very simple to install and data is saved in a single sqlite >> database. It comes with source code management, bug tracker, web >> interface, wiki and timeline tools. > so I'm delighted to see the talk about using Fossil for VCS tool with > Pharo. > >> So all in all, it is pretty nice if one want to move to a private >> souce code management system with very little requirement. > For those Git-lovers, there is plan by Dr Richard Hipp (author of > Fossil) to provide support which "would allow you to "clone" repos off > of GitHub. Or to automatically sync your Fossil repositories on > GitHub." (http://article.gmane.org/gmane.comp.version-control.fossil-scm > .devel/580) Yes this is a smart move > > Where can I find more about using Fossil with Pharo? > > Sincerely, > Gour > |
In reply to this post by HilaireFernandes
On Uto, 2015-12-22 at 15:23 +0100, Hilaire wrote:
> As for now, you have to use filetree, over fossil repo, but from Pharo > you can only save to the repo, no way to fetch back I think. OK. > But if you are potential Pharo users, you should not waste your time > on the CVS question but discover first the Pharo language and > environment. Sure, I'm really excited about it and exploring further. However, it's nice to find users within Pharo community who can see the merits of Fossil DVCS. Sincerely, Gour -- He is a perfect yogī who, by comparison to his own self, sees the true equality of all beings, in both their happiness and their distress, O Arjuna! |
On Wed, Dec 23, 2015 at 09:38:20AM +0100, Saša Janiška wrote:
> Sure, I'm really excited about it and exploring further. However, it's > nice to find users within Pharo community who can see the merits of > Fossil DVCS. I use Fossil as personal wiki, VCS for config files, and ticketing system. I like it very much. For now I'm not bothered about integrating Fossil as a Pharo VCS though. I just use Monticello. Pierce |
Free forum by Nabble | Edit this page |