btw this is pharo-dev discussion, redirecting there.
Esteban
> On 7 Nov 2016, at 08:50, Esteban Lorenzano wrote:
>
> We are developing Iceberg… and I know is not enough :)
> Which “unifying tools” are you referring ?
>
> I have followed very close your TOdE development…
We are developing Iceberg… and I know is not enough :)
Which “unifying tools” are you referring ?
I have followed very close your TOdE development… in a moment I was planning a
migration of it for pure-pharo, just… lack of time as always and then later we
started iceberg.
now, we are in the
Am 06.11.2016 21:04 schrieb "Dimitris Chloupis" :
>
> yeah as I said the chapter needs a complete rewrite. I am not even it is
necessary to exist separately.
>
> On Sun, Nov 6, 2016 at 9:27 PM Nicolai Hess wrote:
>>
>> 2016-11-03 15:11 GMT+01:00
Mcz repos are useful.
STH storage works nicely, that's more the frontend which si bitrotting.
I actually have a local FTP based thing on my Synology and it is neat and
needs no time to work.
Did you ever look into Zinc and see there is also a server there for that?
Now, GitHub is better for
Hi Dale,
I think I missed your mails. I would be interested in hearing your opinion.
Let’s aim for a chat sometime next week. Would this work for you?
Cheers,
Doru
> On Nov 7, 2016, at 6:30 AM, Dale Henrichs
> wrote:
>
>
>
> On 11/6/16 1:12 PM, Tudor
On 11/6/16 1:12 PM, Tudor Girba wrote:
Hi Stef,
I think that you are raising a valid point, and I actually agree with it.
But I think there is another side of the coin as well.
I think that right now we are in between worlds and this is not quite
beneficial. Switching to GitHub is a
On 11/6/16 9:05 AM, stepharo wrote:
Hi
I would like that you think a bit about our community and that there
is a value in using common tools
to share and develop common libraries. Because to me it feels like we
are getting balkanize.
It may look super cool and be hyper trendy to use
On 6 November 2016 at 17:21, Stephan Eggermont wrote:
> Kilon wrote:
> > If you really want to embrace Github , kill Smalltalkhub
>
> We are not close to doing that. We'll need
> Monticello support indefinitely, and at least a few years two-way. And
> that assumes we
Paul,
Quick comment: I was about to make an ANN soon but I have been
refactoring it a LOT these last days and I did:
1) make it fully the auto-generation code (already done)
2) making it work for highcharts 5.0.2 (already done)
3) start supporting highstocks (was going to start this this
Maybe you can give some brief explanaition how to create Spec-compatible custom
UI control? (Like TextModel or ButtonModel, etc.) How to create model class,
corresponding adapter and how to process common and custom UI events
(mouse\keyboard\focus ordering\changing).
I think such guide should
> On 6 Nov 2016, at 22:17, Dimitris Chloupis wrote:
>
>
> "Now my challenges after reading the UFFI documentation are the following
oh crap… I forget I have to finish that :(
UFFO doc: back to my TODO list...
Esteban
>
> 1) How I can pass things like O_CREAT ,
"Now my challenges after reading the UFFI documentation are the following
1) How I can pass things like O_CREAT , MAP_SHARED
2) How I cast a void pointer (its what mmap returns) to a C++ string or
C++ int"
After carefully re-reading the documentation its seems the answer to
question 1 is that I
Hi Stepharo,
On 5 November 2016 at 18:14, stepharo wrote:
> you can use the webportal (it supports subtitles in french and english -
> but read carefully what we wrote because we got trapped into a bug with
> certain configurations).
>
>
yeah as I said the chapter needs a complete rewrite. I am not even it is
necessary to exist separately.
On Sun, Nov 6, 2016 at 9:27 PM Nicolai Hess wrote:
> 2016-11-03 15:11 GMT+01:00 Nicolai Hess :
>
>
>
> 2016-11-03 15:02 GMT+01:00 stepharo
2016-11-03 15:11 GMT+01:00 Nicolai Hess :
>
>
> 2016-11-03 15:02 GMT+01:00 stepharo :
>
>> Hi nicolai
>>
>> I started to work on the reflection chapter.
>>
>
>
> The reflection chapter (and maybe some other too) could new some new
> screenshots.
>
And for us, without Git :-).
Offray
On 06/11/16 13:27, Dimitris Chloupis wrote:
I agree Pharo works great for me with Git apart from the file tree issue.
On Sun, 6 Nov 2016 at 20:22, Offray Vladimir Luna Cárdenas
> wrote:
Hi,
The commit messages, say nothing about the commits
On Sun, 6 Nov 2016 at 17:47, Sven Van Caekenberghe wrote:
>
> > On 6 Nov 2016, at 16:27, Dimitris Chloupis
> wrote:
> >
> > A biggy one is the pharo repo of the pharo image on github. Its a mess.
> >
> >
I agree Pharo works great for me with Git apart from the file tree issue.
On Sun, 6 Nov 2016 at 20:22, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:
> Hi,
>
> This thread derived on using GitHub, the transitions to it, the mismatch
> between the Smalltalk code model and the
Hi,
This thread derived on using GitHub, the transitions to it, the mismatch
between the Smalltalk code model and the files code model. I would like
to offer another view.
Pharo is working pretty well here. We have just finished our seventh
edition of the Data Week workshop+hackathon. This
Hello Vikenti,
I think that you are using the SpecAdapter for morphs in ways it has never been
tried or used. So the problems you are having reveal bugs in the SpecAdapter.
Please file a bug report, and feel free to contribute a fix as well of course
;-) (more about bugreports here:
Hey fellow Pharoers
I have great news, I was able to finally understand how shared memory
file works and actually do it
Why is that great news you may ask.
A shared memory file is a file that maps a specific area of memory, which
means when you write to a specific part of the memory it
Le 6/11/16 à 17:21, Stephan Eggermont a écrit :
Kilon wrote:
If you really want to embrace Github , kill Smalltalkhub
We are not close to doing that. We'll need
Monticello support indefinitely, and at least a few years two-way. And that
assumes we automatically migrate all open projects.
Le 6/11/16 à 17:12, Tudor Girba a écrit :
Hi Stef,
I think that you are raising a valid point, and I actually agree with it.
But I think there is another side of the coin as well.
I think that right now we are in between worlds and this is not quite
beneficial. Switching to GitHub is a
Kilon wrote:
> If you really want to embrace Github , kill Smalltalkhub
We are not close to doing that. We'll need
Monticello support indefinitely, and at least a few years two-way. And that
assumes we automatically migrate all open projects.
First we need good workflows that also work for
Hi Stef,
I think that you are raising a valid point, and I actually agree with it.
But I think there is another side of the coin as well.
I think that right now we are in between worlds and this is not quite
beneficial. Switching to GitHub is a significant effort, and treating it as
business
> On 6 Nov 2016, at 16:27, Dimitris Chloupis wrote:
>
> A biggy one is the pharo repo of the pharo image on github. Its a mess.
>
> https://github.com/pharo-project/pharo-core/commits/6.0
>
> seriously, Github makes us visible , this does not look good at all.
why not
If you really want to embrace Github , kill Smalltalkhub.
Smalltalkhub should have been dead years ago. Its unmaintained anyway apart
from when it crashes and Esteban fixes. Smalltalkhub has been a constant
state from crashes since 2011 when I joined Pharo community.
Give people a month to move
Dimitris
better reread what I wrote because you missed it.
My point is let us minimize the mess and act in a concerted way. Do you
think that we would pay 9 months of dev + esteban that will started to
push there too
and base all our dev on it if we would not believe that moving to git is
> It may look super cool and be hyper trendy to use github (because like
> that you can say that you use latest hyper cool
>
> features), but I would like to ask especially people building libraries
> to pay attention that it is important
>
> that other people can contribute back easily and that
Hi
I would like that you think a bit about our community and that there is
a value in using common tools
to share and develop common libraries. Because to me it feels like we
are getting balkanize.
It may look super cool and be hyper trendy to use github (because like
that you can say
Hi,
> On 5 Nov 2016, at 22:28, stepharo wrote:
>
> I do not think that Kevin is following this list. I strongly suggest that the
> repo is moved to one that we can control and let people contribute.
>
AFAIK this is the case:
https://github.com/DuneSt/MaterialDesignLite
As any person with an ounce of self awareness.
Remember that you are one interesting way the universe is introspecting
itself.
Phil
On Sun, Nov 6, 2016 at 10:08 AM, Robert Withers
wrote:
> Thank you. It breaks my heart I'm who I am, so at odds with who I wish to
What does the Time Profiler show?
Can you link to a sample picture?
cheers -ben
On Sat, Nov 5, 2016 at 11:11 PM, Matteo via Pharo-users
wrote:
>
>
> -- Forwarded message --
> From: Matteo
> To: "Pharo is welcome (ML)"
You are forgiven.
Now get back to delivering us awesome features.
Namaste.
Phil
On Sun, Nov 6, 2016 at 8:24 AM, Robert Withers
wrote:
> Forgive me for being such a huge unbearable fucking asshole.
>
>
>
>
Great! Thanks for all your work.
Sent from my iPhone
> On Nov 5, 2016, at 04:31, Marcus Denker wrote:
>
> Hi,
>
> Current Status:
>
> - SPF record DONE, mails are now send from @association.pharo.org
> - DNS setup now uses association.pharo.org for normal viewing,
35 matches
Mail list logo