Setools June 2006

setools@lists.squeakfoundation.org

10 participants
12 discussions

Re: [Setools] What we have yet
by Alexandre Bergel 29 Jun '06

29 Jun '06

Hi Klaus! > I'm interested in better (not necessarily faster) prototyping, in > the sense of drafting new or refining existing software at the > draft level, with full support of a running+reflexive system (and > of DNU, of course :) Do you have an idea of what is currently missing in Squeak ? > I also want to see diff's of a draft against what is already > implemented, in a nice GUI. A good draft is > 20 pages and is > impossible to review together with the customer (user) by using > system / OB / etc browser alone. What kind of navigation tool would you need? Do you mean something more graphical? > And as already was posted in the "Better write a test or a comment > for a given method?" thread in squeak-dev, I'd like to see better > support for tests (don't care on the syntax level). Examples: test > 1 is related to test 2 by this and that; a method is no longer > accepted if a test fails; etc. Omnibrowser enables extensions to be quickly written and added. This is why it is important to push OB. Cheers, Alexandre > > On Sun, 25 Jun 2006 11:36:36 +0200, Alexandre Bergel > <Alexandre.Bergel(a)cs.tcd.ie> wrote: > >> Hi Hans and others! >> >> This list is a very good initiative. >> I am interested in improving Omnibrowser. I hope it can become the >> default Squeak browser. I produced some changeset that enhance OB >> in two different ways: >> - Comments are displayed below the definition of a class whenever >> I click on one. >> - The list of methods are displayed whenever a class is selected. >> >> I believe this two improvements are important. With this two >> improvements, I do not use the classical browser anymore. >> >> Roel has been working on improving OB with a Package/Hierarchy >> button. This idea come from in Visualworks. >> >> Is Colin part to this mailing list ? If not, maybe you should >> invite him :-) >> >> Cheers, >> Alexandre >> >> NB: Hans, could you set the mailing list has "replying to the >> list" instead of "replying to the author" ? >> >> >> Am Jun 25, 2006 um 10:27 AM schrieb Hans N Beck: >> >>> Hi, >>> >>> for the beginning, I would collect, which tools there are >>> already for Squeak and/or using Squeak related to Software >>> Engineering. >>> >>> As far as I remember, we have >>> >>> - of course the browsers: (Star-, Omni- , .....?) >>> - Syntax highlighting >>> - Monticello -> Versioning >>> - Refactoring >>> - .... >>> >>> >>> Regards >>> >>> >>> Hans >>> _______________________________________________ >>> Setools mailing list >>> Setools(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/setools >> > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 8

[ENH] OB
by Alexandre Bergel 27 Jun '06

27 Jun '06

Is Stef part of this mailing list ? Change Set: OBFixFindClass Date: 27 June 2006 Author: Alexandre Bergel When you find a class by pressing Alt-f for example, you may have a very long list. Even if you type the exact name of the class. This changeset place as the first choice the class you entered. For instance, try to search for Object. You have a very long list, this change makes Object the first entry of the menu. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[ENH] Moving methods to packages with OB
by Alexandre Bergel 27 Jun '06

27 Jun '06

This change adds a new entry in the method menu list. You can move a method into different monticello package. It creates a method category and move the method there. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Looking for papers about 'Dealing with workflows in Smalltalk'
by Damien Cassou 27 Jun '06

27 Jun '06

Hi, Karsten Kusche and I are working for Georg Heeg eK to improve Smalltalk developers workflow while keeping flexibility. Ideas have to be grabbed to help average Smalltalk developers to make a good design and follow an established workflow. We would like to finish our work with a tool that everybody can use for development. It should be an extension to the existing browser that displays more information. Attention is being put in easing unit tests, making the comprehension of an existing system simpler, and giving lots of information about methods, classes and packages. If you have ideas, publications or things that we can test or read, it would be interesting to share with us. Thank you for your help, we hope we will be able to present something at ESUG 2006. Bye -- Damien Cassou

2 3

Let me introduce myself
by A. Kuhn 27 Jun '06

27 Jun '06

Hello list, My name is Adrian, and I am a member of the SCG. Beside Tudor, I am the other maintainer of the Moose Reengineering Framework. But currently I'm working on integrating Mondrian visualizations into VW's RB and inspector. I'm new to squeak, but very eager to get into it and see Mondrian ported to Squeak :) mit freundlichen Grüssen, Adrian

3 2

The Q2 issue tracker
by goran＠krampe.se 26 Jun '06

26 Jun '06

Hi folks! Colin wrote: > So that's what I'm working on these days. What other projects are on > the go? Are there any concrete plans for the bug tracker? Not only plans but *real code*. :) I have been building a system called "Q2" (not the real name hopefully) for a customer (full time) since january, with the help of Magnus Kling (a collegue from Toolkit Software). It is a web based issue tracker (not specifically bugs but issues in general) written in Squeak3.8/Seaside/Magma. It is designed to be a really flexible and customizable system for advanced issue tracking - but with a very simple but smart user interface using Seaside spiced a little bit with Scriptaculous. :) The best part is that (I will get the definite *go or no go* this week) it will be MIT licensed with a probability of 95%. When the license is decided I will post again and immediately set up a website around it. Some of the important features (from memory): - Models different "processes" which are fully separate "systems within the system" with separate permission models, forms, fields, workflows etc. - Users are given access to one or more processes and can work within all those processes at the same time (searching across them all for example). - Uses a directed graph workflow model with visualization of graph using Graphviz. - Full email integration with creation of cases including attachments, threaded discussion (tracking replies and so on) etc. - Free text engine Swish-e integrated for advanced boolean free text searching etc combined with advanced query filtering. - Has a model of "forms" with "fields" (a la Mewa/Magritte) allowing custom information to be "attached" to the issues in the form of "extra tabs" in the tab book UI. - A very good validation model following the idea that you can always edit and save partially with validations invalid, but you are restricted in moving the issue to another stage in the workflow. These validation criteria can be placed upon enter or exit to a stage, or on a specific transition. - An advanced search/filtering mechanism with personal filters. - An advanced subscription/notification mechanism based on listening on low level events, filtering through personal search filters and then if the subscription is triggered, emailing with optional digest. - Integrated editable Swiki help (!) down to the field level. If you switch on this help you get tons of "question marks" in the app and clicking on them expands a little swiki page inlined into the web page. Superb for explaining fields etc. Editable in place just like a Swiki. - Export/reports in CSV, XML, HTML. - Mirroring of external data into the system using ODBC to enable for example selections in the issues (like selecting an entity from an external system like "project" or "article" or whatever). - A simple UI using the "left side TOC, right side currently selected function"-style. And finally, the killer feature for our customer: - Full offline operation. The system can be installed in full locally on a laptop and you "check out" a mirror of one or more processes - work offline - and then sync your modifications with the master server. This is enabled by the use of the "Command Pattern" for all modifications to the domain objects in the form of a series of "transaction" objects that are also persisted. So the system has a full, complete traceability of all changes. :) The system is currently 250 classes, domain model of course totally clean of UI, and system in total about 20 kloc. It has quite a bit of tests - even though we would want to have more. :) The system *works* today but it has not been fully tested and we are still working on selected parts like for example filtering, subscriptions, exports/reports. And some parts are lacking proper UIs. regards, Göran PS. There is nothing preventing the Squeak community from building an extra Morphic/Tweak UI on top of the system possibly combined with setting Magma up in a client/server model over the Internet to get a fully integrated issue tracker inside the Squeak image. Or simply using the builtin "offline" mechanism to enable the same use.

3 2

Hi
by Colin Putney 26 Jun '06

26 Jun '06

Hi guys, Good to see people interested in tools; this list should be fun. I have a few things I want to bring up as we get started. One is the roadmap for OmniBrowser. Here's the plan I've been working off for the past few months: 1. convert the event handling code to use Announcements 2. deprecate Actions and convert OB over to services 3. add refactoring support 4. implement multiple-selection in browser columns 5. replace the optional button bar with a VW- or Dolphin-style tool panel There's also some supporting work that needs to be done, along side the technical work. 6. document the framework on the OB wiki 7. document the standard Smalltalk browsers, for users 8. document the standard Smalltalk browsers, for programmers 9. create a directory of OB-based tools for download 10. Clean up test cases and improve coverage Item number 1 is done, and I'm almost finished 2. Lately the SCG (and ex-SCG) guys have been doing some interesting things with OB, and we'll want to see how they'll be affected by the changes above. The other project that might be interesting to folks here is Monticello2. It's a fragile stage just now, where it has lots of functionality in place, but it's not quite ready for production use. There's still one chunk of functionality that needs to be implemented before it can be considered beta: class renaming. Right now if you rename a class, that won't be noticed, and all the instances will be come obsolete. Once that's in place, the core will be complete, and it's a matter of fleshing out the UI. So that's what I'm working on these days. What other projects are on the go? Are there any concrete plans for the bug tracker? Colin

2 1

Fwd: [Setools] What we have yet
by Alexandre Bergel 25 Jun '06

25 Jun '06

Hans, please, set the mailing list as "reply to the mailing list" instead of "reply to the author" :-) It will be more convenient for everybody. Cheers, Alexandre Anfang der weitergeleiteten E-Mail: > Von: "Klaus D. Witzel" <klaus.witzel(a)cobss.com> > Datum: June 25, 2006 1:38:57 PM GMT+01:00 > An: "Alexandre Bergel" <Alexandre.Bergel(a)cs.tcd.ie> > Betreff: Re: [Setools] What we have yet > > Hi Hans & all, > > I'm interested in better (not necessarily faster) prototyping, in > the sense of drafting new or refining existing software at the > draft level, with full support of a running+reflexive system (and > of DNU, of course :) > > I also want to see diff's of a draft against what is already > implemented, in a nice GUI. A good draft is > 20 pages and is > impossible to review together with the customer (user) by using > system / OB / etc browser alone. > > And as already was posted in the "Better write a test or a comment > for a given method?" thread in squeak-dev, I'd like to see better > support for tests (don't care on the syntax level). Examples: test > 1 is related to test 2 by this and that; a method is no longer > accepted if a test fails; etc. > > The next item gets more visionary: what is a software author > without the ability to release her/his work on more than one > platform, more than one OS vendor, more than one HW vendor. I'd > like to see: one source+some annotations = more platforms. Compare > that to, for example, a port of Squeak to a new platform: the > "average" software author cannot do (nor afford) such a port by any > means. > > /Klaus > > On Sun, 25 Jun 2006 11:36:36 +0200, Alexandre Bergel > <Alexandre.Bergel(a)cs.tcd.ie> wrote: > >> Hi Hans and others! >> >> This list is a very good initiative. >> I am interested in improving Omnibrowser. I hope it can become the >> default Squeak browser. I produced some changeset that enhance OB >> in two different ways: >> - Comments are displayed below the definition of a class whenever >> I click on one. >> - The list of methods are displayed whenever a class is selected. >> >> I believe this two improvements are important. With this two >> improvements, I do not use the classical browser anymore. >> >> Roel has been working on improving OB with a Package/Hierarchy >> button. This idea come from in Visualworks. >> >> Is Colin part to this mailing list ? If not, maybe you should >> invite him :-) >> >> Cheers, >> Alexandre >> >> NB: Hans, could you set the mailing list has "replying to the >> list" instead of "replying to the author" ? >> >> >> Am Jun 25, 2006 um 10:27 AM schrieb Hans N Beck: >> >>> Hi, >>> >>> for the beginning, I would collect, which tools there are >>> already for Squeak and/or using Squeak related to Software >>> Engineering. >>> >>> As far as I remember, we have >>> >>> - of course the browsers: (Star-, Omni- , .....?) >>> - Syntax highlighting >>> - Monticello -> Versioning >>> - Refactoring >>> - .... >>> >>> >>> Regards >>> >>> >>> Hans >>> _______________________________________________ >>> Setools mailing list >>> Setools(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/setools >> > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

What we have yet
by Hans N Beck 25 Jun '06

25 Jun '06

Hi, for the beginning, I would collect, which tools there are already for Squeak and/or using Squeak related to Software Engineering. As far as I remember, we have - of course the browsers: (Star-, Omni- , .....?) - Syntax highlighting - Monticello -> Versioning - Refactoring - .... Regards Hans

3 2

Hello
by Damien Cassou 24 Jun '06

24 Jun '06

Gutten tag, I'm currently in Köthen and I would like to follow your discussions about Squeak. Bye

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Setools June 2006