[Cuis-dev] Porting from Pharo

[Gerald Klix]

Thank you for for helping with tips!

I gave up on it.

I does not work on Pharo 8,7 and 6, at least not
out of the box. I did not try Pharo 5, I was
to peeved to (re)install 32-bit compatibility
libraries on my Ubuntu 18.04.


Lessons learned:

Pharo's motto is obviously MS' old mantra:
"Portability is for kayaks".

There is no use in not forking Pharo Code,
because you have to fork your code just to
be compatible between the different Pharo
versions.
I am pretty sure, Dr.Geo's developers can
elaborate on that topic.

--- Important --
Lesson for Haver's module system:
I had "wonderful" 20 minutes in guessing which
repo-format to choose to load that package.
I just wanted to work with it.

*Haver needs an auto-import feature for modules*

Users just want to work on their problems
and not on some bureaucratic conventions,
which might be necessary for really
large projects.


Yours ever ranting,

Gerald



On 2021-05-02 11:50, Douglas Brebner via Cuis-dev wrote:
> On 02/05/2021 07:15, Gerald Klix via Cuis-dev wrote:
>> Perhaps revealing my intentions is best:
>>
>> I want have some tool to distribute updates
>> and maybe applications. I ran across this Smalltalk BitTorrent 
>> implementation:
>>
>> https://github.com/dgraciac/BitTalk
>>
>> I had the intention of porting it to Cuis.
>> I think a forking port/porting fork (sorry
>> couldn't resist that pun) is ok,
>> it wasn't updated for nearly to years.
>>
>> Now I am under the impression, it isn't
>> trackerless, therefore I am not sure anymore.
>> So I will give it a spin on Pharo and
>> see how it works.
>>
> I had a quick look at this and it appears to be in filetree/cypress 
> format which was a cross-dialect export format developed at Camp Smalltalk.
> 
> There's an implementation of cypress here 
> (https://github.com/CampSmalltalk/cuis-cypress) though I don't know how 
> up to date it is.
> 
> Regarding portability, I think the ANSI standard is all we really have.
> 
>