- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

by Mariano Martinez Peck

I found a way!!!! Much cleaner and easier. Awesome! I will clean it, test it a bit more and try to package it for public usage :) On Fri, Dec 4, 2015 at 12:31 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Fri, Dec 4, 2015 at 12:05 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 04 Dec 2015, at 14:29, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which >> are completely different. WADynamicVariable uses exception mechanism >> while DynamicVariable uses the ProcessSpecificVariable. >> But thanks anyway! >> >> >> Oh manâ¦. Sorry :) >> >> I wonder, why WADynamicVariable *isnât* a DynamicVariable. The semantics >> are the same if Iâm not mistaken (e.g. only available in the current >> process) and I think access to a dynamic variable may even be faster >> because it *doesnât* use the exception mechanism (i.e. no need to walk down >> the stack). >> If someone knows the answer, Iâd be happy to hear it. >> >> > I bet it's because of portability. For example, i remember in GemStone the > ProcessorLocalVariable did not behave the same as in Pharo. And it was > actually an experiment. I think you cannot expect all this stuff to be ansi > (or easily portable), while exceptions do. > > >> Iâve played around with Process>>signalException: and >> Context>>handleSignal: (which looked quite promising) but didnât get any >> results. Iâm out of ideas. >> >> > I have played all morning with an idea of using local variables. I arrive > to the point where I DO HAVE the request context at hand, but I don't find > an easy way to hook into do-its, print-it etc so that the closure evaluated > gets the request context plugged. In other ways... let's say I have the > context stored somewhere. I am at the SmalltalkEditor >> > evaluateSelectionAndDo: aBlock > > and so..somewhere I need to do something like: > > WACurrentRequestContext use: self storedContextSomewhere during: [ self > theSelectionToBeEvaluated ] > > and that's where I am now :) > > > > >> Cheers, >> Max >> >> >> On Fri, Dec 4, 2015 at 7:32 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Hereâs a snippet to play with: >>> >>> p := Processor activeProcess. >>> x := 2. >>> v := TestDynamicVariable value: x during: [ >>> ((p instVarNamed: 'env') ifNotNil: [ :env| >>> env copyWithout: nil ]) inspect >>> ]. >>> >>> ((p instVarNamed: 'env') ifNotNil: [ :env| >>> env copyWithout: nil ]) inspect >>> >>> Cheers, >>> Max >>> >>> On 04 Dec 2015, at 10:47, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> I feel you :) >>> >>> Without having thought this through completely: if you look at the >>> implementation of DynamicVariable>>value:during: youâll see that the way it >>> works is that the variable is bound to the active process. In the debugger >>> you have access to the process that is being debugged and thus you should >>> have access to the variables bound to it. You could try accessing all such >>> variables by iterating over them (which I think will require an extension >>> on Process because youâd need to access at least the PSKeys class variable). >>> >>> Cheers, >>> Max >>> >>> On 04 Dec 2015, at 00:34, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> >>> Hi guys, >>> >>> This thing I will ask in this email it's in my mind since YEARS. But I >>> have always thought it was like that and that there was nothing we could >>> do. However, I think it's time I ask again :) >>> >>> For those that have used Seaside, and you try to debug, you know that >>> upon request processing seaside uses Exceptions mechanisim to always have >>> access to the request, session, etc. They way that is done is very smart :) >>> >>> WACurrentRequestContext use: self during: aBlock >>> >>> In that case, "self" is the request instance and aBlock the closure that >>> takes care of the request processing. So, inside that closure, everywhere >>> you do "WACurrentRequestContext value" you get the correct request instance. >>> >>> So..that's great for Seaside, but debugging gets complicated. While you >>> can restart, proceed, etc, once inside debugger, you cannot evaluate any >>> piece of code that will use the session or request because you get >>> a WARequestContextNotFound. Of course, because I guess the evaluation you >>> do from cmd+d on a piece of text or via the debugger inspector, creates >>> another closure/context which does not receive the WACurrentRequestContext >>> instance. >>> >>> Now....besides WACurrentRequestContext I have my own class >>> UserContextInformation where I basically have a bunch of stuff associated >>> to the logged user. And I do exactly the same as the >>> WACurrentRequestContext. And I have the same problem. I really want to be >>> able to fix this. >>> >>> Anyone have an idea on how can I do it? I guess I can change the >>> debugger, in the place where I evaluate code so that I wrap that evaluation >>> with my request context instance??? >>> >>> Thoughts? >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Dec. 4, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50485 Home: https://github.com/pharo-project/pharo-core

Dec. 4, 2015

[pharo-project/pharo-core] 7a8e6d: 50485

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7a8e6d1b8907aa8fa9d5b71564122941517413f6 https://github.com/pharo-project/pharo-core/commit/7a8e6d1b8907aa8fa9d5b715… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-04 (Fri, 04 Dec 2015) Changed paths: M Monticello.package/MCVersion.class/instance/accessing/loadCompleteSnapshot.st M Nautilus.package/NautilusUI.class/instance/package filter/buildPackageSearch.st A OpalTools.package/extension/SymbolicBytecode/instance/gtSpotterCodePreviewIn_.st A OpalTools.package/extension/SymbolicBytecode/instance/spotterActDefault.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50484.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50485.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50484.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50485.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50485 16964 Nautilus package search field cursor goes back to start when space is inserted at the end of the field https://pharo.fogbugz.com/f/cases/16964 17185 Broken changes view https://pharo.fogbugz.com/f/cases/17185 17172 SymbolicBytecode should be embeddable in Spotter https://pharo.fogbugz.com/f/cases/17172 http://files.pharo.org/image/50/50485.zip

Dec. 4, 2015

Re: [Pharo-dev] Unicode Support

by Max Leske

Hi Euan I think itâs great that youâre trying this. I hope you know what youâre getting yourself into :) Iâm no Unicode expert but I want to add two points to your list (although youâve probably already thought of them): - Normalisation and conversion (http://unicode.org/faq/normalization.html) Unicode / ICU provide libraries (libuconv / libiconv) that handle this stuff. Specifically normalisation conversions arenât trivial and I think it wouldnât make much sense to reimplement those algorithms. I do think however, that having them available is important (where I work weâre currently writing a VM plugin for access to libiconv through primitives so that we can clean out combining characters through normalisation. And weâll obviously get nice sorting properties and speeds for free) - Sorting and comparison. Basically the same point as above. libuconv / libiconv provide algorithms for this. Do we need our own implementation? Cheers, Max > On 04 Dec 2015, at 12:42, EuanM <euanmee(a)gmail.com> wrote: > > I'm currently groping my way to seeing how feature-complete our > Unicode support is. I am doing this to establish what still needs to > be done to provide full Unicode support. > > This seems to me to be an area where it would be best to write it > once, and then have the same codebase incorporated into the Smalltalks > that most share a common ancestry. > > I am keen to get: equality-testing for strings; sortability for > strings which have ligatures and diacritic characters; and correct > round-tripping of data. > > Call to action: > ========== > > If you have comments on these proposals - such as "but we already have > that facility" or "the reason we do not have these facilities is > because they are dog-slow" - please let me know them. > > If you would like to help out, please let me know. > > If you have Unicode experience and expertise, and would like to be, or > would be willing to be, in the 'council of experts' for this project, > please let me know. > > If you have comments or ideas on anything mentioned in this email > > In the first instance, the initiative's website will be: > http://smalltalk.uk.to/unicode.html > > I have created a SqueakSource.com project called UnicodeSupport > > I want to avoid re-inventing any facilities which already exist. > Except where they prevent us reaching the goals of: > - sortable UTF8 strings > - sortable UTF16 strings > - equivalence testing of 2 UTF8 strings > - equivalence testing of 2 UTF16 strings > - round-tripping UTF8 strings through Smalltalk > - roundtripping UTF16 strings through Smalltalk. > As I understand it, we have limited Unicode support atm. > > Current state of play > =============== > ByteString gets converted to WideString when need is automagically detected. > > Is there anything else that currently exists? > > Definition of Terms > ============== > A quick definition of terms before I go any further: > > Standard terms from the Unicode standard > =============================== > a compatibility character : an additional encoding of a *normal* > character, for compatibility and round-trip conversion purposes. For > instance, a 1-byte encoding of a Latin character with a diacritic. > > Made-up terms > ============ > a convenience codepoint : a single codepoint which represents an item > that is also encoded as a string of codepoints. > > (I tend to use the terms compatibility character and compatibility > codepoint interchangably. The standard only refers to them as > compatibility characters. However, the standard is determined to > emphasise that characters are abstract and that codepoints are > concrete. So I think it is often more useful and productive to think > of compatibility or convenience codepoints). > > a composed character : a character made up of several codepoints > > Unicode encoding explained > ===================== > A convenience codepoint can therefore be thought of as a code point > used for a character which also has a composed form. > > The way Unicode works is that sometimes you can encode a character in > one byte, sometimes not. Sometimes you can encode it in two bytes, > sometimes not. > > You can therefore have a long stream of ASCII which is single-byte > Unicode. If there is an occasional Cyrillic or Greek character in the > stream, it would be represented either by a compatibility character or > by a multi-byte combination. > > Using compatibility characters can prevent proper sorting and > equivalence testing. > > Using "pure" Unicode, ie. "normal encodings", can cause compatibility > and round-tripping probelms. Although avoiding them can *also* cause > compatibility issues and round-tripping problems. > > Currently my thinking is: > > a Utf8String class > an Ordered collection, with 1 byte characters as the modal element, > but short arrays of wider strings where necessary > a Utf16String class > an Ordered collection, with 2 byte characters as the modal element, > but short arrays of wider strings > beginning with a 2-byte endianness indicator. > > Utf8Strings sometimes need to be sortable, and sometimes need to be compatible. > > So my thinking is that Utf8String will contain convenience codepoints, > for round-tripping. And where there are multiple convenience > codepoints for a character, that it standardises on one. > > And that there is a Utf8SortableString which uses *only* normal characters. > > We then need methods to convert between the two. > > aUtf8String asUtf8SortableString > > and > > aUtf8SortableString asUtf8String > > > Sort orders are culture and context dependent - Sweden and Germany > have different sort orders for the same diacritic-ed characters. Some > countries have one order in general usage, and another for specific > usages, such as phone directories (e.g. UK and France) > > Similarly for Utf16 : Utf16String and Utf16SortableString and > conversion methods > > A list of sorted words would be a SortedCollection, and there could be > pre-prepared sortBlocks for them, e.g. frPhoneBookOrder, deOrder, > seOrder, ukOrder, etc > > along the lines of > aListOfWords := SortedCollection sortBlock: deOrder > > If a word is either a Utf8SortableString, or a well-formed Utf8String, > then we can perform equivalence testing on them trivially. > > To make sure a Utf8String is well formed, we would need to have a way > of cleaning up any convenience codepoints which were valid, but which > were for a character which has multiple equally-valid alternative > convenience codepoints, and for which the string currently had the > "wrong" convenience codepoint. (i.e for any character with valid > alternative convenience codepoints, we would choose one to be in the > well-formed Utf8String, and we would need a method for cleaning the > alternative convenience codepoints out of the string, and replacing > them with the chosen approved convenience codepoint. > > aUtf8String cleanUtf8String > > With WideString, a lot of the issues disappear - except > round-tripping(although I'm sure I have seen something recently about > 4-byte strings that also have an additional bit. Which would make > some Unicode characters 5-bytes long.) > > > (I'm starting to zone out now - if I've overlooked anything - obvious, > subtle, or somewhere in between, please let me know) > > Cheers, > Euan >

Dec. 4, 2015

Re: [Pharo-dev] Java Future

by stepharo

> We do need more ease of integration with other software. > I agree Normally we should have spur by next wednesday > > * 64 bit > > * OS Process made easier. > Mariano did you started to work on that? > * FFI not requiring a PhD > Yes. > * Being able to use Pharo with normal text based tools (like mount an > image like a filesystem). > * Full integration with trendy tools. e.g. MongoTalk missing GridFS, > sharding, HA. > > These things are moving forward. > > I am pissed that Julia got $600 000 and we are struggling due to cash > issues. > Well I do not know how to do that. > We do not miss brainpower. We miss being able to focus on progress > because we can't fund it well enough. > > Phil > > > > On Nov 30, 2015 12:21 PM, "Tudor Girba" <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > > > Hi, > > > > Increasing the community is certainly important, and we welcome any > action that anyone would want to undertake in this direction. > > > > However, talking about the future of Java does not fall in this > category. > > > > Cheers, > > Doru > > > > > > > On Nov 30, 2015, at 4:44 AM, EuanM <euanmee(a)gmail.com > <mailto:euanmee@gmail.com>> wrote: > > > > > > We also need to concentrate on building our community. > > > > > > We build a better platform faster if we have more people. > > > > > > We build a more valuable platform if we have a wider range of valuable > > > use cases to target. > > > > > > Unless and until we hit a critical mass of people joining our > > > community, we *need* to spend some of our focus on community-building. > > > > > > Part of great is being able to build things to sufficient completeness > > > *and* keep them in working order over the long haul. This is easier > > > with more contributors. > > > > > > On 27 November 2015 at 21:27, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > >> Hello everyone, > > >> > > >> Please stop this thread on this mailing list. We need to focus on > building a great platform. > > >> > > >> Cheers, > > >> Doru > > >> > > >> > > >>> On Nov 27, 2015, at 10:05 PM, EuanM <euanmee(a)gmail.com > <mailto:euanmee@gmail.com>> wrote: > > >>> > > >>> First of all - is this true? Where can we read about it? > > >>> > > >>> I cannot find anything about this at > > >>> https://www.oracle.com/search/press > > >>> > > >>> ======================================= > > >>> > > >>> If Oracle did make this statement, then what people have said so far > > >>> is true. BUT... > > >>> > > >>> Java got about 40% of its initial momentum from IBM dumping > VisualAge > > >>> and putting all their resources into Java. > > >>> > > >>> Oracle are targetting this move at IBM more than anyone else. > > >>> > > >>> IBM will start to think about how to migrate from Java - as > Oracle are > > >>> telling them they will have to. (It's OUR bat and its OUR ball, and > > >>> no-one else can play with it. Not even the Java Community). And > > >>> IBM's coders do not pay for Java, Eclipse users do not pay for > Java. I > > >>> expect the licence-fee income for JREs is small. > > >>> > > >>> Oracle are doing one of two things - announcing that Java is for > sale > > >>> to device providers - phones (Google is the obvious buyer) or the > > >>> impending Internet of Things (which was what Java was designed for > > >>> originally) or announcing that no-one making an internet of things > > >>> offering should consider Java. > > >>> > > >>> Yes, things live on and on in a kind of zombie state. So yes, > things > > >>> live on as long as their ecosystem does. And they gently wither and > > >>> their ecosystem withers is a long slow drawn out spiral. Which > is why > > >>> we still have Cobol. > > >>> > > >>> People and organisations tend to move from one technology to another > > >>> in an incremental fashion. Swapping a little bit here, and a little > > >>> bit there. > > >>> > > >>> The new target platforms are ones which > > >>> 1) look like they have longevity, and > > >>> 2) have a migration pathway that provides incremental steps. > > >>> > > >>> Offering a compelling advantage is good - but only if the steps 1) > > >>> and 2) are catered to. > > >>> > > >>> IBM VisualAge Smalltalk is still robust, commercially available > > >>> software, and VisualStudio and Gemstone continue to represent > > >>> Smalltalk out to the big world of corporate development. > > >>> > > >>> So that's a start. > > >>> > > >>> Say only 5% of the Java world moves away from Java each year, as a > > >>> result of this announcement. > > >>> > > >>> We *should* wish to take advantage of this announcement. > > >>> > > >>> After all, think what difference having even 0.01% of the > world's Java > > >>> coders moving to Smalltalk would make. How could we help that > > >>> happen? > > >>> > > >>> Think what it would be like to have thought-leaders like Kent > Beck and > > >>> Ward Cunningham back in the Smalltalk fold. How could we help that > > >>> happen? > > >>> > > >>> Think what it would be like to get back all the universities who > moved > > >>> from teaching OO concepts using Smalltalk into teaching them via > Java. > > >>> We now know almost all the ones using Smalltalk as a teaching > language > > >>> by name. Does anyone know even how many universities teach OO via > > >>> Java? What would it be like if 5% of those universities moved to > > >>> Smalltalk each year. How could we help that happen? > > >>> > > >>> Next - do we have any big brained thinkers who can see specific ways > > >>> we can improve interoperation between Java facilities and libraries > > >>> and the Smalltalks? For the next 12 months, we should work on Java > > >>> integration, rather than C++ integration. We should identify the > > >>> three best things for us to do in this regard, and make them > polished > > >>> and compelling. Who is in a position to help that happen? > > >>> > > >>> The final way we can take advantage help the maximum number of > people > > >>> find their way to us is to present a united community front to the > > >>> outside world. In the same way I am both a European and a Scot, we > > >>> need to be Smalltalkers *and*members of our individual > > >>> Smalltalk-platform communities. > > >>> > > >>> How can we help make that happen? > > >>> > > >>> This is not a silver bullet. It's going to cause a long-term > trend in > > >>> events, not a sudden abrupt change. But it will have a real, if > > >>> gradual effect. (assuming that > > >>> > > >>> Equally, it is not something we should ignore. It is something we > > >>> should make use of. We need to put effort into raising our profile > > >>> over the next 6 months. > > >>> > > >>> On 25 November 2015 at 19:51, Casimiro - GMAIL > > >>> <casimiro.barreto(a)gmail.com <mailto:casimiro.barreto@gmail.com>> > wrote: > > >>>> Em 25-11-2015 17:21, Nicolas Anquetil escreveu: > > >>>> > > >>>> > > >>>> > > >>>> On 25/11/2015 19:55, Jimmie Houchin wrote: > > >>>> > > >>>> Much truth in what you say. However, what Oracle choose to > invest its money, > > >>>> time, personnel resource into Java does affect its present and > future. It > > >>>> has a great affect. But it isn't the whole story. Java has > enough momentum > > >>>> in what already exists in the language and vm and what has been > release > > >>>> under its license, for businesses to keep going for some time > with only what > > >>>> currently exists. > > >>>> > > >>>> Cobol is still alive (and well) after > 50 years. > > >>>> You can expect Java programmers to find jobs for many years yet > to come > > >>>> :-) > > >>>> > > >>>> nicolas > > >>>> > > >>>> -- > > >>>> Nicolas Anquetil > > >>>> RMod team -- Inria Lille > > >>>> > > >>>> 1st: Java is extremely profitable. Each android phone, each > android TV, each > > >>>> android embedded system pays copyrights to Oracle. > > >>>> 2nd: Much of current cloud infrastructure depends on java. > > >>>> 3rd: Java is already obsolete, like Frotran, Cobol, C, C++. It > will continue > > >>>> to be used by same reasons these languages are used. > > >>>> > > >>>> IMHO, discussing java is not profitable. Better to discuss > things to be than > > >>>> talk about things that already happened. > > >>>> > > >>>> casimiro > > >>>> > > >>>> -- > > >>>> The information contained in this message is confidential and > intended to > > >>>> the recipients specified in the headers. If you received this > message by > > >>>> error, notify the sender immediately. The unauthorized use, > disclosure, copy > > >>>> or alteration of this message are strictly forbidden and > subjected to civil > > >>>> and criminal sanctions. > > >>>> > > >>>> == > > >>>> > > >>>> This email may be signed using PGP key ID: 0x4134A417 > > >>> > > >> > > >> -- > > >> www.tudorgirba.com <http://www.tudorgirba.com> > > >> > > >> "Reasonable is what we are accustomed with." > > >> > > >> > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Presenting is storytelling." > > > > >

Dec. 4, 2015

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

by Mariano Martinez Peck

On Fri, Dec 4, 2015 at 12:05 PM, Max Leske <maxleske(a)gmail.com> wrote: > > On 04 Dec 2015, at 14:29, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which > are completely different. WADynamicVariable uses exception mechanism > while DynamicVariable uses the ProcessSpecificVariable. > But thanks anyway! > > > Oh manâ¦. Sorry :) > > I wonder, why WADynamicVariable *isnât* a DynamicVariable. The semantics > are the same if Iâm not mistaken (e.g. only available in the current > process) and I think access to a dynamic variable may even be faster > because it *doesnât* use the exception mechanism (i.e. no need to walk down > the stack). > If someone knows the answer, Iâd be happy to hear it. > > I bet it's because of portability. For example, i remember in GemStone the ProcessorLocalVariable did not behave the same as in Pharo. And it was actually an experiment. I think you cannot expect all this stuff to be ansi (or easily portable), while exceptions do. > Iâve played around with Process>>signalException: and > Context>>handleSignal: (which looked quite promising) but didnât get any > results. Iâm out of ideas. > > I have played all morning with an idea of using local variables. I arrive to the point where I DO HAVE the request context at hand, but I don't find an easy way to hook into do-its, print-it etc so that the closure evaluated gets the request context plugged. In other ways... let's say I have the context stored somewhere. I am at the SmalltalkEditor >> evaluateSelectionAndDo: aBlock and so..somewhere I need to do something like: WACurrentRequestContext use: self storedContextSomewhere during: [ self theSelectionToBeEvaluated ] and that's where I am now :) > Cheers, > Max > > > On Fri, Dec 4, 2015 at 7:32 AM, Max Leske <maxleske(a)gmail.com> wrote: > >> Hereâs a snippet to play with: >> >> p := Processor activeProcess. >> x := 2. >> v := TestDynamicVariable value: x during: [ >> ((p instVarNamed: 'env') ifNotNil: [ :env| >> env copyWithout: nil ]) inspect >> ]. >> >> ((p instVarNamed: 'env') ifNotNil: [ :env| >> env copyWithout: nil ]) inspect >> >> Cheers, >> Max >> >> On 04 Dec 2015, at 10:47, Max Leske <maxleske(a)gmail.com> wrote: >> >> I feel you :) >> >> Without having thought this through completely: if you look at the >> implementation of DynamicVariable>>value:during: youâll see that the way it >> works is that the variable is bound to the active process. In the debugger >> you have access to the process that is being debugged and thus you should >> have access to the variables bound to it. You could try accessing all such >> variables by iterating over them (which I think will require an extension >> on Process because youâd need to access at least the PSKeys class variable). >> >> Cheers, >> Max >> >> On 04 Dec 2015, at 00:34, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> Hi guys, >> >> This thing I will ask in this email it's in my mind since YEARS. But I >> have always thought it was like that and that there was nothing we could >> do. However, I think it's time I ask again :) >> >> For those that have used Seaside, and you try to debug, you know that >> upon request processing seaside uses Exceptions mechanisim to always have >> access to the request, session, etc. They way that is done is very smart :) >> >> WACurrentRequestContext use: self during: aBlock >> >> In that case, "self" is the request instance and aBlock the closure that >> takes care of the request processing. So, inside that closure, everywhere >> you do "WACurrentRequestContext value" you get the correct request instance. >> >> So..that's great for Seaside, but debugging gets complicated. While you >> can restart, proceed, etc, once inside debugger, you cannot evaluate any >> piece of code that will use the session or request because you get >> a WARequestContextNotFound. Of course, because I guess the evaluation you >> do from cmd+d on a piece of text or via the debugger inspector, creates >> another closure/context which does not receive the WACurrentRequestContext >> instance. >> >> Now....besides WACurrentRequestContext I have my own class >> UserContextInformation where I basically have a bunch of stuff associated >> to the logged user. And I do exactly the same as the >> WACurrentRequestContext. And I have the same problem. I really want to be >> able to fix this. >> >> Anyone have an idea on how can I do it? I guess I can change the >> debugger, in the place where I evaluate code so that I wrap that evaluation >> with my request context instance??? >> >> Thoughts? >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

Dec. 4, 2015

Re: [Pharo-dev] GTDebugger not draggable with latest VM

by Andrei Chis

Seems to happen due to the fix in issue 17178 <https://pharo.fogbugz.com/f/cases/17178> On Fri, Dec 4, 2015 at 4:21 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Seems that starting with Pharo 50483 one cannot drag the > inspector/playground/debugger. > > No idea what happened. > > On Fri, Dec 4, 2015 at 3:19 PM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > >> Hi, >> >> >> >> I have a problem on the latest Moose6.0 image. >> >> I was not able to open a Roassal view, I had a NativeBoost Generic >> failureâ¦ >> >> So I updated the VM to last stable, and, now, the GTdebugger and the >> Moose panel are not draggable anymoreâ¦ >> >> Can somebody is able to reproduce the problem? >> >> >> >> Thanks >> >> >> >> Cheers, >> >> Vincent >> >> ------------------------------ >> >> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage >> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret >> professionnel. Si vous recevez ce message par erreur, merci d'en avertir >> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de tout >> virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >> responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un >> virus transmis. >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As >> its integrity cannot be secured on the Internet, the Worldline liability >> cannot be triggered for the message content. Although the sender endeavours >> to maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. >> > >

Dec. 4, 2015

Call for Papers: Constrained and Reactive Objects Workshop at Modularity 2016

by timfelgentreff

CROW 2016 - Constrained and Reactive Objects Workshop The Constrained and Reactive Objects Workshop (CROW) invites papers that present research results related to using constraints and reactive programming in combination or integrated with imperative and object-oriented systems. This research area has recently received increasing interest again. Object-constraint, constraint-reactive, constraint-imperative systems and others were proposed in response to challenges posed by, for example, the requirements for applications to work across different devices and form-factors, to provide best-effort computing in the face of unreliable devices and networks, and to more fully utilise HPC technology. However, many questions remain. For example, the interactions among constraints, reactive or event-based programming, and mainstream imperative and object-oriented languages are still not well-understood, and different implementation techniques to combine these paradigms are still being explored. The lack of large applications written with combinations of these paradigms means that there is little experience with patterns and tools for such applications, and modularity mechanisms required for such large applications are in their infancy or completely absent. This workshop is intended to gather researchers working on using constraints or reactive programming in combination with mainstream imperative and object-oriented languages. The goal of this workshop is to present technical research results related to such systems, discuss applications, tools, and patterns used in these systems, and to define better the directions into which this field may evolve by providing overviews of existing work. Call for Papers Even though constraint-based and reactive programming are not new concepts, their combination and interaction with more mainstream imperative and object-oriented languages are receiving more and more attention. This workshop is an attempt to gather researchers working on models, languages, and implementations relating these paradigms. We welcome all submissions on language design, implementation, runtime systems, program analysis, software metrics, patterns, modularity principles, case-studies and benchmarks of systems that combine constraint-based or reactive programming with imperative paradigms. Of particular interest are topics from the following areas: â¢Study of the interactions of constraints and reactive programming with imperative language features such as object-oriented programming, mutable state, encapsulation, modules, or concurrency â¢Applications and case-studies that showcase examples in which the combination of constraints and reactive programming facilitates systems development â¢Empirical studies that motivate further research in the field â¢Patterns, modularity mechanisms, and best-practices for larger applications â¢IDEs and Tools â¢Language runtimes, virtual machine support, or compilers â¢Related fields that constraints and reactive programming can help facilitate, such as self-healing systems, best-effort computing, acceptability-oriented computing, or end-user programming Authors are invited to submit short position papers or long technical papers. using the ACM sigplanconf style at 9pt font size (see http://www.acm.org/publications/article-templates/proceedings-template.html) Short papers are imited to a maximum of 4 pages, excluding references. Long papers are limited to a maximum of 10 pages, including references. Submissions should not have been previously published nor be under review at other events. All submitted papers will be peer reviewed. Accepted papers will be published in the ACM Digital Library (unless the authors wish otherwise). Papers should be submitted via EasyChair: https://easychair.org/conferences/?conf=crow16. Workshop Format The format of the workshop will be that of a mini-conference. Participants can present their work in slots of 30 minutes including Q&A. Because it is often hard to understand the semantics of novel combinations of multiple paradigms as in this workshop just by looking at the code, we also encourage authors to present live demos. The goal of the workshop is to come to a better understanding of the the field. We hope to use the late afternoon session to draw conclusions from the presented work, and to identify fundamental paradigmatic problems that still need to be resolved to reconcile these different technologies and paradigms. Important Dates â¢Submission deadline: January 15, 2016 â¢Notification: February 6, 2016 â¢Camera ready: February 13, 2016 â¢Workshop: March 14-15, 2016 -- View this message in context: http://forum.world.st/Call-for-Papers-Constrained-and-Reactive-Objects-Work… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 4, 2015

Re: [Pharo-dev] GTDebugger not draggable with latest VM

by Andrei Chis

Seems that starting with Pharo 50483 one cannot drag the inspector/playground/debugger. No idea what happened. On Fri, Dec 4, 2015 at 3:19 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Hi, > > > > I have a problem on the latest Moose6.0 image. > > I was not able to open a Roassal view, I had a NativeBoost Generic > failureâ¦ > > So I updated the VM to last stable, and, now, the GTdebugger and the Moose > panel are not draggable anymoreâ¦ > > Can somebody is able to reproduce the problem? > > > > Thanks > > > > Cheers, > > Vincent > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Dec. 4, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] d12673: 50483

by Pavel Krivanek

Thank you. -- Pavel 2015-12-04 13:37 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > I copied the package to the Glamour repo. > But I have no idea why the integrator decided to create that package. > > Cheers, > Andrei > > On Fri, Dec 4, 2015 at 12:20 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> ConfigurationOfIDE job fails because of this error: >> Could not resolve: Glamour-Morphic-Brick-Tests >> [Glamour-Morphic-Brick-Tests-TheIntegrator.14] in >> /builds/workspace/Pharo-5.0-Update-Step-1-Tracker/package-cache >> http://smalltalkhub.com/mc/Moose/Glamour/main/ >> >> Can someone with write permissions push this package version to the >> Glamour repository? >> >> Cheers, >> -- Pavel >> >> 2015-12-04 11:16 GMT+01:00 GitHub <noreply(a)github.com>: >> >>> Branch: refs/heads/5.0 >>> Home: https://github.com/pharo-project/pharo-core >>> Commit: d1267341a42b97e366de51b22cf83e5cb2f1f22a >>> >>> https://github.com/pharo-project/pharo-core/commit/d1267341a42b97e366de51b2… >>> Author: Jenkins Build Server <board(a)pharo-project.org> >>> Date: 2015-12-04 (Fri, 04 Dec 2015) >>> >>> Changed paths: >>> M FontChooser.package/FontChooserMorph.class/instance/interface >>> building/newFontPointSizeField.st >>> M >>> Morphic-Core.package/Morph.class/instance/events-processing/handleMouseMove_.st >>> A >>> Morphic-Core.package/Morph.class/instance/events-processing/handlesMouseMove_.st >>> R Morphic-Widgets-NewList.package/NewListExample.class/README.md >>> R Morphic-Widgets-NewList.package/NewListExample.class/definition.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/accessing/listMorph.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/accessing/listMorph_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialization/ >>> initialize.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/buildMorph.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/buildMorphWithOld.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/buildTextMorph.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/openInWindow.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/openInWorld.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/withNewList.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/initialize/withOldList.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/allowToSelect.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/displayItem_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/drop_at_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/getIndex.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/getItems.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/headerTitle.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/iconFor_at_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/iconMaxSize.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/menu_shifted_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/setIndex_.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/morphic/ >>> title.st >>> R >>> Morphic-Widgets-NewList.package/NewListExample.class/instance/protocol/toggleTitle.st >>> M >>> NECompletion.package/NECContext.class/instance/accessing/createModel.st >>> A >>> NECompletion.package/NECContext.class/instance/private-type-guessing/completionTokenIsComment.st >>> A >>> NECompletion.package/NECContext.class/instance/private-type-guessing/completionTokenIsLiteralOrComment.st >>> M >>> NECompletion.package/NECContext.class/instance/private/createRanges.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/ >>> script50482.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/ >>> script50483.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/ >>> update50482.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/ >>> update50483.st >>> M >>> ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>> M Slot.package/extension/Behavior/instance/classLayout.st >>> M Slot.package/extension/Behavior/instance/layout.st >>> M Slot.package/extension/Behavior/instance/layout_.st >>> M >>> SmartSuggestions-Tests.package/SugsMockContext.class/instance/api-context/sourceTextArea.st >>> >>> Log Message: >>> ----------- >>> 50483 >>> 17167 disable NEC completion in method comments >>> https://pharo.fogbugz.com/f/cases/17167 >>> >>> 17181 Rename layout to classLayout (step 3.5 replace implementation in >>> Behavior) >>> https://pharo.fogbugz.com/f/cases/17181 >>> >>> 16724 new removal of RubPluggableTextMorph >>> https://pharo.fogbugz.com/f/cases/16724 >>> >>> 17178 Move checking logic of #handleMouseMove: into #handlesMouseMove: >>> https://pharo.fogbugz.com/f/cases/17178 >>> >>> http://files.pharo.org/image/50/50483.zip >>> >>> >>> >> >

Dec. 4, 2015