Setools June 2007

setools@lists.squeakfoundation.org

6 participants
7 discussions

MagmaServerRequests
by Keith Hodges 18 Jun '07

18 Jun '07

Dear All, I have uploaded an add-on package to http://www.squeaksource.com/MagmaTester called 'Magma server requests'. This is as mentioned in a previous email to this list but it is now packaged in a generic form independent of Gjallar. to install with Installer use: Installer mc http: 'http://www.squeaksource.com'; project: 'MagmaTester'; install: 'Magma server requests'. After installing the package into a working Magma installation, you will need to do a MagmaSession cleanUp to get it adopted by the MagmaRepositoryController's I have made it fairly generic since it passes arbitrary messages, and returns any values, trapping server-side errors, it transports them back over the wire in order to signal them in the client. Actions are atomic since, and I quote from the "Magma client server" read-me text. "The answer block is only ever evaluated for one client request at a time." So to use this all you have to do is implement the Client side and the server side in MyOwnServerRequestResponder e.g. Client side: MyClass-counterValue ^ (self magmaSession serverRequest counterValue) submit e.g Server side MagmaRequestResponder subclass: MyOwnRequestResponder -- MyOwnRequestResponder-#counterValue ^ Count := Count + 1 -- RequestResponder-class-#requestsSupported ^ #( #counterValue ) -- You can send a batch of requests like so... (self magmaSession serverRequest counterIncrement; counterIncrement; counterIncrement; counterValue) submit -- Then there is a handy server backdoor! Normally each request in a batch of requests is sent to the responder which can handle each request. However if we enable requests to be chained, such that the next request is sent to the result of the previous request we can gain full remote control of the server. This is enabled by MagmaServerBackdoorResponder which in itself only serves one request: #login:password: e.g. ((self magmaSession serverRequest login: 'admin' password: 'magma rocks') repositoryController isReadOnly) submit To do: The login could be tied in to magma's exisitng users management. Some responders need simple persistence for their use which I do not know how to do enjoy Keith

2 4

MagmaReadStrategies
by Keith Hodges 17 Jun '07

17 Jun '07

Dear Chris, I was using read strategies and found a bug in the depths generation process, here is a test which shows the problem. Problem A: Subclass defines depths on instVars, superclass defines a depth for all instVars - raises an error .. not indexable. This test case demonstrates the problem: (MagmaSession new) readStrategy: (MaReadStrategy new onAny: Collection readToDepth: 2; forVariableNamed: 'tally' onAny: Dictionary readToDepth: 3; yourself). Problem B: Looking at the code, if a class defines a depth for all instVars, no attempt is made to see if the superclasses have defined a greater depth. The code has an (a max: b) statement as if to intend this behaviour but in reality it looks to me like it is actually (a max: a). (MagmaSession new) readStrategy: (MaReadStrategy new onAny: Collection readToDepth: 3; onAny: Dictionary readToDepth: 2; yourself). Also Problem C: The ObjectExplorer behaviour is not completely in sync with Magma's behaviour. Ideally you want Magma to realize objects when you select them in explorer, not unexplicably due to explorers inner workings. And finally very useful Logging "D" ------ Solutions: In package 'magma seaside' I have included the fixes for A and B, in WAMagmaReadStrategyDefault. I have also added a couple of methods to MagmaMutatingProxy, and a MagmaProxyStandIn class to improve the way that ObjectExplorer behaves. Now you can really explore how magma thinks when it is using read strategies. Logging: The class WAMagmaReadStrategyWithQ2Logging, logs realizations verbosely to the Q2Log, a logging facility available in Gjallar. This is very useful. My fixes for A and B, have a couple of enhancements to the basic scheme. Negative depths are valid and subtracted from the inherited value. This can be useful so as to specify pulling a whole datastructure except this instVar or class type. ---- cheers Keith

3 6

Clock Faking Test Resource
by Keith Hodges 16 Jun '07

16 Jun '07

Dear Ralph, you asked about a clock faking test resource. A while ago I developed a ClassClonerTestResource, this allows you to take a current class which is normally a singleton that is in use, e.g. DateAndTime, and to clone it especially for testing purposes so as to be able to test the clone separately. This would allow me to set my clock under test to some crucial rollover points and test its behaviour. I developed this especially to test bug fix 474 on mantis. [ Edgar/Ralph - here is a fix with tests for you!] However what this doesn't do is replace DateAndTime, so if you want to run code which calls "DateAndTime now" and have it do something clever like run last week, or run backwards it will not work. However you raise an interesting problem which I think it may be worth solving for everyone, and I think that as a result of my recent discovery of the amazing ProcessLocalVariables I may have an answer. At present ProcessLocalVariables only support value and #value: As it happens I added a #doesNotUnderstand: handler as an experiment in allowing gjallar Sessions to spoof as MagmaSessions for Magma. At the time I thought that this would have some interesting possibilities. For us it means that a ProcessLocalVariable can spoof a class for us within a defined scope (process or block). ProcessSpecificVariable-doesNotUnderstand: aMessage ^ aMessage sendTo: self value So I made a DateAndTimeWarp a subclass of DynamicVariable (a variant of the ProcessLocalVariable which has block scope as well as process scope) and set the default to return DateAndTime. We now have a psuedo DateAndTime "class" which is pluggable on a per process basis. If we swap DateAndTime in the system dictionary for DateAndTimeWarp, it works! (i.e. nothing breaks!!!) DateAndTimeWarp-installImposter (DateAndTime respondsTo: #installImposter) ifTrue: [ self error: 'DateAndTime is already spoofed' ]. DateAndTimeReal := Smalltalk at: #DateAndTime. Smalltalk at: #DateAndTime put: self. Now we can substitute our clone with some modifications. The fixed DateAndTime implementation available on mantis via "Installer mantis fixBug: 474." (tested in 3.8 and Gjallar0,4) has already been refactored to refer to its ClassVar "ClockProvider" for all clock references. (default setting is class Time) So all we need to do is replace ClockProvider, we will replace it with an instance of DateAndTimeWarp, DateAndTimeWarp-class-warpedClockBeginAt: t speed: s | newClock newSystemClockProvider | newSystemClockProvider := self new setStart: t speed: s. newClock := ClassClonerTestResource cloneOf: DateAndTimeReal. newClock classPool at: #ClockProvider put: newSystemClockProvider. clock initializeOffsets. ^ newClock We instantiate our new clock provider with a start time, (nil for now), and a speed. The new clock provider saves some offsets, and re-implements #totalSeconds, #millisecondClockValue and #secondsWhenClockTicks (this method waits until the clock ticks and is used for syncing the seconds and milliseconds clocks together. The new clock is substituted for the default clock with the following code: DateAndTimeWarp-class-beginAt: start warpSpeed: s during: aBlock ^ self value: (self warpedClockBeginAt: start speed: s) during: aBlock To Test: DateAndTime beginAt: DateAndTime yesterday warpSpeed: 3 during: [ 10 timesRepeat: [ Transcript cr; show: DateAndTime now. (Delay forSeconds: 1) wait. ] ]. I thought that was pretty impressive stuff. I am well impressed with these process local variables! Also speed wise: au natural, DateAndTime nowBenchmark. '6.84 µs' (I did improve DateAndTime now by a factor of 50-80 in fix 474) The equivalent benchmark spoofed using process local variable DynamicVariable, benchmark gives: 29.09 µs, i.e. not slow. This code is available in Gjallar monticello repository 'http://mc.gjallar.se' in the ProcessSpecific package. enjoy Keith

1 0

Re: [Setools] Gjallar report
by goran＠krampe.se 13 Jun '07

13 Jun '07

Hi Raymond! Raymond Asselin <raymondasselin(a)sympatico.ca> wrote: > >o. :) > Hi GÃ¶ran, Iâm following the work on Gjallar from the beginning. > It is very interesting continue the good work as all your team. > > I would like to help but Iâm shy because Iâm not an expert and > because I donât want to slow you down taking the time to inform > me..... We should always be able to find tasks to work on! Drop by on IRC and we can chat a bit. > But....I would like to help..even for tiny work...I donât know if > Gjallar run on Mac platform, I would say I donât know what doesnât > work on Mac platform, nore if this is something I can do...where > can I found some information on that. If this implies FFI or > Pluggins..sorry this is too heavy for me. Anything else...? If I am not mistaken Gjallar does run on the Mac - Keith Hodges has details. We haven't packaged it yet so to speak, but I think it works. > Raymond regards, Göran

1 0

Gjallar report
by Göran Krampe 13 Jun '07

13 Jun '07

Hi all! Work is steaming ahead on Gjallar and the team works quite well I think! We are having fun and producing code, IRC has turned into our primary channel for communication (#gjallar on irc.freenode.net - try ircatwork.com just to pop in and say hi). Generally I can say that all work being done right now is "good" even if it is a difficult balance keeping our eyes on the ball and focusing on immediate needs compared to refactorings/design improvements/framework improvements. :) The transaction level work made by Balazs and Levente has now been merged into the gk-line, I haven't had time to look closely but my impression is that we have a much better and *tested* mechanism in place for replaying transactions reliably - which of course is the basis for our offline mechanisms. Ralph is working on "builtin statistics" and he has gotten PlotKit into the platform and has gotten some nice graphs up on the screen. Next step is to create a view presenting the statistics we estimate to be the most important - we have a draft on that and it will be interesting to see how it all plays out. Igor has been finishing his plugin work, especially the so called "spawn-and-link"-plugin which is an important new mechanism which allows users - given that a Process admin has configured it - to create a new case in a different Process, copy over selected forms and create a link with a particular type from the source case to the new case - all in a single button click! This is the first example IMHO where the advanced model and framework of Gjallar is showing its potential for tailor made functions. Now Igor is moving onto some "small fish" but which are important for the users - like for example configurable "color coding" in case tables. The next dish on the table is performance, performance, performance. Keith is moving forward with the Process editing views and is also involved in general reworkings of the Gjallar framework aimed to enable running Gjallar in a multi-image setup. I myself has unfortunately not been able to put my hours into filters as I intended, instead I have to a large extent been caught in "team support" and bug fixing of stuff that has popped up as results of all our other efforts. I hope to refocus on filters ASAP but will most definitely also be involved in all the previously mentioned efforts too. :) Sadly this paid "boost" will end soon, but hopefully some of the developers might find it worthwhile to continue development on low intensity. Personally I am committed to Gjallar, and Toolkit Software is also committed and I think we will soon begin to see Gjallar reaching a state where it gets really interesting. :) And... finally - anyone who wants to join us in development - just say "hello!" and we will try to guide you the best we can. :) regards, Göran PS. Gjallar is also a great open source "sample app" for an advanced Squeak/Magma/Seaside application. If you are about to build a web app using Squeak there are several pieces of the puzzle to be found in Gjallar.

1 0

Introduction
by Adrien Sebbane 10 Jun '07

10 Jun '07

Hello everybody, I just joined the squeak mailing list and created an account on Squeak Map although I know Squeak for almost two years. For various reasons I could not spend much time to try and write a lot of lines of Smalltalk, but know I have more time for myself, so I would like to get involved in the Squeak development process. I'm an IT engineer, I have skills in other programming languages as Java, C++, Perl, Python, Ruby and also in Smalltalk although I am far from beeing an expert with that last one. I read the "Community" part of Squeak web site, but I do not really know where to start. So if you agree to accept my contribution, maybe someone could tell me what's next. Best regards Greetings Adrien Sebbane ps: I'm french so excuse me if I look awkward in my expressions ! :)

5 4

Gjallar statistics (and national holiday)
by goran＠krampe.se 06 Jun '07

06 Jun '07

Hi all! Two things: 1. Its national holiday today, so I will not be around today. ;) 2. Ralph is working on statistics in Gjallar and *anyone* with some firm ideas on the major important 4-6 "numbers" to present in an issue tracker (as changing over time) - please post to this list. regards, Göran

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Setools June 2007