[Cuis-dev] Seaside says Welcome on Cuis

Agustin Martinez agustincico at gmail.com
Tue Mar 30 14:17:32 PDT 2021


Hi Nico, great to hear you'll check it out, then tell me what you think.
The main sensitive point I've found so far, where Cuis differs from Squeak,
is in Character and String implementation. But just adding protocol seemed
to solve the issues (protocol that latter could be removed, replacing it by
existing one that addresses the same).
It's worth considering in this porting process the idea of presenting
something as a problem report and submitting it to Seaside.
Thanks!
Agustin

On Tue, Mar 30, 2021 at 2:31 PM Nicolás Papagna Maldonado <
nicolas.papagna at gmail.com> wrote:

> Yay Agustin!
>
> This is a great start!
> Will try to take some time to check it out.
>
> Have you identified any points of contact where Cuis differs from Squeak
> to see if any PR can be submitted to Seaside to make it play nice with both
> of them?
>
> Thanks for sharing!
> Nico PM
>
> On Tue, Mar 30, 2021 at 1:51 PM Agustin Martinez via Cuis-dev <
> cuis-dev at lists.cuis.st> wrote:
>
>> Hello everyone,
>> One day of work and Seaside says welcome, as you can see in the picture
>> it doesn't mean it's working.
>> I have a project I've been doing on cuis and it's sad to move to Squeak
>> (or Pharo) to use Seaside. I am comfortable in Cuis so I give it a shot and
>> it seems possible.
>> The strategy was to port it by brute force, file out from squeak, file in
>> on cuis. First the classes, then some method categories and methods alone
>> (under category *Seaside or so). Luckily there are lots of tests, I make
>> them pass (still a lot to solve) bringing what's necessary from a running
>> Seaside on Squeak (latest version of both). With a couple of these
>> iterations I got this result, not sure how far is the goal.
>>
>> *Is there someone who wants to take a look and give a diagnosis?*
>> *Someone who wants to participate?*
>> *Someone who wants to make some pair programming?*
>>
>> I think we need a mature web tool like this in Cuis, it could be worth
>> joining some forces.
>> I gess the best is to share the software running as I have it. Later,
>> after we make it work on cuis, extract it as packages.
>> Here it is, once you open cuis, http://localhost:8080/ will show the
>> welcome page on your browser:
>>
>> https://wetransfer.com/downloads/96fb36a301a6e75c8fa4c21fedce27db20210330154924/4153f5563b36fcbfe0d7addec253db4a20210330154948/873d9e
>>
>> As you will see, I started with a clean Cuis University (I probably
>> should have started with a clean Cuis). For those who don't know me, I work
>> with Hernán Wilkinson at the University of Buenos Aires, teaching OOP and
>> software design.
>> Best,
>> Agustín
>> --
>> Cuis-dev mailing list
>> Cuis-dev at lists.cuis.st
>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>
>
>
> --
>
> Nicolás Papagna
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20210330/8f11e5f9/attachment.htm>


More information about the Cuis-dev mailing list