Re: [Pharo-users] STON encoding of slashes

[Sven Van Caekenberghe]

> On 18 Jan 2017, at 16:38, Sven Van Caekenberghe  wrote:
> 
> So my conclusion would be (while writing), always escape $\ and not $/, in 
> pure STON mode (the default), escape $' and not $", in JSON mode, escape $" 
> and not $'. 

I implemented these changes in writing behaviour:

===
Name: STON-Core-SvenVanCaekenberghe.81
Author: SvenVanCaekenberghe
Time: 31 January 2017, 11:43:15.520367 pm
UUID: d83172d8-f01e-4e63-9382-515399ffa7bc
Ancestors: STON-Core-SvenVanCaekenberghe.80

Change the encoding of characters while writing so that in default STON mode 
only the following named character escapes are used: \b \t \n \f \' and \\ 
while in JSON mode \' is replaced by \" - this means that / is normally not 
escaped.

Add STONWriter>>#escape:with: as API

Adjust 2 unit tests to reflect this change

Update time tag of STONWriter class>>#initialize 
===
Name: STON-Tests-SvenVanCaekenberghe.71
Author: SvenVanCaekenberghe
Time: 31 January 2017, 11:43:43.88292 pm
UUID: 65045513-6f48-43b7-a112-89dabf34a8f8
Ancestors: STON-Tests-SvenVanCaekenberghe.70

Change the encoding of characters while writing so that in default STON mode 
only the following named character escapes are used: \b \t \n \f \' and \\ 
while in JSON mode \' is replaced by \" - this means that / is normally not 
escaped.

Add STONWriter>>#escape:with: as API

Adjust 2 unit tests to reflect this change

Update time tag of STONWriter class>>#initialize 
===


Sven

Re: [Pharo-users] Phobos and printing

[Pavel Krivanek]

So I tried to run Phobos on Pharo 6 and it is able to run fine with the old
Json package. It only needed two simple patches. To convert Phobos to
NeoJSON will require some extra effort. In next days I will put the code on
the Git repository.

Cheers,
-- Pavel

2017-01-31 20:19 GMT+01:00 kmo :

> I'm afraid not. But I did start experimenting with Phobos and thought it
> was
> a very capable framework. Then I was put off a bit when it stopped being
> compatible with later versions of pharo.
>
> Ken
>
>
> HilaireFernandes wrote
> > Hi Ken,
> > Did you have former experience using Phobos for real desktop application?
> > Hilaire
>
>
>
>
>
> --
> View this message in context: http://forum.world.st/Phobos-and-printing-
> tp4932002p4932558.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>

Re: [Pharo-users] These beautiful tooltips

[Hilaire]

Blue is fine too. It was so before.

Le 31/01/2017 à 14:14, Ben Coman a écrit :
> Any opinions from the rest of the community on making one of those two 
> default?

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Phobos and printing

[kmo]

I'm afraid not. But I did start experimenting with Phobos and thought it was
a very capable framework. Then I was put off a bit when it stopped being
compatible with later versions of pharo.

Ken


HilaireFernandes wrote
> Hi Ken,
> Did you have former experience using Phobos for real desktop application?
> Hilaire





--
View this message in context: 
http://forum.world.st/Phobos-and-printing-tp4932002p4932558.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Phobos and printing

[Mark Bestley]

There is Electron  - although the GUI is 
HTML/Javascript


Mark

On 30/01/2017 14:16, Hilaire wrote:

Hi Pavel,

I am in prospective mode exploring alternative for desktop application
vs SAAS application (in the later, the cost to maintain may be too high
for only one technical guy, me).

As I saw in the Phobos demo the Print feature, I just did a quick hack
to test print over a html document.

So xulrunner is abandonware? The new way to build UI in Firefox is
totally different I guess so then?.

Beside Phobos, there is no reliable and feature complete alternative to
build desktop application, is it that?

Thanks

Hilaire

Le 30/01/2017 à 11:36, Pavel Krivanek a écrit :

Hi Hilaire,

I will look at it. Are you interested to have Phobos for Pharo 6?
The main problem of Phobos is the stopped support of XULRunner by
Mozilla without substitute so it's not good idea to use it for long-term
projects.

Cheers,
-- Pavel





--
Mark

Re: [Pharo-users] self in Nautilus

[Siemen Baader]

On Fri, Jan 27, 2017 at 9:11 PM, stepharong  wrote:

> I should tell you that I do not like it at all.
> Hey students inside comments self means the class and outside the
> instance! WTF?
>

Which behaviour do you no like, Stef? The current or the one we are
discussing?

>
> I think that we should have another kind of pseudo variable but not self.
>

Also an option and more explicit than `self `working, but meaning something
else than at run-time. In the case where `self` is the current object (as
in the debugger) the code can be executed with DO like when it is later
run. That is what I would find useful for prototyping.

-- Siemen


>
>
> Hi all,
>
> in Nautilus, `self` is always the current class instance. This is great
> for coding class side methods because we can test code fragments live in
> the editor, but for instance side methods I have not seen the usefulness of
> it. At times it can even be confusing and cause errors since a "print it"
> of it looks quite like an instance (`a Listener` vs `Listener`).
>
> Is there a rationale why `self` in instance view does not raise an error
> or is nil? And, more importantly, could there be a way to set it to a
> specific value (= can we browse a class with self bound to an specific
> instance).
>
>
> In Pharo 6 if you tag a class method with
>
>
>...
> ^ return the instance
>
> then you get automatically an icon to get an inspector on the instance.
> From there you can do whatever you want.
>
>
> This would resemble programming in the debugger, but provide the overview
> that a class browser provides.
>
> cheers,
> Siemen
>
>
>
>
>
> --
> Using Opera's mail client: http://www.opera.com/mail/
>

[Pharo-users] Fwd: PharoDays: Possible dates

[Marcus Denker]

Hi,

I have updated the poll with some dates in May.

If you can not come at any date but would be interested in general, please
respond with the “can not make it” option.

Marcus

> Hello,
> 
> First for the board only: We checked with Stef what dates would make sense
> The best here is April, either before or after school holidays.
> 
> I made a doodle:
> 
> 
>   http://doodle.com/poll/f8n5zhv7p8fqwyih 
> 
> 
> 
> if this looks ok I would send it around to get an impression what people 
> think.
> 
>   Marcus

Re: [Pharo-users] GitFileTree in Pharo 5

[Cyril Ferlicot D.]

On 31/01/2017 06:31, Pierce Ng wrote:
> On Wed, Dec 14, 2016 at 02:12:40PM -0500, sergio ruiz wrote:
>> I am trying to install GitFileTree from the Catalog Browser. I get a warning
>> that it’s not tested with Pharo 5. I go ahead anyway, and it just hangs.
>>
>> Has anyone else installed it on macOS?
> 
> Just tried the same on Linux Mint 17 (based on Ubuntu 14.04) and got the same.
> 
> Pierce
> 

Hi!

To load gitFileTree I use this script:

```
Metacello new
  baseline: 'FileTree';
  repository: 'github://dalehenrich/filetree:pharo' , SystemVersion
current dottedMajorMinor , '_dev/repository';
  load: 'Git'
```

Works for me on Pharo 5/windows and pharo 6/osx

-- 
Cyril Ferlicot

http://www.synectique.eu

2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-users] Phobos and printing

[Hilaire]

I mean no offense to Esteban, I appreciate him well (he slept a couple
of days at my place :) but GTK looks so odd on Mac and OSX desktop, then
it is not that much well featured. There are richer alternative like
wxWidget or Qt.

Le 30/01/2017 à 16:45, Hilaire a écrit :
> GTK binding? Thanks but no thanks, it does not fit for pro desktop
> application.

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Phobos and printing

[Hilaire]

Hi Ken,
Did you have former experience using Phobos for real desktop application?
Hilaire

Le 30/01/2017 à 20:03, kmo a écrit :
> I think Phobos is really good. It would be great to have Pharo 6 version.
> It's a pity about XULRunner being abandoned but all is not lost. There is a
> fork of Firefox that is committed to keeping XULRunner support - Pale Moon -
> https://www.palemoon.org/
> 
> Ken

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

[Hilaire]

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 of GLMBrickColorThemer so dark themes get
> hardcoded light colors in places for example.
> 

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

[p...@highoctane.be]

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 xxxColor items whenever possible.

Also we should have a way to reset its color registry that is cached and
makes it hard to do things especially in a playground that uses it...

Maybe Brick can help in the future with a clean skinning and color theme
setup. Especially if Bloc can do whatever window shape (pours oil on the
fire...).

Phil

On Tue, Jan 31, 2017 at 4:08 AM, Paul DeBruicker  wrote:

> 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 contrasting colors for a palette:
>
> http://colorsafe.co
>
>
> And all themes could be subject to passing at a minimum contrast grade (AA
> seems not too hard?) before being added to the core. And in that way we
> have
> a standard of 'good enough' that is more widely accepted than 'works on my
> machine, for my eyes, in this physical space, with this ambient lighting'
>
>
> Paul
>
>
>
>
>
>
>
> HilaireFernandes wrote
> > Hi,
> >
> > So in Pharo5 we have these 'beautiful' unreadable tooltips: tiny black
> > font on light gray (ie. take a look to its squeak counter part, it looks
> > so much more pro)
> >
> > Is there a way to programmatically change the backround color?
> >
> > Thanks
> >
> > Hilaire
> >
> > --
> > Dr. Geo
> > http://drgeo.eu
>
>
>
>
>
> --
> View this message in context: http://forum.world.st/These-
> beautiful-tooltips-tp4932206p4932319.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>
>