March 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] 10258 Test package created
by StÃ©phane Ducasse March 21, 2009

March 21, 2009

Created a bunch a testpackage based on mike proposal. Now the inbox should be empty and we should focus on the closures (and not removing project :). Stef

1 0

Re: [Pharo-project] [squeak-dev] Organising and Documenting Micro-Universes in Squeaksource
by Damien Pollet March 21, 2009

March 21, 2009

On Thu, Mar 19, 2009 at 22:46, Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: > I have long been frustrated that there is no place in squeaksource for > documenting what is in a repository, and offering feedback as to what > works where. Yes, and the MC tools should support that IMHO. BTW I'd also add: no nice support for named/tagged branches (I mean, in a big project there should be released/working/devel/in-progress branches, or at least documented sequences of snapshots for stable versions, and we have package-developerUniversallyKnownToNotRegularlyBreakThings.biggestNumber.mcz) > I have started to use Sake/Packages as a kind of micro "universe" for my > Seaside "Client" UI & Backend Component Framework. Having seen how > useful this is I thought that this might be useful for pier, and of > course seaside and other projects. Yup, I like the idea. > Some have reservations about Sake/Packages because they say it is not > declaritive. Huhâ¦ it's a rule system, right ? The alternative I know about being scripts that explicitly load snapshots in sequence, I fail to see where sake is not declarative. >From my discussions on the subject, problems are more about the perception of what level of predictability and control one would get by using sake. Questions like "how do I know what will get installed if I pull this one" or "how do I install this, but with this particular version of that", and so on. Maybe it's a problem of polishing the DSL, of documentation, maybe of tools, I'm not sure; that could be investigated a bit more. For me it's clear that automatic dependancy management is the way to go, though the squeak/pharo community does not have resources or organization like debian's, so I think we need a more decentralized and agile way of managing dependancies, detecting and resolving incoherencies, etc. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

7 34

[Pharo-project] Fwd: I have the following version of Seaside
by StÃ©phane Ducasse March 21, 2009

March 21, 2009

Hi Fritz I think that some guys already answer that question in the pharo mailing-list I have to run now (kid business). Stef Begin forwarded message: > From: "Fritz Schenk" <Fritz_Schenk(a)Countrywide.Com> > Date: March 21, 2009 1:28:11 AM CEST > To: stephane.ducasse(a)inria.fr > Subject: I have the following version of Seaside > > > Smalltalk version 'Squeak3.9' > > Where do I get the latest pharo, and how do I install it on my image? > > Thanks > > ====================================================================== > Confidentiality Notice: The information contained in and transmitted > with this communication is strictly confidential, is intended only > for the use of the intended recipient, and is the property of > Countrywide Financial Corporation or its affiliates and > subsidiaries. If you are not the intended recipient, you are hereby > notified that any use of the information contained in or transmitted > with the communication or dissemination, distribution, or copying of > this communication is strictly prohibited by law. If you have > received this communication in error, please immediately return this > communication to the sender and delete the original message and any > copy of it in your possession. > ======================================================================

2 1

Re: [Pharo-project] [squeak-dev] Re: Rewriting an Input/EventSensor code
by Igor Stasenko March 21, 2009

March 21, 2009

2009/3/21 Andreas Raab <andreas.raab(a)gmx.de>: > Igor Stasenko wrote: >> >> Recently , we discussed it with Andreas, and had an idea to integrate >> this with Announcement framework (and Announcement will become a core >> package). > > Actually, Jecel propsed the combination. > >> Here is my vision , how things should look like: > > [... big snip ...] > >> Michael, Andreas, i'd like to hear your comments and remarks, as well >> as any others are wellcome. > > It's too much to do all that in one go around. What I would propose is to > start simple by having an event source which maps from raw event buffers to > some kind of (non-morphic) event objects and have InputSensor be a client of > that. I believe that is a straightforward extension of the work that has > already been done. > Wait, i proposing nearly same: Have an event source which produces (non-morphic) event objects and InputSensor. I just want to know where Announcements takes part of it, or should be postpone that for a next step? > Cheers, > Â - Andreas > -- Best regards, Igor Stasenko AKA sig.

3 5

[Pharo-project] [ANN] 10257 System Package creation
by StÃ©phane Ducasse March 21, 2009

March 21, 2009

with this version System have now packages So far I learned that merging is quite broken when only moving between packages both merge tools do not work and this is probably a MC problem Pavel I got a conflict wiht the more general beep. I reverted and hope this is ok. What is left to do Dealing with the Tests standalone packages and the three new packages containing tests. SystemChangeNotification-Tests-sd.11.mcz Tests-sd.46.mcz Tests-System-Digital Signatures-sd.2.mcz Tests-System-Object Events-sd.2.mcz Tests-SystemChangeNotification-sd.2.mcz Now leaving, let me know if this is ok. What energy spent for just creating packages. Stef

1 0

[Pharo-project] if you want to reproduce my merge conflict bug
by StÃ©phane Ducasse March 21, 2009

March 21, 2009

take 10256 merge the inbox slice made by michael press conflict -> DNU Using the old merging tool I cannot keep or reject (buttons not activated) when I press diff/install I get a DNU Stef

1 0

[Pharo-project] How to rename a package ?
by Alain Plantec March 21, 2009

March 21, 2009

Thanks Alain

6 12

[Pharo-project] Rewriting an Input/EventSensor code
by Igor Stasenko March 21, 2009

March 21, 2009

Hello lists, I making a cross-post, because there are interest from both camps to make it done :) Michael published a changesets with new event sensor code for Pharo, which mainly focused on supporting multiple event consumers(frameworks). Recently , we discussed it with Andreas, and had an idea to integrate this with Announcement framework (and Announcement will become a core package). I very like this idea, but i think we should discuss the implementation details before starting it. Here is my vision , how things should look like: - role 1. Event source. VM, is an events source, in most cases it is the only source, but not always. I would like to be able to plug-in a different event source.. imagine a remote socket connection, or previously recorded events and then replayed. So, an event source should be a separate, abstract entity, where VM is one of the concrete kind of it. There is also, sometimes a need to inject a fabricated events into event queue, to simulate user input, or for producing a synthetic events. - role 2. Event listener/Event sensor (or InputSensor) is a mediator between event source and higher level framework (Morphic.. etc), its role is to listen events from event source and then dispatch it to concrete consumer(s), if any. - role 3. Events. Events should be a full featured objects, with good protocol. A high level framework should not peruse with raw data, as it currently does with raw event buffers which coming from VM. This means, that changes will affect the Morphic. Morphic having a classes for user input events (keyboard/mouse) and decifering raw VM events into own representation. I think we should move the 'decifering' part to EventSource (sub)classes, and make sure EventSensor (and its consumers) dealing with full featured event objects, leaving event consumers free to decide what to do with them. - role 4. Event consumers. Note, there can be multiple different consumers, not just one, as its currently Morphic. We should make sure, that integration with any other framework will be painless. - be ready for supporting multiple host windows. This part is quite simple to do in EventSensor.. but not so simple in Morphic. One thing would be is to refactor all code which uses the Sensor global directly, and replace it with appropriate thing(s). But this is out of scope of event handling framework, at initial stage , we could keep things compatible with old ways (1 Sensor, 1 Display, 1 Morphic World). I started prototyping a classes for events, where each event kind having own event subclass, and directly decoding the VM raw event buffer, so then any event consumer(s) don't have to poke raw events. But since there were a good idea to make use of Announcements for it, it may need some refactoring. Michael, Andreas, i'd like to hear your comments and remarks, as well as any others are wellcome. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Problem with cdelc and apicall
by Mariano Martinez Peck March 20, 2009

March 20, 2009

People: I am having a problem with cdelc and apicall in windows with SqueakDBX. I have a abstract class OpenDBX with the subclasses: OpenDBXWin32 and OpenDBXUnix. SqueakDBX detects which OS you are using and instances one of them. They have these methods: OpenDBXWin32: apiBind: handle database: databaseName name: userName password: password method: method "int odbx_bind(odbx_t* handle, const char* database, const char* who, const char* cred,int method )" <apicall: long 'odbx_bind' (ulong char* char* char* ulong) module: 'libopendbx-1.dll'> ^self externalCallFailed OpenDBXUnix: apiBind: handle database: databaseName name: userName password: password method: method "int odbx_bind(odbx_t* handle, const char* database, const char* who, const char* cred,int method )" In linux, I don't have problems, but in windows, when I try to download it from MC, I have a "sintax errror" "OpenDBXUnix api calls apiBind: handle database: databaseName name: userName password: password method: method" apiBind: handle database: databaseName name: userName password: password method: method "int odbx_bind(odbx_t* handle, const char* database, const char* who, const char* cred,int method )" <> expected ->cdecl: long 'odbx_bind' (ulong char* char* char* ulong) module: 'opendbx'> ^self externalCallFailed <cdecl: long 'odbx_bind' (ulong char* char* char* ulong) module: 'opendbx'> ^self externalCallFailed Does anyone have an idea of what can be happening ? thanks in advance. Mariano

1 0

March 20, 2009

Hi today I was helping a new coder here to recover some changes and I noticed that the changeset was full of doit. Apparently the tests execution seems to be added to the changesets. I will investigate that more but we should pay attention. Stef

1 0