Picon

EyeMorph inspector issue

I wanted to look at a form and did

aForm asMorph explore.

Then selected the Morph view in the drop down and then, MNU.


What to do?

I've crappily patched but someone educated should look at this since this is a cool feature of Pharo3.

Phil
Lorenzo Schiavina | 18 Apr 08:07 2014
Picon

R: [ANN] FontAwesome for Seaside

Really nice!

Lorenzo

-----Messaggio originale-----
Da: Pharo-dev [mailto:pharo-dev-bounces@...] Per conto di
Torsten Bergmann
Inviato: giovedì 17 aprile 2014 10:27
A: seaside@...;
seaside-dev@...; Pharo Development
List; pharo-users@...; pharo-business@...
Oggetto: [Pharo-dev] [ANN] FontAwesome for Seaside

Hi,

FontAwesome is (as you may know) an iconic font designed for the user with Twitter Bootstrap.

I now created a "FontAwesome for Seaside" project - which is a small Seaside wrapper for the FontAwesome
project (using the latest version 4.0.3). 

This is intended as an addition to the already available "Bootstrap for Seaside" [2] project that I wrote
and both should allow you to give your Smalltalk based web application a nice stylish look.

The project is located on STHub, see [1] where you will also find the documentation.

A live demo can be found on http://pharo.pharocloud.com/fontawesome.

To try yourself load it from the Pharo config browser or read the docu to see what is required.

Thx
T.

[1] http://smalltalkhub.com/#!/~TorstenBergmann/FontAwesome
[2] http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap

Sean P. DeNigris | 18 Apr 05:06 2014

Phexample: Image Destroying Bug

Gofer it
	url: 'http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20';
	configurationOf: 'Phexample';
	loadStable.

"In 2.0, evaluating the following line brings up a debugger (the expected
behavior). In 3.0, it never returns, creating an more and more debugger
processes until the image becomes unresponsive."

true should beFalse.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Phexample-Image-Destroying-Bug-tp4755253.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Picon

RBClassRegexRefactoring & Nautilus madness

I have been able to refactor my class names with:

RBClassRegexRefactoring new
  renameClasses;
  replace: '^XXX(.*)$' with: 'YY$1' ignoreCase: false;
  execute

But since then, Nautilus looks like quite lost with a number of weird behaviors.

Is there a way to reset Nautilus after such refactorings? I suspect that there is a cache somewhere that begs to be rebuilt...

Phil
Picon

UndefinedObject>>allSuperclassesDo: aBlockContext self shouldBeImplemented

Weird...

is this a bug?

Phil

Picon

Re: 13204 Hard to see Morph halo label

why do we need a special class for that?
Why not just a StringMorph with correct background?

On 17/4/14 16:20, Ben Coman wrote:
Build 30507 integrated slice 11492 "Kill UpdatingStringMorph, UpdatingMenu, and NameInHaloMorph"
that removed class UpdatingStringMorph its subclass NameInHaloMorph.  As a consequence the halo "morph label"
became hard to read.  Compare the red circled areas in the snapshots from build.



Technically its pretty easy fix. Restoring just the #drawOn: part of NameStringInHalo (now subclassed from StringMorph) solves the problem as follows...
Adding...
    StringMorph subclass: #NameStringInHalo
        instanceVariableNames: ''
        classVariableNames: ''
        category: 'Morphic-Base-Widgets'

    NameStringInHalo>>drawOn: aCanvas
        aCanvas fillRectangle: self bounds color: Color white.
        super drawOn: aCanvas.

and modify the following line in HaloMorph>>addNameBeneath:string: ...
    nameMorph := StringMorph contents: aString font: StandardFonts haloFont.
to..
    nameMorph := NameStringInHalo contents: aString font: StandardFonts haloFont.

However I'm seeking a broader picture to understand if that is the right way to proceed...
1. Was NameStringInHalo particularly undesired or was it more a consequence of UpdatingStringMorph being removed ?

2. Should the same class name "NameStringInHalo" be used having a different superclass than before. Actually as I write that I am thinking this creates an unnecessary clash with Squeak and derivatives that still have NameStringInHalo, and so...

3. Any suggestions for another more generic class name?  SolidStringMorph, OpaqueStringMorph, etc

4. Any suggestions for another way for a StringMorph to have a solid background?

cheers -ben

Luc Fabresse | 17 Apr 21:13 2014
Picon

Condense changes

hi all,

In a fresh image #30826, I tried:

Smalltalk image condenseChanges -> ZnInvalidUTF8 error

describes that but it is closed.

I tried the new version:

PharoChangesCondenser condense. -> parse error

Do we open a new bug?

Is there another way that I missed?

Do you agree that we should remove condenseChanges from SmalltalkImage?

Cheers,

#Luc
Nicolás Paez | 17 Apr 16:29 2014
Picon

[ANN] CFP Argentine Symposium on Software Engineering - Extended Deadline

The submission deadline has been extended to April 25, 2014.

=================
Second Call for Papers

Universidad de Palermo, Buenos Aires, Argentina
part of 43 JAIIO - 43 Argentine Conference of Informatics -
1st - 5th September, 2014

==============================================================================

ASSE is an annual event that brings together researchers, developers, and practitioners to discuss and exchange ideas, problems and experiences in the field of Software Engineering.  ASSE  seeks  original  works  in  the wide  spectrum  of  Software Engineering,  from  academic  research  to industrial  and  business  applications  with  significant  impact  and lessons learned from application development.

This year, ASSE will be held during the week 1st - 5th September 2014, in Buenos Aires, Argentina, at the Universidad de Palermo.

ASSE will be part of the JAIIO (Argentine Conference on Informatics), which is one of the most prestigious conferences in South America,  organized  by  SADIO  (Argentine  Society  of  Informatics and Operations Research) since  1961,  with  the  participation  of professionals from industry and academia. JAIIO is organized as a series of thematic symposia including topics such as: software engineering,artificial intelligence, technology, agro-informatics, high performance computing, industrial informatics, free software, law, health, information
society, and a students’ contest.


SUBMISSIONS

Submissions are invited in the following track categories:
• Full research papers: 15 pages maximum length
• Experience Reports: 10 pages maximum length
• Communications: Communications are talks on high quality articles authored by the presenter and published in the
recent past. This category aims at sharing and discussing recent work at a local forum.

For research papers we invite submissions describing original research results, case studies, and empirical studies. Some Full papers, which in the opinion of the committee, may be proposed as Short research papers with a maximum of 6 pages maximum length.
We encourage submissions relating to all aspects of Software Engineering, especially on topics of emerging interest. Topics of interest include but are not limited to the following:

Agile Methods and Practices 
Cloud-based Systems 
Development Paradigms and Software Processes and Methods 
Distributed Systems and Middleware 
Formal Methods 
Mobile and Embedded Systems 
Model Driven Engineering 
Object Oriented, Component-based, Aspect-oriented, Service-oriented Software Engineering 
Open Standards and Certification 
Patterns and Frameworks 
Program Comprehension and Visualization 
Requirements Engineering 
Reverse Engineering, Refactoring, and Evolution 
Software Architecture and Design 
Software Configuration and Deployment 
Software Craftsmanship 
Software Engineering Education and Training 
Software Metrics & Quality Assurance 
Software Product Lines
Software Project Management 
Software Specification 
Tools and Environments 
Verification, Validation and Testing 
Web Engineering

For experience reports we are inviting practitioners to present new advances or insights in Software Engineering methods,
practices or tools. A contribution should consist of a brief explanation of the method, practice, or tool in question, a description
of the context and particulars in which you have experience, the results you have achieved, and the lessons you and your
organization have learned relative to this method, practice or tool, its applicability, its effectiveness, or insights on how to
further improve it. In particular, the content must be practical and relevant, and be presented in a well-documented and
thorough manner.
All papers must be written in English, Spanish or Portuguese. They will be reviewed by an international Program Committee,
which is composed of members from both Industry and Academia, so that research papers and experience reports can be
evaluated by experts in the subject.
Papers may be accepted for presentation as talks or as posters during the conference. All papers and experience reports will be
published in SADIO Proceedings of the JAIIO. Best papers will be invited for publication in the Electronic Journal of SADIO.
Communications will be selected by the Program Committee based on a one-page abstract, which must follow the same format
as research papers and include references (conference/workshop/journal where the work has been published, link to the full
article, date of publication, etc.). This type of contributions will not be published in the Proceedings.


SUBMISSION GUIDELINES

The versions submitted for review must be uploaded in .PDF format. The format for the camera-ready copy will be in Springer
format, which can be found at http://www.springer.de/comp/lncs/authors.html. The correct reception of a submission will be
acknowledged immediately to the contact author.
Submission (Full research papers and experience reports) must follow the following format: they must be written in English,
Spanish or Portuguese, up to 15 pages for full papers and 10 pages for experience reports, 11 points font, times, A4 (210 x 297
millimeters) paper, including name, affiliation and address of the author/s, figures and references. Papers should also include
keywords and an abstract of no more than 200 words. In case a Full Paper is accepted as a Short Paper, the format is the same as
the Full Paper but restricted to 6 pages.
Each accepted paper must be presented in the symposium, and the presenter must be registered in the conference.
All the symposia at 43 JAIIO use SADIO's conference management system to handle submissions. To upload your contribution
you first need to register and sign in. Detailed instructions for registration and submission are available online.

IMPORTANT DATES

Submission deadline: April 25th, 2014 (NEW!!)
Acceptance notification: June 16th, 2014
Final version (camera ready) deadline: June 30th, 2014


PROGRAM COMMITTEE

CHAIRS
Luciana Roldán, INGAR, Universidad Tecnológica Nacional FRSF, Argentina. 
Nicolás Páez, Universidad de Buenos Aires, Buenos Aires, Argentina. 

COMMITTEE
Adrián Lasso (Baufest, Argentina)
Alejandro Bianchi (Liveware, Argentina)
Alejandro Russo (Chalmers University of Technology, Suecia)
Álvaro Ruiz de Mendarozqueta (Fund. Sadosky, UTN FRC, Argentina)
Andrés Díaz Pace (ISISTAN, UNCPBA, Argentina)
Carlos Fontela (UBA, Argentina)
Claudia Marcos (ISISTAN, UNCPBA, Argentina)
Claudia Pons (UAI, Argentina)
Cristian López (Hexacta, Argentina)
Diego Fontdevila (UNTREF, Argentina)
Diego Garbervetsky (UBA, Argentina)
Diego Rubio (ARRIS, UTN FRC, Argentina)
Eduardo Almeida (Universidade Federal da Bahia, Brasil)
Eduardo Mangarelli (Microsoft, Universidad ORT, Uruguay)
Fernando Asteasuain (UBA, Argentina)
Gabriela Aranda (GIISCO, UNCOMA, Argentina)
Gabriela Robiolo (Universidad Austral, Argentina)
George Fernández (MIT, Australia)
Germán Montejano (Universidad Nacional de San Luis, Argentina)
Israel Antezana Rojas (Universidad Católica Boliviana, Bolivia)
José Palazzo Moreira de Oliveira (Universidade Federal do Rio Grande do Sul, Brasil)
Juan Gabardini (Kleer, UBA, UNTREF, Argentina)
Laura Brandán Briones (FAMAF, UNC, Argentina)
Luca Cernuzzi (Universidad Católica Nuestra Señora de la Asunción, Paraguay)
Luis Olsina (UNLPamp, Argentina)
Marcela Vegetti (INGAR, UTN FRSF, Argentina)
Marcelo Frias (Instituto Tecnológico Buenos Aires, Argentina)
María de los Ángeles Martín (Universidad de la Pampa, Argentina)
Nicolás D’Ippolito (FCEyN UBA, Argentina)
Pablo Fillottrani (UNS, Argentina)
Pablo Villareal (CIDISI, UTN FRSF, Argentina)
Pedro Colla (Instituto Universitario Aeronáutico, Argentina)
Raúl Martínez (RMyA, UBA, Argentina)
Ricardo Medel (INTEL, Argentina)
Ricardo Orosco (UADE, Argentina)
Silvia Gordillo (LIFIA, UNLP, Argentina)
Silvio Gonnet (INGAR, UTN FRSF, Argentina)
Verónica Bogado (UTN FRVM, Argentina)


CONTACT

For further information, visit ASSE 2014 webpage: http://www.43jaiio.org.ar/asse
Alexandre Bergel | 17 Apr 15:01 2014

Closure vs BlockClosure

Hi!

Just wondering, would it not make sense to rename BlockClosure into Closure?

Cheers,
Alexandre
--

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Yuriy Tymchuk | 17 Apr 10:31 2014

Re: [ANN] FontAwesome for Seaside

Super awesome! Thank you.

On 17 Apr 2014, at 11:27, Torsten Bergmann <astares@...> wrote:

> Hi,
> 
> FontAwesome is (as you may know) an iconic font designed for the user with Twitter Bootstrap.
> 
> I now created a "FontAwesome for Seaside" project - which is a small Seaside wrapper for the 
> FontAwesome project (using the latest version 4.0.3). 
> 
> This is intended as an addition to the already available "Bootstrap for Seaside" [2] project 
> that I wrote and both should allow you to give your Smalltalk based web application a nice 
> stylish look.
> 
> The project is located on STHub, see [1] where you will also find the documentation.
> 
> A live demo can be found on http://pharo.pharocloud.com/fontawesome.
> 
> To try yourself load it from the Pharo config browser or read the docu to see what is required.
> 
> Thx
> T.
> 
> [1] http://smalltalkhub.com/#!/~TorstenBergmann/FontAwesome
> [2] http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap<fontawesome.png>

Norbert Hartl | 17 Apr 10:26 2014

Understanding WeakValueDictionary

While looking at the code in voyage I got to WeakValueDictionary as voyage uses it as object cache. If I
looked correctly the WeakValueDictionary is based on equality and not identity. Is that correct? Feels wrong!

Norbert


Gmane