Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

On Tue, Apr 22, 2014 at 7:26 PM, Sean P. DeNigris wrote: > Stefan Marr-3 wrote > > Still, I will state it anyway: I don’t like the change. > > I expected it to be unpopular ;) > > > Stefan Marr-3 wrote > > So, just for the sake of argument, are there other ways? > > I don't know. I'm open... > > A

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

Stefan Marr-3 wrote > Still, I will state it anyway: I don’t like the change. I expected it to be unpopular ;) Stefan Marr-3 wrote > So, just for the sake of argument, are there other ways? I don't know. I'm open... As far as making #= mean something different the first time, I think this gets

Re: [Pharo-dev] Smalltalk Hub on Chrome

It looks like this: - Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788p4755918.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Pharo success story for Issys Tracking broken?

Yes - but the question remains where did this story come from. I would like to know more about it. Thx T. > Gesendet: Dienstag, 22. April 2014 um 16:20 Uhr > Von: "Marcus Denker" > An: "Pharo Development List" > Betreff: Re: [Pharo-dev] Pharo success story for Issys Tracking broken? > > > On

Re: [Pharo-dev] updated documentation on magritte?

On Tue, Apr 22, 2014 at 9:14 PM, Esteban Lorenzano wrote: > > On 22 Apr 2014, at 20:20, stepharo wrote: > > > Not that I know. > > I started a chapter on the pharo for the entreprise (with the idea to > base it on the seaside book) but I need help. > > If you start writing a draft I will do a pas

Re: [Pharo-dev] About fonts (again)

2014-04-22 21:30 GMT+02:00 stepharo : > > On 22/4/14 14:19, Tudor Girba wrote: > > I do not see what this has to do with anything. > > Right now we are offering the possibility to not be able to load > FreeType fonts and this leads to buggy behavior when the user starts > playing with that toggle

Re: [Pharo-dev] About fonts (again)

Why is this buggy? Right now, the meaning of the checkbox is to allow the user to have FT in addition to bitmap fonts. That is why I say we should just drop the checkbox altogether and we have solved a source of problems. We can rethink the infrastructure for Pharo 4. Doru On Tue, Apr 22, 2014

Re: [Pharo-dev] About fonts (again)

On 22/4/14 14:19, Tudor Girba wrote: I do not see what this has to do with anything. Right now we are offering the possibility to not be able to load FreeType fonts and this leads to buggy behavior when the user starts playing with that toggle. In fact this is buggy even without that. The s

Re: [Pharo-dev] About fonts (again)

Hi nicolas I agree with you :). My goal is not to drop strike fonts because I think that the code is working and it can be useful for some people. I just want to make sure that StandardFonts (TextStyle and others...) does not mess up FreeType and StrikeFonts. We got a lot of problems with this

Re: [Pharo-dev] updated documentation on magritte?

On 22 Apr 2014, at 20:20, stepharo wrote: > Not that I know. > I started a chapter on the pharo for the entreprise (with the idea to base it > on the seaside book) but I need help. > If you start writing a draft I will do a pass. I was fearing that… but ok :) > > Stef > > On 22/4/14 09:28,

Re: [Pharo-dev] Lost in spec

2014-04-22 13:56 GMT+02:00 Igor Stasenko : > i want to use different adaptor for TextModel, when opening my UI > so that when widget is built for it, it will be my own widget, > not PluggableTextMorph.. > > but i found it hard to do.. here what i tried: > > > I try to replace bindings, so at the s

Re: [Pharo-dev] Confused by NewListExample

- title toggling doesn’t work - doesn’t have a usable size - window title not set - dragging doesn’t work - disallows selection in one place, allows it somewhere else - menu the same on list title - uses halts directly instead of calling a method on self displaying the action (open a dialog

Re: [Pharo-dev] Lost in spec

TxText-Athens-IgorStasenko.27 (TxText on smalltalkhub) just committed see TxApplicationWithToolbar TxApplicationWithToolbar new openWithSpec etc On 22 April 2014 20:21, stepharo wrote: > Igor where is your code so that I can give a try? > > > > On 22/4/14 13:56, Igor Stasenko wrote: > >> i

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

If done right, TimeStamp would have not caused any confusion. Now that I discovered that a TimeStamp is a DateAndTime with rounded seconds (read: non-sense) I agree with you. On Apr 22, 2014, at 6:42 PM, Sven Van Caekenberghe wrote: > TimeStamp is deprecated, because it creates too much confus

Re: [Pharo-dev] Lost in spec

Igor where is your code so that I can give a try? On 22/4/14 13:56, Igor Stasenko wrote: i want to use different adaptor for TextModel, when opening my UI so that when widget is built for it, it will be my own widget, not PluggableTextMorph.. but i found it hard to do.. here what i tried: I

Re: [Pharo-dev] updated documentation on magritte?

Not that I know. I started a chapter on the pharo for the entreprise (with the idea to base it on the seaside book) but I need help. If you start writing a draft I will do a pass. Stef On 22/4/14 09:28, Esteban Lorenzano wrote: Hi, is there an updated documentation on magritte? where can I f

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

TimeStamp is deprecated, because it creates too much confusion, you better use DateAndTime. On 22 Apr 2014, at 17:11, roberto.mine...@usi.ch wrote: > "TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * > 10e9. > > Doing “DateAndTime now” solves my issue, but this is a

[Pharo-dev] Versionner screencast

Hello, I made a small screencast on Versionner to explain how to use it: https://www.youtube.com/watch?v=S5Dbmmln8tA Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature

Re: [Pharo-dev] Smalltalk Hub on Chrome

Sean P. DeNigris writes: > I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on > Mavericks), but if I open it alongside in Safari, it loads fine... Does the page load but stays without content, or is it another issue? Nico > > > > - > Cheers, > Sean > -- > View this

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

"TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * 10e9. Doing “DateAndTime now” solves my issue, but this is a total non-sense. Cheers, R On Apr 22, 2014, at 4:54 PM, Yuriy Tymchuk wrote: > Well, it has #asNanoSeconds, how finer can you go? > > Uko > > On 22 Apr

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

Hi Sean: First of all, I enabled public write access on the repository. While I am the admin on the project, I took it over from Niko and Adrian, and at this point, I would consider it ‘community maintained’. The rest inline: On 22 Apr 2014, at 16:40, Sean P. DeNigris wrote: > - change matche

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

Well, it has #asNanoSeconds, how finer can you go? Uko On 22 Apr 2014, at 17:13, roberto.mine...@usi.ch wrote: > Hi, > > I am wondering if there is the possibility to get milliseconds in a TimeStamp. > > I need to record fine-grained events and second-granularity is not enough. > > Cheers, >

[Pharo-dev] Smalltalk Hub on Chrome

I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on Mavericks), but if I open it alongside in Safari, it loads fine... - Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788.html Sent from the Pharo Smalltalk Developer

[Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

Reverting EyeInspector>>#updateList revealed the error when Phexample is used in latest Pharo 3.0... PhexMatcher uses #= as part of it's DSL e.g. "1 should = 1". Because it doesn't respond normally to #=, #hash is implemented to signal an error (self error: 'Don''t put a matcher into a dictionary.

Re: [Pharo-dev] Phexample: Image Destroying Bug

Problem found and fix proposed in new thread - "Phexample: API Change Proposal (was Phexample: Image Destroying Bug)" - Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-Image-Destroying-Bug-tp4755253p4755786.html Sent from the Pharo Smalltalk Developers mailing

Re: [Pharo-dev] Pharo success story for Issys Tracking broken?

On 22 Apr 2014, at 13:53, Sean P. DeNigris wrote: > Torsten Bergmann wrote >> Unfortunately none of the links work. Any infos on that? > > I did a little googling and checked the wayback machine; didn't come up with > anything relevant… > I have removed the article for now… Marcus

[Pharo-dev] Milliseconds in DateAndTime or TimeStamp

Hi, I am wondering if there is the possibility to get milliseconds in a TimeStamp. I need to record fine-grained events and second-granularity is not enough. Cheers, Roberto

Re: [Pharo-dev] Phexample: Image Destroying Bug

Sean P. DeNigris wrote > 13156 EyeInspector does not automatically refresh its list > https://pharo.fogbugz.com/f/cases/13156 This is the culprit. Loading into 30807 gives the broken behavior. Here's a snippet of the call chain: MultiByteFileStream(WriteStream)>>space EyeInspector(Object

Re: [Pharo-dev] Phexample: Image Destroying Bug

Sean P. DeNigris wrote > "...In 3.0, it never returns, creating an more and more debugger processes > until the image becomes unresponsive." This broke with 30808 http://forum.world.st/pharo-project-pharo-core-447842-30808-td4752289.html : Log Message: --- 30808 13156 EyeInspector d

Re: [Pharo-dev] About fonts (again)

I do not see what this has to do with anything. Right now we are offering the possibility to not be able to load FreeType fonts and this leads to buggy behavior when the user starts playing with that toggle. I fail to see why we need the option in the first place. All I am saying is that we shoul

Re: [Pharo-dev] WhatsUp from: 2014-04-21 until: 2014-04-30

### Here's what I've been up to since the last WhatsUp: - fixed Pharo bugs for the 3.0 release - worked a lot on Marina, a new CMS based on Pillar, Tide and Amber (https://github.com/tide-framework/marina) ### What's next, until 2014-04-30 (*): - python parsing -- Damien Cassou http://damienc

Re: [Pharo-dev] Pillar in TextMate

On Sun, Apr 20, 2014 at 8:35 AM, Yuriy Tymchuk wrote: > > I'm happy to announce that I've created a small bundle for TextMate. You can > find it here: https://github.com/Uko/Pillar.tmbundle > > Also I've exported it to ATOM (new editor from github) package, but it's > crappy because ATOM lacks s

[Pharo-dev] Lost in spec

i want to use different adaptor for TextModel, when opening my UI so that when widget is built for it, it will be my own widget, not PluggableTextMorph.. but i found it hard to do.. here what i tried: I try to replace bindings, so at the stage when spec interpreted, it uses my bindings: openWit

Re: [Pharo-dev] Pharo success story for Issys Tracking broken?

Torsten Bergmann wrote > Unfortunately none of the links work. Any infos on that? I did a little googling and checked the wayback machine; didn't come up with anything relevant... - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-success-story-for-Issys-Tracking-b

Re: [Pharo-dev] updated documentation on magritte?

EstebanLM wrote > is there an updated documentation on magritte? where can I find it? I didn't find any. I was referencing a combination of the original papers, and slides I found online about the differences in Magritte 3. For Morphic, I implemented as I needed features, so there is none :/ --

Re: [Pharo-dev] About fonts (again)

2014-04-22 8:21 GMT+01:00 Tudor Girba : > I am not arguing for dropping of bitmap fonts at all. I am only arguing > for removing the option of not having freetype. People on slow devices will > still be able to use the bitmap fonts. > > Is that wrong? > Well, look at it this way: who should be ab

[Pharo-dev] Messages reported as spam by Gmail

Please note that I found two threads reported as spam in my spam folder. One was about a competition for Roassal to create a visualisation with it and the second one was about a finder bug, both have not recieved any replies since then so this issue does not affect just me. So make sure you check

[Pharo-dev] Pharo success story for Issys Tracking broken?

http://www.pharo-project.org/about/success-stories includes a story about scaling seaside. Unfortunately none of the links work. Any infos on that?

[Pharo-dev] updated documentation on magritte?

Hi, is there an updated documentation on magritte? where can I find it? cheers, Esteban

Re: [Pharo-dev] About fonts (again)

Hi, I think my message generated a misunderstanding. I am not arguing for dropping of bitmap fonts at all. I am only arguing for removing the option of not having freetype. People on slow devices will still be able to use the bitmap fonts. Is that wrong? Cheers, Doru On Tue, Apr 22, 2014 at

Re: [Pharo-dev] About fonts (again)

2014-04-22 6:30 GMT+02:00 Tudor Girba : > One question is why do still have the disable free type fonts option? > This was useful when free type was still in development, but I think now > it is no longer useful. > Or are there still use cases for it? > > Doru > > > At the risk of repeating myself