December 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] - New SqueakDBX release

by Mariano Martinez Peck

We are very glad to announce our second beta release of SqueakDBX. The aim of this project is to build an OpenDBX (http://www.linuxnetworks.de/doc/index.php/OpenDBX/) plugin which will allow users to perform relational database operations (DDL, DML and SQL) through a truly open source library. The features for this release are: Bugs fixed: - Bug in odbx_query(), odbx_result() and odbx_result_finish() execution order. - Timeout in DBXPlatform #nextResultSet: was wrong mapped with FFI. Now, it is nil. - Some bugs in OpenDBXWin32 with apiCalls. New Features: -Support for SQLite in Linux -Support for MSSQL in linux and windows (with MinGW) -Support for PostgreSQL in Windows (with MinGW). -Better error handling. See http://wiki.squeak.org/squeak/6076 -New non-blocking plugin to replace FFI (just a proof of concept, but running). See OpenDBX-Plugin package in Monticello. -New SqueakDBX tutorial: how to compile openDBX in linux and windwos, common problems and solutions. You can download it from: http://www.assembla.com/spaces/Proyecto-Proyecto/documents/a0bKPg0qCr3Aeaab…. However this pdf will be converted into "wiki format" and put there. -Configurable Log. See http://wiki.squeak.org/squeak/6099 -Refactorized and updated wiki: http://wiki.squeak.org/squeak/6052 - We will be adding benchmarks on different backends and OS soon in the wiki: http://wiki.squeak.org/squeak/6063. - You must use openDBX 1.3.10 version. Useful links from wiki: - Current supported backends, operating system and squeak images here: http://wiki.squeak.org/squeak/6108 - ChangeLog: http://wiki.squeak.org/squeak/6109 - Targets and Features: http://wiki.squeak.org/squeak/6106 Again, help wanted. We are really convinced about open source projects. A software project is better when people share opinions, work, advice, comments, etc. 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 :) Full documentation, installation and getting started instructions can be found at wiki page: http://wiki.squeak.org/squeak/6052 Packages can be installed from Universe (3.10) or SqueakMap. Current version is 0.8 Sources can be download from SqueakSource http://www.squeaksource.com/SqueakDBX (it requires FFI installed) Cheers, SqueakDBX team

Dec. 23, 2008

[Pharo-project] Pharo image builds (was Re: Notifiers)

by Michael Roberts

If i'm right in thinking Damien's Pharo-Dev images are early release candidates going forwards for the Pharo image, without the one-click, would it make sense to start naming them Pharo. i.e. drop the -Dev. That way we could start to get consistent with our naming, get the web documentation consistent etc. thoughts? cheers, Mike On Sun, Dec 21, 2008 at 10:31 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Here is an answer for "what is Pharo?" > > There will be two images: > "Pharo-Core": the image in which the development of Pharo takes place > "Pharo": the image to develop your application with (= "Pharo-Core" + > IDE tools [1]) > > "Pharo" is the image that will be officially shipped (packaged as a > one-click image). "Pharo-Core" on the other hand will be important for > deployment as it has a low memory footprint. > > Cheers, > Adrian > > [1] http://code.google.com/p/pharo/wiki/Packages >

Dec. 23, 2008

Re: [Pharo-project] Closing a workspace windows

by Alexandre Bergel

Thanks Keith, I will look at it. Alexandre On 23 Dec 2008, at 12:37, Keith Hodges wrote: > Alexandre Bergel wrote: >> Exact. I will do some coding today or tomorrow. I will try to >> implement the suggestion of Damien. >> >> Alexandre >> >> > Please before you do could you pick up, Installer mantis ensureFix: > 5669. > > Honestly you guys, you don't have to fork absolutely everything, > please > incorporate something in to your philosophy of working and tools which > means that you don't have to. > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 23, 2008

Re: [Pharo-project] Closing a workspace windows

by Keith Hodges

Alexandre Bergel wrote: > Exact. I will do some coding today or tomorrow. I will try to > implement the suggestion of Damien. > > Alexandre > > Please before you do could you pick up, Installer mantis ensureFix: 5669. Honestly you guys, you don't have to fork absolutely everything, please incorporate something in to your philosophy of working and tools which means that you don't have to. Keith

Dec. 23, 2008

[Pharo-project] On not unnecessarily closing down the language

by Lukas Renggli

Seaside depends on external packages, that we don't have control over. For example there the Swazoo package contains a class-instance variable that is uppercase. Unfortunately Pharo throws a notification (instance variables should begin with a lower case characters) when loading that code. This is awkward, because it makes it impossible to load code automatically and gives us additional work. In my opinion a programming language should be as open as possible, and if possible not restrict the user in any way, even if this is against best practices. Unfortunately many of those restrictions are built into our language that wouldn't be necessary: - class names and class-variable names are enforced to be uppercase - class instance-variable names are enforced to be lowercase - it is not possible to assign a new value to a method argument - variable names are enforced to be unique in all scopes In my opinion the language should be as open as possible. It is the purpose of Code Critics to point out smells, not the task of the compiler to reject code that doesn't follow best practices. I am slightly frustrated trying to work around these restrictions ... Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 23, 2008

Re: [Pharo-project] Vocabulary

by David RÃ¶thlisberger

> OBClassAwareNode>>allCategories depends on the class Vocabulary which > does not seem to be present anymore. ok, I fixed this method to not use Vocabulary anymore. (OB-Standard-dr.383) David

Dec. 23, 2008

Re: [Pharo-project] Closing a workspace windows

by Alexandre Bergel

Exact. I will do some coding today or tomorrow. I will try to implement the suggestion of Damien. Alexandre On 23 Dec 2008, at 10:31, Keith Hodges wrote: > Damien Cassou wrote: >> On Mon, Dec 22, 2008 at 8:59 PM, Alexandre Bergel >> <Alexandre.Bergel(a)inria.fr> wrote: >> >>> Just a check. When I close a workspace I have a popup window asking >>> for "Changes have not been saved, is it OK to cancel those >>> changes?". >>> I find this pretty annoying. I do not remember to have said "yes", >>> even once. >>> >>> Am I the only one? >>> >> >> I've also never answered yes. The best solution would be to store the >> last 5 contents of the workspaces and close without confirmation. If >> the user closed his workspace accidentally, he can still open a new >> one, go to the menu and select one of the saved entries. How does >> that >> sound? > At present workspaces are not very good at editing files. I added some > fixes that allow you to open a workspace on a file. If save on accept > was implemented then the dialog would make sense > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 23, 2008

Re: [Pharo-project] Closing a workspace windows

by Keith Hodges

Damien Cassou wrote: > On Mon, Dec 22, 2008 at 8:59 PM, Alexandre Bergel > <Alexandre.Bergel(a)inria.fr> wrote: > >> Just a check. When I close a workspace I have a popup window asking >> for "Changes have not been saved, is it OK to cancel those changes?". >> I find this pretty annoying. I do not remember to have said "yes", >> even once. >> >> Am I the only one? >> > > I've also never answered yes. The best solution would be to store the > last 5 contents of the workspaces and close without confirmation. If > the user closed his workspace accidentally, he can still open a new > one, go to the menu and select one of the saved entries. How does that > sound? At present workspaces are not very good at editing files. I added some fixes that allow you to open a workspace on a file. If save on accept was implemented then the dialog would make sense Keith

Dec. 23, 2008

Re: [Pharo-project] Vocabulary

by StÃ©phane Ducasse

Exact and I think that OB should be cured from relying on vocabulary stuff. Stef On Dec 23, 2008, at 11:42 AM, Damien Cassou wrote: > OBClassAwareNode>>allCategories depends on the class Vocabulary which > does not seem to be present anymore. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 23, 2008

[Pharo-project] Vocabulary

by Damien Cassou

OBClassAwareNode>>allCategories depends on the class Vocabulary which does not seem to be present anymore. -- Damien Cassou http://damiencassou.seasidehosting.st

Dec. 23, 2008