October 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Newbie question: Connection to SQLite DB

by nullPointer

The final work must be in MacOSX... IÂ´m searching for the existence of binary but I donÂ´t found. Perhaps is needed compile :( Anything, I need OpenDBX for use Sqlite3 project? ( http://squeaksource.com/@7SFD7f008dKbC-Yt/rKzITl0- http://squeaksource.com/@7SFD7f008dKbC-Yt/rKzITl0- ) I donÂ´t need use glorp for the work; is for a very dummy DB. Thanks for the help. -- View this message in context: http://forum.world.st/Newbie-question-Connection-to-SQLite-DB-tp2954195p295… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 4, 2010

Re: [Pharo-project] Newbie question: Connection to SQLite DB

by Mariano Martinez Peck

On Mon, Oct 4, 2010 at 4:36 PM, nullPointer <epicfan(a)gmail.com> wrote: > > > Mariano Martinez Peck wrote: > > > > > > You need the opendbx and sqlite libraries. > > Everything is explained here: > > http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX > > > > or here http://www.squeakdbx.org/Compiling%20for%20different%20backends > > > > > > glups! that must be the problem :| I did install the binary sqlite on OS ( > in the bin folder, correct? ) > yes > but not the OpenDBX. Anything Sqlite3 project donÂ´t work of that way. I > will > try with SqueakDBX and installing OpenDBX before. > > in which OS are you? if Windows, just download the dlls and put it there. > As you can see IÂ´m very newbie on that things :( > > Thanks. > > > -- > View this message in context: > http://forum.world.st/Newbie-question-Connection-to-SQLite-DB-tp2954195p295… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 4, 2010

Re: [Pharo-project] Ocean (was Re: Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm))

by Sven Van Caekenberghe

Noury, One of the other aspects that I find important is elementary efficiency. A lot of stream related code in Smalltalk is not efficient, the actual data is copied around like crazy, turning it from a stream to a collection and then back into a stream multiple times. For Zinc HTTP Components I made a lot of effort to make it possible to read data from a socket stream in true streaming fashion (instead of just returning a byte array). Now, the idea was then that for example JPEGReadWriter>>#nextImage would work transparaently on that raw stream. Sadly, the code in JPEGReadWriter and friends just reads everything into an array before it starts to work ! Doing a #nextPutAll: <some byte array> should really try never to copy the array. Similary, a #next: <count> into: <some byte array> should similary write directly into the given array. What I see in the current SocketStream is <censored/> ;-) But OK, maybe this is easier said than done. The step from Smalltalk to system call should also not copy if that is possible, but then FFI and GC come into play. Anyway, good luck, I am willing to try using Ocean as soon as it becomes available. Sven On 04 Oct 2010, at 10:59, Noury Bouraqadi wrote: > > On 3 oct. 2010, at 16:28, Schwab,Wilhelm K wrote: > >> For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. The calls need to block their calling Process and let the other Processes run as though nothing is happening. >> > You're right. > Another option is having a multi-threaded VM. Eliot seem to work on it. > So far we're working on cleaning up the design of basic functionalities before going on. > Then, we'll try to find a workaround for non-blocking calls. > All ideas are welcome :-) > > BTW, some people (you included) proposed to help for the Ocean project. > Luc and I want to thank you and we are happy that others are willing to help. > We thought about the best way to integrate others help. > Our conclusion is that we should first do alone (luc and me) the reference design, before integrating other developers. > So, we all can work on solid foudations. > > Noury > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 4, 2010

Re: [Pharo-project] Soap Webservices for pharo

by Janko MivÅ¡ek

Hi guys, Nice to see that SOA Web Services in Squeak/Pharo is rolling on again. We really need that, if we want Pharo to be useful in commercial, specially in so called "enterprisely" world. Those who listen Andreas ThÃ¶nne's talk on ESUG, know what I mean. What we really need on SOA Web Services front: - WSDL support, - XML <-> Object mapping. - Tools Goal should be a "one-click" use of Web Services. From both client and server setup. As all Smalltalks support it, except Squeak/Pharo yet not. Look at excellent VW or VA Smalltlak WebServices suport for inspiration. Best regards Janko On 04. 10. 2010 16:21, Guillermo Polito wrote: > http://www.mars.dti.ne.jp/~umejava/smalltalk/soapOpera/soapCore.html > > So, we have some tasks now: > > - put it in squeaksource > - test it in pharo > - build a metacello config > - document it? > > Any help is really appreciated, since I don't have too much time. > > Cheers, > Guille > > ---------- Forwarded message ---------- > From: *Masashi Umezawa* <umejava(a)mars.dti.ne.jp > <mailto:umejava@mars.dti.ne.jp>> > Date: Mon, Oct 4, 2010 at 8:46 AM > Subject: Re: About SoapOpera and SoapCore > To: Guillermo Polito <guillermopolito(a)gmail.com > <mailto:guillermopolito@gmail.com>> > > > Hi Guillermo, > > I am happy to hear that SoapOpera and SoapCore would be useful for your > projects. Please feel free to reuse my Soap stuff. > Recently I do not have enough time to upgrade those packages. So I > really appreciate your offer. > > I hope SoapOpera and SoapCore will start growing again! > > Best regards, > > Guillermo Polito <guillermopolito(a)gmail.com > <mailto:guillermopolito@gmail.com>> wrote: >> Hi! >> >> My name's Guillermo and I'm from Argentina. I'm participating in the > pharo >> project (www.pharo-project.org <http://www.pharo-project.org>), and I > would love to integrate your soap >> package into our available packages :). >> I was wandering if you let us put it into squeaksource > (www.squeaksource.com <http://www.squeaksource.com>) >> and mantain it for our use, because pharo is growing very quickly and it >> needs this kind of really cool stuff :). Of course we will keep the MIT >> license. >> >> Thank you for your time and sorry for bothering :P! >> Guille > > --- > [:masashi | ^umezawa] -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Oct. 4, 2010

[Pharo-project] Wrong fix: Issue 2947: SmalltalkEditor doesn't handle ESC key.

by Fernando olivero

I argue that this fix is wrong, giving the morph logic to the Editor instead of the View ( the morph). this conceptual problem, leads to having to ask for the Global ActiveEvent in the Editor>>offerMenuFromEsc:. If you take a look at the already present method, which should be the one to be used. Editor>>escapePressed "The message is sent when the user hits esc" self announceEscape Which allows the Morph to take care of the view related behavior. So i propose reverting to this behavior: Editor>>escapePressed self morph escapePressed . ^ false Then adding TextMorph>>escapePressed self yellowButtonActivity: false. TextMorphForEditView>>escapePressed self editView yellowButtonActivity: false . Given that TextMorphForEditView is the only implementor of #editView, and following the logic in TextEditor>>raiseContextMenu: TextEditor>>offerMenuFromEsc: aKeyboardEvent The attached change set implements the fixes.

Oct. 4, 2010

Re: [Pharo-project] Newbie question: Connection to SQLite DB

by nullPointer

Mariano Martinez Peck wrote: > > > You need the opendbx and sqlite libraries. > Everything is explained here: > http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX > > or here http://www.squeakdbx.org/Compiling%20for%20different%20backends > > glups! that must be the problem :| I did install the binary sqlite on OS ( in the bin folder, correct? ) but not the OpenDBX. Anything Sqlite3 project donÂ´t work of that way. I will try with SqueakDBX and installing OpenDBX before. As you can see IÂ´m very newbie on that things :( Thanks. -- View this message in context: http://forum.world.st/Newbie-question-Connection-to-SQLite-DB-tp2954195p295… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 4, 2010

Re: [Pharo-project] Ocean (was Re: Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm))

by Igor Stasenko

On 4 October 2010 11:59, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > On 3 oct. 2010, at 16:28, Schwab,Wilhelm K wrote: > >> For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. Â The calls need to block their calling Process and let the other Processes run as though nothing is happening. >> > You're right. > Another option is having a multi-threaded VM. Eliot seem to work on it. > So far we're working on cleaning up the design of basic functionalities before going on. > Then, we'll try to find a workaround for non-blocking calls. > All ideas are welcome :-) > There are two ways. Use sockets in blocking mode or in non-blocking mode. In both variants its possible to not block VM thread during the call(s), but depending on socket's mode, implementation will be different. i think it would be cool to have non-blocking socket at language side (i.e. doing socket calls does not blocks VM as well as smalltalk Process which made it). What could block the process , is putting it on wait , till socket's state change (ready for write, connected, closed etc). Now i think that with such approach you don't even need generic non-blocking FFI callout mechanism. You just need to run extra native thread(s), which periodically polls the socket(s) state and signals its semaphores accordingly. > BTW, some people (you included) proposed to help for the Ocean project. > Luc and I want to thank you and we are happy that others are willing to help. > We thought about the best way to integrate others help. > Our conclusion is that we should first do alone (luc and me) the reference design, before integrating other developers. > So, we all can work on solid foudations. > > Noury > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 4, 2010

Re: [Pharo-project] Refactoring>checkPreconditions behaves funny about the errorBlock

by Lukas Renggli

> Ok, let's summarize: If an error occurs, the handler block is not > evaluated, but attached to a new exception, that exception is raised. > Then, the caller catches that exception, retrieves the handler block, > does some more ballyhoo, and then runs the handler block. Yes, the block mostly contains some code to that allows the user to fix the problem (like to show all references of a class to be removed, etc.). > And you get invited to this construction by these methods in > RBAbstractCondition: > > errorBlock > Â Â Â Â ^self errorBlockFor: false > > errorBlockFor: aBoolean > Â Â Â Â ^nil These methods (and subclass implementations) are used to retrieve the right block that caused the composite condition to fail. > We can clean it up on the next sprint, if you want :) The implementation in RBCondition is fine, the problem is more the way how exceptions are used to pass the values. This mainly stems from the fact that exceptions evolved over the past 15 years and are no longer the same as the signals that were used when the refactoring code was originally written. Now of course it is difficult to change this code because there are various users out there that depend on it, e.g. OB, RefactoringBrowser, SmaCC, ... Lukas -- Lukas Renggli www.lukas-renggli.ch

Oct. 4, 2010

Re: [Pharo-project] Refactoring>checkPreconditions behaves funny about the errorBlock

by Niko Schwarz

Ok, let's summarize: If an error occurs, the handler block is not evaluated, but attached to a new exception, that exception is raised. Then, the caller catches that exception, retrieves the handler block, does some more ballyhoo, and then runs the handler block. And you get invited to this construction by these methods in RBAbstractCondition: errorBlock ^self errorBlockFor: false errorBlockFor: aBoolean ^nil We can clean it up on the next sprint, if you want :) Niko On Mon, Oct 4, 2010 at 4:14 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > The tool that triggers the refactoring, e.g. ORCommand>>#handleError: > > Ok, the code is quite ugly, but this is how the original refactoring > browser implemented it. > > On 4 October 2010 16:06, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote: >> Ok, help me out, how is that block ever invoked? The above code >> snippet just appends the block as a parameter to an exception, which >> looks just funny. >> >> Niko >> >> On Mon, Oct 4, 2010 at 3:44 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >>> See for senders of #errorBlock:, e.g. >>> PushDownInstanceVariableRefactoring, RemoveClassRefactoring or >>> RemoveInstanceRefactoring. >>> >>> On 4 October 2010 15:40, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> This is used to validate the preconditions of refactorings and inform >>>> the user about any mismatches. >>>> >>>> It should better not be removed. >>>> >>>> Lukas >>>> >>>> On 4 October 2010 15:36, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote: >>>>> Hi, >>>>> >>>>> The RB refactorings do some obscure dance around an errorBlock, which >>>>> is always nil, as far as I can see. As I was trying to supply a >>>>> non-nil error block, I was astonished to find out that even if it >>>>> isn't nil, it won't be executed. Here's the relevant snippets: >>>>> >>>>> checkPreconditions >>>>> Â Â Â Â | conditions block | >>>>> Â Â Â Â conditions := self preconditions. >>>>> Â Â Â Â conditions check >>>>> Â Â Â Â Â Â Â Â ifFalse: >>>>> Â Â Â Â Â Â Â Â Â Â Â Â [block := conditions errorBlock. >>>>> Â Â Â Â Â Â Â Â Â Â Â Â block notNil >>>>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [self refactoringError: conditions errorString with: block] >>>>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [self refactoringError: conditions errorString]] >>>>> >>>>> refactoringError: aString with: aBlock >>>>> Â Â Â Â ^ RefactoringError signal: aString with: aBlock >>>>> >>>>> I can't imagine how that could help anyone. I suggest either removing >>>>> the errorBlock, or turning it into a good old instance variable, and >>>>> running it in case of an error. >>>>> >>>>> Cheers, >>>>> >>>>> Niko >>>>> >>>>> -- >>>>> http://scg.unibe.ch/staff/Schwarz >>>>> twitter.com/nes1983 >>>>> Tel: +41 076 235 8683 >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://scg.unibe.ch/staff/Schwarz >> twitter.com/nes1983 >> Tel: +41 076 235 8683 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

Oct. 4, 2010

Re: [Pharo-project] Ocean (was Re: Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm))

by Schwab,Wilhelm K

Noury, I am very interested in seeing this done well. At a minimum, I'll give the result some serious abuse. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Noury Bouraqadi [bouraqadi(a)gmail.com] Sent: Monday, October 04, 2010 4:59 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Ocean (was Re: Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm)) On 3 oct. 2010, at 16:28, Schwab,Wilhelm K wrote: > For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. The calls need to block their calling Process and let the other Processes run as though nothing is happening. > You're right. Another option is having a multi-threaded VM. Eliot seem to work on it. So far we're working on cleaning up the design of basic functionalities before going on. Then, we'll try to find a workaround for non-blocking calls. All ideas are welcome :-) BTW, some people (you included) proposed to help for the Ocean project. Luc and I want to thank you and we are happy that others are willing to help. We thought about the best way to integrate others help. Our conclusion is that we should first do alone (luc and me) the reference design, before integrating other developers. So, we all can work on solid foudations. Noury _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 4, 2010