Setools August 2006

setools@lists.squeakfoundation.org

9 participants
14 discussions

Gjallar status report
by goran＠krampe.se 29 Aug '06

29 Aug '06

Hi folks! Its hectic here, we are working hard on getting 0.2 into shape and I wanted to tell a bit about what we are doing. My plan is to get a new 0.2 release out around friday, or if we miss that - monday at the latest. Gjallar is currently running in "parallell test deployment" for a few users with a very simple Process. But there are more groups itching to get started. The current verdict is that it seems quite stable, is a bit sluggish when you login (creating Seaside components and caching objects into the session etc) but gets snappier when you have clicked around a bit. There are a few known smaller issues but apart from that it looks pretty good. The Win32 VM blows up on us now and then - but typically when debugging low level somewhere - not easy to isolate why. Magnus added a nice javascript datepicker. The Scheduler has been enhanced, especially the various services it is running. The LDAP mirroring of user accounts works great. The email popping and sending works good including attachment detection etc. One of the more important low level bits I have been working on is to ensure that the Q2Txn pattern works as it is meant to do. The initialize/bootstrap of Gjallar has now been fully txnized so that we can actually spool out all txns on a single file, initialize Gjallar - and then read them back and reapply them. This now works and is important for two reasons: 1. The offline operation depends on it of course. And we want to get that working ASAP. 2. The Txn hierarchy is much less prone to changes which means that this offers a great easy way to migrate an older db to a new version. Just write out all txns, reinitialize with new code, read them back in. One thing I will be looking at soon is to migrate 13000 old cases into Gjallar. This will of course show us a bunch of places where we need to take greater care with Magma collections and indexing etc. We are aware of several "cheats" in the code that will not scale that good. And I am also going to fix some glaring UI issues. :) regards, Göran

1 0

Re: [Gjallar] user creation from root login
by goran＠krampe.se 21 Aug '06

21 Aug '06

Hi! (moving this to setools list, remove squeak-dev in any responses - the Gjallar discussion is better held in setools.) florent trolat <trolat.florent(a)laposte.net> wrote: > On Gjallar : > > I try to do > > self newUser: 'toto'. > > with an admin consol and I obtain > > MessageNotUnderstood: ByteString>>canRead:' Mmmm, obviously a String receives #canRead: instead of a Q2User. > I've tried to debug it but I have to understand your event mechanism and > its seems to be hard for me at the moment... > > I want to add a simple user to my gjallar application.... > > May be I've not understand something? No, the above is correct. > thanks for your help! First of all - we should add an option to "debug" console errors on the Squeak side instead of just returning the error as a String. Evidently this is permission related and I think it is triggered by someone having a Subscription on the "User added" event and somewhere down there something goes awry. The Subscription code is being hacked on by us right now - a range of issues. I will see if I can track it down. It would be great if you could supply more info - like where it is being called. You can put a "self halt" into the #newUser: method and then step through it on the server side. regards, Göran PS. We are doing a testdeployment this week. At the end of the week we could gather all fixes together and push out a new release. But this will mainly be a bug fix release.

1 0

Do we have a report for gjallar
by Stéphane Ducasse 17 Aug '06

17 Aug '06

hi goran - where do we report potential bugs or problems? - florent could not pinpoint to me why Gjallar is only working on PC? Stef

2 2

bug tracking system for Squeak
by florent trolat 15 Aug '06

15 Aug '06

I'm working on a new bug tracking system for Squeak. (SummerTalk 2006 mentor S Ducasse :-) ) a first step for this project is certainly to open a brainstorming 1/ about the features you need with a bug tracking sytem. 2/ Bugzilla give me a start point to make a stupid first workflow graph of our new bug tracking system : http://membres.lycos.fr/artemice/ what's your opinions? 3/ we need to defined a hierarchy for all the users of this sytem : admin, MasterProgrammer, Begginer.... Some Ideas?

3 5

[ANN] Gjallar release "Eldrimner" 0.1
by goran＠krampe.se 12 Aug '06

12 Aug '06

Hi folks! We are pleased to announce the first public availability of Gjallar (see http://swiki.krampe.se/gjallar) as release "Eldrimner", modestly numbered 0.1, typically for daredevil developers only. The license for Gjallar is the new BSD license. Note that this is merely a decent checkpoint during development, Gjallar is not yet ready for anything else than experimental use and of course - development. But it does *work* by some definition and we are about to start small test deployments at our customer. But we haven't fully tested it, there are glaring things missing and probably also things missing that we do not know about. :) We are trying hard to make Gjallar easily accessible for development. One thing is that we have prepared a development image ready for download. We are also writing down different procedures and describing the design. We have not yet written a detailed tested tutorial/user guide, but it is coming. If Gjallar seems interesting and you wish to help, make addons or even base a product around the codebase - feel free to contact us to get on the team and join the mailinglist - we are currently using the setools list. For more info (including screenshots) check the homepage: http://swiki.krampe.se/gjallar regards, Göran & Magnus PS. If I messed something up when preparing the release, sorry. It was late. :) Feel free to email privately or post to the setools list. PPS. Yes, a public Gjallar server for handling Gjallar bugs and as a demo will be coming too.

3 6

A great logo for Gjallar
by goran＠krampe.se 11 Aug '06

11 Aug '06

Hi! Just wanted to mention that I got a great logo sent to me from Elfi Heck which I now have added to the Swiki: http://swiki.krampe.se/gjallar/logo In short - I love it and asked Elfi about some variations (with or without name) and if it is allright to mention him on that page. regards, Göran

2 1

Re: Gjallar : questions
by goran＠krampe.se 11 Aug '06

11 Aug '06

Hi Florent! florent trolat <trolat.florent(a)laposte.net> wrote: > Hi, > > Good job : http://swiki.krampe.se/gjallar, it's very usefull for me :-) I will try to get even more info up there. > 1/ > About architecture I've tried to understand this part on the > requirements document, but it's for me a difficult point ;-). > > "Sripting" seems to be very usefull but can you use it to move case for > example? Today there is no Scripting mechanism implemented but we had a meeting just today where a few things popped up that would be best dealt with using simple scripting, so I will probably add it soon. The idea is to be able to tie Smalltalk code easily into both forms and as "handlers" of events. One example is to fill in a calculated value in one field when editing another. Another example is more complex notification triggers, or more advanced integration needs. > 2/ > What's the main idea to make a distinction between Process and > ProcessPrototype ? An organization like Micronic (or any one) has a LOT of different issue processes - some of them are clearly visible and known, others are "hidden" in the way people work - like a group of people sending an Excel document around gathering information, or a group of people sharing an email account in order to have a common "inbox" for issues etc. So the system should easily support setting up new Processes that are "pre configured". The best way to do that is to be able to clone an existing Process which has been configured. So there is no class ProcessPrototype - a prototype of a Process is just a Process that is not kept in the list of "real" Processes and is only used by cloning it to get a new such Process. The same technique exists in the system for creating Cases (by cloning an existing prototype case) and Users (or at least that was the idea, not implemented yet IIRC). > thanks, > > Flo regards, Göran

1 0

Process / case / task : general requirements found in another nice tool
by Klaus D. Witzel 08 Aug '06

08 Aug '06

List, referring to Hans' quest for requirements and their transformation(s), the following paper is (perhaps) of interest "Rediscovering Workflow Models from Event-Based Data" - http://citeseer.ist.psu.edu/582807.html The paper is loaden with domain unspecific requirements and their transformation(s). Enjoy! /Klaus

1 0

Gjallar let's go
by trolat.florent 08 Aug '06

08 Aug '06

Hi, > Hi folks! > > I can gladly announce that we today decided the license for the Gjallar > code/project: > > "new" BSD > Good news.... "Gjallar Original Requirement and Design" is actually a great tool to understand Gjallar... but some points (ok 95%... ;-) ) are still wooly for me.... Can I ask you about functionalitys of your UI on seaside? 1/ I supposed your Ui allows a Gjallar admin to create process ( p 6 Requirements). This functionality is reachable by 'Global admin' => 'processes'? When I try to acces this item : nothing Something is not implemented or my configuration is wrong? :-( 2/With a Gjallar user you can manage processes by 'process admin' I suppose, but in my browser 'user' 'category' and 'forms' seems to do nothing... (Something is not implemented or my configuration is wrong?) About Design 3/"Case linking" : This mechanism is a manual decision (like moving a case in a new stage) or we can define some rules ? In your document you write "a case can !!!normally!!! not move between processes" Why "normally" ;-)? 4/ Where (class...) can I find informations about the Meta Level? Thanks :-) , Florent Cet été, pensez aux cartes postales de laposte.net !

3 5

Gjallar license decided
by goran＠krampe.se 07 Aug '06

07 Aug '06

Hi folks! I can gladly announce that we today decided the license for the Gjallar code/project: "new" BSD See http://www.opensource.org/licenses/bsd-license.php Since this was the last hurdle for distributing the source (except from going through it and "clean it" a bit from customer specific data) we expect to be able to put out the code within a day or two. regards, Göran

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Setools August 2006