Re: One Last Description

As a document, it looks good... I have a few questions though, but they
depend on me understanding your layout correctly.

xwt.theme // a theme (with boxes?) and preapplies?
(what I don't like about this is that for the sake of a few boxes
difference, you'll have to basically copy the xwts from xwt.theme into your
themedir and just change 2 lines out of 50 or so for each xwt that differs
slightly.)

xwt.lib // theme independent code - we all agree on this one :P

xwt.widget // documentation only?  no preapplies in this one?  so we're not
separating out the preapplies from the 'theming code' in xwt.theme?

-----Original Message-----
From: David Crawshaw [mailto:[email protected]]
Sent: 03 April 2003 15:56
To: [email protected]
Subject: [xwt-dev] One Last Description


Okay, in that last pdf I compromised on a few points to try and get 
everything moving. Charlie's arguments have made it clear to me that 
the points I compromised ruined the clean structure of what I've been 
pushing for.

As such, I've written it up again, only this time all the way. There's 
an xwt.theme, it has a default theme in it. It doesn't have 
subdirectories splitting off behaviors. There's an xwt.lib, with theme 
independent code. It doesn't have subdirectories either. There's an 
xwt.widget, which is a simple interface for xwt.theme.

It provides a power toolbox to the application developers, and a simple 
intuitive toolbox. It does this with the separate theme implementations 
only having to consider one of the two interfaces.

It keeps theme independent code away from theme dependent shared code, 
and doesn't have any redundancy, unless a theme decides it has to do 
something differently, in which case it has to implement it. It would 
have do that anyway.

http://zentus.com/WidgetReference.pdf
http://zentus.com/WidgetReference.lyx

In my opinion, this represents everyone's best ideas.

I don't have any more time to spend on this. I've tried really hard to 
show the merits of the double user interface with the single theme 
development interface, but it's not this important to me. These 
constant circular emails have really lost me a lot of development time 
which I'm going to have to make up on weekends and in the early hours 
of the morning. This is not something I'm going to loose any more sleep 
over.

If you guys decide to go with a design that can do everything this 
design can do, then I'm still willing to the cvs transition. If it 
can't provide the power to the developer, or is messier for 
implementing a theme, then one of you will have to do it, because I 
don't want to do a lot of work implementing something like that.

For now, I'm going to work on the richtext/html implementation. It'll 
be a few weeks before I have anything to show you, but there will 
probably be a few core patches from me relating to the whole deal.

(Do with the widget reference document as you will.)

d


_______________________________________________
http://lists.xwt.org/listinfo/dev
_______________________________________________
http://lists.xwt.org/listinfo/dev