[squeak-dev] The Trunk: Morphic-cmm.1484.mcz

Chris Muller asqueaker at gmail.com
Sat Apr 6 19:42:23 UTC 2019


> On Fri, Apr 05, 2019 at 11:28:46PM -0500, Chris Muller wrote:
> > Hi Dave, we're discussing how to integrate these tools into the IDE
> > more elegantly.  I'd like to hear your thoughts on how we can do that.
> > So far, after much discussion, FIVE proposals* have made it to the
> > table, at least one of which is good with both Jakob and I.
> >
> > 1. Tools or Apps menu.
> > 2. Extending the System workspace
> > 3.  SqueakMap
> > 4. "ensureMetacello" at the top of README's.
> > 5. Include all of it in trunk
> >
>
> I explained my preference in the last email. You can also find it in
> the inbox as System-dtl.1059.

a.k.a., Hannes' proposal 0.

Just curious, why the class check?  MCFileBasedRepository is a
permanent resident in Squeak, and its just encoded in a String so it
doesn't create unwanted package dependency, so...?

> > I appreciate your point about the consistency of Tools items opening a
> > window or not, but this is benign and the Do menu is almost certainly
> > not the university's "final solution" to configuration of github
> > projects.  Its worth discussing how to elegantly include Squeak in
> > these projects.  Please help.
> >
>
> I'm quite interested in the topic of how best to use git with Squeak.
> I see several different approaches in circulation now (in Cuis, in
> Pharo, and the Squit/Squat tools),

and possibly another in the future -- GitQL -- a GraphQL based client
that interfaces directly with github's api.  Github was one of the
earliest and largest adopters of GraphQL, they have a whole team
dedicated to developing and maintaining its API.  I'm planning to look into it.

> and it is not clear to me what is
> best.

Squeak should support all which need to be supported due to legacy
projects.  So if, for example, Cuis' is the best, filetree projects
still need to be supported at least until they can convert, but
probably forever anyway.

> Other people on the list have more experience with this than
> I do, but it seems to be an evolving topic at this point.
>
> I think that the Do menu entries are good enough for now. It's a
> simple solution to a real problem, and they can be easily removed
> when a better approach is established.

Agree, but the only way a better approach will be established, or the
evolving topic evolve, is with positive energy that moves things
forward.

 - Chris


More information about the Squeak-dev mailing list