On 04/02/2017 18:26, stepharong wrote:
> It would be nice to have a palette class with some nice defaults.
> Cyril could you package what you have in MDL out of MDL so that we can
> add it to Pharo?
>
> Stef
>
I extracted it here:
https://github.com/DuneSt/MaterialColors
In the future I
Thanks for the vote of confidence :-) but sadly due to my move I won’t be able
to spend much time on Pharo in the near future :-(
--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please
see http://emailcharter.org .
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD
May be more naive eyes will more likely see glitches
Le 04/02/2017 à 22:45,
serge.stinckw...@gmail.com a écrit :
> I guess we can find better qualified people about UI quality than me ;-)
> Doru or Johan are examples.
--
Dr. Geo
http://drgeo.eu
I guess we can find better qualified people about UI quality than me ;-)
Doru or Johan are examples.
Envoyé de mon iPhone
> Le 4 févr. 2017 à 21:07, Cyril Ferlicot D. a écrit
> :
>
>> Le 04/02/2017 à 20:46, Hilaire a écrit :
>> Will Serge, Dimitris willing to join in
Le 04/02/2017 à 20:46, Hilaire a écrit :
> Will Serge, Dimitris willing to join in with me?
>
> Hilaire
>
> Le 04/02/2017 à 18:26, stepharong a écrit :
>>> How does it sound?
>>
>> good but will we find these people?
>
If you create a mailing list I would be interested to subscribe.
I would
Will Serge, Dimitris willing to join in with me?
Hilaire
Le 04/02/2017 à 18:26, stepharong a écrit :
>> How does it sound?
>
> good but will we find these people?
--
Dr. Geo
http://drgeo.eu
Damned you are inferring a lot on my writing, but I understand now.
In my previous post I had no argument against the *new* debugger, nor I
wrote its interface degraded. I just made an absolute remark regarding
lack of information on non obvious function, in the debugger in my
example, which
On Fri, 03 Feb 2017 22:20:28 +0100, Hilaire wrote:
UI quality team could be fun.
Here are some ideas how it could be organised:
- at least 3/5/7 persons looking at issues and reporting it. Why three?
Easier to decide and UI may for some part be very opinionated
These
It would be nice to have a palette class with some nice defaults.
Cyril could you package what you have in MDL out of MDL so that we can add
it to Pharo?
Stef
And there are useful A11Y (Accessibility combos down the page)
http://clrs.cc/a11y/
Phil
On Thu, Feb 2, 2017 at 7:38 PM,
Hilaire
can you create bug entry to little usability glitches. Esteban told me
that he will do a pass.
Stef
On Fri, 03 Feb 2017 09:21:18 +0100, Hilaire wrote:
A UI quality team review would be needed before each Pharo release, I
mean with a real constraint to postpone
Well, we got a real Debugger Model which says:
DebugSession>>#stepInto: aContext
"Send the selected message in selectedContext, and take control in
the method invoked to allow further step or send."
DebugSession>>#stepOver: aContext
"Send the selected message in
> > On Feb 3, 2017, at 13:29, Hilaire wrote:
> >
> > what are the differences between 'over' and 'through' buttons in the
> > debugger.
On Sat, Feb 4, 2017 at 8:09 AM, John Pfersich wrote:
>
> The over button means step over the message highlighted, the
Hi Hilaire,
I did not reinterpret your intention. I gave you feedback. You can take it into
account or not.
But, I actually do not understand where the original problem comes from. I
probably miss something and that is why please allow me to describe what I see
and then you can indicate more
The over button means step over the message highlighted, the through button
means step into the message highlighted and single step through the statements
in the message.
Sent from my iPhone
> On Feb 3, 2017, at 13:29, Hilaire wrote:
>
>
>
>> Le 03/02/2017 à 17:12, Tudor
Le 03/02/2017 à 17:12, Tudor Girba a écrit :
> Unfortunately, your message sounded like an angry complaint and this often
> has the tendency to stifle collaboration. As I am sure this was not your
> intention, let’s try to take that energy and transform it into something
> positive that can
UI quality team could be fun.
Here are some ideas how it could be organised:
- at least 3/5/7 persons looking at issues and reporting it. Why three?
Easier to decide and UI may for some part be very opinionated
These persons could discuss how to fix it, if no consensus, the team
could ask to the
Hi Hilaire,
Thanks for caring about the UI.
Unfortunately, your message sounded like an angry complaint and this often has
the tendency to stifle collaboration. As I am sure this was not your intention,
let’s try to take that energy and transform it into something positive that can
lead to
On Fri, Feb 3, 2017 at 4:54 PM, denker wrote:
>
>
> > On 3 Feb 2017, at 09:21, Hilaire wrote:
> >
> > A UI quality team review would be needed before each Pharo release, I
> > mean with a real constraint to postpone release until a good enough
> >
>
> Complaining on the list about the overall Pharo quality. Oh I appear to
> be the bad guy, I should take responsibility, ok may be during my bed
> time then.
>
> If you read carefully I proposed to help in my previous, so no need to
> reply with this trivial "show me the code". If there is a
On Fri, Feb 3, 2017 at 12:00 PM, Hilaire wrote:
> Yes, my words as yours are cheap, but life not:
Hi Hilaire,
> - 6:30am, wake up, speedy breakfast, heading to school
>
> - all days: teaching kid, getting grads, metting other teachers, oh
> using DrGeo during class, it is
Yes, my words as yours are cheap, but life not:
- 6:30am, wake up, speedy breakfast, heading to school
- all days: teaching kid, getting grads, metting other teachers, oh
using DrGeo during class, it is cool, it is super stable, hopefully I
kept it on Pharo 3 to avoid undetected incompatibility
On 03/02/2017 07:55, p...@highoctane.be wrote:
> About colors, I am using these ones for some projects: http://clrs.cc/
>
> Phil
>
For my part I use these colors:
https://www.materialui.co/colors
500 been the default color and the going higher or lower for contrasts.
In fact these colors are
> On 3 Feb 2017, at 09:21, Hilaire wrote:
>
> A UI quality team review would be needed before each Pharo release, I
> mean with a real constraint to postpone release until a good enough
> quality is reached!
> In that context I can help.
>
> There are many place where tiny
A UI quality team review would be needed before each Pharo release, I
mean with a real constraint to postpone release until a good enough
quality is reached!
In that context I can help.
There are many place where tiny efforts could make the UI so much better
for newcomers.
For example when I saw
And there are useful A11Y (Accessibility combos down the page)
http://clrs.cc/a11y/
Phil
On Thu, Feb 2, 2017 at 7:38 PM, stepharong wrote:
> On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire wrote:
>
> I would like to help in both accessibility and
About colors, I am using these ones for some projects: http://clrs.cc/
Phil
On Thu, Feb 2, 2017 at 7:38 PM, stepharong wrote:
> On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire wrote:
>
> I would like to help in both accessibility and implementation detail of
On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire wrote:
I would like to help in both accessibility and implementation detail of
the theme. In the other hand I fell we are in such flux with the future
UI in Pharo. What are the grounds we can stand on regarding UI?
Improve now.
+1 there are colors that I cannot see well in the drak theme and I'm not
disabled or color blind.
One way to address this going forward is for theme developers to check
their
color selections against the e.g. Web Content Accessibility Guidelines
(https://www.w3.org/TR/WCAG20/)
Using a
I would like to help in both accessibility and implementation detail of
the theme. In the other hand I fell we are in such flux with the future
UI in Pharo. What are the grounds we can stand on regarding UI?
Hilaire
Le 31/01/2017 à 11:21, p...@highoctane.be a
écrit :
> Well there is no subclass
Well there is no subclass of GLMBrickColorThemer so dark themes get
hardcoded light colors in places for example.
The Sublimish theme revealed these kind of problems. I am busy
investigating.
I made such a subclass and it is used by #colors now. Was missing.
GLM stuff should use UITheme current
One way to address this going forward is for theme developers to check their
color selections against the e.g. Web Content Accessibility Guidelines
(https://www.w3.org/TR/WCAG20/)
Using a readily available tool:
https://leaverou.github.io/contrast-ratio/
And/or one that makes suggestions of
31 matches
Mail list logo