Setools October 2006

setools@lists.squeakfoundation.org

12 participants
21 discussions

OmniBrowser in squeak-dev image
by Damien Cassou 17 Oct '06

17 Oct '06

Hi Colin and all, can I use source.wiresong.ca/ob and the last OmniBrowser here in the image I maintain for squeak developers ? Bye -- Damien Cassou

2 2

Gjallar user names
by Herbert König 14 Oct '06

14 Oct '06

Hello, how do I find the names of all users in Gjallar? The obvious would be: Q2session current model users do: [:each | each name]. But (using the sample database) in an explorer you can rename oden to mimer by sending #name:. In this case the above will return two mimers but Q2session current model findUserNamed: 'oden' will still return the old oden with 'mimer' in his name instVar. In some place usernames must be unique otherwise the result of #findUserNamed would not make much sense? The reason for all this: In the process creating UI I started to add users and admins to a process and I'm not sure where to get the names from and how to deal with not unique names. Another question: User lists are said to be process wide in the design document. Is there something like global user lists? Are categories the key to this? If a process has many users, it would be convenient to just add a global group of users instead of adding them one by one. Cheers, Herbert mailto:herbertkoenig@gmx.net

1 0

Gjallar process design
by Herbert König 14 Oct '06

14 Oct '06

Hello, in the original design document, p1 I understand that Gjallar should be able to accommodate the fact that processes change over time. From all other docs and the discussion here I only find: 'If a process is used in a single case, don't dare to touch the workflow again'. So how to deal with changes in a business process? Cheers, Herbert mailto:herbertkoenig@gmx.net

1 0

Gjallar Error
by Herbert König 13 Oct '06

13 Oct '06

Hello Göran, sorry for the private mail, but this is too big for the list. When going through the screenshots (swiki page 8) I got an error when I wanted to create the case in the developer process. See pointOfError.htm What I did was: Enter a source like in screenshot009.1.png, click on processes, view the development process, use the back button of the browser, reenter the source and click on create case. FullStack.htm is what I got. Then I tried debug, but didn't manage to find something useful in the squeak debugger. So I selected continue, the browser went back to the create case page and this time I could create the case. I used Version 0.2 and updated to Q2v0.2-gk.181.mcz. and an up to date Firefox. Yesterday I played with viewing creating and moving cases. There I had copied the Gjallar directory to a slower computer and had the browser on my laptop. There I also did the update. Then I copied everything back to the laptop. I started with the sample data I get with Q2Model>>recreateDatabase and iirc I issued Q2Scheduler>>stop. I also attach the gjallar log. I have only sporadic internet access right now. Great concept! Regards, Herbert mailto:herbertkoenig@gmx.net

2 2

Gjallar Error if trying to create cases
by HNBeck＠t-online.de 11 Oct '06

11 Oct '06

5 15

gjallar morpic UI status
by Herbert König 11 Oct '06

11 Oct '06

Hello, I put the first actually useful version of the Create Process UI in the repository. Had to learn that a process without an admin *and* a user doesn't work. Right now root is user and admin. Next steps will be selection of user(s) and admin in the UI and either learning how to create a working process from scratch (without copying a prototype) or scanning the prototypes, in case somebody removed or changed simple prototype. After manually adding MessageSend>>fixTemps (same problem Hans had) I could create cases. The problem with Magma queries in view cases persits. Hans seems to have the same, Hans have you gotten rid of it? @Göran, renaming kategories: I think I should put my stuff into Q2-MorpicUI, as I intend to proceed with User administration, Forms and other things that are done in the console. My process UI has to be extended for constraints and whatever can be done to a process I'm not yet aware of. General request: Whoever has an admin script or process console script (if possible a working one), please send it to me, so I can learn what's needed and how to do it in the UI's. Cheers, Herbert mailto:herbertkoenig@gmx.net

2 1

Squeak day in Berne
by Hans N Beck 07 Oct '06

07 Oct '06

Hi Göran, you may know that at the end of october there is a Squeak day in Berne. I suppose, you can not come, because 1) you are at a completely different place (OOPLSA..) and 2) this place is far away.... In the case you or your collegue can not come, what do you think if I show a little bit Gjallar ? We are searching points for the agenda :-) Greetings Hans

3 2

Re: Re[2]: [Setools] gjallar graphic UI to create a process
by goran＠krampe.se 05 Oct '06

05 Oct '06

Hi! =?ISO-8859-15?B?SGVyYmVydCBL9m5pZw==?= <herbertkoenig(a)gmx.net> wrote: > Hello Göran, > > gks> First of all - cool! It is great that you guys are getting into this and > gks> producing code. And especially Morphic stuff which I probably will stay > gks> clear of, so that gamefield is yours to play with! :) > > my not so good English translates that into "There's work for You to > do" :-)) Hehe, well - I more meant that I will not spend any time on Morphic stuff soon AFAICT. So it was more like "feel free to come up with good solutions, I will not have any strong views on the subject". :) > gks> I opened it up, glanced at the source and played with it. The UI "feel" > gks> didn't work very well with my reflexes - I kept trying to drag the > gks> stages using normal left mouse button for example. But don't let me > gks> influence you - others may feel differently. > > I noticed the same after some time, maybe squeakers are deeply formed > by flaps and the object catalog. I will make both possibilities, so it > works on drag and on click. Dunno how to do this yet but there are > enough examples. > > Deep in the future I think this should run in the squeak plugin and in > a browser we would not try to drag it. Mmmm, the plugin. Yes. Yummy. :) > gks> 1. I would like for all classes in Gjallar to retain the Q2 prefix to > gks> avoid any confusion/collisions and also to make it easy to recognize > gks> Gjallar classes. We could later make a global change of that prefix at > gks> any time - the Q2 letters is an internal name from the customer. > > Noticed that after the release. I wonder what MC will make of renaming > the classes. Duplicate? Will try. I think it handles it. :) > gks> 2. You and Balázs both have Morphic tools but two different class > gks> categories. Either we put them in the same category or we distinguish > gks> them better IMHO. No biggie. > > They aim at different goals and IMO should be kept in different > categories. Then it would be nice if you could name the cats more specifically somehow. Again, no biggie. :) > gks> 3. Put the Documentation class comment in one of the classes itself > gks> (like CreateProcessBigUI) instead. Otherwise we will end up with tons of > > Definitely! Needed my bed when I did this :-)) :) > gks> these "documentation" classes! :) There is only one such "non class" in > gks> Gjallar and that is Q2Gjallar which holds the license as the class > gks> comment and class side high level developer doits only. > > I'm not happy with the class names yet and threw it out so it didn't > get stale here. Having people comment on it gives me little things to > do without having a lot to think. > > gks> I will wait with merging until the above three things are fixed - if it > gks> that is ok with you of course. :) > > I'm not sure what I want, as I don't understand the implications yet > (my first go at MC. Thanks for your intro). My feeling says I'd prefer > it in different mcz, as I fear if it's drowned in the mcz of the whole > Gjallar project it will be slow to save and load as MC has to look at > too many things in doing its work. Working with Gjallar, which is my largest MC project I think, has shown that operations are quite fast. I don't think that is an issue. > I would not mind using your repository and I'll give you a warning > *before* I start messing with anything of the system. Just to keep > your integration work at a minimum. I feel the swiki is the wrong > place for the code. > > What do you say? Yes, the Swiki is the wrong place. :) Feel free to use the repo in any case. There are two options here: 1. Use a different PI name (a different package). You do this by renaming your cats to say "GjallarTool-blabla" and then add a new package in the Monticello browser called "GjallarTool". Thus your code will not be in the "Q2" package and can be considered an optional addon to Gjallar. The positive side is that you are then isolated from Gjallar - I will not need to merge stuff etc. The negatives are of course: - To make adjustments in Gjallar to support your tool you will need to modify the Q2 package and store such snapshots separately for me to pick up and merge. - Not all people will have your addon in their images so when they hack on Gjallar they might change stuff you depend on without really knowing. - Users will need to "know" which version of GjallarTool works with which version of Q2. 2. Use the "Q2" prefix like today. Do not bother warning me - you can make any changes you see fit and save such snapshots to the repo - they will be marked with your initials and since you write a nice summary snapshot comment :) I will have no trouble seeing what you have done and I am free to either merge it in or ignore it. ;) Personally I would prefer for you to take route 2, it is the simplest and also IMHO I want developers to feel that they can dig in, contribute and change Gjallar - that it is not *dangerous* to do that, the worst thing that can happen is that I will not merge it into my "line" and explain why. ;) And non merged versions show up in bold in the repository so it is always very clear what versions are merged in and what are not (from the perspective of the current version in the image). > Cheers, > > Herbert mailto:herbertkoenig@gmx.net regards, Göran

2 1

Gjallar status
by goran＠krampe.se 04 Oct '06

04 Oct '06

Hi! A few things going on with Gjallar right now: - I am working on filters, my view and View cases. These are all connected. Currently View cases is slow and there is a ton of things we can do to make it fast - like for example get Magma queries working (!) and not materialize all hits from Swish-e before we calculate the intersection - instead we should use the UUIDs that Swish-e gives us and fold that into the Magma query. - Magnus has been adding direct links (permalinks) for cases including "login first, then get to the right place" mechanism. Unfortunately we probably need to start fiddling with cookies unless we want to login each and every time, but later. Magnus has possibly isolated the "Magma processes gone hogwild issue" and we intend to dump a fat zip on Chris for postmortem analysis. - Balázs tried building a new image using the gjallar.st script and it didn't work out. This is due to the script tryijng to use the latest Scriptaculous from Lukas, which needed a newer Seaside. I sat up last night trying to back merge us forward to the latest Seaside - and almost made it. It is in the repo but still has at least one known caching issue with the Process overview gifs. If you decide to play with the 2.7a1 of Seaside with the latest Scriptaculous - you need the Q2v0.3-194 too. Ok, over and out. regards, Göran

1 0

gjallar gk 190 view cases
by Herbert König 03 Oct '06

03 Oct '06

Hello Göran, after you wrote that recreate database worked for you,'ve tried again: install Gjallar 0.2 from the zip in a fresh directory. Load Seaside2.6b1-gk.80.mcz, load Q2v0.3-gk.190.mcz. In Gjallar i did: Q2Gjallar cleanImage (unnecessary, just to be save), Q2Model recreateDatabase and then Q2Gjallar startServer then I logged in as root with a Firefox 1.5.06 on the same computer. View cases broght me the attached view (zipped 16 colour bmp is the only way to get it to this list). Verified on a second computer, except: did not clean image and before login I stopped the scheduler. What information can I send? Thanks, Herbert mailto:herbertkoenig@gmx.net

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Setools October 2006