April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how to completely ignore mouse wheel events?

by Alexandre Bergel

I have modified the following methods HandMorph>>generateKeyboardEvent: evtBuf ScrollPane>>scrollByKeyboard: event The effect is now milder. Esteban, would it make sense to remove the event generation bu the VM? This works only for the old-style mouse with an actual wheel. Mighty mouse does not work at all with Pharo. We have to get this right. Emulation of events is a bad idea. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Apr 15, 2014, at 10:36 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Mouse wheel events are so poorly handled in Pharo, that they are not useful. > With Ronie we are seeing how we can better handle events with a window generated with SDL. But this is for the future. > > Is there a way to easily unable them? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 17, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Yuriy Tymchuk

Itâs like saying that we have to run Pharo on JVM because everyone is doing that. In 80s block was invented. Why should we rename it because of some other languages? Uko On 17 Apr 2014, at 16:35, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Wellâ¦ the whole community of programming language call a closure a closure. Calling a block what is actually a closure may not be a well-marketed move in my opinion. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Apr 17, 2014, at 10:29 AM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> On Apr 17, 2014, at 10:08 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> I would rather rename is to Block, as everyone is calling it a âblockâ. >> >> That might be actually a good idea >> >> sebastian >> >> o/ >> >> PS: thinking in that line there is also âContextâ as, conceptually, what these blocks of code want to do is to keep the evaluation in a specific context. But to ease know-how transference and type less Iâd rather go with the most popular name, as you suggested: âBlock' >> >> > >

April 17, 2014

Re: [Pharo-dev] Understanding WeakValueDictionary

by Norbert Hartl

Am 17.04.2014 um 16:06 schrieb Igor Stasenko <siguctua(a)gmail.com>: > > On 17 April 2014 10:26, Norbert Hartl <norbert(a)hartl.name> wrote: > 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! > > > well, comparison used for keys.. > and i agree that for caching, an identity comparison makes much more sense, > since you want it to be fast, and identity comparison is no doubt faster than > equality comparison, especially if keys are complex objects which implement equality based on comparing own fields. > Agreed. But I think that equality based comparison is not only slower but wrong! Implementing an object cache based on equality can easily screw up your graph. You can call it the crappiest kind of become: youâve never wanted! > but for that, i think we would need new kind of dictionary, e.g. > WeakValueIdentityKeyDictionary (or some similar name). > Agreed. > Btw, for caching i prefer to use round-robin cache with limited size You mean those things where you can state: âHey, Iâm fast because I exchanged * with + ?â :) Norbert > (like that cache never grows too big, and instead simply drops/overrides existing entries when it become full).. this helps maintaining cache size under control. > > A good example is LRUCache, which is very suitable method to cache objects.. albeit at cost of some extra processing for accessing it. > > Norbert > > -- > Best regards, > Igor Stasenko.

April 17, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Noury Bouraqadi

+1 for BlockClosure :-) On 17 avr. 2014, at 15:44, Sean P. DeNigris wrote: > abergel wrote >> Wellâ¦ the whole community of programming language call a closure a >> closure. Calling a block what is actually a closure may not be a >> well-marketed move in my opinion. > > Given that Smalltalkers consider it a block and outsiders would understand > the closure part, maybe it is well-named as it is, as it is an obvious link > of these two terms. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Closure-vs-BlockClosure-tp4755091p4755104.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --

April 17, 2014

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

by NicolÃ¡s Paez

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 - http://www.43jaiio.org.ar/ 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 or send an e-mail to: asse(a)43jaiio.org

April 17, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Norbert Hartl

Am 17.04.2014 um 15:57 schrieb Sebastian Sastre <sebastian(a)flowingconcept.com>: > > On Apr 17, 2014, at 10:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> the whole community of programming language call a closure a closure. Calling a block what is actually a closure > > javascript is teaching every day to thousands what a real Closure is every day, so yeah that would be probably better > You mean the thing the is called Function? :) Norbert

April 17, 2014

13204 Hard to see Morph halo label

by Ben Coman

April 17, 2014

Re: [Pharo-dev] Understanding WeakValueDictionary

by Igor Stasenko

On 17 April 2014 10:26, Norbert Hartl <norbert(a)hartl.name> wrote: > 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! > > well, comparison used for keys.. and i agree that for caching, an identity comparison makes much more sense, since you want it to be fast, and identity comparison is no doubt faster than equality comparison, especially if keys are complex objects which implement equality based on comparing own fields. but for that, i think we would need new kind of dictionary, e.g. WeakValueIdentityKeyDictionary (or some similar name). Btw, for caching i prefer to use round-robin cache with limited size (like that cache never grows too big, and instead simply drops/overrides existing entries when it become full).. this helps maintaining cache size under control. A good example is LRUCache, which is very suitable method to cache objects.. albeit at cost of some extra processing for accessing it. > Norbert > -- Best regards, Igor Stasenko.

April 17, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Sebastian Sastre

On Apr 17, 2014, at 10:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > the whole community of programming language call a closure a closure. Calling a block what is actually a closure javascript is teaching every day to thousands what a real Closure is every day, so yeah that would be probably better

April 17, 2014

Re: [Pharo-dev] Closure vs BlockClosure

by Sean P. DeNigris

abergel wrote > Wellâ¦ the whole community of programming language call a closure a > closure. Calling a block what is actually a closure may not be a > well-marketed move in my opinion. Given that Smalltalkers consider it a block and outsiders would understand the closure part, maybe it is well-named as it is, as it is an obvious link of these two terms. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Closure-vs-BlockClosure-tp4755091p4755104.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 17, 2014