- Pharo-dev - lists.pharo.org

[Pharo-project] OmniBrowser optimizations
by David RÃ¶thlisberger April 21, 2009

April 21, 2009

Hi, Alex and me did some optimizations for the OmniBrowser framework. We focused on optimizing the updating of browser windows upon code changes (recompilation, recategorization, removing, doIts, etc.). Such browser updates are now an order of magnitude faster than before. For details, have a look at class OBBenchmarks in OB-Enhancements. To update you OmniBrowser installation, load the latest version of all installed OB-packages (typically OmniBrowser, OB-Standard, OB-Morphic, and OB-Enhancements) from http://source.wiresong.ca/ob. In Pharo, you can also execute 'ScriptLoader loadOBAlpha'. If you find any problems after this update, please let us know. Cheers, Alex and David

1 0

[Pharo-project] Input sensor rewrite
by Michael Rueger April 21, 2009

April 21, 2009

Hi all, there is a updated version of the input sensor/event rewrite in the Pharo inbox: -load the config map Event-rewrite1.mcm (it's in the Event category in the repository) -load the slice EventRewrite2-michael_rueger.2 - in a workspace execute InputEventSensor installPollingEventSensorFramework voila... Sensor should now be an InputEventSensor. At a later point we can the remove the EventSensor and InputSensor classes. Michael P.S. Could someone please remove Collections-Sequenceable-michael_rueger.15 from the inbox? It's a bogus version

6 14

[Pharo-project] Pharo demo at BarCampHanoi'09
by Serge Stinckwich April 21, 2009

April 21, 2009

Hi all, just a short breve : i use Pharo to make a demo during my Smalltalk talk at the last BarCamp Ha Noi'09 ;-) There is some pictures of my talk here : http://www.flickr.com/photos/crazyhands/3456228434/ http://www.flickr.com/photos/crazyhands/3455420077/ http://www.flickr.com/photos/gunner_ac50/3458847094/ I was pretty stable (more than last Squeak 3.10-dev where method finder doesn't not work ...). Thank you for the good work. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

1 0

[Pharo-project] Delays Semaphores and Processes
by Nicolas Cellier April 21, 2009

April 21, 2009

I took a look at http://bugs.squeak.org/view.php?id=7321 and http://code.google.com/p/pharo/issues/detail?id=688 I started publishing PharoInbox/SLICE-DelayFixFromMantis7321-nice to integrate Andreas' changes. Now I did integrate all but DelayCleanup.1.cs This change set does cure the failing testSemaphore in Pharo, but has two problems: 1) It requires a preamble, and I don't know how they are handled in Monticello 2) It probably does not include change about LargeInteger delays included in 3.9 (Dave kindly pointed me to http://bugs.squeak.org/view.php?id=854) 3) it makes DelayTests>>#testBounds fail I think that the limit of (SmallInteger maxVal//2) is not necessary... if LargeInteger delay fix is in the image. I can try to fix 2) mixing Andreas and Tim fixes. What about 1) ?

3 12

[Pharo-project] Lots of characters lost while typing in Unix
by Nicolas Cellier April 20, 2009

April 20, 2009

Since latest 10284 Pharo update, i experience lost of keystroke vanishing.

7 26

[Pharo-project] [ANN] - SqueakDBX first stable version 1.0!!!
by Mariano Martinez Peck April 20, 2009

April 20, 2009

Hi folks: After a continuous work since January 08, we are very glad to announce our first stable version of SqueakDBX. For those who don't know what this is about, the aim of this project is to build an OpenDBX (http://www.linuxnetworks.de/doc/index.php/OpenDBX/) wrapper which will allow users to perform relational database operations ( DDL, DML and SQL) through a truly open source library. Through this feature, the squeak community will hopefully be able to interact with major database engines, such as Oracle and SQL Server, besides those which are open source, like PostgreSQL, MySQL or Sqlite. Moreover, by integrating this with GLORP ( http://www.glorp.org/) will allow us to generate a complete and open source solution to relational data base access. Why did we do squeakDBX? reeThere are several approaches to persistence in Squeak, some very interesting: OODB like Gemstone and magma, image, CouchDB or TokyoT/C, and so on. All of this options get sense if you can actually decide the way you will persist your objects. However, this is not something that happens very frequently. FREQUENTLY, the client (the one who pays you for making the software) requires you to use a particular persistence strategy (RDBMS). Not only that, but also a database in particular (like Oracle, MS SQL, and so on). They have lots of reasons: they already have license for it, they have support and companies for it, they know SQL, they want to do selects, legacy systems, and so on. But Squeak only provides drivers for MySQL and PostgreSQL natively, so... what would you do in the rest of the cases? move to another language? OK, we don't. We want to program systems in Squeak. If you know about SqueakDBX you can just see changelog here: http://wiki.squeak.org/squeak/6109; If you don't, you should continue reading ;) SqueakDBX features: -Cross-platform support: Linux, Windows (using MinGW) and Mac. See http://wiki.squeak.org/squeak/6108 -Runs on Squeak and Pharo. -Mini VM blocks when using FFI (asynchronous queries). See http://wiki.squeak.org/squeak/6060#External%20call%20implementation. -Own SqueakDBX plugin (experimental). Ability to easily change the external call strategy (FFI or our own plugin). -Support for: Oracle, PostgreSQL, MySQL, MS SQL Server, ODBC and SQLite3 -Transactional concept: begin transaction, commit and rollback. See http://wiki.squeak.org/squeak/6071 -Mappings from String to specific types in selects. See http://wiki.squeak.org/squeak/6075 -Special OpenDBX options: multistatements, ï»¿encryption, compression, paged results, MySQL modes, and more. See http://wiki.squeak.org/squeak/6068 -Automated database connection ralease (although manual disconnection is recommended ;-) -Automated results retrieving in order to do another query, after doing a query and not iterating ALL results -Lots of unit tests that buck up our project ;-) (85 right now). See http://wiki.squeak.org/squeak/6077. -Lots of benchmarks and comparison with native drivers (PostgreSQL and MySQL). See http://wiki.squeak.org/squeak/6063. -Error handling: Not only errors, but levels associated with an error in order to avoid FFI calls (if you get a fatal error, it has no sense to do another query and the resources must be free). See http://wiki.squeak.org/squeak/6076 -Query timeout (this is very useful for web applications) and page size can be set for each query. See http://wiki.squeak.org/squeak/6069 -Very completed documentation in wiki and getting started. -Code critics and SwaLint were run several times. -Good design (at least all the major refactors demonstrated that). Full documentation, installation and getting started instructions can be found at wiki page: http://wiki.squeak.org/squeak/6052 . We spent a lot of time in it. It has all the information you may need and is in continuosdevelopment. Benchmarks: We have a lot of SqueakDBX benchmarks and also some for native squeak drivers (PostgreSQL and MySQL) and SqueakDBX seems to be faster than both of them. You can read more here: http://wiki.squeak.org/squeak/6063 Packages can be installed from Universe (3.10) or SqueakMap. Current version is 1.0. Sources can be download from SqueakSource http://www.squeaksource .com/SqueakDBX (it requires FFI installed). OpenDBX version: 1.4. Remember that you can compile OpenDBX by yourself or use precompiledbinaries. For more information please read: http://wiki.squeak.org/squeak/6129. GLORP integration: Actually, this may include two parts: 1) The integration of GLORP with squeak is completely hardcoded with PostgreSQL native driver. Because of this, first we will do a refactor in GLORP in order to enable it to support different drivers. We will create a PostgreSQL driver with the things that GLORP already has. We invited Alan Night to have dinner with us when he came to Argentina. We told him our ideas and discuss for a while till we got a first design of this refactor. We have already started this part. 2) Create a SqueakDBX driver for GLORP just like the one we are planning to do for PostgreSQL. The last squeak port of GLORP is very old and there is nobody to do it. A friend of us, Diogenes Moreira, has accepted this job, so, thanks to him, we hope to have latest GLORP releases in Squeak. You can see our Glorp progress here: http://wiki.squeak.org/squeak/6132 Help is always wanted. We would really appreciate if you: -Give us opinions, comments, ideas, new features, complaints and so on. -Tell us if you find a bug. -Tell us if you test SqueakDBX with other RDMBS or OS different from the ones we tested. Just to know if it works or not :) If you try SqueakDBX and you write something somewhere like a blog, let us know. We have this link: http://wiki.squeak.org/squeak/6131 where we put useful links for all the people. Special thanks to: -ESUG, for supporting us through Summer of Talk 08; -To Norbert (author of openDBX) for his help and to all the people who tested it and help us. Cheers, SqueakDBX team

1 0

[Pharo-project] [ANN] 10287 Delay cleanup
by StÃ©phane Ducasse April 20, 2009

April 20, 2009

>> To install DelayCleanup.1.cs it is necessary to write a ScriptLoader >> script like: >> script363 >> Delay startTimerEventLoop. >> (self buildConfigurationMapFor: >> #('Kernel-nice.renggli.300.mcz')) load >

1 0

[Pharo-project] Kernel Branch Name (was: Delays Semaphores and Processes)
by Lukas Renggli April 20, 2009

April 20, 2009

> does it make sense if I load kernel-nice.renggli.300 I am enjoying to see these nice.renggli branch names everywhere, but maybe sometime this tag should be removed ;-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

4 3

[Pharo-project] windows xp theme
by Steve Wirts April 20, 2009

April 20, 2009

Is there any chance a windows xp theme might eventually be included in pharo?

3 4

April 20, 2009

Thanks mike. Now I will do the delay fixes and some others of mine. Stef

1 0