Currently wildcard are not supported. I think this is in the roadmap of the GT
team. But not supported for now.
However, there is strictly no need for it. Since you have the dive-in category:
https://dl.dropboxusercontent.com/u/31543901/MyPapers/Kube15a-VISSOFTNIER-SpotterAnalyzer.pdf
Cheers,
Al
Hello
Where export setting save the prefrence in the host file system, on Linux.
I am stuck with it and need to delete it
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
http://google.com/+DrgeoEu
2015-12-06 16:22 GMT+01:00 Hilaire :
> Hello
>
> Where export setting save the prefrence in the host file system, on Linux.
>
> I am stuck with it and need to delete it
>
>
which version?
in pharo 5.0 latest:
~/.config/pharo/5.0/system-settings.ston
Thanks
>
> Hilaire
>
> --
> Dr. Geo
> http:
On 12/06, Hilaire wrote:
> Hello
>
> Where export setting save the prefrence in the host file system, on Linux.
Linux config is normally in '~/.config/pharo/'
>
> I am stuck with it and need to delete it
>
> Thanks
>
> Hilaire
>
> --
> Dr. Geo
> http://drgeo.eu
> http://google.com/+DrgeoEu
Have a look at:
http://www.mail-archive.com/help-smalltalk@gnu.org/msg01225.html
http://www.squeaksource.com/PharoTaskForces.html
http://www.smalltalkhub.com/#!/~Moose/CollectionExtensions
Hernán
2015-12-05 23:21 GMT-03:00 Peter Uhnak :
> Hi,
>
> what would be the equivalent of an OrderedSet?
I submitted an article at Reddit called "Stop Thinking in Terms of Files."
Some guy with the handle "audioen" wrote the following comment:
We have heard that smalltalk appears to use model similar to a LISP machine
of yore in that the programming environment = the OS = the runtime
environment. Onc
There are a lot of questions in there, too much to answer.
The basic answer is that everything is modelled as objects, even the objects
themselves. There is a complete meta model of what could be considered code and
even the execution of code. Furthermore, even versioning is modelled nicely
too
"
*Files belong in the Stone Age"*
*No they do not !*
"Smalltalk is an *image-based* programming language."
An image IS a file !!!
"An image is essentially a self-contained operating system that manages all
the code for you, thanks to
*an easy-to-use IDE"*
*no its not!!! the vm is the virtu
"An image is essentially a self-contained operating system that manages all
the code for you, thanks to an easy-to-use IDE."
I'm not trying to be pedantic. I'm using general parlance to convey an idea,
and the idea is essentially correct. And I'm hardly alone. GemTalk's own
"Pharo, the collaborAct
I didn't say I cannot answer the questions; I said I may not answer them
/optimally/. After all, *I haven't used Smalltalk in a long while*, and I
was never an expert to begin with. I'm certainly not up with the latest
developments in Pharo. (For example, I didn't know that Pharo no longer has
file
And for the record, a number of long-time Smalltalkers have expressed their
appreciation for the work I've done. One of them (a 25-year Smalltalk
veteran!!!) said to me: "You may think the job was thankless, but I think
you did a great job." I really, truly appreciate his accolade.
Hey, I get it.
Excerpts from Sven Van Caekenberghe's message of 2015-12-06 19:39:51 +0100:
> There are a lot of questions in there, too much to answer.
i am interested in the versioning of code and objects.
the poster makes a good point there.
what if i am on a non-networked machine, running pharoNOS or even sq
Le 07/12/2015 02:50, Martin Bähr a écrit :
Excerpts from Sven Van Caekenberghe's message of 2015-12-06 19:39:51 +0100:
There are a lot of questions in there, too much to answer.
i am interested in the versioning of code and objects.
the poster makes a good point there.
The traditional, full
Excerpts from Thierry Goubier's message of 2015-12-07 06:42:51 +0100:
> > i am interested in the versioning of code and objects.
> > the poster makes a good point there.
> The traditional, full approach, would have been to use an object
> oriented database like GemStone. Anything that can version
Sounds a lot like good-old envy, which basically is an always-connected
object db for versioned code artefacts - from Methods, to Classes,
Applications to Configuration Maps. I always miss it immediately when I
work in other languages or Smalltalk dialects. The only thing that comes
close to it
>
> well, i wouldn't need or even want it in memory, so on disk is fine. the
> problem is more likely management of the same. browsing the changes is not
> really convenient. ideally i'd like to see versions in the class-browser
> and
> in the debugger, where on error i could then take a look at o
Le 07/12/2015 07:13, Martin Bähr a écrit :
Excerpts from Thierry Goubier's message of 2015-12-07 06:42:51 +0100:
i am interested in the versioning of code and objects.
the poster makes a good point there.
The traditional, full approach, would have been to use an object
oriented database like Ge
"A Smalltalk Image is your entire system. The Image includes all the tools
required to interact, customize and add functionality to your system, so
Smalltalk’s IDE is a very Integrated Development Environment."
Thats not the case even for someone like me that has been working with
smalltalk for o
Excerpts from Dimitris Chloupis's message of 2015-12-07 08:24:13 +0100:
> > well, i wouldn't need or even want it in memory, so on disk is fine. the
> > problem is more likely management of the same. browsing the changes is not
> > really convenient.
> There are versions already for methods. So th
19 matches
Mail list logo
