Well, this probably needs talking.
Best approach to running with current Amber is indeed "use new project.
move old source by hand". In fact, it is not that bad as it looks, as
many things work as they should.
But if anything does not, it would need an exchange of errors from
console,
Hi Esteban, hi Herbert,
On 22.3.2018 at 12:07 AM, he...@mailbox.sk wrote:
> [...]
> So if tide indeed fills fs with all the needed pieces so it then
only needs a few 'load deps' steps, then
> make it work by hand, then
^^
> simply remove all transient pieces
On March 21, 2018 11:18:42 PM GMT+01:00, in_pharo_us...@nym.hush.com wrote:
>Hi Esteban, hi Herbert,
>
>so, formally, it is a Tide integration issue now, IMHO.
>
>As I understand it now:
>
>Tide's setup procedure generates a file system out of a Monticello
>archive
>and puts Tide related
Hi Esteban, hi Herbert,
so, formally, it is a Tide integration issue now, IMHO.
As I understand it now:
Tide's setup procedure generates a file system out of a Monticello
archive
and puts Tide related extensions for Amber in it. Then the user is
directed to that fs's root
to install Amber.
In newer version of Amber the loading code changed significantly, as
promises are used (best way to migrate old code is to actually created
new project using `amber init` and only move the needed pieces (src/*.st
files, .amd.json files, lists of packages in deploy.js / testing.js /
devel.js /
hi,
no idea :)
as I said this is more a matter for Amber list than Pharo.
but amber maintainer (Herbert) hangs here so he will probably reply if he sees
this :P
Esteban
> On 21 Mar 2018, at 21:42, in_pharo_us...@nym.hush.com wrote:
>
> Hi Esteban,
>
> after I got Amber running separately,
Hi Esteban,
after I got Amber running separately, I set up Tide according to
https://github.com/tide-framework/tide readme.md
Everything went fine so far, but after the page loaded, Helios did not
pop. Blank page.
So I looked into the page source and, suspiciously, at line 18 I
found
