I just tried it on my Ubuntu workstation and it appeared to save
everything like it should. So it seems specific to the Windows version.
On 6/14/2016 11:37 PM, Bernardo Ezequiel Contreras wrote:
im on debian with
Pharo5.0
Latest update: #50760
i just add a whitespace in the class comment of t
im on debian with
Pharo5.0
Latest update: #50760
i just add a whitespace in the class comment of the class RxParser and then
follow your steps, saving the slice locally in a directory.
On Wed, Jun 15, 2016 at 12:08 AM, Mark Bratcher wrote:
> Thanks for trying it. Are you on Windows and Pharo
Thanks for trying it. Are you on Windows and Pharo 5.0?
Can you tell me what item you changed? I'd be curious just to try the
same thing.
On 6/14/2016 11:04 PM, Bernardo Ezequiel Contreras wrote:
i tried your steps locally in a directory with a fake change and i
couldnt reproduce the bug, i
i tried your steps locally in a directory with a fake change and i couldnt
reproduce the bug, i got the slice and the dependent package(with the fake
change).
please report it, someone with more knowledge should check it.
On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher wrote:
> Just saving th
Just saving the slice to the repository (as the instructions indicate)
does not save the code also, and Monticello marks the slice and
associated packages all clean when just saving the slice. So I'm
thinking bug...?
On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote:
the slice has no c
the slice has no code, it just a reference to the dependencies (the dirty
packages), those dirty packages should be save in the repository(files
ended with mcz in your directory)
if you don't have those files in the local repository(directory), theres a
bug.
On Tue, Jun 14, 2016 at 11:33 PM, Mark
I opened the MCZ file saved for the slice package and it has no code
changes in it. It just has the dependency information. So it does seem
that more has to be saved to the repository than just the SLICE. Or, the
SLICE operation isn't "capturing" the code properly as part of the
package. In one
I have the same error, even if I save the slice to a local repository.
So my steps are:
1) Open a clean Pharo 5.0 image
2) Modify one class#selector in Regex-Core
3) "Accept" the change (it prompts me to enter my name, which I do as
MarkBratcher)
4) Open Monticello, and see "*Regex-Core (Th
there's something fishy going on. (the dependency wasn't save to the inbox).
in the other hand, the contribution steps could be improved
On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher wrote:
> Bernardo
>
> Thank you. That's a good idea. I'll try that. I was surprised that it
> didn't go to th
Bernardo
Thank you. That's a good idea. I'll try that. I was surprised that it didn't go
to the inbox as I thought I set up the repository path properly.
Mark
Sent from TypeApp
On Jun 14, 2016, 10:00 PM, at 10:00 PM, Bernardo Ezequiel Contreras
wrote:
>i forgot to mention that i used to sa
i forgot to mention that i used to save my slices locally in a directory,
and test the slice with a new image and see if the merge of the slice has
no conflicts, to be sure that the monkey will work without problems.
and then i copy the slice to the inbox
On Tue, Jun 14, 2016 at 10:53 PM, Bernard
Hi mark,
it seems that your package: Regex-Core-MarkBratcher.39.mcz is not the
inbox.
if you have the package, then you can Copy(button in the monticello
browser) it to the inbox, and try again.
On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher wrote:
> I am trying to push a simple enhancement
I am trying to push a simple enhancement to Pharo50inbox on
smalltalkhub.com. I am running Pharo 5.0 (downloaded within the last
month) on Windows 10.
I started from a completely clean image, made my small change (about 5
lines in an existing Pharo 5.0 class), and I followed all of the
direct
On Wed, Jun 15, 2016 at 1:27 AM, Milan Vavra via Pharo-users
wrote:
>
>
> -- Forwarded message --
> From: Milan Vavra
> To: pharo-users@lists.pharo.org
> Cc:
> Date: Tue, 14 Jun 2016 09:47:21 -0700 (PDT)
> Subject: Re: Pharo 5 accented chars bug/regression
> Thank you all,
> your
Hello, trying to install Pharo on my FreeBSD (11-CURRENT 64bit) with no luck :(
Facts:
1) I can run Linux (even 64bit Linux ELF) binaries on FreeBSD
2) but I can't use precompiled Linux 32binaries from Pharo.org, because there
is no 32libs (32bit linux libs) support on 64bit FreeBSD
3) tried b
Thanks Esteban. I had had also stumbled upon what the latest release actually
is by browsing the ConfigurationOfGarage file. So I'm off to the races now.
Thank you! Apologies, again, for the false alarm.
Mark
Sent from TypeApp
On Jun 14, 2016, 12:57 PM, at 12:57 PM, "Esteban A. Maringolo"
--- Begin Message ---
Thank you all,
your feedback is appreciated.
You have raised many points and so I probably won't be addressing
them all. But thanks again for all. I did read all the responses.
I will re-read them for more inspiration.
I understand posting on this list is like going into a r
Thanks
--
View this message in context:
http://forum.world.st/Don-t-understand-Array-creation-syntax-tp4900533p4900874.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
I don't know about the instructions because I don't maintain the
DBXTalk/Garage website.
But for Pharo 5 the #stable/#release version is 0.5, which in the case
of MySQL should load the package Garage-Mysql-GuillermoPolito.24.
You should load it by executing:
Gofer it
smalltalkhubUser: 'DBXTa
You can add me to the list of interested parties
Sent from the road
> On Jun 14, 2016, at 07:28, sergio ruiz wrote:
>
> Please keep us posted on this.
>
> I have a project that his waiting on this.
>
> Thanks!
>
>
>> On Jun 13, 2016, at 11:10 AM, Steven Costiou wrote:
>>
>> Hi,
>>
>> i h
I don't understand what you've understood…
Parentheses need to be paired for the outer literal array to be recognized.
Technically, opening parentheses could become elements, but not closing
parentheses, since then there would be nothing to close the literal array.
And it would be strange to read
Wiring pi imply that you configure a little bit GPIO also.
Small manipulation that I do not remember really well.
You can check http://wiringpi.com/reference/setup/
If I remember well, you need also i2c.
I now that you need to setup it before using GPIO.
The code was proof of concept and early bi
There doesn't seem to be many Pharoisms in WiringPi; for a much snappier
experience, you might want to check out Squeak instead.
Raspbian ships with both Spur and Non-Spur VM's included (courtesy of Scratch)
which include optimized BitBlt primitives (may be absent from the old Pharo VM)
+ it use
Hi Steven,
I'm also interested. I'll received a Pi 3 soon and I'll want to use the
GPIO as well, as well as looking
at performances issues, especially at the IDE level.
Have you tried to use:
- command line manipulation of the GPIO via OSProcess ?
Create a GPIO file access:
echo 11 > /sys/class
Please keep us posted on this.
I have a project that his waiting on this.
Thanks!
> On Jun 13, 2016, at 11:10 AM, Steven Costiou wrote:
>
> Hi,
>
> i have tried to make it work but so far i can't get it right. Have you been
> able to work with it ?
>
> I used pharo 5 latest non spur image
My bad, the leds were not on the right pins. Now all my leds are off and
my wiring is ok. It still doesn't work, but i'm not sure whether my
setup is wrong or if it just doesn't work anymore on Pharo5.
I will attempt to use the library outside Pharo, reconfigure a Pharo
image & vm and then try it
So if I understood it well, closing Parenthesis are telling that it's the
same element in the Array
--
View this message in context:
http://forum.world.st/Don-t-understand-Array-creation-syntax-tp4900533p4900813.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
27 matches
Mail list logo
