- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Can Monticello version message be a Text?

by Thierry Goubier

Le 06/04/2015 19:37, Yuriy Tymchuk a Ã©crit : > I guess so. Also partially because how monticello works and how > komitter uses it. As far as I understand, Komitter generates a diff, > then you select which changes you want to commit and then it somehow > commits the ancestor with selected changes applied. So if you say > that the actual ancestor in a wrong one and user will deselect some > changes - Komitter will commit the old thing + selected new changes. Then I don't understand, because: - git, and gitfiletree, doesn't give a damn about the ancestry. The full package is written to disk; ancestry and diff is determined later, by reading from the repository. - The only thing I could understand would be that komitter shows you the diff to a given version (say v.X), let you select which changes are applied, then read the top version from a repo (say v.Y) and apply the diff to it. > Maybe itâs a problem of Komitter. On the other hand maybe doing it > correctly is too complicated because of how monticello works. As described, I don't see any difficulty, really. I'll look into Komitter to see what it does (and how it does it). Thierry

April 6, 2015

Re: [Pharo-dev] UpdatedPharoByExample for 3.0, 4.0, 5.0

by Sean P. DeNigris

stepharo wrote > My point is... Just plain time to update the contents. Iâm not suggesting we commit to maintain previous versions. But simply place a flag in the ground before we start to update for the next version. ----- Cheers, Sean -- View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514p48178… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 6, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Yuriy Tymchuk

I guess so. Also partially because how monticello works and how komitter uses it. As far as I understand, Komitter generates a diff, then you select which changes you want to commit and then it somehow commits the ancestor with selected changes applied. So if you say that the actual ancestor in a wrong one and user will deselect some changes - Komitter will commit the old thing + selected new changes. Maybe itâs a problem of Komitter. On the other hand maybe doing it correctly is too complicated because of how monticello works. Uko > On 06 Apr 2015, at 18:58, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Uko, > > Le 06/04/2015 18:48, Yuriy Tymchuk a Ã©crit : >> Actually there is a bigger problemâ¦ Because of hot gitfiletree finds >> the ancestor (which is one of the previous ancestors) Komitter >> commits the changes related to that ancestor. >> >> E.g. it shows you that youâve added two methods (while in fact youâve >> modified them, but they were not present in the previous ancestor) >> and you select to commit only one of them, then one method will be >> committed and one deleted. > > Can you explain a bit? Is it because GitFileTree only uses git to determine the ancestors? > > Thierry >

April 6, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Thierry Goubier

Hi Uko, Le 06/04/2015 18:48, Yuriy Tymchuk a Ã©crit : > Actually there is a bigger problemâ¦ Because of hot gitfiletree finds > the ancestor (which is one of the previous ancestors) Komitter > commits the changes related to that ancestor. > > E.g. it shows you that youâve added two methods (while in fact youâve > modified them, but they were not present in the previous ancestor) > and you select to commit only one of them, then one method will be > committed and one deleted. Can you explain a bit? Is it because GitFileTree only uses git to determine the ancestors? Thierry

April 6, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Yuriy Tymchuk

Actually there is a bigger problemâ¦ Because of hot gitfiletree finds the ancestor (which is one of the previous ancestors) Komitter commits the changes related to that ancestor. E.g. it shows you that youâve added two methods (while in fact youâve modified them, but they were not present in the previous ancestor) and you select to commit only one of them, then one method will be committed and one deleted. Uko > On 06 Apr 2015, at 17:51, stepharo <stepharo(a)free.fr> wrote: > > please fix Komitter :) > > > Le 6/4/15 13:44, Yuriy Tymchuk a Ã©crit : >> Hi, in gitfiletree there is a piece of code like this: >> >> aVersion info message convertToSystemString >> >> But if you commit using Komitter `aVersion info message` is an instance of Text. Is this ok? I.e. should we fix Komitter to assign String as version message, or should gitfiletree convert message to string explicitly? >> > >

April 6, 2015

Re: [Pharo-dev] Spotter

by Esteban Lorenzano

> On 06 Apr 2015, at 18:06, stepharo <stepharo(a)free.fr> wrote: > > >>> On 05 Apr 2015, at 17:37, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >>> >>> aliaksei >>> >>> what would be nice is that each time we click on a button or press a command key >>> you emit a growl notification with the description. >> >> for debug, I suppose? > > To learn the key combinaison. > You could make sure that after a couple of the same use you do not show it anymore. >> because otherwise is too much pollutionâ¦ tooltips are created for that and I think they do right their job. >> > Emacs is doing that really well. > How to learn key-bindings.... simple show them to the user. some time ago I suggested Guille implement something like that. But not a growl announcement, that would be too disruptive: just like an emacs menuâ¦ there were some problems at the moment to implement it (and the fact that he was doing his phd and I was, as always, running with something else didnât helped). cheers, Esteban > > Stef

April 6, 2015

Re: [Pharo-dev] Spotter

by stepharo

>> On 05 Apr 2015, at 17:37, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> aliaksei >> >> what would be nice is that each time we click on a button or press a >> command key >> you emit a growl notification with the description. > > for debug, I suppose? To learn the key combinaison. You could make sure that after a couple of the same use you do not show it anymore. > because otherwise is too much pollutionâ¦ tooltips are created for that > and I think they do right their job. > Emacs is doing that really well. How to learn key-bindings.... simple show them to the user. Stef

April 6, 2015

Re: [Pharo-dev] UpdatedPharoByExample for 3.0, 4.0, 5.0

by stepharo

My point is not related to technical issues. Just plain time to update the contents. Stef Le 4/4/15 16:19, Sean P. DeNigris a Ã©crit : > stepharo wrote >> there is a huge time / energy investment problems. > I don't see it. The simplest thing (which is 0 extra work AFAICT) would be > to tag the last version before we start updating for 5.0 as something like > 'Pharo-4-final'. Almost as easy would be to have a branch per version, so > e.g. typos could be merged back if someone was interested. But maybe I'm > missing something - where specifically do you see the time & energy > investment? Because I think we could've set it up in less time than it took > me to write this reply! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514p48175… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 6, 2015

Re: [Pharo-dev] MySQL driver

by nacho

This is great news. I'm struggling too with MySQL in Pharo. Filling the Poll right now! thanks *Lic. Ignacio Sniechowski, MBA* *Prosavic SRL* *Tel: (011) 4542-6714* On Mon, Apr 6, 2015 at 12:41 PM, Pharo Smalltalk Developers mailing list [via Smalltalk] <ml-node+s1294792n4817841h64(a)n4.nabble.com> wrote: > Often times, I have to work with Smalltalk (pick your favorite one) and > MySQL. I have to deal with multiple versions of MySQL and, unfortunately, > incompatible code between Squeak and Pharo. > > I'm thinking of rewriting the MySQL driver to handle different MySQL > versions (3.23 up to 5.7), Squeak (3.x up to 4.6) and Pharo (1.0 up to > 4.0). Obviously, I'd make sure the driver would handle the different MySQL > handshake protocols, password encryption methods and different storage > engines (MyISAM, InnoDB and MEMORY) as well as partitions, MERGE tables and > views and the oooooh-soooo-different behaviors of the ZEROFILL option and > ever-changing server commands (that come and go between versions)! > > I already have a gazillion versions of MySQL servers installed and a bunch > of SUnit tests (for another project of mine) to handle all the subtleties > of those different versions. Is there any interest in such a thing before > I spend (quite) some time on this? > > I created 2 polls to get an idea of what versions of MySQL people use as > well as MySQL & Pharo versions used. Please, fill out the 2 polls at: > > MySQL et Squeak et Pharo > <https://endormitoire.wordpress.com/2015/04/05/mysql-et-squeak-et-pharo/> > > > > [image: image] > <https://endormitoire.wordpress.com/2015/04/05/mysql-et-squeak-et-pharo/> > > > > > > MySQL et Squeak et Pharo > <https://endormitoire.wordpress.com/2015/04/05/mysql-et-squeak-et-pharo/> > Dans l'Ã©ventualitÃ© d'une rÃ©Ã©criture du driver de MySQL pour Squeak et > Pharo, j'aimerais avoir une idÃ©e de ce que les gens utilisent! RÃ©pondez > aux so... > View on endormitoire.wordpress... > <https://endormitoire.wordpress.com/2015/04/05/mysql-et-squeak-et-pharo/> > Preview by Yahoo > > > > P.S. Sorry for the cross posting! > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/MySQL-driver-tp4817841.html > To start a new topic under Pharo Smalltalk Developers, email > ml-node+s1294792n1294837h40(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Developers, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/MySQL-driver-tp4817841p4817844.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 6, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by stepharo

please fix Komitter :) Le 6/4/15 13:44, Yuriy Tymchuk a Ã©crit : > Hi, in gitfiletree there is a piece of code like this: > > aVersion info message convertToSystemString > > But if you commit using Komitter `aVersion info message` is an instance of Text. Is this ok? I.e. should we fix Komitter to assign String as version message, or should gitfiletree convert message to string explicitly? >

April 6, 2015