Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
October 2011
- 101 participants
- 899 messages
Re: [Pharo-project] startup errors
by Andrea Brühlmann
I tried it with this option now, but it did not solve the problem, because it just saved a new
version of the image and quit, but did not open a debugger. Opening the new version does the same as
the original. Did I miss something?
I would appreciate a command line option that either opens a debugger or ignores the errors, because
like this you usually have a clean image but if you have a problem, you can open the image and do
something.
Andrea
Igor Stasenko schrieb:
> On 25 October 2011 23:26, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote:
>> Sig,
>>
>> All too true, and very pure. But what if I just want to save a package, or some data, that might be locked away in the image? Code is generally safe, since one can recover lost changes into a healthy image, but there can still be other data lurking in an image.
>>
>> A middle-ground approach would be to have command line option that lets the image run. One should run w/o it to bring errors to attention, but at least it would be possible to override and at least have an opportunity to recover endangered bits.
>>
> look at settings, there's already an option to save a new version of
> image before quit.
> if you turn this option on, then any unhandled error will open a
> debugger if you open an image saved in such state.
>
>> Bill
>>
>>
>> ________________________________________
>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com]
>> Sent: Tuesday, October 25, 2011 9:40 AM
>> To: Pharo-project(a)lists.gforge.inria.fr
>> Subject: Re: [Pharo-project] startup errors
>>
>> On 24 October 2011 11:40, Andrea Brühlmann <a.bruehlmann(a)netstyle.ch> wrote:
>>> It seems that pharo 1.3 introduced that the image quits if an error happens
>>> during startup. What are the reasons for this?
>>>
>> The reasons are simple:
>> if image fails to startup properly, there are no way to tell, if some
>> services initialized properly or not (UI is one of them),
>> and so, there are no any guarantees that image could run safely.
>> So, the best thing which you can do is to write error to log and quit.
>>
>> This is because startup manager knows what to start-up and in what
>> order, but it doesn't knows, how critical a given service for properly
>> running the whole image. Therefore, if you don't handle startup errors
>> in your service code, a startup manager has no other choice , but just
>> leave to OS.
>>
>>
>>> Or what's the state of the email below?
>>>
>>> Andrea
>>>
>>>
>>> Camillo Bruni schrieb:
>>>> While working on Coral we encountered a rather annoying behavior of pharo
>>>> images when starting up.
>>>>
>>>> We wanted to check if we can debug the CoralScriptLoader, but of corse
>>>> since this happens at image startup time this is not a good idea⦠HOWEVER we
>>>> were no longer able to run the image as it immediately crashes during the
>>>> startup.
>>>>
>>>> Now I wonder if it would make sense to add a couple of on:do: in
>>>> SmalltalkImage >> snapshot:anQuit: to collect the errors of all the startup
>>>> scripts and then only show them after all other startupListItems are
>>>> processed.
>>>>
>>>> All in all the behavior would not much differ from what is going on right
>>>> now, but would prevent stupid users like me from losing a whole image.
>>>>
>>>> camillo
>>>>
>>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>>
>
>
>
--
AB | ANDREA BRÃHLMANN · SOFTWARE ENGINEER
| NETSTYLE · TERRASSENWEG 18 · CH-3012 BERN
| TEL +41 31 356 42 54 · FAX +41 31 356 42 51
| WWW.NETSTYLE.CH · A.BRUEHLMANN(a)NETSTYLE.CH
Oct. 26, 2011
Re: [Pharo-project] How to encrypt a password?
by Francois Stephany
> But I didn't want to put such password in the code... at
> the end what I did (because my scenario is really stupid and only for
> me), is to read the password from a file in my machine :) hahahahha
>
That would be the kind of thing that belongs to a .pharoconf file in
your /home directory ;)
Oct. 26, 2011
Re: [Pharo-project] How to encrypt a password?
by Mariano Martinez Peck
On Wed, Oct 26, 2011 at 12:36 AM, <mkobetic(a)gmail.com> wrote:
> "Milan Mimica"<milan.mimica(a)gmail.com> wrote:
> > Yes, having the salt randomly generated and storing it with a hash is a
> > better idea. Note taken. Combining it with a fixed salt (and trying to
> keep
> > it secret) is even better. Keeping a hardcoded salt in the image running
> on
> > the remote machine serving WEB pages makes it quite secret IMO.
>
> I was referring to Mariano's intent (at least how I understand it) to
> hardcode it "in code". If he's confident he'll be able to keep the code
> secret then hey may as well have the password in it in plain text, hashing
> it with or without salt, doesn't make much difference IMO.
>
>
Yes, indeed. I didn't give details. It was something very very stupid and
simple. All I wanted to do is to commit a class I use to build my images and
such class sets my username/password for squeaksource repotistories. But I
didn't want to put such password in the code... at the end what I did
(because my scenario is really stupid and only for me), is to read the
password from a file in my machine :) hahahahha
Anyway, I learn from the thread :)
> Generating random salt and keeping a hashed password on a deployed system
> is a different scenario. In this case it's different and unpredictable with
> every deployment. When it's hardcoded it's the same everywhere.
>
>
--
Mariano
http://marianopeck.wordpress.com
Oct. 26, 2011
Re: [Pharo-project] startup errors
by Stéphane Ducasse
we should document that somewhere.
On Oct 25, 2011, at 11:40 PM, Igor Stasenko wrote:
> On 25 October 2011 23:26, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote:
>> Sig,
>>
>> All too true, and very pure. But what if I just want to save a package, or some data, that might be locked away in the image? Code is generally safe, since one can recover lost changes into a healthy image, but there can still be other data lurking in an image.
>>
>> A middle-ground approach would be to have command line option that lets the image run. One should run w/o it to bring errors to attention, but at least it would be possible to override and at least have an opportunity to recover endangered bits.
>>
> look at settings, there's already an option to save a new version of
> image before quit.
> if you turn this option on, then any unhandled error will open a
> debugger if you open an image saved in such state.
>
>> Bill
>>
>>
>> ________________________________________
>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com]
>> Sent: Tuesday, October 25, 2011 9:40 AM
>> To: Pharo-project(a)lists.gforge.inria.fr
>> Subject: Re: [Pharo-project] startup errors
>>
>> On 24 October 2011 11:40, Andrea Brühlmann <a.bruehlmann(a)netstyle.ch> wrote:
>>> It seems that pharo 1.3 introduced that the image quits if an error happens
>>> during startup. What are the reasons for this?
>>>
>>
>> The reasons are simple:
>> if image fails to startup properly, there are no way to tell, if some
>> services initialized properly or not (UI is one of them),
>> and so, there are no any guarantees that image could run safely.
>> So, the best thing which you can do is to write error to log and quit.
>>
>> This is because startup manager knows what to start-up and in what
>> order, but it doesn't knows, how critical a given service for properly
>> running the whole image. Therefore, if you don't handle startup errors
>> in your service code, a startup manager has no other choice , but just
>> leave to OS.
>>
>>
>>> Or what's the state of the email below?
>>>
>>> Andrea
>>>
>>>
>>> Camillo Bruni schrieb:
>>>>
>>>> While working on Coral we encountered a rather annoying behavior of pharo
>>>> images when starting up.
>>>>
>>>> We wanted to check if we can debug the CoralScriptLoader, but of corse
>>>> since this happens at image startup time this is not a good idea⦠HOWEVER we
>>>> were no longer able to run the image as it immediately crashes during the
>>>> startup.
>>>>
>>>> Now I wonder if it would make sense to add a couple of on:do: in
>>>> SmalltalkImage >> snapshot:anQuit: to collect the errors of all the startup
>>>> scripts and then only show them after all other startupListItems are
>>>> processed.
>>>>
>>>> All in all the behavior would not much differ from what is going on right
>>>> now, but would prevent stupid users like me from losing a whole image.
>>>>
>>>> camillo
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
Oct. 26, 2011
[Pharo-project] Fwd: [Smalltalks 2011] --- Tu conferencia / your conference
by Mariano Martinez Peck
---------- Forwarded message ----------
From: Fundacion FAST <fast(a)smalltalk.comcastbiz.net>
Date: Wed, Oct 26, 2011 at 7:13 AM
Subject: [Smalltalks 2011] --- Tu conferencia / your conference
To: marianopeck(a)gmail.com
==================== ENGLISH
Did you know that the Smalltalks Conference will be held again this year? (
http://www.fast.org.ar/**smalltalks2011<http://www.fast.org.ar/smalltalks2011>
)
Maybe youâre wondering why you should care about a conference that deals
with a language you most certainly donât use for your job, and of whose
existence you may not even be aware. But if you take 5' to read this I can
tell you that you wonât regret it and that after that you will probably be
eager to come to the conference :-)
To begin with, this conference isnât only about a programming language, itâs
about a technology and a development culture which still has a wide
influence on our profession. For example, last year Gilad Bracha came to the
conference. Who is Gilad Bracha? Maybe the name rings a bell... well, thatâs
because heâs one of the people behind Dart, Googleâs new language (
http://www.dartlang.org/) And what does that have to do with Smalltalk?
Precisely: Gilad Bracha was one of the creators of Strongtalk (
http://www.strongtalk.org/) the fastest Samlltalk at that time, which used
adaptive compilation, Polimorphic Inline Caching (PIC), optional variable
typing, etc. - all of which are being implemented now in Dart. This year one
of his closest collaborators will visit us, Vassili Bykov, who implemented
the UI of Newspeak, the latest language he has been working on.
But Smalltalk has to do not only with whatâs happening with Dart, but with
Ruby as well... Have you heard about MagLev? (http://ruby.gemstone.com/)
Itâs Rubyâs server for transactional and automatically persistent objects.
Guess where that comes from... MagLev is the implementation of Ruby running
on GemStone/S, a Transactional and Persistent object server for Smalltalk
that is more than 25 years old and that has been bought by VMWare because of
its great potential as a transactional memory manager for Java. If you
didnât know, read here: http://www.springsource.com/**
products/data-management/**gemfire65<http://www.springsource.com/products/data-management/gemfire65>
And where does the conference come in here? Martin McClure himself,
responsible for MagLev, and GemStone architect Norman Green are coming! The
guy in the know! Do you have any doubts about object bases? Now you know
where the answers are.
But maybe youâre not interested in any if this... perhaps the way
programming languages work or how they are implemented is not your scene,
you just make web applications and only want the infrastructure to scale, to
be quick at persisting information etc. In that case we also have a place
for you. Have you heard of GLASS? (http://seaside.gemstone.com/) Itâs the
implementation of Seaside, a dynamic framework based on continuations for
web applications using GemStone! (http://www.seaside.st/) Thatâs to say,
you develop a web application just like a desktop application, and you get
transactionality and persistence at the object level, for free... and whatâs
better, without relational databases!!! Yes!!!! No more hibernating, no more
SQL, no more tables, only objects! It may sound crazy, you may think it
doesnât make sanse... my advice is, donât draw any conclusions until you
come and hear Dale Heinrichs, who is in charge of this product and who will
tell us all the details and explain how it is impacting web developments.
Not convinced yet? OK, let me try just a bit more... Do you know Alan Kay?
Turing award, âfather of the personal computerâ, creator of Smalltalk? (
http://en.wikipedia.org/wiki/**Alan_Kay<http://en.wikipedia.org/wiki/Alan_Kay>)
No, heâs not coming - yet. But Ian Piumarta and Kim Rose are, two of his
closest collaborators in the projects heâs currently working on at his
foundation dedicated to minimal programming languages such as OMeta and
learning environments like SqueakLand
(http://www.vpri.org/index.**html<http://www.vpri.org/index.html>).
Are you interested in the use of computers for teaching? You can ask Kim.
Would you like to know how a good VM is implemented? Ian will be right there
to tell you.
If youâre still reading and havenât scrolled down to the bottom of the page
it means I havenât convinced you yet... hmmm, letâs see what you say about
this: MOOSE (http://www.moosetechnology.**org<http://www.moosetechnology.org>),
a platform for analyzing your programs - no matter if they are written in
Java, C++, C# or Smalltalk, you can visualize your systemâs design, not by
using those little UML diagrams but by means of graphics specially designed
to let you spot at a glance some bugs that may have crept in. Its developer,
Tudor Girba, will be there to explain how it works, how it was developed and
what you can do with it, because itâs free!
Maybe youâre already tired of reading. I donât blame, but donât you blame me
either! Itâs a great conference! You just canât miss it! Because this is not
all... if you want to find out more about the main Smalltalk development
environments, both open source and commercial, you will have the chance to
talk to Markus Denker from Pharo
(http://www.pharo-project.org/**home<http://www.pharo-project.org/home>)
and John OâKeefe, architect of VASmalltalk
(http://www.instantiations.**com/<http://www.instantiations.com/>
).
A little too much stuff that is industry-oriented? And what about research,
do they keep researching on Smalltalk? Well, let me tell you that this will
be the second year the conference has a section devoted entirely to
research, with an enviable review committee and publication in journals.
This way, if youâre doing research on objects and need to present your work
at a widely recognized conference, Smalltalks is your place. And I wouldnât
like to forget the university... Smalltalk is still the language used to for
teaching objects at almost every university, instead of a merely commercial
language.
But I havenât told you yet about the most important part of this, besides
all these people that will be visiting us and with whom we can share our
experiences: The Argentine Smalltalk community, one of the most important
worldwide concerning this technology. This community has been putting their
best efforts during the last five years to organize these conferences, and
the last three years some of its members have won the 1st and the 3rd place
at the ESUG Technology Award, an international award for the best
developments in Smalltalk! And the best part of it is that the winners are
from different universities - the UBA, the UAI and the UTN!
The community does not stop there. Did you know that there is an Argentine
Smalltalk? A Smalltalk developed by an Argentinian and which is being used
all over the world? Itâs called CUIS and it was developed by Juan Vuletich (
http://www.jvuletich.org/**Cuis/Index.html<http://www.jvuletich.org/Cuis/Index.html>),
who is also working on the Morphic 3.0 project, and worked together with
Alan Kay developing Squeak. Or did you know that the most widely used layer
open source for communicating with relational databases from Pharo or Squeak
was developed by an Argentinian too? Or that Fuel, the open source object
serialization framework, was also created by an Argentinian? Are you
familiar with these names - Mariano Martinez Peck, Guillermo Polito, MartÃn
Dias, Esteban Lorenzano, and others? They are also part of our community and
a constant reminder of the excellent technical quality we have in our
country. Another Argentinian is the architect of the fastest Smalltalk VM in
existence, that of VisualWorks (http://www.cincomsmalltalk.**
com/main/products/visualworks/<http://www.cincomsmalltalk.com/main/products/visualworks/>
**), and you can ask him how he was able to speed up the GC about 70% during
the last year, and you will have the chance to listen to another Argentinian
who has been a Smalltalker for more than 20 years... Can you imagine what
your productivity would be if you had been working for 20+ years on the same
language? On a language that keeps being productive to our profession? These
people are part of this great community and will also be at this wonderful
meeting... which is important not only for the people who are coming, but
also for those that are already here!
I hope Iâve been able to convince you. I hope youâve realized that this is
not a conference about a programming language, but about a community of
developers who want to share with you all they know, and also learn from
you. If you want to help this community to keep growing, if you want this to
be not just a conference of developers but also for developers, sign up
here: http://www.fast.org.ar/**smalltalks2011<http://www.fast.org.ar/smalltalks2011>
Itâs free, and I can grant you that you wonât regret it. You can see the
list of talks at:
http://www.fast.org.ar/**smalltalks2011/talks<http://www.fast.org.ar/smalltalks2011/talks>
This year it takes place on November 3-5, at the University of Quilmes. And
it wonât be restricted to the world of objects: this year we will also have
a talk on objects by Fidel (Pablo E. MartÃnez López), one of the leading
Argentinians in the field of Functional Programming, a community that shares
the conviction that we are all, after all, programmers! See the response it
is already getting: http://vimeo.com/30529851
Weâll be waiting for you!
FAST
http://www.fast.org.ar
==================== SPANISH
¿Te enteraste que este año se hace nuevamente el congreso Smalltalks? (
http://www.fast.org.ar/**smalltalks2011<http://www.fast.org.ar/smalltalks2011>
)
Por ahà te estás preguntando qué puede tener de interesante un congreso
sobre un lenguaje que seguro no usas para trabajar y que por ahà no conoces,
pero si tenés 5 minutos, lee este mail, te puedo asegurar que no te vas a
arrepentir y seguramente querrás venir al congreso :-)
Para empezar, este congreso no es únicamente sobre un lenguaje de
programación sino sobre una tecnologÃa y cultura de desarrollo que aún sigue
influenciando fuertemente nuestra profesión. Por ejemplo, el año pasado vino
a esta conferencia Gilad Bracha. ¿Quién es Gilad Bracha?, por ahà te suena
el nombre... bueno, te suena porque es uno de los que está detrás de
desarrollo de Dart, el nuevo lenguaje de Google (http://www.dartlang.org/)
¿Y qué tiene que ver Smalltalk? Justamente Gilad Bracha fue uno de los
desarrolladores de Strongtalk (http://www.strongtalk.org/) el Smalltalk más
rápido en su época, que utiliza compilación adaptiva, Polimorphic Inline
Caching (PIC), tipado de variables opcional, etc. Todas soluciones que ahora
se están implementando en Dart. Este año nos visita uno de sus más Ãntimos
colaboradores, Vassili Bykov, implementador del UI de Newspeak, el último
lenguaje en el que estaba trabajando.
Pero no solo Smalltalk tiene algo que ver en lo que está sucediendo con
Dart, sino también en Ruby... ¿escuchaste hablar de MagLev? (
http://ruby.gemstone.com/) Es el servidor de objetos transaccionales y
automáticamente persistibles para Ruby, ¿adiviná de dónde viene? MagLev es
la implementación de Ruby corriendo sobre GemStone/S, un servidor de objetos
transaccionales y persistibles para Smalltalk que tiene más de 25 años y que
ahora VMWare compró por su gran potencial y solución como administrador de
memoria transaccional para Java, si no lo sabÃas mirá
http://www.springsource.com/**products/data-management/**gemfire65<http://www.springsource.com/products/data-management/gemfire65>¿Qué
tiene que ver con el congreso? que justamente viene al mismo Martin McClure,
responsable de MagLev y Norman Green, arquitecto de GemStone! o sea, el que
tiene la papa!! ¿Tenés dudas sobre las bases de objetos? ya sabés donde
podés obtener las respuestas.
Pero por ahà a vos no te interesa nada de esto... por ahà cómo funcionan los
lenguajes de programación o cómo están implementados no es lo tuyo, vos
haces aplicaciones web y solo necesitás que la infraestructura escale,
persista información rápido, etc. Si ese es tu interés, tenemos un lugarcito
para vos también. ¿Escuchaste hablar de GLASS? (http://seaside.gemstone.com/)
Es la implementación de Seaside, un framework dinámico basado en
continuations para aplicaciones web usando GemStone! (http://www.seaside.st/)
O sea, desarrollas una aplicación web como si fuese una aplicación desktop y
tenés gratis la transaccionabilidad y persistencia a nivel objetos... y lo
que es mejor, sin base de datos relacionales!!! Si!!!!, no más hibernate, no
más SQL, no más tablas, solo objetos!.... Por ahà te parece una locura, por
ahà te parece que no tiene sentido... te aconsejo que no saques ninguna
conclusión y no dejes de venir a escuchar a Dale Heinrichs, el encargado de
este producto quien nos contará todos los detalles del mismo y cómo influye
en los desarrollos web.
¿Aún no te convenc� ok... dejame intentar un poquito más... ¿Conoces a Alan
Kay? ¿Turing award, "padre de la computadora personal", creador de
Smalltalk? (http://en.wikipedia.org/wiki/**Alan_Kay<http://en.wikipedia.org/wiki/Alan_Kay>)
No, no, no viene él, todavÃa :-),pero vienen Ian Piumarta y Kim Rose, dos de
los más Ãntimos colaboradores de Alan Kay en los proyectos que están
llevando adelante en su fundación sobre lenguajes de programación mÃnimos
como OMeta y ambientes de enseñanza como SqueakLand. (
http://www.vpri.org/index.**html <http://www.vpri.org/index.html>). ¿Te
interesa saber cómo usar la computadora para enseñar? Le vas a poder
preguntar a Kim. Te interesa saber cómo implementar una buena VM, lo vas a
tener a Ian cerquita para conversar.
Si aún estás leyendo y no fuiste al final de la página significa que aún no
te convencÃ... hmmm, a ver qué te parece esto: MOOSE (
http://www.moosetechnology.**org <http://www.moosetechnology.org>), una
plataforma para hacer análisis de tus programas, no importa si están
escritos en Java, C++, C# o Smalltalk, te permite ver visualmente el diseño
de tu sistema no usando esos diagramitas simples de UML sino por medio de
gráficos especialmente preparados para reconocer rápidamente algunos
errorcitos que por ahà tiene tu sistema :-). Tudor Girba, desarrollador de
esta plataforma vendrá a comentarnos cómo funciona, cómo está desarrollada y
qué podés hacer con ella puesto que además es gratis!
Por ahà ya estás aburrido de leer tanto, no te culpo y tampoco me culpes a
mi! es un congreso excelente! no te lo podés perder!, puesto que la cosa no
termina acá... si te interesa saber sobre los principales ambientes de
desarrollo en Smalltalk tanto opensource como comerciales, tendrás la
oportunidad de conversar con Markus Denker de Pharo (
http://www.pharo-project.org/**home)y<http://www.pharo-project.org/home%29y>John
O'Keefe, arquitecto de VASmalltalk (
http://www.instantiations.**com/ <http://www.instantiations.com/>)
¿Muchos temas relacionados con la industria no? ¿y qué hay acerca de
investigación, aún se investiga algo en con Smalltalk? Te comento que este
es el segundo año consecutivo que el congreso tiene una sección
completamente dedicada a la investigación, con un comité evaluador
envidiable y con publicaciones en journals. Por lo tanto, si te interesa
hacer investigación con objetos y necesitas que tus publicaciones sean en
congresos reconocidos, te comento que Smalltalks es uno de ellos. Y no me
quiero olvidar de la docencia universitaria... Smalltalk sigue siendo el
lenguaje utilizado para enseñar objetos en casi todas las universidades y no
para enseñar meramente un lenguaje de programación comercial.
Y a pesar de todo esto, de toda esta gente que nos va a visitar y con
quienes podremos compartir su experiencia y la nuestra, falta lo más
importante: La comunidad argentina de Smalltalk, una de las principales
comunidades en el mundo de esta tecnologÃa. Es esta comunidad que hace 5
años está organizando este congreso a todo pulmón y hace 3 años viene
ganando de manera consecutiva el primer y tercer puesto del "Esug Technology
Award", premio a los mejores desarrollos hechos en Smalltalk a nivel
mundial! y lo más interesante es que los ganadores son de distintas
universidad de nuestro paÃs como la UBA, la UAI y la UTN!
Y la comunidad no se limita a eso... ¿sabés que hay un Smalltalk argentino?
¿un Smalltalk desarrollado por un argentino y utilizado a nivel mundial? se
llama Cuis y su desarrollador Juan Vuletich (http://www.jvuletich.org/**
Cuis/Index.html <http://www.jvuletich.org/Cuis/Index.html>), quien además
está llevando adelante el desarrollo de Morphic 3.0 y trabajó junto a Alan
Kay desarrollando Squeak. ¿O sabÃas que el layer open source para
comunicarse con base de datos relacionales desde Pharo o Squeak más usado
también fue desarrollado por argentinos? o que el framework de serialización
de objetos opensource Fuel también fue desarrollado por un argentino? Te
suenan Mariano Martinez Peck, Guillermo Polito, MartÃn Dias, Esteban
Lorenzano entre otros?, ellos son parte de nuestra comunidad y nos recuerdan
constantemente la muy buena capacidad técnica que tenemos en nuestro paÃs.
También es argentino el arquitecto de la VM de Smalltalk más rápida que hay,
la de VisualWorks (http://www.cincomsmalltalk.**
com/main/products/visualworks/<http://www.cincomsmalltalk.com/main/products/visualworks/>
**) y le podés preguntar cómo hizo para acelerar hasta cerca de un 70% el GC
en el último año, y vas a poder escuchar una charla de un argentino que es
smalltalkero hace más de 20 años... ¿te imaginás cómo serÃa tu productividad
si estuvieras trabajando hace más de 20 años en el mismo lenguaje? ¿un
lenguaje que además sigue dando mucho a nuestra profesión?... Esta gente es
parte de esta gran comunidad y también participarán de este maravilloso
evento.... este congreso no es solo importante por la gente que viene sino
por la gente que ya está!
Espero haberte convencido, espero que te hayas dado cuenta que este congreso
no es acerca de un lenguaje de programación sino de una comunidad de
desarrolladores que quiere compartir con vos lo que conoce y también
aprender de vos. Si querés ayudar a que esta comunidad siga creciendo, si
querés ayudar a que este congreso siga siendo un congreso de desarrolladores
y para desarrolladores, anotate acá:
http://www.fast.org.ar/**smalltalks2011<http://www.fast.org.ar/smalltalks2011>Es
gratis y te puedo asegurar que no te vas a arrepentir. Podes ver las
charlas que se darán
en:http://www.fast.org.ar/**smalltalks2011/talks<http://www.fast.org.ar/smalltalks2011/talks>
Este año se hace del 3 al 5 de Noviembre, en la Universidad de Quilmes. Y no
está cerrada sólo al mundo de los objetos, este año Fidel (Pablo E. MartÃnez
López), uno de los referentes argentinos de Programación Funcional, una
comunidad que comparte que en definitiva somos todos desarrolladores, dará
una charla sobre objetos! Mirá las reacciones que ya está provocando:
http://vimeo.com/30529851
Te esperamos!
FAST.
http://www.fast.org.ar
--
Mariano
http://marianopeck.wordpress.com
Oct. 26, 2011
Re: [Pharo-project] Text for 1.3 announcement?
by Marcus Denker
On Oct 25, 2011, at 8:24 PM, Bernhard Pieber wrote:
> May I humbly suggest to at least add a link to known open issues for 1.3 right next to the release download? Then at least a newbie knows what to expect.
>
There is nothing different with 1.3 than with any other release we did.
And the discussion was more about unknown bugs, not known ones. "You can not release because maybe I found a bug
yesterday that I have not yet reported".
To make is clear: there are 7 (seven) open issues tagged for 1.3:
http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3
Most of which are not even show stoppers (are already a bug in 1.2, just cosmetic...)
None is important enough to have seen any work done since the last sprint.
In a way of course many reports on the issue tracker are describing an improvement or problem that could
be related to 1.3:
http://code.google.com/p/pharo/issues/list
These are 421 issues.
Marcus
--
Marcus Denker -- http://marcusdenker.de
Oct. 26, 2011
Re: [Pharo-project] Text for 1.3 announcement?
by Sven Van Caekenberghe
On 25 Oct 2011, at 20:24, Bernhard Pieber wrote:
> May I humbly suggest to at least add a link to known open issues for 1.3 right next to the release download? Then at least a newbie knows what to expect.
It is a good idea to put known issues in the release notes.
It would be a marketing mistake to do it like you suggest.
> Thanks for all your effort!
>
> Cheers,
> Bernhard
>
> Am 21.10.2011 um 15:24 schrieb Marcus Denker:
>> On Oct 21, 2011, at 3:17 PM, Igor Stasenko wrote:
>> On 21 October 2011 13:59, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote:
>>>> I am concerned about the error handling failure that I (easily) encountered, at least on Linux. Has anyone tried to reproduce it?
>>> How does that prevent from releasing 1.3?
>>>
>>> If there are obscure bugs, they will be fixed in 1.4.
>>
>> Or even in 1.3... (just added 3 fixes today).
>>
>> The thing is that there are indefinit unknown problems. If we wait a week, for sure someone finds another.
>>
>> "Release" does not mean "Bug free", because "bug free" does not exist.
>> (and it is even harder in a system with a huge, historical code base and an undefined feature set... I am
>> always amazed to learn new features that people seem to not be able to life without that I did not even
>> know existed. How can we gurantee that these don't break? We just can't).
>>
>> Marcus
>
>
Oct. 26, 2011
Re: [Pharo-project] How to encrypt a password?
by mkobetic@gmail.com
"Milan Mimica"<milan.mimica(a)gmail.com> wrote:
> Yes, having the salt randomly generated and storing it with a hash is a
> better idea. Note taken. Combining it with a fixed salt (and trying to keep
> it secret) is even better. Keeping a hardcoded salt in the image running on
> the remote machine serving WEB pages makes it quite secret IMO.
I was referring to Mariano's intent (at least how I understand it) to hardcode it "in code". If he's confident he'll be able to keep the code secret then hey may as well have the password in it in plain text, hashing it with or without salt, doesn't make much difference IMO.
Generating random salt and keeping a hashed password on a deployed system is a different scenario. In this case it's different and unpredictable with every deployment. When it's hardcoded it's the same everywhere.
Oct. 25, 2011
Re: [Pharo-project] Correct usage of exception handlers with ensure and ifCurtailed
by Igor Stasenko
On 25 October 2011 22:13, John Toohey <jt(a)parspro.com> wrote:
> - Yes it quits, not aborts. The issue is that the WAListenerAdapter
> throws ConnectionTimedOut exceptions, and in the headless state, these
> un-handled exceptions cause the VM to shutdown. My Seaside app has a
> custom Exception handler registered for the app, but its not called
> here.
>
> This code is from the WAListenerAdapter, so all I want to do is catch
> the exception and ignore it. Sockets timing out in a web app is not an
> exception. The stack trace runs from the Socket class back to the
> WAListenerAdapter class, so that is why I wanted to put a handler
> there. The code is the original code from that class.
>
> In the context of my web app, a socket timing out is not exceptional,
> so all I want to for the code to clean up after itself, and accept
> back on the socket. I was hoping that the handler that I put it would
> be sufficient, but your comments on the background process it making
> me wonder.
>
>
Absolutely, WA..Adapter should handle such situations, or at least let
user to handle them
in a way he prefers to.
But since this code related to Seaside, i guess you should open a
discussion in seaside mailing list
otherwise there are big chances that it will remain like today,
because this code outside of pharo developers responsibility.
--
Best regards,
Igor Stasenko.
Oct. 25, 2011
Re: [Pharo-project] startup errors
by Igor Stasenko
On 25 October 2011 23:26, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote:
> Sig,
>
> All too true, and very pure. Â But what if I just want to save a package, or some data, that might be locked away in the image? Â Â Code is generally safe, since one can recover lost changes into a healthy image, but there can still be other data lurking in an image.
>
> A middle-ground approach would be to have command line option that lets the image run. Â One should run w/o it to bring errors to attention, but at least it would be possible to override and at least have an opportunity to recover endangered bits.
>
look at settings, there's already an option to save a new version of
image before quit.
if you turn this option on, then any unhandled error will open a
debugger if you open an image saved in such state.
> Bill
>
>
> ________________________________________
> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com]
> Sent: Tuesday, October 25, 2011 9:40 AM
> To: Pharo-project(a)lists.gforge.inria.fr
> Subject: Re: [Pharo-project] startup errors
>
> On 24 October 2011 11:40, Andrea Brühlmann <a.bruehlmann(a)netstyle.ch> wrote:
>> It seems that pharo 1.3 introduced that the image quits if an error happens
>> during startup. What are the reasons for this?
>>
>
> The reasons are simple:
> if image fails to startup properly, there are no way to tell, if some
> services initialized properly or not (UI is one of them),
> and so, there are no any guarantees that image could run safely.
> So, the best thing which you can do is to write error to log and quit.
>
> This is because startup manager knows what to start-up and in what
> order, but it doesn't knows, how critical a given service for properly
> running the whole image. Therefore, if you don't handle startup errors
> in your service code, a startup manager has no other choice , but just
> leave to OS.
>
>
>> Or what's the state of the email below?
>>
>> Andrea
>>
>>
>> Camillo Bruni schrieb:
>>>
>>> While working on Coral we encountered a rather annoying behavior of pharo
>>> images when starting up.
>>>
>>> We wanted to check if we can debug the CoralScriptLoader, but of corse
>>> since this happens at image startup time this is not a good idea⦠HOWEVER we
>>> were no longer able to run the image as it immediately crashes during the
>>> startup.
>>>
>>> Now I wonder if it would make sense to add a couple of on:do: in
>>> SmalltalkImage >> snapshot:anQuit: to collect the errors of all the startup
>>> scripts and then only show them after all other startupListItems are
>>> processed.
>>>
>>> All in all the behavior would not much differ from what is going on right
>>> now, but would prevent stupid users like me from losing a whole image.
>>>
>>> camillo
>>>
>>
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
>
>
--
Best regards,
Igor Stasenko.
Oct. 25, 2011