Hi Sean,
Sorry (and to Offray) for the trouble, but thanks for persevering.
On 15 November 2017 at 01:47, Sean P. DeNigris wrote:
> Alistair Grant wrote
>> This looks like you are using an old (cached?) version.
>
> Ugh, yes. I just deleted the local clone and let Iceberg reclone.
>
> Now when I
I would say that is an entirely different question. If a test isn't stable,
you have a completely different scenario from a test that interrupts
execution and is resumed.
On Nov 14, 2017 20:45, "Stephan Eggermont" wrote:
Op 15-11-2017 om 01:49 schreef Sean P. DeNigris:
Again, it seems that just
Hi Offray,
On 15 November 2017 at 00:18, Offray Vladimir Luna Cárdenas
wrote:
> Hi Alistair,
>
> The example is not working for me. When I run it, a chrome session is
> open but nothing happens there, except that my image gets frozen until I
> close chrome and then I get this message: "Connection
There are two presentations (tabs):
- ‘Contents' shows the plain file
- ‘Pillar’ shows the syntax highlighting.
Can you check?
Doru
> On Nov 14, 2017, at 9:57 PM, Offray Vladimir Luna Cárdenas
> wrote:
>
> Thanks Doru,
>
> Installation works, but syntax hightligthning and image preview are
What is the recommended way for a C basic type to be passed-by-reference to
function wanting to use it for output.
For example 'width' & 'height' here in this library unction...
int FPDF_GetPageSizeByIndex(FPDF_DOCUMENT document,
int page_index,
Op 15-11-2017 om 01:49 schreef Sean P. DeNigris:
Again, it seems that just automatically rerunning the test immediately after
a human-manipulated run and setting the color based on that second run
addresses all points on both sides, no?
How many times do you want to restart execution? I have wr
If this is a problem with OSSubprocess I am happy to help it debug it, but
please share with me the exact steps to reproduce it and which code to look
at. And which OS and which Pharo. And it should be 32 bits (OSSubprocess
doesn't work on 64 yet)
Thanks,
On Tue, Nov 14, 2017 at 9:47 PM, Sean P.
>
> Again, it seems that just automatically rerunning the test immediately
> after a human-manipulated run and setting the color based on that second run
>
Absolutely!
(Although, I was kind of looking forward to the third colour discussions.
My vote would have been for paisley!)
On Tue, Nov 14
Ben Coman wrote
> Or it could go to Amber, half-way between green & red to mean probably
> correct.
Ha ha.
Again, it seems that just automatically rerunning the test immediately after
a human-manipulated run and setting the color based on that second run
addresses all points on both sides, no?
Alistair Grant wrote
> This looks like you are using an old (cached?) version.
Ugh, yes. I just deleted the local clone and let Iceberg reclone.
Now when I tried:
`GoogleChrome get:
'https://finance.yahoo.com/quote/%5EAXJO/history?p=%5EAXJO'`
I got:
Error: Error: posix_spawn(), code: 2, d
On 15 November 2017 at 00:14, Richard Sargent wrote:
> >> I would expect it to turn green if I press resume.
>
> I disagree with your expectations. You are arguing that we should operate
> is if "probably correct" is the same as "correct". That's why we have
> ty software.
>
> I have no objec
On 15 November 2017 at 00:07, Todd Blanchard wrote:
> I've got it loaded, have fixed up the library path and fixed the test for
> version (built in lib returns very different version string).
>
> I have many tests green. However, as before, tests involving
> CXSourceRange that return CXSourceLoc
On 15 November 2017 at 00:17, Todd Blanchard wrote:
> Yeah, I don't know if that is necessarily worth doing TBH.
>
> Generally enumerations are going to be default int size unless you have
> values that are out of range.
>
> In this case you have a function that returns a long. In a strictly typ
The last was a question :-P Is PharoChrome expecting to be logged in to
some Google account to work?
Cheers,
Offray
On 14/11/17 18:18, Offray Vladimir Luna Cárdenas wrote:
> Hi Alistair,
>
> The example is not working for me. When I run it, a chrome session is
> open but nothing happens there,
Hi Alistair,
The example is not working for me. When I run it, a chrome session is
open but nothing happens there, except that my image gets frozen until I
close chrome and then I get this message: "ConnectionTimedOut: Cannot
connect to 127.0.0.1:9222". What is the expected behavior? PharoChrome
e
OK, the development branch solve this, as shown in
http://ws.stfx.eu/O6J4CJ1FZF89. Now I'm getting an unresponsive image
until I close Chrome, but I think that was talked in the thread. I'll
revise.
Cheers,
Offray
On 14/11/17 17:28, Offray Vladimir Luna Cárdenas wrote:
> Hi Alistar,
>
> I have
Hi Alistar,
I have tried to run the examples, but seems that installation doesn't
include all needed package. At the beginning I installed OSUnix and then
OSLinuxUbuntu. None of them seems to include "AKGOSProcess", so the
"GoogleChrome get: 'http://pharo.org'" example raises:
"#command:arguments:
Hi
we have a PhD position in France around IoT and Pharo.
Description
Over the last years, the RMOD team of INRIA Lille and the CAR theme of
IMT Lille Douai have been working together on creating tiny language
core. For example, Guillermo Polito demonstrated in his PhD a fully
reflective kernel
On 10 November 2017 at 22:30, Alistair Grant wrote:
> On 9 November 2017 at 22:12, Norbert Hartl wrote:
>> is there a good explanation why
>>
>> ‚foo‘ asFileReference parent basename
>>
>> gives ‚/‘ ?
>
> I'd like to think about this a bit more, but at first glance the
> problem seems to be that
Hi,
The readme is clearer now about Iceberg integration as an option not as
prerequisite. Installation works, but Pillar preview tab is grey and
clicking on it rises: "Instance of FFIExternalResourceManager class did
not understand #removeResource:". Also the syntax highlighting in the
(plain) Pil
Thanks Doru,
Installation works, but syntax hightligthning and image preview are
disabled. I don't know if this is because is the same image with the
installation of GT Documenter, installed.
Cheers,
Offray
On 14/11/17 12:15, Tudor Girba wrote:
> Hi,
>
> Please retry again by loading the #deve
On 14 November 2017 at 19:13, Alistair Grant wrote:
> Hi Sean,
>
> On 14 November 2017 at 19:06, Sean P. DeNigris wrote:
>> Alistair Grant wrote
>>> I've committed some fixes to the development branch:
>>
>> Thanks!
>>
>> I tried your example, but apparently the OSXProcess class, which is
>> refe
Hi Sean,
On 14 November 2017 at 19:06, Sean P. DeNigris wrote:
> Alistair Grant wrote
>> I've committed some fixes to the development branch:
>
> Thanks!
>
> I tried your example, but apparently the OSXProcess class, which is
> referenced in openChromeWith: is missing. Also, no class in the image
Alistair Grant wrote
> I've committed some fixes to the development branch:
Thanks!
I tried your example, but apparently the OSXProcess class, which is
referenced in openChromeWith: is missing. Also, no class in the image seems
to define #createProcess:, which is sent to OSXProcess there
-
Thanks both, Alex and Doru for your quick answers. I'm using Manjaro
Cinnamon Edition[1]. If you need any help with 32 bits over 64 bits
systems, let me know.
[1] https://manjaro.org/community-editions/
Cheers,
Offray
On 14/11/17 12:46, Aliaksei Syrel wrote:
> Offray, which edition of Manjaro
Offray, which edition of Manjaro do you have? (XFCE, KDE or Gnome)
Cheers,
Alex
On 14 November 2017 at 18:41, Aliaksei Syrel wrote:
> Hi Offray,
>
> I agree with your point of view. It is in our best interests to make it
> work as smoothly as possible, ideally automagically :)
> Now I will try
Hi Offray,
I agree with your point of view. It is in our best interests to make it
work as smoothly as possible, ideally automagically :)
Now I will try to install Pharo6.1 on Manjaro Linux in order to see if
there is something that needs to be noted in README.md.
One of the biggest problems on l
Hi,
We changed the baseline to not require Moz2D on Linux. Could you please try
again?
I also updated the README.
Cheers,
Doru
> On Nov 14, 2017, at 6:25 PM, Offray Vladimir Luna Cárdenas
> wrote:
>
> Alex,
> I understand that frustration on installation could be motivated by other
> issu
Alex,
I understand that frustration on installation could be motivated by
other issues instead of GT Documenter, but if the team ask to use
"|Iceberg enableMetacelloIntegration: true." |in the project readme,
where it also says that is supported for Pharo 6.1 and 7.0, is natural
to think that some
Hi,
Please retry again by loading the #development version in Pharo 6.1:
Gofer new
smalltalkhubUser: 'Pier' project: 'Pillar';
configuration;
loadDevelopment.
You should get the extension out of the box.
Please let me know if it works.
Cheers,
Doru
> On Nov 14, 2017, at 5:55 PM,
Hi Doru,
On 14/11/17 11:36, Tudor Girba wrote:
> Hi Offray,
>
> There are two issues that I take from your email. So, please allow me to
> address them separately:
>
> 1. The process of installing the new GT (with Documenter)
> GT is meant to load in Pharo 6.1. It is tested tested automatically
Sven
>From the thread discussion here my take.
- I do not think that we want to reuse any of the old streams.
- So first Zn to replace the binary and MultiUglyStream and after we
will have to check
if we should port the design of Xtream (but not the API) to Pharo.
Stef
On Tue, Nov 14, 2017 at 5
Denis I agree. I do not like to code in reverse order.
On Tue, Nov 14, 2017 at 4:49 PM, Denis Kudriashov wrote:
> 2017-11-14 16:30 GMT+01:00 Steffen Märcker :
>>
>> I forgot to mention, that the most recent code for Pharo is already on
>> Github: https://github.com/Pharophile/Transducers
>>
>> R
For git / iceberg first time users:
Please read the tip and tricks booklet available on http://books.pharo.org
On Tue, Nov 14, 2017 at 5:45 PM, Aliaksei Syrel wrote:
> Hi Offray,
>
> I understand your frustration, but with all respect, the fact that you have
> problems with Iceberg does not mean
Thank you, Sven. That was a much better place for internalizing after
reconstituting. I now have bi-directional substitutions working with STON. I’m
grateful.
Sent from ProtonMail Mobile
On Tue, Nov 14, 2017 at 09:24, Sven Van Caekenberghe wrote:
> Henry, > On 14 Nov 2017, at 15:02, henry wro
Hi Offray,
I understand your frustration, but with all respect, the fact that you have
problems with Iceberg does not mean that GT Documenter or any other GT tool
is responsible for described problems.
Most complains about bloc, brick, whatever is because of unrelated stuff.
It is a little bit di
What operating system are you on? What version of Pharo do you use? Is it 32b
or 64b?
Cheers,
Doru
> On Nov 14, 2017, at 5:33 PM, Offray Vladimir Luna Cárdenas
> wrote:
>
>
>
> On 14/11/17 10:36, Offray Vladimir Luna Cárdenas wrote:
>
> [...]
>> I have thought that Git is overcomplicated
Hi Offray,
There are two issues that I take from your email. So, please allow me to
address them separately:
1. The process of installing the new GT (with Documenter)
GT is meant to load in Pharo 6.1. It is tested tested automatically several
times a day both on Windows (Appveyor) and on Linux
On 14/11/17 10:36, Offray Vladimir Luna Cárdenas wrote:
[...]
> I have thought that Git is overcomplicated for most of the developers'
> tasks and communities. I don't know if the root of previous issues is
> in the "Iceberg enableMetacelloIntegration: true" line, but having to
> get your pair o
I've committed some fixes to the development branch:
1. MacOS hopefully works now (I don't have access to the platform, so
can't test it).
2. The development version of Beacon is loaded (which is required for
the InMemoryLogger).
3. The README is a tiny bit better.
4. Added #extractTables.
As an
Yeah, I don't know if that is necessarily worth doing TBH.
Generally enumerations are going to be default int size unless you have values
that are out of range.
In this case you have a function that returns a long. In a strictly typed
language you would be required to do a type cast anyhow.
I
>> I would expect it to turn green if I press resume.
I disagree with your expectations. You are arguing that we should operate is
if "probably correct" is the same as "correct". That's why we have ty
software.
I have no objection to leaving the method uncoloured when you resume after
corre
I've got it loaded, have fixed up the library path and fixed the test for
version (built in lib returns very different version string).
I have many tests green. However, as before, tests involving CXSourceRange
that return CXSourceLocations return all zero'd data. The CXSourceRange struct
loo
2017-11-14 16:30 GMT+01:00 Steffen Märcker :
> I forgot to mention, that the most recent code for Pharo is already on
> Github: https://github.com/Pharophile/Transducers
>
> Reducers was the name of the first very first implementation.
>
> (In fact, I was originally inspired by clojures Reducers l
I have been just trying to install GT Documenter and is really
frustrating (I have been unable to install it even for the first time!).
This was the list of errors I got and steps I followed, in almost
sequential order, just to get a (bittersweet!) taste of GT Documenter:
* 1st: LGit_GIT_ERROR:
I forgot to mention, that the most recent code for Pharo is already on
Github: https://github.com/Pharophile/Transducers
Reducers was the name of the first very first implementation.
(In fact, I was originally inspired by clojures Reducers lib. After
implementing it in Smalltalk, I developed
> On 14 Nov 2017, at 16:00, Steffen Märcker wrote:
>
> Hi,
>
>> Are transducers the subject of your thesis ?
>
> No. Transducers is my side project. I've implemented a package for
> VisualWorks. Unfortunately, I did not finish the port to Pharo yet, simply
> due to a lack of time. Originall
Found this on /r/programming today. Seemed relevant. Gist is that YAML spec
is ambiguous and implementations seem to disagree widely on proper
interpretation.
https://github.com/cblp/yaml-sucks
> On Nov 10, 2017, at 10:37 AM, Andrew Glynn wrote:
>
> YAML is what it says, lol.
>
> I still
Hi,
Are transducers the subject of your thesis ?
No. Transducers is my side project. I've implemented a package for
VisualWorks. Unfortunately, I did not finish the port to Pharo yet, simply
due to a lack of time. Originally, transducers evolved in the clojure
community. I figured, the c
> On 14 Nov 2017, at 15:33, Steffen Märcker wrote:
>
> Hi!
>
>>> Yes, I agree, Xtreams is much better (but steep learning curve).
>>>
>>> I just wanted to point out that my contributions in Zn streams focus and
>>> better/simpler byte/character IO.
>>
>> Yes, and it is really nice.
>> Intere
Hi!
Yes, I agree, Xtreams is much better (but steep learning curve).
I just wanted to point out that my contributions in Zn streams focus and
better/simpler byte/character IO.
Yes, and it is really nice.
Interesting how many users we have in system for general streams?
(created on arbitrary
Henry,
> On 14 Nov 2017, at 15:02, henry wrote:
>
> Hello, I am trying to extend STON to allow for substitutions as data is
> written out or read in. On the write side I got it working as #nextPut: is
> recursively called, so that is the perfect place to substitute before an
> object is writt
Richard - I better understand what you are saying now. If you change the method
and save it (hence restarting on the stack) I would expect it to turn green if
I press resume. That is the TDD flow I expect, and one which sunit and coding
in the debugger was predicated on.
However, there is the p
I’ll agree that YAML is not an ideal syntax - but I have to also add that I
wasn’t that impressed with Travis either, and reading between the lines its the
combo of both that might be catching you out.
Even with a few glitches, I’ve been impressed with GitLab although the team I
worked with rec
Thx. Thats exactly what I was looking for. The key part being "self
isInitializer" where...
isInitializer
^ selector = #initialize and: [classIsMeta]
Now I also see "self isExternalStructureFieldDefinition"
"Postloading of FFI fields. This code will be called when loading FFI
struc
Hello, I am trying to extend STON to allow for substitutions as data is written
out or read in. On the write side I got it working as #nextPut: is recursively
called, so that is the perfect place to substitute before an object is written.
I have tested and my changes work well, where I have an a
2017-11-14 14:25 GMT+01:00 Sven Van Caekenberghe :
>
> > Yes, Zn streams focus on classic binary(byte) / character streams.
> >
> > Streaming over arbitrary data is very cool and well covered by the old
> ones.
> >
> > While I really like traditional streams I can not agree here. Sometimes
> it rem
> On 14 Nov 2017, at 14:18, Denis Kudriashov wrote:
>
>
> 2017-11-14 14:00 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 14 Nov 2017, at 09:53, Denis Kudriashov wrote:
> >
> > I look at the code, So Zinc provides only binary/character streams. Right?
>
> Yes, Zn streams focus on classic bin
2017-11-14 14:00 GMT+01:00 Sven Van Caekenberghe :
>
>
> > On 14 Nov 2017, at 09:53, Denis Kudriashov wrote:
> >
> > I look at the code, So Zinc provides only binary/character streams.
> Right?
>
> Yes, Zn streams focus on classic binary(byte) / character streams.
>
> Streaming over arbitrary dat
> On 14 Nov 2017, at 10:20, Prof. Andrew P. Black wrote:
>
>
>> On 13 Nov 2017, at 20:27 , Sven Van Caekenberghe wrote:
>>
>> There is a discussion about positioning (#position , #position: and related)
>> but these cannot be supported _in general_ by the kind of streams described
>> above
> On 14 Nov 2017, at 09:53, Denis Kudriashov wrote:
>
> I look at the code, So Zinc provides only binary/character streams. Right?
Yes, Zn streams focus on classic binary(byte) / character streams.
Streaming over arbitrary data is very cool and well covered by the old ones.
> About contribut
> On 14 Nov 2017, at 09:40, Pavel Krivanek wrote:
>
> Hi,
>
> the #initialize message is sent only to the classes that implement this
> method. In *.st files it is an explicit call, Monticello does it slightly
> smarter way, see MCMethodDefinition>>#postloadOver:
Note: the actual source cod
right now FFIExternalEnumeration support int32 and uint32 types, but I think is
not hard to create a FFIExternalLongEnumeration or whatever is need.
FFIExternalEnumeration >> initializeEnumeration, however, could be better
refactored, I admit ;)
> On 13 Nov 2017, at 23:41, Ben Coman wrote:
>
Hi
Try this one:
#(1 2 3) with: 'abc' do: [ :aNumber :aLetter | do
something first with 1 and $a,
then with 2 and $b,
and finally with 3 and $c ]
2017-11-14 10:10 GMT+01:00 Prof. Andrew P. Black :
> What method will execute a t
> On 13 Nov 2017, at 20:27 , Sven Van Caekenberghe wrote:
>
> There is a discussion about positioning (#position , #position: and related)
> but these cannot be supported _in general_ by the kind of streams described
> above.
I agree with that. But I think that general streams can, and shoul
Stephane Ducasse-3 wrote
> I wonder if we packaged somewhere the removed deprecated method.
> We should do that but since we do it manually I guess that this is ad-hoc.
>
> Stef
>
> On Sun, Nov 12, 2017 at 2:45 PM, Alistair Grant <
> akgrant0710@
> > wrote:
>> Hi Stef,
>>
>> On 12 November 2017
What method will execute a two-parameter block with corresponding pairs of
elements from two separate Ordered Collections.
something like this example:
#(1 2 3) and: 'abc' do: [ :aNumber :aLetter | do
something first with 1 and $a,
2017-11-14 9:53 GMT+01:00 Denis Kudriashov :
> I look at the code, So Zinc provides only binary/character streams. Right?
>
> About contribution: it is in external repository of Sven. Can we
> contribute with normal process, create pull request into Pharo repo?
>
yes, time to time we make sync wi
Hi Sean,
You can always try:
exception freeze.
freeze will copy the stack so it is usable in a posterior debug session
even if the original contexts died.
exception debug.
Opens a debugger :)
On Mon, Nov 13, 2017 at 5:20 PM, Sean P. DeNigris
wrote:
> Tim Mackinnon wrote
> > you can overri
I look at the code, So Zinc provides only binary/character streams. Right?
About contribution: it is in external repository of Sven. Can we contribute
with normal process, create pull request into Pharo repo?
2017-11-14 9:36 GMT+01:00 Guillermo Polito :
> To a package next to block?
>
> On Tue,
In the end, you need to have bitmaps for the screen.
Rendering is the projection of vectors onto pixels.
But you don't want to lose the vectors, because you need them for interactions
(mouse, keyboard focus).
I think that it is extremely sexy to have an interactive viewer for PDF!
Writing a ren
Hi,
the #initialize message is sent only to the classes that implement this
method. In *.st files it is an explicit call, Monticello does it slightly
smarter way, see MCMethodDefinition>>#postloadOver:
Cheers,
-- Pavel
2017-11-14 3:08 GMT+01:00 Ben Coman :
> Because I'm lazy to experiment this
Class side #initialize is executed only when a class is loaded for the
first time.
Posteriors "updates" to the class, or even to the initialize method do not
re-execute #initialize.
Now, about the FFI particular requirements, I'd let Esteban answer :)
On Tue, Nov 14, 2017 at 3:08 AM, Ben Coman w
To a package next to block?
On Tue, Nov 14, 2017 at 9:16 AM, Denis Kudriashov
wrote:
> What about contributing to zinc streams? Imaging that I will create block
> based streams, collecting:/selecting streams like in XSteam. Where I should
> put them?
>
>
> 2017-11-13 23:51 GMT+01:00 Norbert Hart
What about contributing to zinc streams? Imaging that I will create block
based streams, collecting:/selecting streams like in XSteam. Where I should
put them?
2017-11-13 23:51 GMT+01:00 Norbert Hartl :
>
>
> > Am 13.11.2017 um 21:08 schrieb Stephane Ducasse >:
> >
> >> On Mon, Nov 13, 2017 at
75 matches
Mail list logo
