Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 91857 invoked from network); 20 Jan 2004 18:42:49 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Jan 2004 18:42:49 -0000 Received: (qmail 98789 invoked by uid 500); 20 Jan 2004 18:42:36 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 98734 invoked by uid 500); 20 Jan 2004 18:42:36 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 98679 invoked from network); 20 Jan 2004 18:42:36 -0000 Received: from unknown (HELO imf25aec.mail.bellsouth.net) (205.152.59.73) by daedalus.apache.org with SMTP; 20 Jan 2004 18:42:36 -0000 Received: from mail.bellsouth.net ([205.152.59.160]) by imf25aec.mail.bellsouth.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20040120184239.YYIZ1944.imf25aec.mail.bellsouth.net@mail.bellsouth.net> for ; Tue, 20 Jan 2004 13:42:39 -0500 X-Mailer: Openwave WebEngine, version 2.8.12 (webedge20-101-197-20030912) X-Originating-IP: [206.105.196.2] From: Alex Karasulu Organization: Solarsis Group To: "Apache Directory Developers List" Subject: Re: Re: [ot] Guiapp Date: Tue, 20 Jan 2004 13:42:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20040120184239.YYIZ1944.imf25aec.mail.bellsouth.net@mail.bellsouth.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Vince, I think I'm going to start looking at it more extensively. It really makes sense to use IoC especially with management applications that need plugins and may actually load different plugins based on the permissions of the user starting the application. Thanks for the synopsis. Alex > > From: Vincent Tence > Date: 2004/01/20 Tue AM 03:17:06 EST > To: Apache Directory Developers List > Subject: Re: [ot] Guiapp > > Berin has been doing some changes to the maven build for the better, but > I think you have to upgrade the jar plugin to be able to build. The code > itself is not broken, I have an example app built on top of it. > > On Mon, 2004-01-19 at 21:15, Vincent Tence wrote: > > It's the introduction of COP to Swing. A framework for building > > component based swing apps. It uses fortress for container. > > > > The idea is to use fine grained components as application "Screens". > > (Think of them like component versions of regular JPanels). You get the > > benefit of COP in that your swing app screens are no longer so coupled > > and you avoid traditional Swing spaghetti code. All screens are wired > > together with the help a some key components provided by the framework: > > > > - The EventBus - which you already know of, provides the event subsystem > > that screens use to communicate > > - The ActionManager well ... manages Swing Actions run in response to > > button/menus/.. clicks. Commands can be run in sync or async mode using > > the excalibur event package. > > - The ScreenManager embeds Screens in panels or dialogs for display. > > > > Then there are some utlity components, useful in almost any Swing app: > > document manager, document store, ... > > > > If you're thinking of developping a *maintainable* Swing app, that's the > > way to go. > > > > - Vincent > > > > On Mon, 2004-01-19 at 15:20, Alex Karasulu wrote: > > > Vince, > > > > > > What was this guiapp thing you worked on over at sf.net. The cvs stuff > > > is broke and I ran across it wondering if I can use if for a client. > > > Could you give me some background and functionality. > > > > > > Alex > > > > > > > > > >