Thanks for the update. Looking forward to the better fonts, but also
appreciate all the hard work everyone has put in so far!
--
View this message in context:
http://forum.world.st/Retina-support-in-Pharo-tp4895245p4895558.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.
2016-05-17 18:19 GMT+02:00 Peter Uhnák :
>
> Now, I only know that comments in block closures are placed behind the
>> block code.
>> Do you know more examplmes where the formatter still misplaces the
>> comment.
>
>
> Maybe just comments now? I've added a formatting configuration that
> preserved
World submorphs
select: [ :sm |
sm isSystemWindow and: [ sm label =
PharoWelcomePage title ]
]
thenDo: [ :window | window delete ].
Best regards,
Henrik
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Be
Is there a clean way how to close or not open the Pharo 5.0 welcome window?
Short of going through the stack and closing it (courtesy of Cyril)
(SystemWindow allInstances select: [ :w | w labelString
includesSubstring: 'Welcome' ]) do: #delete
Thanks,
Peter
yes template looks fine to me, basic classes is a good place to start too.
I will give it a try and see how it goes :)
On Tue, May 17, 2016 at 10:55 PM stepharo wrote:
>
> I really like to start writing some class and method comments to make
> Pharo image more beginner friendly.
>
>
> This would
On Tue, May 17, 2016 at 10:21 PM, Damien Pollet
wrote:
> On 17 May 2016 at 22:14, Alexandre Bergel wrote:
>>
>> My email was _not_ about judging the community effort, but more on whether
>> pharo work on a Retina laptop.
>> What happens if Pharo is launched on a retina computer?
>
>
> You get the
Le 17/5/16 à 22:14, Alexandre Bergel a écrit :
My email was _not_ about judging the community effort, but more on whether
pharo work on a Retina laptop.
ok
What happens if Pharo is launched on a retina computer?
you get pixelized fonts.
But I have other mac app doing the same.
Stef
Ch
On 17 May 2016 at 22:14, Alexandre Bergel wrote:
> My email was _not_ about judging the community effort, but more on whether
> pharo work on a Retina laptop.
> What happens if Pharo is launched on a retina computer?
>
You get the same thing as on a non-retina display, except instead of each
fuz
Okay, this is what I suspected. So buying a new laptop will not prevent me from
using Pharo :-)
Alexandre
> On May 17, 2016, at 2:38 PM, Esteban Lorenzano wrote:
>
> it works.
> just fonts could be better (and eventually, they will).
>
> Esteban
>
>> On 17 May 2016, at 21:32, Alexandre Ber
My email was _not_ about judging the community effort, but more on whether
pharo work on a Retina laptop.
What happens if Pharo is launched on a retina computer?
Cheers,
Alexandre
> On May 17, 2016, at 2:47 PM, stepharo wrote:
>
>
>> I am about to buy a new laptop. Pharo does not work with R
Thanks Johan
We looked at
RadioButtonGroupExample
but you see we cannot have a RadioButtonGroupPresenter having 2, 3 or 4
radioButton.
Stef
Le 17/5/16 à 18:52, Johan Fabry a écrit :
Hi Marion,
the class side message of defaultSpec is generally meant to be used if you use
a fixed number
I really like to start writing some class and method comments to make
Pharo image more beginner friendly.
This would be really coool.
Did you check the class comment template because I wrote it thinking
about this.
What I think would be great is to have great comments for the basic
I am about to buy a new laptop. Pharo does not work with Retina display?
How can it be?
Alexandre
I'm sorry to see this email.
We all worked like mad and Esteban did A MASSIVE AMOUNT OF WORK.
Nearly nobody on this list really understand what is to write a new FFI
framework and Esteban
got near
it works.
just fonts could be better (and eventually, they will).
Esteban
> On 17 May 2016, at 21:32, Alexandre Bergel wrote:
>
> I am about to buy a new laptop. Pharo does not work with Retina display?
> How can it be?
>
> Alexandre
>
>
>> On May 17, 2016, at 2:13 PM, Luis Felipe Strano Mo
I am about to buy a new laptop. Pharo does not work with Retina display?
How can it be?
Alexandre
> On May 17, 2016, at 2:13 PM, Luis Felipe Strano Moraes
> wrote:
>
> I asked about this just a few days ago, here's the reply:
>
> http://forum.world.st/Pharo-and-HiDPI-tc4894853.html
>
>
>
The problem I have with braking methods to much smaller ones is that it
makes browsing code far more tedious. I think the 10 lines limit is fine
but once you get 5 lines it becomes unnecessarily modular. I think like all
things comments and braking methods should be exercised with some critical
thi
I asked about this just a few days ago, here's the reply:
http://forum.world.st/Pharo-and-HiDPI-tc4894853.html
On Mon, May 16, 2016 at 10:37 PM, markm wrote:
> Hi
>
> Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I
> have tried searching for some answers, but alas c
You are absolutely right. Many without comments. Some of which may not
need comments as they are self revealing in what and why. But many which
do need some good comments.
As I read Peter's email. What he was saying is that my intent or why can
be placed in the method comment when broken into
Hi Marion,
the class side message of defaultSpec is generally meant to be used if you use
a fixed number of widgets, so you can put the reference to the name of each
widget there (in cour case #buttons). For variable number of widgets you should
have a look at the dynamic features of Spec.
Tha
ok guys then it seems all is as expected
I am a fan of inline comments when needed, I am with full agreement with
Jimmie here , braking methods to smaller methods cannot reveal intend, an
inline comment can but thats not big deal i can put everything on the start
so everyone is happy
The problem
On Mon, May 16, 2016 at 08:15:28PM +0200, stepharo wrote:
> Hi all :)
> > Hi All,
> >
> > TextAction appears to have a couple of issues:
> >
> >
> > TextAction>>actOnClick: anEvent for: anObject in: paragraph editor: editor
> > "sent when a user clicks on a piece of text to which I am applie
I don't have time right now to give you a proper example…
however if you have layout on the instance side, then you need to call the
build method explicitly with the proper layout… well, that's what I do at
least
https://github.com/dynacase/dynacase/blob/master/repository/DynaCASE-Spec.package/DC
> Now, I only know that comments in block closures are placed behind the
> block code.
> Do you know more examplmes where the formatter still misplaces the comment.
Maybe just comments now? I've added a formatting configuration that
preserved vertical white space (and I believe also comment posit
Hi,
I'm trying to create a widget whith Spec, managing a collection of
RadioButton. But I have a problem with defaultSpec (the accessor of the
collection is the methods "buttons") :
If i put defaultSpec on class side, i can't acces the collection of the
instance. (the following code iterate o
On 05/17/2016 01:40 AM, Peter Uhnák wrote:
As a note, maybe try to avoid inline comments unless formatter is
fixed, because autoformatting _will_ misplace them. (Not to mention
that imho inline comments in Smalltalk are a result of a bad design…
if you need an inline comment, maybe turn that in
2016-05-17 8:40 GMT+02:00 Peter Uhnák :
> As a note, maybe try to avoid inline comments unless formatter is fixed,
> because autoformatting _will_ misplace them.
>
There were some fixes to make this better.
Now, I only know that comments in block closures are placed behind the
block code.
Do yo
26 matches
Mail list logo
