Ok - my love affair with Github ends at the wiki - what a load of $%$%^$%…
there is no sane and easy way to fork a wiki, make some changes and then submit
a PR. (how the hell did they get into that state?).
Can we agree to scrap the wiki Iceberg wiki and just have a longer readme.md
(with
completely explained)
> On 28 Jun 2018, at 12:25, Ben Coman wrote:
>
>
>
> On 28 June 2018 at 07:38, Tim Mackinnon <mailto:tim@testit.works>> wrote:
> Hey thanks Ben - this still doesn’t work for me… good idea to try on the
> Pharo repo itself.
>
> I
; On 28 Jun 2018, at 00:46, Tim Mackinnon wrote:
>
> And just to add to this - I just did a git clone (git clone g...@github.com
> <mailto:g...@github.com>:pharo-project/pharo.git) in a fresh directory and
> can see that same deleted file - and when I try to do a checkout, it
ing? I will try it on ubuntu - but I feel
I must be missing something, like do I need a different prefix on path names
(but you didn’t seem to need one)?
I’d be very worried if git is acting up… but I still suspect user error here.
Tim
> On 28 Jun 2018, at 00:38, Tim Mackinnon wrote:
>
ious - but damned if I can see how I’m doing anything different to you. And
it wouldn’t make sense that git is broken on OSX?
Tim
> On 25 Jun 2018, at 14:21, Ben Coman wrote:
>
> On 25 June 2018 at 19:41, Tim Mackinnon <mailto:tim@testit.works>> wrote:
> I’d be really
When we get confirmation of success - we need to make sure this gets applied to
both zeroconf and official downloads.
Anything we can do to simplify and make it robust is gratefully appreciated as
there is nothing worse than falling at the lunch hurdle.
It’s cool to see so many clever minds on
I’ve not noticed that problem on ubuntu or AWS lambda so there must be
something different going on.
Sent from my iPhone
> On 27 Jun 2018, at 07:30, Otto Behrens wrote:
>
> Hi,
>
> I just installed pharo 6.1 using the .zip file
> (http://files.pharo.org/platform/Pharo6.1-64-linux.zip) and
18:14, Tudor Girba wrote:
>
> Hi Tim,
>
> Thanks a lot for the detailed comments! More inline.
>
>
>> On Jun 26, 2018, at 2:57 PM, Tim Mackinnon wrote:
>>
>> Hi Doru - I’ll comment inline below:
>>
>>> On 26 Jun 2018, at 13:05, Tudor Girb
gt;> On 6/26/18, Tim Mackinnon wrote:
>> As I mentioned - the user in question was quite complimentary, just confused
>> on first launch.
>>
>> Equally we don’t want to impact power users, and ultimately we want to
>> encourage everyone to try newer images to help with
Hi Doru - I’ll comment inline below:
> On 26 Jun 2018, at 13:05, Tudor Girba wrote:
>
> Hi,
>
>> On Jun 26, 2018, at 1:16 PM, Tim Mackinnon wrote:
>>
>> Hi guys - not sure how many people noticed this, but at the end of the
>> tutorial for gtDocume
Hi guys - not sure how many people noticed this, but at the end of the tutorial
for gtDocumentor, there is a section on Examples as Documentation.
What is neat (and easily missed) is how when an example references another -
there is a little triangle you can toggle to expose that example
gt; Doru
>
>
>> On Jun 26, 2018, at 12:54 AM, Tim Mackinnon wrote:
>>
>> Hi - so I managed to load up the full monty gtDocumentor into an image (a
>> few false starts as it you try and load the full monty on top of just
>> gtDocumentor e.g in a
>
>> On 26 June 2018 at 06:17, Tim Mackinnon wrote:
>>> Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice
>>> compliments on the state of Pharo (the participants - all ex small talkers
>>> - although ex in so much as they fondly remember
?
This is on OSX with the a 64bit image - labelled 6.1 - 64bit (tech preview) -
so the current stable pharo for 64 bit.
Is this a known issue?
Tim
> On 20 Jun 2018, at 02:53, Tim Mackinnon wrote:
>
> Actually I realised it ended up on the be moose forum - here’s what Doru
> repl
Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice
compliments on the state of Pharo (the participants - all ex small talkers -
although ex in so much as they fondly remembered it and wanted to use it for
something relevant now because they enjoyed it in the past).
Anyway,
A - mouse blindness - glad you pointed that out, it was driving me batty.
> On 25 Jun 2018, at 14:03, Cyril Ferlicot D. wrote:
>
> On 25/06/2018 14:48, Tim Mackinnon wrote:
>> Hi - in Calypso in Pharo 7, there is a neat concept of method changes that
>> are yet sav
Hi - I don’t want to case a UI war, particularly as I was very impressed with
Denis’ presentation about Calypso at the PharoDays conference last year.
Now that I’ve made a concerted effort to try and use Calypso, and in general
like it, I do however find that the bar of Radio Buttons above the
Hi - in Calypso in Pharo 7, there is a neat concept of method changes that are
yet saved (and the top right of the editor has the normal orange smudge
indicator).
I like the idea (which lets you naviaged elsewhere to check something before
making your change) - however if you want to revert
we can rely on
normal git tools in a case of emergency. At the moment, I’m a bit nervous that
we are corrupting something .
Tim
> On 22 Jun 2018, at 01:39, Tim Mackinnon wrote:
>
> Just to add more information to this - I did try what was suggested here (it
> refers to a branch a
Nice - now you’ve really got to work out the details of the competition and how
your going to judge it.
Sent from my iPhone
> On 23 Jun 2018, at 11:07, horrido wrote:
>
> Alan Kay contributed to my campaign! This is so frickin' amazing!
>
> Can we spell S-T-A-R P-O-W-E-R, boys and
Actually, although I appear crazy talking to myself… its true - you have to use
SSH to clone Calypso? Not sure why (other projects have all been fine with
https) but there you go.
Tim
> On 22 Jun 2018, at 17:39, Tim Mackinnon wrote:
>
> Grrr - I think I didn’t have the imag
Grrr - I think I didn’t have the image setting RemoteType set to https in the
image I was trying. False alarm - sorry.
> On 22 Jun 2018, at 17:29, Tim Mackinnon wrote:
>
> Ok - I give up - how do you add Calypso as a project to help contribute to it?
>
> I’ve downloaded the
It seems that you have to use ssh for Calypso - not sure why, but at least I’ve
got a clone now.
> On 22 Jun 2018, at 17:29, Tim Mackinnon wrote:
>
> Ok - I give up - how do you add Calypso as a project to help contribute to it?
>
> I’ve downloaded the latest Pharo 7 image (
Ok - I give up - how do you add Calypso as a project to help contribute to it?
I’ve downloaded the latest Pharo 7 image (1081), and I’ve tried to use the
Github template to load my fork of Calypso. After several read herrings where I
was getting a Github timeout (it turns out that Calypso isn’t
Makes sense - I didn’t scroll enough through the issues… trying to clone the
repo to see how to contribute … ;)
> On 22 Jun 2018, at 16:03, Cyril Ferlicot D. wrote:
>
> On 22/06/2018 16:59, Tim Mackinnon wrote:
>> Hi - In nautilus there was a handy menu item on a class to j
Hi - In nautilus there was a handy menu item on a class to jump to its test
class (and create it if need by) - Is there any easy way to do this in Calypso?
I know it was a simple thing - but I found it did encourage me to write tests…
Tim
the campaign would take off. Star power.
> (Cross my fingers.)
>
>
>
> Tim Mackinnon wrote
>> Hey guys - lets just try and give this some support - I’d like to see
>> something useful come out of it that hopefully can be applied to other
>> countries. I’d really like
Hey guys - lets just try and give this some support - I’d like to see something
useful come out of it that hopefully can be applied to other countries. I’d
really like to see some kids enjoy programming.
I once met one of the original participants of the Parc experiments who was ~14
at the
:36, Ben Coman wrote:
>
>
>
>> On 22 June 2018 at 10:25, Ben Coman wrote:
>>
>>
>>>
>>> > On 21 Jun 2018, at 22:42, Cyril Ferlicot D.
>>> > wrote:
>>> >
>>> > Le 21/06/2018 à 23:18, Tim Mackinnon a écrit
Pharo
class in git?
Tim
> On 21 Jun 2018, at 16:07, Tim Mackinnon wrote:
>
> Guille - just following up on this thread as I’d like to get more confident
> with this stuff.
>
> You mentioned a Calypso plugin for versions - where is that? I loaded a
> recentish P7 image
22:42, Cyril Ferlicot D. wrote:
>
> Le 21/06/2018 à 23:18, Tim Mackinnon a écrit :
>> Hi
>
> Hi,
>
>
> - in the new menu system (which I kind of like, and certainly see the
> value for new user, but worry about the loss of screen space for
> advanced users
Hi - in the new menu system (which I kind of like, and certainly see the value
for new user, but worry about the loss of screen space for advanced users) - is
the order of browsers specified for any particular reason?
I ask, because the 2 main one System and Playground should both be at the top
> - the selected commit and its main parent
>
> Of course any of these can be improved, but if you have concrete requests, it
> is much easier :)
>
> https://github.com/pharo-vcs/iceberg <https://github.com/pharo-vcs/iceberg>
>
> Guille
>
> On Wed, Ju
I noticed that your gofundme update email went into my spam mail box - so I
wasn’t aware it had gone live.
Are you able to apply the funds from your previous campaign (The Ultimate
Smalltalk Tutorial) to this one? As a contributor to that last one - which
unfortunately didn’t manage to deliver
; corruption and recovery services were paid for but not rendered. If you need
> your data to be safe, I'd pick something else.
>
> Sorry if that seems offensive, that's my experience with it.
>
>> On Jun 20, 2018, at 11:13 PM, Tim Mackinnon > <mailto:tim@testit.works>&
I too used it in Dolphin and it was fine, But i don’t think it gets used much
in Pharo and so has probably decayed, isn’t Voyage an object dB or Gemstone?
(Todd & everyone, a gentle reminder to try and leave personality opinions at
the door , we’ve already had another thread that got overly
A simple way is to have a tick box - don’t show me again?
Sent from my iPhone
> On 20 Jun 2018, at 15:08, Sean P. DeNigris wrote:
>
> demarey wrote
>> I just released PharoLauncher 1.2
>
> Thanks!
>
> Warning to users: This new release is based on 64-bit Pharo. This caused a
> bit of
Actually I realised it ended up on the be moose forum - here’s what Doru
replied (for any lurkers)
Sent from my iPhone
> On Jun 18, 2018, at 1:21 PM, Tim Mackinnon wrote:
>
> Guys this is really impressive!
Thanks.
> 2 things I noticed when going through the example in a n
Bump (not sure this got through , and keen to know how to load the diagramming
bit)
Guys this is really impressive!
2 things I noticed when going through the example in a new Pharo 6.1 image
(with the latest Iceberg) -
1) The example "IceRepository repositoriesLocation / 'feenkcom'/
system projects so they don’t get in the way of your own projects.
But then if you accidentally save a method in a system class - how are we going
to spit it and know?
I hate getting burned when you thought you were on a roll
Tim
Sent from my iPhone
> On 20 Jun 2018, at 02:26, Tim Mackin
Hi - so in trying to improve the sendersof/implementors of - I thought I had
nailed it (and got working what I had done in Pharo 6 for Pharo 7) - but when I
loaded my commit into a fresh image I realised that none of the (minor) changes
I had made to Calypso had been committed.
This is
have just that option.
> What we were saying with Esteban is that if you go to the *Repair* and then
> *Create new Branch* you should have it.
>
> But in the main menu you don't have a "Checkout branch" option?
> That's then maybe a bug, I'll check.
>
> On Tue, Jun
-> Create branch
>
> And I have the "New branch" option.
>
> On Tue, Jun 19, 2018 at 3:28 PM Esteban Lorenzano <mailto:esteba...@gmail.com>> wrote:
>
>
>> On 19 Jun 2018, at 15:18, Tim Mackinnon > <mailto:tim@testit.works>> wrote:
with that -
but I think it is handy to create a generic branch so that you can experiment
(while easily tracking your changes)?
Tim
> On 19 Jun 2018, at 14:01, Guillermo Polito wrote:
>
> Hi,
>
> On Tue, Jun 19, 2018 at 2:26 PM Tim Mackinnon <mailto:tim@testit.works>> wrote:
&
Cyril who helped you to commit to ST.
>
> Cheers,
> Christophe.
>
>> Le 18 juin 2018 à 19:20, Tim Mackinnon a écrit :
>>
>> While I’m at it - improve the icon for Launch without Settings (it needed
>> Alpha)
>>
>> Name: PharoLauncher-Core-TimM.174
problems as I don’t have a windows
machine any more.
> On 18 Jun 2018, at 17:35, Tim Mackinnon wrote:
>
> Ok - I’ve done a save for both packages - hopefully they are useful:
>
> Name: PharoLauncher-Spec-TimM.70
> Author: TimM
> Time: 18 June 2018, 5:32:00.928101 pm
> UUID:
2018, 5:34:46.055084 pm
UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd
Ancestors: PharoLauncher-Core-TimM.171
> On 18 Jun 2018, at 16:30, Cyril Ferlicot D. wrote:
>
> On 18/06/2018 17:27, Tim Mackinnon wrote:
>> Hi Cyril - I have to confess that I don’t recall what the steps ar
> On 18 Jun 2018, at 16:20, Cyril Ferlicot D. wrote:
>
> On 18/06/2018 17:15, Tim Mackinnon wrote:
>> Given Pharo Launcher is a bit in the limelight, I’m a bit nervous
>> contributing blindly. Can someone point me/advice me towards how to safely
>> push changes to S
pernickety about nested tables).
Tim
> On 15 Jun 2018, at 22:25, Tim Mackinnon wrote:
>
> Hi Christophe - you are right, I did contribute many years ago (I found the
> Mcz field on my disk when I just checked now) - but I’ll be darned If I can
> remember how it works (I have to c
> Do you have enough balls to call out Steph for his obviously wrong decision
That’s a bit provocative - I think the launcher is pretty good, and helps
ensure people get correct versions of things as well as feel more comfortable
checking out newer Pharo’s (like 7) or other projects. I’ll admit
I don’t think it would make Cincom and instantiations unhappy - they recognise
how Pharo and Oss feed an interesting pipeline - if you need more support or
just commercial backing, they can offer that (not that Pharo can’t - but it’s a
handy symbiotic relationship that seems to work well)
Tim
Not quite the same usecase . But on github it’s a brilliant format for a side
project - I can hack code on the tube on my phone with a build ci server to
report the results when I surface (very lazy programming, but with a family and
limited time - needs must) .
Tim
Sent from my iPhone
> On
Jun 15, 2018, at 2:05 AM, Esteban Lorenzano > <mailto:esteba...@gmail.com>> wrote:
>>
>>
>>
>>> On 15 Jun 2018, at 10:29, Tim Mackinnon >> <mailto:tim@testit.works>> wrote:
>>>
>>>
>>> In many parts of the dev worl
, 2018, at 2:05 AM, Esteban Lorenzano > <mailto:esteba...@gmail.com>> wrote:
>>
>>
>>
>>> On 15 Jun 2018, at 10:29, Tim Mackinnon >> <mailto:tim@testit.works>> wrote:
>>>
>>>
>>> In many parts of the dev world - ever
08:14, Christophe Demarey
> wrote:
>
> Hi Tim,
>
>> Le 14 juin 2018 à 18:48, Tim Mackinnon a écrit :
>>
>> Is PharoLauncher using git - there is a note saying the StHub repo is about
>> to be moved?
>>
>> I ask as I wanted to cont
I think Let’s Encrypt can be your friend (that seems to be the instructions all
of the providers give - e.g.
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04
8 um 13:12 schrieb Thierry Goubier :
>>
>> Hi Norbert, Tim,
>>
>> 2018-06-14 11:33 GMT+02:00 Norbert Hartl :
>>>
>>>
>>>> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon :
>>>>
>>>> Hi - yes I’m pleased you check out t
more sophisticated - as the full atomic commit is the obvious end goal.
Tim
> On 14 Jun 2018, at 12:12, Thierry Goubier wrote:
>
> Hi Norbert, Tim,
>
> 2018-06-14 11:33 GMT+02:00 Norbert Hartl <mailto:norb...@hartl.name>>:
>
>
>> Am 14.06.2018 um 10:30
ote:
>
> Wait... so it is no longer possible to #addtoIndex: external files from
> Pharo? I thought that this functionality was supposed to be preserved.
>
> Peter
>
>> On Thu, Jun 14, 2018 at 10:30 AM, Tim Mackinnon wrote:
>> Hi - yes I’m pleased you check out th
n-memory files (not only text files, right?
> but also any kind of binary file...)
>
> So far we cover the bare minimum that allows us to *not lose* changes :)
>
>> On Wed, Jun 13, 2018 at 11:07 PM Tim Mackinnon wrote:
>>
>> > yeah… but is a lot of work and no t
our current version and the selected commit
> - the selected commit and its main parent
>
> Of course any of these can be improved, but if you have concrete requests, it
> is much easier :)
>
> https://github.com/pharo-vcs/iceberg
>
> Guille
>
>> On Wed, J
elp us along while we work out better ways to do things.
Tim
> On 13 Jun 2018, at 21:53, Sean P. DeNigris wrote:
>
> Tim Mackinnon wrote
>> I didn’t quite get your fu to work
>
> Interesting.
>
> When I searched for commits affecting the deleted class SuDebianK
ep.
>
>>
>> Tim
>>
>> Sent from my iPhone
>>
>>> On 13 Jun 2018, at 21:28, Esteban Lorenzano wrote:
>>>
>>> hi,
>>>
>>>
>>>> On 13 Jun 2018, at 16:50, Tim Mackinnon wrote:
>>>>
>>>>
13 Jun 2018, at 16:50, Tim Mackinnon wrote:
>>
>> Hi - my second attempt at using Pharo with Git has proven very satisfying (I
>> saw the potential in phase 1, but it was often difficult to understand what
>> was happening and the workflow to use).
>>
>&
is the short hash with the
Repository explorer in the new Iceberg shows). So you then get something like
this:
Mon Jun 11 01:33:59 2018 +0100|65363ad|Tim Mackinnon
Refactor to a more consistent design with support for a basic link resolver
delete mode 100644 src/PrismicDemo/PrismicBlock.class.st
Hi - I am interested in what the future holds with Iceberg for things like
finding deleted classes or reverting to older versions of things.
As we tend to use lots of classes in Smalltalk (and view them as cheap) - I
often create them, then move behaviour around and delete things I don’t need
Hi - my second attempt at using Pharo with Git has proven very satisfying (I
saw the potential in phase 1, but it was often difficult to understand what was
happening and the workflow to use).
One thing that has come up a few times for me however - and its something that
using git nicely
elements in the
json - and this is something you can rely on. So, its not really in my control
to do otherwise.
Tim
> On 11 Jun 2018, at 09:19, Tim Mackinnon wrote:
>
> Yes i was a bit nervous about the ordering, but had also noticed other
> examples like this - but it is a good rem
t when it does what do you do? It is pretty clear that the order is
> important for that format. So saying it shouldn’t matter does not make it
> better. If you work with mongo DB you will see the same that for some queries
> you have to provide proper order of keys.
>
&
at format. So saying it shouldn’t matter does not make it
> better. If you work with mongo DB you will see the same that for some queries
> you have to provide proper order of keys.
>
> Norbert
>
>>> On 8 June 2018 at 00:16, Tim Mackinnon wrote:
>>> Thanks guys - it
Ah that’s interesting- it’s happened to me 4 or 5 tines in the last 2 days.
Recent enough that maybe I can figure out a test case I’ll try.
Sent from my iPhone
> On 8 Jun 2018, at 18:57, Steven Costiou wrote:
>
> Concerning the bug 22085, i commented on fogbuzz:
>
>> I believe it is
; On 08/06/2018 08:30, Tim Mackinnon wrote:
>> Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup that
>> if I restart a method in the debugger - particularly from a breakpoint or
>> correcting a dnu issue the environment frequently locks up. Fearing the
I should also mention these extra debuggers don’t have the stack either, just a
single dnu method.
Tim
Ps thank god for close windows to right. ...
Sent from my iPhone
> On 8 Jun 2018, at 12:30, Tim Mackinnon wrote:
>
> Hi, I’ve noticed lately when using a reasonably recent Pharo
Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup that if
I restart a method in the debugger - particularly from a breakpoint or
correcting a dnu issue the environment frequently locks up. Fearing the worst
(after a few seconds), if I repeatedly press cmd . (Say 5 times)
anything.
>
> Peter
>
> On Thu, Jun 7, 2018 at 2:20 PM, Tim Mackinnon <mailto:tim@testit.works>> wrote:
> Hi - are the methods like #select:thenCollect: frowned upon?
>
> They seem quite readable , however in using them I’ve noticed that unlike the
> co
ple page with some content."
spans: [ ]
}
-+{ … }
--{
type: "paragraph"
text: "There are 4 rules:"
--spans: [
--{
start: 10
end: 17
type: "strong"
}
]
}
> On 7 Jun 2018, at 21:58, Tim Mackinnon wrote:
>
> Hey thanks - so maybe there are more legs to t
- but they are horrid, filled with tons
on instanceof crap...
I’ve gotten reasonably far but as the structures can be recursive for a cms, I
think I can do much better somehow.
Tim
Sent from my iPhone
> On 7 Jun 2018, at 21:44, Esteban A. Maringolo wrote:
>
>> On 07/06/2018 17:21, T
Hi - is there something I can read/study to get a bit more familiar with Json
mapping? I have read the Pharo enterprise book (chapter 8).
I’ve been using NeoJSONObject but then it occurred to me that maybe I could map
better domain objects directly and simplify things. However it seems that the
Hi - are the methods like #select:thenCollect: frowned upon?
They seem quite readable , however in using them I’ve noticed that unlike the
core methods they done return the result of evaluation (they are missing a ^).
This is a shame, but possibly an oversight?
Tim
Sent from my iPhone
;>> Am 07.06.2018 um 07:29 schrieb Sven Van Caekenberghe :
>>>
>>> Tim,
>>>
>>>> On 7 Jun 2018, at 01:37, Tim Mackinnon wrote:
>>>>
>>>> Hi - I’ve hit some Json where the outputted values (they are field names)
>>>
my earliest post,
>>> I've
>>> looked everywhere in the Mac environment for ways to turn this Mac
>>> behavior
>>> off, with no success.
>>>
>>> Hey, I can live without keyboard shortcuts, but I thought I'd put some
>>> energy int
Hi - I’ve hit some Json where the outputted values (they are field names) are
written out in a specific order - and the author hasn’t chosen to use an array
to represent those fields in a specific order.
{ ‘field1’ : { ….}, ‘field2’: { … } }
I think this is technically incorrect and should be:
Hi Greg - meta is the Cmd key on a Mac.
So you type cmd-shift-f for reformat code in a method, cmd-s to save.
There are some chorded keys - eg cmd-b cmd-m (keep holding the cmd then press b
followed by m) to browse implementers of the selected method.
On Linux the meta key is Ctrl (just an
> P7 will force you to be in the right branch or you will not be able to do…
> almost anything :)
> you can have two (or ten) images opened at once and work on them, but at a
> moment you will need to “repair” each image to commit.
So are we saying that the easiest and less complicated option
Might have been a blip? Works fine for me from the U.K.?
Sent from my iPhone
> On 3 Jun 2018, at 09:39, Bruce O'Neel wrote:
>
> Hi,
>
> Pharo.org and
> http://www.pharo-project.org/news?rss
>
> both give a 503 right now.
>
> cheers
>
> bruce
Hi - what shortcuts don’t work? On my MacBook Pro and also a Mac air with
external keyboard they all seem to work fine? This is Pharo 6.1.
Tim
Sent from my iPhone
> On 2 Jun 2018, at 19:11, Gregg Williams wrote:
>
> I just can't get keyboard shortcuts to work on Mac. I’ve tried a lot of
>
That’s exactly the exploratory attitude we like to see...
I think the code completer is pluggable and can be selected in the settings (I
think there are 2, and their history is probably in this list somewhere), so
you can try your own too.
Tim
Sent from my iPhone
Sent from my iPhone
> On
Hi - I’m slightly ahead of you on that journey - but what I do is press
shift-enter which gives you a great tool called spotter that lets you explore
more interactively. In spotter if you also press cmd-p it will also preview
method source too - so it’s close to what you are asking (and many
Guille - the text reads very well, I’ll try and look at the videos later. I
just submitted a PR to pharo to try and get the contributions text pointing to
the “newer way” so that people don’t get off track (like we did earlier this
week).
(Aside: Its quite nice having these docs in GitHub as
er, but you saw this, right ?
>
> https://github.com/pharo-vcs/iceberg/wiki/Iceberg-glossary
>
>> On 22 May 2018, at 17:23, Tim Mackinnon <tim@testit.works> wrote:
>>
>> Hi - when trying out the new Iceberg with a bunch of developers and
>> explaining the ch
018, at 16:18, Sven Van Caekenberghe <s...@stfx.eu> wrote:
>
> Hi Tim,
>
> Thanks for the detailed/constructive feedback. I am sure it will be helpful.
>
> Sven
>
>> On 22 May 2018, at 17:15, Tim Mackinnon <tim@testit.works> wrote:
>>
>> Hi -
Hi - when trying out the new Iceberg with a bunch of developers and explaining
the challenges of integrating git and files into a smalltalk realm of the image
- there was a lot of interest in how this works.
When you clone - you obviously see a series of files (in Tonel - nice) that are
then
Hi - last night we managed to explore the new contribution process as well as
the new iceberg ui at the U.K. Smalltalk meetup last night.
Not many had seen it before so it was a good test run.
As an initial comment - we need to invest a small amount of time to get the
right docs in places you
Rather than email you could possibly hook in something like datadog or Pingdom
if you expose some metric - to get a timely alert.
Equally you could perhaps trap something in Pharo and write out a fuel file to
an s3 bucket - with s3 you can then trigger an event and they have tools you
can use
)
Tim
Sent from my iPhone
> On 18 May 2018, at 12:00, Tim Mackinnon <tim@testit.works> wrote:
>
> Hi - I’m wondering if anyone has any experience using Pharo in a Remote
> Desktop environment?
>
> Ive been experimenting with MacInCloud.com and running Pharo there -
Hi - I’m wondering if anyone has any experience using Pharo in a Remote Desktop
environment?
Ive been experimenting with MacInCloud.com and running Pharo there - however
I’ve noticed that while it appears to run (and it reasonably performant) after
a few seconds/minutes (I can’t quite work
a nice test report?
I just spotted Seaside isn’t loading cleanly with my RegEx setup - but its
crude.
This has been very fruitful BTW , thanks
Tim
Sent from my iPhone
Sent from my iPhone
> On 16 May 2018, at 19:54, Sean P. DeNigris <s...@clipperadams.com> wrote:
>
> Tim
gh - and by no means is this a
citicism of SmalltalkCI or Gitlab-Smalltalk-CI - both of which help the
community (and me) immensely through providing great examples and knowledgable
people in this stuff.
Tim
> On 16 May 2018, at 02:50, Sean P. DeNigris <s...@clipperadams.com> wrote:
>
> T
with the assets that you have?
I’l have to go back and look again.
Tim
> On 15 May 2018, at 14:25, Sean P. DeNigris <s...@clipperadams.com> wrote:
>
> Tim Mackinnon wrote
>> But I don’t understand how it works on Gitlab
>
> The gitlab-smalltalk-ci project performs three
.com>> wrote:
>
> hi Tim,
>
> you cannot use vm “I” (for Itimer) with iceberg. This timer will kill the SSH
> sockets.
> you need the “threaded” VM (which is the default, for obvious reasons :P).
>
> cheers,
> Esteban
>
>> On 15 May 2018, at
401 - 500 of 766 matches
Mail list logo
