I can't find any info at the Affinity list-server about unsubscribing from
this list. Presumably there is a special address but I can't think what
command to add after pharo-users-???. TIA.
Hedley Finger
hedley.fin...@gmail.com
I have been having an enduring problem with Pharo "disappearing" on any machine
I try it on. In an effort to resolve that it isn't my code, I want to remove
the Package that contains all my Seaside code so that I can install a minimal
home page under Seaside. This will, at least exonerate my cod
Hi Tim.
aPackage classTagForClass: aClass
Calypso shows more kind of children than just a package tags. And it can be
extended. That's the reason why you don't have raw packageTag there.
Also in Pharo 6 new API was introduced to handle tags of classes and
methods in similar way
https://pharo.man
Actually - I’ve realised that Calypso can give me the tag name from its context
- (aToolContext lastSelectedClassGroup).
However it does highlight a very strange package/tag design. Are you not
supposed to be easily able to derive RPacakgeTags?
Tim
> On 14 Feb 2019, at 13:19, Tim Mackinnon wr
I’m trying to understand how RPackage and RPackageTag work in Pharo7? It seems
different than Pharo6 at least with Nautilus (vs Calypso) - as previously the
Nautilus UI gave me the RPacakgeTag, and I could just work with that. Calypso
doesn’t seem to give me the tag object, but if I have a known
Thanks,
I made a file out with all the code I have right now.
The code can be found here :
https://gist.github.com/RoelofWobben/00829deff93e98523f5090383a656582
But still I cannot make it work.
What I did is make a class SantaFloorAct
Op 25-11-2018 om 19:12 schreef dorellang:
What you want to do is:
findBasement: input2
"solution to part1 of this challenge"
input2 withIndexDo: [ :element :index | |action| action:=
SantaFloorAction getActionFor: element. floor := action
calculateNewFloor: floor index: index ].
Hi Roelof,
is not easy to understand the question , without contents.
#calculateNewFloor:index:
- I assume you implemented the method on an action class (SantaAction).
- In the method I see no usage from argument index
but to send the method with a index:
aFoor := aAction calculateNewFloor: a
What you want to do is:
findBasement: input2
"solution to part1 of this challenge"
input2 withIndexDo: [ :element :index | |action| action:=
SantaFloorAction getActionFor: element. floor := action
calculateNewFloor: floor index: index ].
^ counter
Notice how I added the '
Hello,
I have made this function :
calculateNewFloor: aFloor index: index
"comment stating purpose of message"
|action floor |
action:= SantaAction getActionFor: aFloor. floor := action
doMovementFor: aFloor
now I want to send a message to this function :
findBasement: input2
To summarize this thread:
Make sure Jupyter (http://jupyter.org/) is installed properly.
Then ZeroMQ will work with the Pharo Smalltalk kernel (
https://github.com/jmari/JupyterTalk)
HH.
On 8/24/18, H. Hirzel wrote:
> user25@Latitude2:~$ find . -name libzmq*
> ./anaconda3/lib/pkgconfig/libzmq.p
user25@Latitude2:~$ find . -name libzmq*
./anaconda3/lib/pkgconfig/libzmq.pc
./anaconda3/lib/libzmq.so.5
./anaconda3/lib/python3.6/site-packages/zmq/backend/cython/libzmq.pxd
./anaconda3/lib/libzmq.so
./anaconda3/lib/libzmq.so.5.1.5
./anaconda3/lib/libzmq.la
./anaconda3/lib/libzmq.a
./anaconda3/pkg
it's done.
please try again
Thanks
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
I see...anaconda installs everything in home directory. ZeroMQ version
won't be a problem, probably it is backward compatible.
I will include $home/anaconda3/lib in the searching path.
El vie., 24 ago. 2018 a las 7:10, H. Hirzel ()
escribió:
> On 8/24/18, H. Hirzel wrote:
> > Thank you, Jesús M
Thinking about it again:
Going for a Python - anaconda distribution related hack is to
specific. I am rather interested in a regular ZeroMQ installation for
Pharo.
I have now created a new Ubuntu 18.04.1 bionic beaver installation and
the question is: how do I set ZeroMQ up togehter with Pharo
(Ju
On 8/24/18, H. Hirzel wrote:
> Thank you, Jesús Marí. I reloaded your updated JupyterTalk Pharo
> Smalltalk package which now looks for more places to find the library
> ZeroMQ.
>
> Unfortunately it still did not find the ZeroMQ library.
>
> The following command shows where there is a ZeroMQ libr
Thank you, Jesús Marí. I reloaded your updated JupyterTalk Pharo
Smalltalk package which now looks for more places to find the library
ZeroMQ.
Unfortunately it still did not find the ZeroMQ library.
The following command shows where there is a ZeroMQ library: [1]
root@Latitude2:/# find / -name
Load it again I've updated the unix64ModuleName to search for the correct
library name.
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Pharo 6.1 - 64bit on Ubuntu 18.04.1 (Bionic Beaver, 64bit).
On 8/23/18, Marten Feldtmann wrote:
> Simple question:
>
> Pharo 32 or 64 bit ?
>
> If you work with Pharo32 you need to install the 32bit (Unix)-libraries
> for 0MQ. If you work with Pharo64 you use the 64bit (Unix)-Libraries.
>
> So -
Simple question:
Pharo 32 or 64 bit ?
If you work with Pharo32 you need to install the 32bit (Unix)-libraries
for 0MQ. If you work with Pharo64 you use the 64bit (Unix)-Libraries.
So - what is your environment ?
Marten
Am 23.08.2018 um 10:54 schrieb H. Hirzel:
> Hello
>
> I installed Jupyter
P.S. I assume I have to install a package on Ubuntu 18.04 Bionic
Beaver. The question is which one.
Note: I plan to write a comprehensive installation instruction for JuypterTalk.
On 8/23/18, H. Hirzel wrote:
> Hello
>
> I installed JupyterTalk [1]. With it comes a ZeroMQ implementation
> [2]. T
Hi Sven,
On 12 March 2018 at 19:38, Sven Van Caekenberghe wrote:
> Hi Alistair,
>
>> On 12 Mar 2018, at 19:06, Alistair Grant wrote:
>>
>> On 12 March 2018 at 10:03, Guillermo Polito
>> wrote:
>>>
>>> Hi,
>>>
>>> do not forget also that there is an entire chapter on FileSystem in here:
>>>
>>>
Hi Alistair,
> On 12 Mar 2018, at 19:06, Alistair Grant wrote:
>
> On 12 March 2018 at 10:03, Guillermo Polito wrote:
>>
>> Hi,
>>
>> do not forget also that there is an entire chapter on FileSystem in here:
>>
>> http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf
>>
On 12 March 2018 at 10:03, Guillermo Polito wrote:
>
> Hi,
>
> do not forget also that there is an entire chapter on FileSystem in here:
>
> http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf
>
> And I particularly recommend everybody dealing with files to read about how
> On 12 Mar 2018, at 10:11, Guillermo Polito wrote:
>
> You can also do:
>
> FileSystem disk workingDirectory parent / 'public'.
>
> I feel it cleaner :)
Indeed, the power of messages.
> On Sun, Mar 11, 2018 at 10:27 AM, john pfersich wrote:
> Works on Ubuntu 16.04
>
> Sent from my iPhone
You can also do:
FileSystem disk workingDirectory parent / 'public'.
I feel it cleaner :)
On Sun, Mar 11, 2018 at 10:27 AM, john pfersich wrote:
> Works on Ubuntu 16.04
>
> Sent from my iPhone
> Encrypted email at jgpfers...@protonmail.com
>
> On Mar 10, 2018, at 12:38, Cyril Ferlicot
> wrote
Hi,
do not forget also that there is an entire chapter on FileSystem in here:
http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf
And I particularly recommend everybody dealing with files to read about how
to manage encodings in here:
http://files.pharo.org/books-pdfs/en
What OS are you using? My code was executed on Ubuntu 16.04.
Sent from my iPhone
Encrypted email at jgpfers...@protonmail.com
> On Mar 11, 2018, at 10:37, Alistair Grant wrote:
>
> Hi Hannes,
>
>> On 11 March 2018 at 17:49, H. Hirzel wrote:
>> The first solution given by Sven works fine.
>>
Hi Hannes,
On 11 March 2018 at 17:49, H. Hirzel wrote:
> The first solution given by Sven works fine.
>
> dir := FileSystem workingDirectory / '..' / 'public'.
> dir ensureCreateDirectory.
> (dir / 'myFile.txt') writeStreamDo: [ :out | out << 'Hello World!' ].
>
>
> The second version
The first solution given by Sven works fine.
dir := FileSystem workingDirectory / '..' / 'public'.
dir ensureCreateDirectory.
(dir / 'myFile.txt') writeStreamDo: [ :out | out << 'Hello World!' ].
The second version
obj := (FileSystem workingDirectory / '..' / 'public' / 'testing
> On 11 Mar 2018, at 10:39, john pfersich wrote:
>
> or try
>
> dir := (FileSystem workingDirectory / '..' / 'public' / 'testing' /
> 'test2.txt') ensureCreateFile.
> dir writeStream.
Indeed!
> On Sun, Mar 11, 2018 at 1:16 AM, Sven Van Caekenberghe wrote:
>
>
> > On 11 Mar 2018, at 09:42
or try
dir := (FileSystem workingDirectory / '..' / 'public' / 'testing' /
'test2.txt') ensureCreateFile.
dir writeStream.
On Sun, Mar 11, 2018 at 1:16 AM, Sven Van Caekenberghe wrote:
>
>
> > On 11 Mar 2018, at 09:42, H. Hirzel wrote:
> >
> > Hello
> >
> > This is a follow up question to 'How
Works on Ubuntu 16.04
Sent from my iPhone
Encrypted email at jgpfers...@protonmail.com
> On Mar 10, 2018, at 12:38, Cyril Ferlicot wrote:
>
>
>> On sam. 10 mars 2018 at 21:36, H. Hirzel wrote:
>> Yes, #ensureCreateDirectory is available.
>>
>> I'd like to make sure a directory 'public' is av
> On 11 Mar 2018, at 09:42, H. Hirzel wrote:
>
> Hello
>
> This is a follow up question to 'How do I make sure a directory exists?'
>
> The answer to that question was
>
> dir := FileSystem workingDirectory / '..' / 'public'.
> dir ensureCreateDirectory.
>
>
> Now I want to cre
Hello
This is a follow up question to 'How do I make sure a directory exists?'
The answer to that question was
dir := FileSystem workingDirectory / '..' / 'public'.
dir ensureCreateDirectory.
Now I want to create a writeStream.
dir writeStream
gives 'Unable to open file'
On sam. 10 mars 2018 at 21:49, H. Hirzel wrote:
> I note that 'workingDirectory' is the directory where Pharo is
> launched from. In my case it happens to be the same where the image is
> in but that cannot be assumed generally.
The fact that "workingDirectory" point to the folder from where Ph
I note that 'workingDirectory' is the directory where Pharo is
launched from. In my case it happens to be the same where the image is
in but that cannot be assumed generally.
So
(FileSystem workingDirectory / '..' / 'public') ensureCreateDirectory
Worked fine.
Thanks to all!
--Hannes
On
Operator priority :); unary messages `#ensureCreateDirectory have
precedence over binary `#/`
(FileSystem disk workingDirectory / '../public') ensureCreateDirectory.
Also please note that the workingDirectory should be based on where Pharow
as launched from, if you are looking for the image direc
On sam. 10 mars 2018 at 21:36, H. Hirzel wrote:
> Yes, #ensureCreateDirectory is available.
>
> I'd like to make sure a directory 'public' is available as a sibling
> directory of the working directory (the directory where the Pharo
> image is in)
>
> However
>
> FileSystem disk workingDirect
Yes, #ensureCreateDirectory is available.
I'd like to make sure a directory 'public' is available as a sibling
directory of the working directory (the directory where the Pharo
image is in)
However
FileSystem disk workingDirectory / '../public' ensureCreateDirectory
does not work as
F
>
> There is #ensureCreateDirectory in Pharo but I don't know if it will check
> the parents exists. (And I don't have a Pharo image to check.
>
It will, at least on Windows.
Peter
On sam. 10 mars 2018 at 21:02, H. Hirzel wrote:
> Hello
>
> In Squeak and the dialect independent FileMan [1] there is
>
>
> FileDirectory
>assureExistence
> "Make sure the current directory exists. If necessary, create
> all
> parts in between"
>
>
> What is the equivalen
Probably #ensureCreateDirectory
> On 10 Mar 2018, at 21:01, H. Hirzel wrote:
>
> Hello
>
> In Squeak and the dialect independent FileMan [1] there is
>
>
>FileDirectory
> assureExistence
> "Make sure the current directory exists. If necessary, create all
> parts in between
Hello
In Squeak and the dialect independent FileMan [1] there is
FileDirectory
assureExistence
"Make sure the current directory exists. If necessary, create all
parts in between"
What is the equivalent Pharo method? BTW is there a cheat sheet for
FileSystem operations in
On 8/28/17, Sean P. DeNigris wrote:
> Tim Mackinnon wrote
>> On OSX, you hold the Shift and Alt keys and then click on something.
>
> There is also `Morph cycleHalosBothDirections: true.` to re-enable
> non-Shift
> (i.e. bidirectional) cycling a la Squeak
>
Nice! Many thanks!
--Hannes
> -
>
Tim Mackinnon wrote
> On OSX, you hold the Shift and Alt keys and then click on something.
There is also `Morph cycleHalosBothDirections: true.` to re-enable non-Shift
(i.e. bidirectional) cycling a la Squeak
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/How-do-I-g
On OSX, you hold the Shift and Alt keys and then click on something. I think on
windows its probably Shift+Alt or Shift+Ctrl.
The in-image help explains this under - Pharo Environment Help - Keyboard
Shortcuts - Visual Exploration.
Tim
> On 28 Aug 2017, at 13:33, H. Hirzel wrote:
>
> On 8/
On 8/28/17, p...@highoctane.be wrote:
>
> Dark theme : can code for hours without any trouble.
>
> At the office I am at now 90% of coders are using dark themes.
>
> Indeed the windows buttons are annoying, I have my own little hack to make
> them better.
> When a control bugs you, bring a h
You can use the Catalog Browser?
In tools.
Is it not what you are looking for?
Stef
On Mon, Aug 21, 2017 at 3:58 PM, H. Hirzel wrote:
> Thank you!
>
>
> "Produce a list of Pharo 6 catalog entries (tag: 'Pharo 6.0') in
> markdown format"
>
> | catalog |
> catalog := CatalogProvider default retri
Thank you!
"Produce a list of Pharo 6 catalog entries (tag: 'Pharo 6.0') in
markdown format"
| catalog |
catalog := CatalogProvider default retrieveProjects select: [ :x |
(x at: 'repositoryUrl') =
'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ].
Transcript show: '# Pharo 6 ca
On Mon, Aug 21, 2017 at 11:06:36AM +0200, H. Hirzel wrote:
> What is the code snippet to get a list of all packages with a '6.0'
> tag and their description?
"CatalogProject availableRepositoryURLStrings" gives:
#('http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main'
'http://smalltalk
H. Hirzel wrote:
This helps me to get at the information for a particular singular
entry. I am looking for a list of all catalog entries in 6.0.
That said, if it has menu item (and catalog has), I use Finder to look
in source code directly for that string, and that is a good starting
point. I
H. Hirzel wrote:
This helps me to get at the information for a particular singular
entry. I am looking for a list of all catalog entries in 6.0.
Ah, sorry. Did not get the question properly.
On 8/21/17, Herby Vojčík wrote:
H. Hirzel wrote:
Hello
On 8/17/17, bdurin wrote:
Maybe somethin
This helps me to get at the information for a particular singular
entry. I am looking for a list of all catalog entries in 6.0.
On 8/21/17, Herby Vojčík wrote:
> H. Hirzel wrote:
>> Hello
>>
>> On 8/17/17, bdurin wrote:
>>> Maybe something like having the list of all packages and their version
>
H. Hirzel wrote:
Hello
On 8/17/17, bdurin wrote:
Maybe something like having the list of all packages and their version
included in a given image version on https://pharo.org could be useful.
What is the code snippet to get a list of all packages with a '6.0'
tag and their description?
The
Hello
On 8/17/17, bdurin wrote:
> Maybe something like having the list of all packages and their version
> included in a given image version on https://pharo.org could be useful.
What is the code snippet to get a list of all packages with a '6.0'
tag and their description?
The spotter brings up
Ben,
Thanks for the responses ... I've just tried it again using a freshly
downloaded Pharo6.0 (60265) and using filetree instead of gitfiletree on
my mac (my earlier attempt was using on older Pharo6.0 on Linux) --- so
I had installed gitfiletree into the linux image at some point apparently.
On Thu, Oct 20, 2016 at 5:06 PM, Ben Coman wrote:
> On Thu, Oct 20, 2016 at 6:35 AM, Dale Henrichs
> wrote:
>> I am trying to debug a problem that showed up loading my version of STON
>> into Pharo-6.0. ON Travis, I see the error message[1]:
>>
>> MessageNotUnderstood: receiver of "ifTrue:ifFal
On Thu, Oct 20, 2016 at 6:35 AM, Dale Henrichs
wrote:
> I am trying to debug a problem that showed up loading my version of STON
> into Pharo-6.0. ON Travis, I see the error message[1]:
>
> MessageNotUnderstood: receiver of "ifTrue:ifFalse:" is nil
>
> The code is loading and passing tests in Ph
It looks like some "Failed magic" is involved here. A bit of the stack
for your viewing pleasure:
MessageNotUnderstood: receiver of "ifTrue:ifFalse:" is nil
UndefinedObject(Object)>>doesNotUnderstand: #ifTrue:ifFalse:
STONWriter>>ExecuteUnOptimizedIn:
UndefinedObject(Object)>>mustBeBooleanInMagi
I am trying to debug a problem that showed up loading my version of STON
into Pharo-6.0. ON Travis, I see the error message[1]:
MessageNotUnderstood: receiver of "ifTrue:ifFalse:" is nil
The code is loading and passing tests in Pharo-5.0, 4.0, 3.0 and several
versions of GemStone, so I am inte
Thank you Stephane for the hint.
Through reading
UIManager createPageTestWorkspace
I found
UIManager default edit: (MyTextCollection at: 101) label: 'Text 101'.
It works fine for my purpose.
--Hannes
On 9/2/16, stepharo wrote:
> Look into UIManager helpers.
>
> I have to run now.
Look into UIManager helpers.
I have to run now.
Le 1/9/16 à 21:47, H. Hirzel a écrit :
Hello
I want to display a string (no code) in a text window.
What is the equivalent of the Squeak expression
StringHolder
new textContents: (MyTextCollection at: 101);
openLabel:
Answer:
To open a text window with text I do
Workspace openContents: (MyTextCollection at: 101).
Display as text only:
At the bottom I can switch between
- plain text
- smalltalk scripting
But the text remains red in both cases.
What am I missing?
--Hannes
On 9/1/16, H. Hirzel wrote
Hello
I want to display a string (no code) in a text window.
What is the equivalent of the Squeak expression
StringHolder
new textContents: (MyTextCollection at: 101);
openLabel: 'theText 101'
in Pharo 5.0?
Regards
Hannes
the problem is that for the shortcut we could to a spy in the menu. For
other actions were
we do not have double ways to access them this is difficult to explain
to the user how to do something
without being far too much boring for the one knowing.
Stef
Le 7/7/16 à 01:58, Ben Coman a écr
On Thu, Jul 7, 2016 at 2:33 AM, Dale Henrichs
wrote:
>
>
> On 07/06/2016 06:37 AM, Cyril Ferlicot Delbecque wrote:
>>
>>
>> On 06/07/2016 15:28, Dale Henrichs wrote:
>>>
>>> Alistair,
>>>
>>> Well thank you very much ... Those two menu items are very well hidden:)
>>> Until you prompted me to look
On 07/06/2016 06:37 AM, Cyril Ferlicot Delbecque wrote:
On 06/07/2016 15:28, Dale Henrichs wrote:
Alistair,
Well thank you very much ... Those two menu items are very well hidden:)
Until you prompted me to look closely I never even noticed that little
icon...
Is there a reason that those tw
On 06/07/2016 15:28, Dale Henrichs wrote:
> Alistair,
>
> Well thank you very much ... Those two menu items are very well hidden:)
> Until you prompted me to look closely I never even noticed that little
> icon...
>
> Is there a reason that those two menu items are not on the stack pane menu?
Alistair,
Well thank you very much ... Those two menu items are very well hidden:)
Until you prompted me to look closely I never even noticed that little
icon...
Is there a reason that those two menu items are not on the stack pane menu?
Now that I used the copystack menu item, I see what ma
Hi Dale,
On Tue, Jul 05, 2016 at 11:53:19AM -0700, Dale Henrichs wrote:
> While we're on the subject, when one does get a debugger How is a beginner
> supposed to share the error information with the folks on this list?
>
> I have a debugger open on the stack after executing:
>
> Metacello new
Nicolas,
Over the long July 4th weekend, I realized that the package-cache needs
to be considered in the package naming scheme ...
As currently implemented, the GitFileTree scheme of sequentially
numbering version numbers based on the order of git commits is
problematic when the package-cach
While we're on the subject, when one does get a debugger How is a
beginner supposed to share the error information with the folks on this
list?
I have a debugger open on the stack after executing:
Metacello new
configuration: 'GitFileTree';
version: #stable;
repository: 'http://s
Using a freshly downloaded Pharo5.0 and the Catalog Browser, I'm getting
a Notification with the message in the subject line while installing
GitFileTree, but I get a notification with no indication of why or what
the error is ... how am I supposed to debug this?
I mean I can guess what load e
Hi Norbert,
Le 30/06/2016 08:51, Norbert Hartl a écrit :
Am 30.06.2016 um 01:26 schrieb Dale Henrichs :
On 6/29/16 3:44 PM, Ben Coman wrote:
On Thu, Jun 30, 2016 at 3:04 AM, Dale Henrichs
wrote:
On 6/29/16 1:00 AM, Thierry Goubier wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
..
> Am 30.06.2016 um 01:26 schrieb Dale Henrichs
> :
>
>
>
>> On 6/29/16 3:44 PM, Ben Coman wrote:
>> On Thu, Jun 30, 2016 at 3:04 AM, Dale Henrichs
>> wrote:
>>>
On 6/29/16 1:00 AM, Thierry Goubier wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
> I'm pretty certai
On Thu, Jun 30, 2016 at 7:26 AM, Dale Henrichs
wrote:
>
>
> On 6/29/16 3:44 PM, Ben Coman wrote:
>>
>> On Thu, Jun 30, 2016 at 3:04 AM, Dale Henrichs
>> wrote:
>>>
>>>
>>> On 6/29/16 1:00 AM, Thierry Goubier wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
>
>
...
>>
On 6/29/16 3:44 PM, Ben Coman wrote:
On Thu, Jun 30, 2016 at 3:04 AM, Dale Henrichs
wrote:
On 6/29/16 1:00 AM, Thierry Goubier wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
while reading the code I recogni
On Thu, Jun 30, 2016 at 3:04 AM, Dale Henrichs
wrote:
>
>
> On 6/29/16 1:00 AM, Thierry Goubier wrote:
>>
>> Le 29/06/2016 00:55, Dale Henrichs a écrit :
>>>
>>>
>> ...
>>> I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
>>> while reading the code I recognized that
On 6/29/16 6:30 AM, Nicolas Passerini wrote:
Thank you Thierry!
I have more questions inline.
On Wed, Jun 29, 2016 at 10:44 AM, Thierry Goubier
mailto:thierry.goub...@gmail.com>> wrote:
All the Monticello GUI : track down version numbers to order stuff
in the lists views everywhere
On 6/29/16 5:30 AM, Thierry Goubier wrote:
Le 29/06/2016 12:57, Ben Coman a écrit :
On Wed, Jun 29, 2016 at 4:00 PM, Thierry Goubier
wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
while reading the code I
On 6/29/16 1:00 AM, Thierry Goubier wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
while reading the code I recognized that many of the basic patterns were
exactly as I had remembered them from years ago ... ho
On 6/29/16 1:44 AM, Thierry Goubier wrote:
Hi Nicolas,
Le 29/06/2016 10:24, Nicolas Passerini a écrit :
Hi Dale, Therry, I am working on a libgit-based git integration for
Pharo and I am facing the same problem about version numbers. So maybe I
can help you if you are working on that.
How i
On 6/29/16 1:24 AM, Nicolas Passerini wrote:
Hi Dale, Therry, I am working on a libgit-based git integration for
Pharo and I am facing the same problem about version numbers. So maybe
I can help you if you are working on that.
I had the same idea as Dale, using short SHAs instead of correlativ
On 6/29/16 1:09 AM, Thierry Goubier wrote:
Dale,
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
Actually, Metacello has a registry of loaded projects (baselines and
configurations) and using Metacello it is possible to determine which
pacakges belong to which projects etc. so it is not
Le 29/06/2016 15:30, Nicolas Passerini a écrit :
Thank you Thierry!
I have more questions inline.
On Wed, Jun 29, 2016 at 10:44 AM, Thierry Goubier
mailto:thierry.goub...@gmail.com>> wrote:
All the Monticello GUI : track down version numbers to order stuff
in the lists views everywhere
On 6/29/16 1:05 AM, Thierry Goubier wrote:
Dale,
you're right, the monticello.meta directory is kept, in part because I
wasn't sure I could get rid of some of the information in some files
in that directory (dependencies, initializers).
Since those files don't usually create conflicts with
On 6/28/16 10:22 PM, Thierry Goubier wrote:
Hi Dale,
Le 29/06/2016 01:50, Dale Henrichs a écrit :
Thierry,
Okay ... it is "working" now ... I was also misled by the fact that you
are continuing to fabricate Monticello version numbers which presumably
cannot be relied upon in any way.
Tugrik
Thank you Thierry!
I have more questions inline.
On Wed, Jun 29, 2016 at 10:44 AM, Thierry Goubier wrote:
> All the Monticello GUI : track down version numbers to order stuff in the
> lists views everywhere.
>
So, if we built a new GUI which does not rely on those version numbers
maybe we coul
Le 29/06/2016 12:57, Ben Coman a écrit :
On Wed, Jun 29, 2016 at 4:00 PM, Thierry Goubier
wrote:
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
while reading the code I recognized that many of the basic patterns wer
On Wed, Jun 29, 2016 at 4:00 PM, Thierry Goubier
wrote:
> Le 29/06/2016 00:55, Dale Henrichs a écrit :
>>
>>
> ...
>>>
>>>
>> I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
>> while reading the code I recognized that many of the basic patterns were
>> exactly as I had rememb
Hi Nicolas,
Le 29/06/2016 10:24, Nicolas Passerini a écrit :
Hi Dale, Therry, I am working on a libgit-based git integration for
Pharo and I am facing the same problem about version numbers. So maybe I
can help you if you are working on that.
How is the libgit integration going?
I had the sa
Hi Dale, Therry, I am working on a libgit-based git integration for Pharo
and I am facing the same problem about version numbers. So maybe I can help
you if you are working on that.
I had the same idea as Dale, using short SHAs instead of correlative
numbers, but I didn't have the time yet to got d
Dale,
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
Actually, Metacello has a registry of loaded projects (baselines and
configurations) and using Metacello it is possible to determine which
pacakges belong to which projects etc. so it is not necessary to
"register packages with a projec
Dale,
you're right, the monticello.meta directory is kept, in part because I
wasn't sure I could get rid of some of the information in some files in
that directory (dependencies, initializers).
Since those files don't usually create conflicts with git, it seemed Ok.
Thierry
Le 29/06/2016 01
Le 29/06/2016 00:55, Dale Henrichs a écrit :
...
I'm pretty certain the MCLazyVersionInfo is the real culprit here ...
while reading the code I recognized that many of the basic patterns were
exactly as I had remembered them from years ago ... however ...
MCLazyVersionInfo this puppy with it
Hi Dale,
Le 29/06/2016 01:50, Dale Henrichs a écrit :
Thierry,
Okay ... it is "working" now ... I was also misled by the fact that you
are continuing to fabricate Monticello version numbers which presumably
cannot be relied upon in any way.
Tugrik-Help-DaleHenrichs.11 will show up in each bran
Thierry,
Okay ... it is "working" now ... I was also misled by the fact that you
are continuing to fabricate Monticello version numbers which presumably
cannot be relied upon in any way.
Tugrik-Help-DaleHenrichs.11 will show up in each branch that includes
the commit for "Tugrik-Help-DaleHen
On 6/28/16 2:16 PM, Thierry Goubier wrote:
Dale,
I'm sure it is possible. Wait, wait! If you have in your .filetree
"Metadata" : "false" then this is fine and it has switched to the
metadata-less mode.
To see the changes on disk, you need to save a new version of your
packages, that shoul
On 6/28/16 2:16 PM, Thierry Goubier wrote:
Dale,
I'm sure it is possible. Wait, wait! If you have in your .filetree
"Metadata" : "false" then this is fine and it has switched to the
metadata-less mode.
To see the changes on disk, you need to save a new version of your
packages, that shoul
1 - 100 of 156 matches
Mail list logo
