[Pharo-project] renggli mirror created on smalltalkhub

Dale Henrichs dhenrich at vmware.com
Wed Jul 4 12:30:55 EDT 2012


If you look at the Cypress format[1] (used by FileTree), it is the Monticello package structure "serialized to disk". Reading the Cypress format from disk is no different than materializing the Monticello package structure from an .mcz file. So any program that an reason about the definitions from an .mcz file can reason about the definitions from the Cypress format.

Cypress format may look like text, but to me I see Smalltalk objects:)


[1] https://github.com/CampSmalltalk/Cypress/blob/master/img/CypressStructure-STIC2012.png
----- Original Message -----
| From: "Dennis Schetinin" <chaetal at gmail.com>
| To: Pharo-project at lists.gforge.inria.fr
| Sent: Wednesday, July 4, 2012 6:29:40 AM
| Subject: Re: [Pharo-project] renggli mirror created on smalltalkhub
| On Wednesday, 4 July 2012 г. at 16:11, Damien Cassou wrote:
| On Wed, Jul 4, 2012 at 2:09 PM, Dennis Schetinin < chaetal at gmail.com
| > wrote:
| Am I wrong considering migration to Git-or-AnythingElseTextOriented
| to be a
| give up on hopes for a real object-oriented source control/management
| as it
| could and should be in Smalltalk?
| can you think of any feature we could have now we couldn't with Git?
| I didn't say "now", I talked about "hopes". E.g. hopes for "Source"
| Control Tool being aware of refactorings and other *operations* I
| apply to my program, instead of treating it as a plain text with
| some changes of unknown nature. I'm not sure it's possible right now
| (I know it's not, better to say?). But with a Smalltalk-based source
| control we can have it on one splendid day in the future. And I
| think on the Git way we'll finish with just some advanced
| text-comparison algorithms. No?
| Best regards,
| Dennis Schetinin
| Sent with Sparrow

More information about the Pharo-dev mailing list