jchassis-devel Mailing List for JChassis
Status: Alpha
Brought to you by:
stainsby
Menu
▾
▴
jchassis-devel — mailing list for JChassis developers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(6) |
Jul
(6) |
Aug
|
Sep
|
Oct
(1) |
Nov
(6) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
(4) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <sjs...@ya...> - 2003-06-06 07:18:30
|
Hi all,
Just a quick update on the progress of JChassis. No doubt you saw
the release of version 0.1 a couple of weeks ago. It was a very
satisfying occasion to produce something that was carefully
planned, designed, written, tested and documented, unhurried by
arbitrary manager-imposed deadlines (OK, so I didn't get any
money either, but never mind, it overrated anyway).
The release news was also posted to the SourceForge and Freshmeat
news facilities. I've got a good screenshot of the JChassis
announcement on the front page of the Freshmeat site (see
attachment). The number of web hits on the JChassis SourceForge
page was well over 300 on that day. There were 4 downloads as
well (woohoo - well not much really, but there again, JChassis is
still in the early stages yet, and not very useful unless you are
willing to make lots of components yourself).
I was going to take a couple of weeks off the project, but I just
couldn't stay away from it this week. I've drafted a "plan" for
the 0.2 release (see below). Also, I may do an 0.1.1 release this
weekend due to a problem in the module guide that prevented
package javadoc from being included (makes the module guide a bit
terse, but still usable). Where is doco QA when you need it!?
(yes, Loretta I mean you - join us or be damned!)
As you can se from the plan, there are about 2 dozen new modules
to produce, and some minor tinkering with a couple of existing
modules. These additions will solidify the core functionality of
JChassis, as well as introducing some services that are actually
quite useful this time. Several modules already have prototype
implementations (jc_ui_if, jc_ui_awt, jc_ui_swing, jc_ui_gtk,
jc_event_*, jc_termctl_* and jc_termgui)
Further in the future, version 0.3 of the SDK will concentrate on
polishing services for client-side and standalone
applications. Version 0.4 will introduce server-side
functionality (thread pools, transactions, remote services,
... etc?). I think version 0.5 will see the transition from alpha
to beta - well that's my intended versioning scheme anyway.
Somewhere down the track, Version 1.0 will signify the first
polished non-beta release.
If you are interested in getting involved with one or more areas
of work outlined below, then let me know now so that can start
scheduling. Any other ideas for the project are welcome too!!!
Cheers, Sam.
Plans for JChassis SDK v. 0.2
=============================
New Features
------------
* investigate using SAX 1 and MinML to save space: mabye use SAX
2 ParserAdapter class
* eliminate the BasicServiceContext interface if possible
* define a shutdown service & default implementation (perhaps
some generic event handling service to base this on?)
* first "real" version of JChassis UI + implementations (AWT,
Swing, GTK)
* ANSI console implementation of JChassis UI
* J2ME MIDP compatible implementation of the core framework &
config. loader
* internationalization (I18N) of strings and icons (and other
resources?) by table lookup - jc_ui_if should depend on this
* resource location (and access) service
* user preferences service? (based on JC Storage service)
* ability to flag deprecation of modules in jcmodule.xml file
(using module metadata?)
* rename jc_ui_if to jc_ui (because its not just a service
interface)? Or maybe just split module into jc_ui_util
(utilities) and jc_display_if (the Display service interface)
* more example programs: more complex this time?
Defect Fixes
------------
* javadoc package summaries were not being included in the module
guide for some reason (this is now fixed in CVS)
New Modules
-----------
jc_event_util: generic event handling utilities
jc_event_if: generic event handling service interface
jc_event_impl: default event handling service implementation
jc_i18n_if: service interface for I18N string & image resource
lookups
jc_i18n_impl: default implementation for I18N string & image
resource lookups (depend on jc_resource_if)
jc_resource_if: resource location service interface
jc_resource_impl: default resource location service
implementation (e.g. uses default Java classpath-based resource
location)
jc_termctl_if: terminal controller interface
jc_termctl_ansi: ANSI/vt100 terminal controller
jc_termgui: an simple GUI toolkit using any terminal control
interface
jc_ui_if: generic UI interface
jc_ui_awt: an AWT implemention of the generc UI interface
jc_ui_swing: a Swing implemention of the generc UI interface
jc_ui_gtk: a GTK binding implemention of the generc UI interface
jc_ui_term: an implemention of the generc UI interface using
jc_termgui
jc_shutdown: shutdown service - notifies listeners when
application is shutting down
... possibly ...
jc_sax1parser_if: SAX 1 parser interface
jc_sax1parser_impl: default SAX 1 parser
jc_core_midp: MIDP compatible core implementation
jc_coreloader_midp: MIDP compatible core configuration loader
implementation
jc_ui_swt: an SWT (Eclipse) implemention of the generc UI
interface
Module Changes
--------------
... possibly ...
jc_basic: elimination of the BasicServiceContext class
jc_prefs_if: a user preferences service interface
jc_prefs_impl: a default user preferences service implementation
(depend on jc_store_if?)
=====
Sam Stainsby
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile. |
|
From: <sjs...@ya...> - 2003-05-23 07:49:26
|
Hi all, I'm pleased to announce the first release to come out of the JChassis project: the JChassis Software Development Kit version 0.1. The JChassis "factsheet" is attached for an overview of what the project is about, otherwise, you can pick the entire package up at http://sourceforge.net/projects/jchassis . The homepage for the project is at http://jchassis.sourceforge.net . The SDK includes a comprehensive user guide and also a guide to JChassis' components, called "modules". If you decide to download the package and have a look at it, please let me know what you think. Cheers, Sam Stainsby. ===== Sam Stainsby http://mobile.yahoo.com.au - Yahoo! Mobile - Check & compose your email via SMS on your Telstra or Vodafone mobile. |
|
From: <sjs...@ya...> - 2003-03-14 02:02:39
|
Hi all!
Just a note to let you know that JChassis v0.1 is now code complete
(apart from some sample code). I'm am testing/documenting and writing
sample code at the moment.
For your entertainment, below is my attempt to compile the "core"
framework under Sun's J2ME wireless toolkit. It gives a good indication
of what is missing in the MIDP profile --- amazing what we take for
granted: no Properties class, no File class or file I/O, no
StringTokenizer, no StringBuffer, no clone() method (!?), etc. ...
Project "jc-core" loaded
Project settings saved
Building "jc-core"
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/DefaultServiceConfigurationLoader.java:37:
cannot resolve symbol
symbol : class Properties
location: package util
import java.util.Properties;
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/ServicesPropertiesParser.java:37:
cannot resolve symbol
symbol : class Properties
location: package util
import java.util.Properties;
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/cmdline/impl/CommandLineParser.java:37:
cannot resolve symbol
symbol : class StringTokenizer
location: package util
import java.util.StringTokenizer;
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Log.java:35:
cannot resolve symbol
symbol : class FileOutputStream
location: package io
import java.io.FileOutputStream;
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/ServiceInstantiator.java:108:
cannot resolve symbol
symbol : class ExceptionInInitializerError
location: class org.jchassis.core.ServiceInstantiator
} catch (ExceptionInInitializerError e) {
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/app/Engine.java:68:
cannot resolve symbol
symbol : method clone ()
location: class java.util.Vector
return ((Vector) ENGINES.clone()).elements();
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/ServicesPropertiesParser.java:90:
cannot resolve symbol
symbol : class Properties
location: class org.jchassis.core.loader.ServicesPropertiesParser
Properties serviceProperties = new Properties();
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/ServicesPropertiesParser.java:90:
cannot resolve symbol
symbol : class Properties
location: class org.jchassis.core.loader.ServicesPropertiesParser
Properties serviceProperties = new Properties();
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/ServicesPropertiesParser.java:110:
cannot resolve symbol
symbol : method intern ()
location: class java.lang.String
prefix = prefix.intern();
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/DefaultServiceConfigurationLoader.java:158:
getProperty(java.lang.String) in java.lang.System cannot be applied to
(java.lang.String,java.lang.String)
String serviceResource =
System.getProperty(SERVICE_RESOURCE_PROPERTY,
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/core/loader/DefaultServiceConfigurationLoader.java:256:
cannot resolve symbol
symbol : method getProperties ()
location: class java.lang.System
System.getProperties().put(propertyName, propertyValue);
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/cmdline/impl/CommandLineParser.java:183:
cannot resolve symbol
symbol : method clone ()
location: class java.util.Vector
Vector ruleSet = (Vector) this.rules.clone();
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/cmdline/impl/CommandLineParser.java:318:
cannot resolve symbol
symbol : class StringTokenizer
location: class org.jchassis.cmdline.impl.CommandLineParser
StringTokenizer tokenizer = new StringTokenizer(ruleString,
":");
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/cmdline/impl/CommandLineParser.java:318:
cannot resolve symbol
symbol : class StringTokenizer
location: class org.jchassis.cmdline.impl.CommandLineParser
StringTokenizer tokenizer = new StringTokenizer(ruleString,
":");
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Log.java:152:
cannot resolve symbol
symbol : method writeBytes (java.lang.String)
location: class java.io.DataOutputStream
this.out.writeBytes(entry);
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Log.java:153:
cannot resolve symbol
symbol : method writeBytes (java.lang.String)
location: class java.io.DataOutputStream
this.out.writeBytes("\n");
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Log.java:177:
cannot resolve symbol
symbol : class FileOutputStream
location: class org.jchassis.log.impl.Log
FileOutputStream rawOut = null;
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Log.java:181:
cannot resolve symbol
symbol : class FileOutputStream
location: class org.jchassis.log.impl.Log
rawOut = new FileOutputStream(this.fileName,
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Logger.java:135:
cannot resolve symbol
symbol : method append (float)
location: class java.lang.StringBuffer
this.buffer.append(f);
^
/home/stainsbs/apps/WTK2.0/apps/jc-core/src/org/jchassis/log/impl/Logger.java:141:
cannot resolve symbol
symbol : method append (double)
location: class java.lang.StringBuffer
this.buffer.append(d);
^
20 errors
com.sun.kvem.ktools.ExecutionException
Build failed
=====
Sam Stainsby
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.
|
|
From: <sjs...@ya...> - 2003-02-19 02:04:26
|
Hi Narendra, Thanks for your interest in JChassis. The good thing about open source projects is that they can accomodate a wide variety of skill variations and levels, sice there are so many different things to do ... so I generally don't turn anyone away that exresses an interest. Below are some suggested steps to get started. All of the scripts are Linux specific at the moment, so there is some extra work if you run Windows. 1. Read the developer info on the website - I think its still pretty up-to-date. Read all of the other general info as well if you haven't already. 1. Get an account on sourceforge if you don't have one yet. I can't add you to the project until you have one. Send me your SF username once you have your account set up. I will add you to the project and notify you one thats done. 2. Join the "jchassis-devel" mailing lists on SF (see the JChassis project page linked off the JChassis home page). 3. Get your tools installed and set up as per the developer info page. 4. Check out the CVS modules "build", "doc" "env", "proto" and "v1". All mainstream development is in "v1" at the moment. 5. Edit "build/build_env" to suit your environment. If you are using WIndows, you will need a similar .BAT file to do the jo of "build_env". 6. Go to the "v1/basic" directory and build and run the unit tests using "./build run.utests". For Windows, you will need a script that operates in a similar way to "build". If you can do all that, you're doing well. Let me know if you get stuck. Cheers, Sam. --- Narendra Tumkur <nar...@ho...> wrote: --------------------------------- Dear Mr. Stainsby, I came across your project on sourceforge and was very interested in it. I am currently a student of software engineering at Queensland University of Technology and I understand that you are also based there. I would like to volunteer my services for the project. I am a "not too bad" java coder and would really appreciate the oppurtunity to work on something like this. I look forward to your reply. Thanking you Narendra Tumkur --------------------------------- Hotmail now available on Australian mobile phones. Click here for more. ===== Sam Stainsby http://mobile.yahoo.com.au - Yahoo! Mobile - Exchange IMs with Messenger friends on your Telstra or Vodafone mobile phone. |
|
From: <sjs...@ya...> - 2003-02-18 00:21:15
|
Now once more with the attachment ... --- Sam Stainsby <sjs...@ya...> wrote: > All, > > Here is a one page fact sheet on JChassis that Mark White > requested. You might find it useful ... paper aeroplance, > placemat, draft stopper, etc. > > Hey Jason, where are my Debian CDs ... ?? > > What about Govindas sometime soon? Let me know. > > Must sleep now ... > > Cheers, > Sam. > > ===== > Sam Stainsby > > http://mobile.yahoo.com.au - Yahoo! Mobile > - Exchange IMs with Messenger friends on your Telstra or Vodafone > mobile phone. > ===== Sam Stainsby http://mobile.yahoo.com.au - Yahoo! Mobile - Exchange IMs with Messenger friends on your Telstra or Vodafone mobile phone. |
|
From: <sjs...@ya...> - 2003-02-17 12:08:32
|
All, Here is a one page fact sheet on JChassis that Mark White requested. You might find it useful ... paper aeroplance, placemat, draft stopper, etc. Hey Jason, where are my Debian CDs ... ?? What about Govindas sometime soon? Let me know. Must sleep now ... Cheers, Sam. ===== Sam Stainsby http://mobile.yahoo.com.au - Yahoo! Mobile - Exchange IMs with Messenger friends on your Telstra or Vodafone mobile phone. |
|
From: <sjs...@ya...> - 2003-02-17 11:48:32
|
Hi all, Its been over a month since the last update. My only excuse is that I've spent 3 weeks designing & writing a software project for the unit I'm co-ordinating this semester. It actually uses JChassis Object Store (which I will mention below). Whats been happening in JChassis? I'm glad you asked ... I have had some discussions with Mark White (managing director in a company called Apviva at the moment (www.apviva.com); he is the ex Vice President and GM of RedHat Pacific-Asia Inc) about collaboration with other companies. He is interested in JC for the embedded Java market, suggesting perhaps Nokia would be interested for example. He suggests getting a couple of companies to evaluate it, altough its not quite ready for that yet (soon though!). Sounds like the feedback from this alone would be worthwhile ... What's remaining before release? 1. Some coding (not much) I have written all of the hard parts now. The guts of the tools for handling "modules" (like ".deb" packages, but for Java projects, instead of for Debian Linux) are done - just needs the applications that wrap around them: all very straightforward. The hard part, the dependency solving is now done as a separate API that is useful in its own right 2. Documentation All though copiously javadoc'd, some user-doc is 'needed to tie it all together, so the user isn't left saying "What the **** is this all about". 3. Examples Some compelling examples are essential. I'm thinking a personal task manager would be one good thing to try. Interested Wes? 4. Package Package it up and away we go .... 5. "Advertising" SourceForge, Freshmeat, newgroups, cheerleaders :-) anything else? What I've gotten around to doing since the last update: * The best part (or worst) of the coding for the "module" tools. See http://jchassis.sourceforge.net/v1/util/apidoc/index.html under the org.jchassis.depend package, for the dependency stuff. The module tools doco isn't online yet, except in the CVS tree. * A protype of a lightweight object storage API - ideal for client preferences, mini-databases, etc. Not on the web site yet: only visble in the CVS tree. That all, I've been too busy at work ... this week is better though. I hope to get more done. Stay tuned, Sam. ===== Sam Stainsby http://mobile.yahoo.com.au - Yahoo! Mobile - Exchange IMs with Messenger friends on your Telstra or Vodafone mobile phone. |
|
From: <sjs...@ya...> - 2003-01-09 07:47:40
|
Latest JChassis news ...
Happy New Year to all!
I haven't been sending much mail over the Xmas break,
although I have been happily coding away at times.
I have removed some developers that haven't
been contributing, but they are welcome to
rejoin after the first release, or before
if they have something urgent to contribute.
Hopefully they will still get this mailing list
traffic.
Some bits and pieces I have been developing:
- a more advanced command line parser component
- an ANSI terminal controller (think curses/ncurses
for Java): this allows you to have colours and
windows in a text console that is ANSI/vt100
compliant (eg. Linux virtual consoles and xterms,
etc. - aparently MS Windows console as well - yet
to check this)
Send me mail if you want more detail ... all of
the code in in the "proto" module.
Most importantly, I've have prototyped the code
required to place JChassis service implementations
and other classes and resources into special JAR
files ("MAR" files"??). These files contain an
XML file that defines the "module" contained in
the JAR file, and other modules that it depends
on. I have also prototyped a tool that can add
and remove MAR files to/from a repository such
that dependencies are always satisfied
(think apt-get, but for software components
instead of applications and libraries). This
ensures the developer has a palette of components
that satisfied each others' requirements (provided
they are used properly in the application).
I think once the "module" work above is properly
design and completed, we will be ready for the
first release. I think the modules work is necessary
since developers will be able to easily download
components and get the dependencies right using the
tools we provide.
Cheers,
Sam.
=====
Sam Stainsby
http://movies.yahoo.com.au - Yahoo! Movies
- What's on at your local cinema?
|
|
From: <sjs...@ya...> - 2002-12-08 02:30:27
|
Hi all, Its been a while since I did an update on the progress of JChassis. Firstly, the web site have been restructured and updated. There are numerous changes, incuding an update to the project status, and the including of the javadoc for the core and basic frameworks. Updates on the project progress: 1. The core framework code has been polished and thoughroughly javadoced, adding all of the material in the original designs into the javadoc. The original designs are now obsoleted. 2. Example code for using the core framework and the existing JChassis utils (command line parser, logging and SAX2 parser) has been produced. See the code in CVS: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jchassis/v1/core/examples/ http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jchassis/v1/util/examples/ 3. I'm working on example code for the basic framework. 4. I'm also working on designs for the JChassis "module" system: modules are deployable JAR files that contain the class files for JChassis services, plus some useful metadata. Basically, think of the JCHassis module system as something similar to the Debian dpkg and apt systems, but for Java software components. The incomplete designs can be viewed here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jchassis/v1/module/doc/designs/ Any comments would be appreciated. 5. Work on polishing the basic framework continues... We also have a new team member, Gautam, who has joined us recently. Pleae make him feel welcome. Cheers, Sam. ===== Sam Stainsby http://www.yahoo.promo.com.au/hint/ - Yahoo! Hint Dropper - Avoid getting hideous gifts this Christmas with Yahoo! Hint Dropper! |
|
From: <sjs...@ya...> - 2002-11-25 23:08:30
|
Dear JChassis project members, Just letting you know two important items: 1. I have made the jchassis-devel mailing list public, so there is no need to be a project member to be on this list. The other two list were already public so the same applies. 2. I intend to REMOVE all members from the project that have not contributed anything to the project by the end of this year, or before the first release, whichever come first. Contributing means writing code, improving build systems, contributing ideas, writing/reviewing documents, etc. At this point it is quite likely that the first release will come before Xmas ... Cheers, Sam. ===== Sam Stainsby http://www.yahoo.promo.com.au/hint/ - Yahoo! Hint Dropper - Avoid getting hideous gifts this Christmas with Yahoo! Hint Dropper! |
|
From: <sjs...@ya...> - 2002-11-22 11:03:38
|
Also, attached is my "generic" research proposal. --- Sam Stainsby <sjs...@ya...> wrote: > Dear JChassis folk, > > Just another update on the progress of JChassis. > > This week I started applying for a small grant > for my QUT research. The closing date is next > Friday - I'll let you know how I go. > > I'm also in the process of negotiating an > intellectual property agreement with the director > of the research group I'm in at QUT (Centre for > Information Technology Innovation = CITI). My aim > is to ensure that IP I develop consisting of JChassis > framework code, algorithms, doco, etc. remain mine, > and not QUTs. They get the other stuff - the results > of the research. Should any of you decide to put > fingers to keyboard and write anything for JChassis, > please ensure that you have clarification, preferably > in writing, from you employers determining that you > own the IP. Let me know if you need help with this. > > Development-wise, JChassis is comming along in leaps > and bounds. The two service containers (contexts), > "core" and "basic" are completed and unit tested. > Three plugin services, CommandLineParser, Log and > SAX2Parser (a convenient point to plug in SAX2 parsers) > are completed and unit tested. The SAX2 parser is used > to load XML configuration into the basic context. > > I am also developing example programs which will aid > understanding of the JCHassis. Several of these are > completed already. > > The next major step are: > > * developing a facility that checks for > dependencies between components and other > resources and ensures that these are satisfied > during runtime (or maybe just at installation time) > * working out how to package components into > easily deployable units (consider EAR files in > Enterprise Java) > * defining some kind of configuration to declare > dependencies between components and other resources > > For example, a service interface "A" might have > an implementation class "AImpl". This implementation > might require a service with interface "B". > Also, If AImpl was doing something with SAX2, > it might require the org.sax.XXX packages. These > only come out-of-the-box with JRE 1.4, but are > also available elsewhere so they can be used with > JRE 1.1 up to JRE 1.3. So there is a set of > dependecies here that I would like to check > automatically, during runtimne (or possible only > once during installation of the components/resources). > > We might declare the dependencies above with a > little XML (I'm just making up the package names > here): > > <interface> > <class>org.jchassis.a.A</class> > <metadata><name>Version</name><value>1.00</value></metadata> > <metadata><name>Author</name><value>Bob > Bilby</value></metadata> > </interface> > > <interface> > <class>org.jchassis.b.B</class> > <metadata><name>Version</name><value>1.01</value></metadata> > <metadata><name>Author</name><value>Mary > Hooha</value></metadata> > </interface> > > <implementation> > <class>org.jchassis.a.impl.AImpl</class> > <metadata><name>Version</name><value>5.15a</value></metadata> > <metadata><name>Author</name><value>Fred > Whatsit</value></metadata> > <depends> > <interface>org.jchassis.b.B</interface> > <choice> > <jre>1.4</jre> > <module>SAX2</module> > </choice> > </depends> > </implementation> > > <module> <!-- module = group of classes and packages --> > <name>SAX2</name> > <package>org.xml.sax</package> > <package>org.xml.sax.ext</package> > <package>org.xml.sax.helpers</package> > <depends> > <jre>1.1</jre> > </depends> > </module> > > > Presumably, each piece of configuration would > be stored with the approriate interface, implementation > or module JAR file ... > > Anyweay, let me know if you have any ideas ... > > Cheers, > Sam. > > ===== > Sam Stainsby > > http://www.yahoo.promo.com.au/hint/ - Yahoo! Hint Dropper > - Avoid getting hideous gifts this Christmas with Yahoo! Hint > Dropper! > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > jchassis-devel mailing list > jch...@li... > https://lists.sourceforge.net/lists/listinfo/jchassis-devel ===== Sam Stainsby http://www.yahoo.promo.com.au/hint/ - Yahoo! Hint Dropper - Avoid getting hideous gifts this Christmas with Yahoo! Hint Dropper! |
|
From: <sjs...@ya...> - 2002-11-22 10:59:55
|
Dear JChassis folk,
Just another update on the progress of JChassis.
This week I started applying for a small grant
for my QUT research. The closing date is next
Friday - I'll let you know how I go.
I'm also in the process of negotiating an
intellectual property agreement with the director
of the research group I'm in at QUT (Centre for
Information Technology Innovation = CITI). My aim
is to ensure that IP I develop consisting of JChassis
framework code, algorithms, doco, etc. remain mine,
and not QUTs. They get the other stuff - the results
of the research. Should any of you decide to put
fingers to keyboard and write anything for JChassis,
please ensure that you have clarification, preferably
in writing, from you employers determining that you
own the IP. Let me know if you need help with this.
Development-wise, JChassis is comming along in leaps
and bounds. The two service containers (contexts),
"core" and "basic" are completed and unit tested.
Three plugin services, CommandLineParser, Log and
SAX2Parser (a convenient point to plug in SAX2 parsers)
are completed and unit tested. The SAX2 parser is used
to load XML configuration into the basic context.
I am also developing example programs which will aid
understanding of the JCHassis. Several of these are
completed already.
The next major step are:
* developing a facility that checks for
dependencies between components and other
resources and ensures that these are satisfied
during runtime (or maybe just at installation time)
* working out how to package components into
easily deployable units (consider EAR files in
Enterprise Java)
* defining some kind of configuration to declare
dependencies between components and other resources
For example, a service interface "A" might have
an implementation class "AImpl". This implementation
might require a service with interface "B".
Also, If AImpl was doing something with SAX2,
it might require the org.sax.XXX packages. These
only come out-of-the-box with JRE 1.4, but are
also available elsewhere so they can be used with
JRE 1.1 up to JRE 1.3. So there is a set of
dependecies here that I would like to check
automatically, during runtimne (or possible only
once during installation of the components/resources).
We might declare the dependencies above with a
little XML (I'm just making up the package names
here):
<interface>
<class>org.jchassis.a.A</class>
<metadata><name>Version</name><value>1.00</value></metadata>
<metadata><name>Author</name><value>Bob
Bilby</value></metadata>
</interface>
<interface>
<class>org.jchassis.b.B</class>
<metadata><name>Version</name><value>1.01</value></metadata>
<metadata><name>Author</name><value>Mary
Hooha</value></metadata>
</interface>
<implementation>
<class>org.jchassis.a.impl.AImpl</class>
<metadata><name>Version</name><value>5.15a</value></metadata>
<metadata><name>Author</name><value>Fred
Whatsit</value></metadata>
<depends>
<interface>org.jchassis.b.B</interface>
<choice>
<jre>1.4</jre>
<module>SAX2</module>
</choice>
</depends>
</implementation>
<module> <!-- module = group of classes and packages -->
<name>SAX2</name>
<package>org.xml.sax</package>
<package>org.xml.sax.ext</package>
<package>org.xml.sax.helpers</package>
<depends>
<jre>1.1</jre>
</depends>
</module>
Presumably, each piece of configuration would
be stored with the approriate interface, implementation
or module JAR file ...
Anyweay, let me know if you have any ideas ...
Cheers,
Sam.
=====
Sam Stainsby
http://www.yahoo.promo.com.au/hint/ - Yahoo! Hint Dropper
- Avoid getting hideous gifts this Christmas with Yahoo! Hint Dropper!
|
|
From: <sjs...@ya...> - 2002-11-07 00:59:26
|
As the subject says. The is also a simple implementation of the Log service as well. Just need command line parsing and we're got something thats starting to look useful ... Read it and rejoice: stainsbs$ cat tmp-utest/results/TEST-*.txt | grep -e Testsuite -e "Tests run" Testsuite: org.jchassis.basic.AttributeMapTest Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.027 sec Testsuite: org.jchassis.basic.DefaultBasicServiceContextTest Tests run: 14, Failures: 0, Errors: 0, Time elapsed: 0.069 sec Testsuite: org.jchassis.basic.DefaultServiceTemplateTest Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.05 sec Testsuite: org.jchassis.basic.loader.XmlServiceConfigurationLoaderTest Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 0.272 sec Testsuite: org.jchassis.basic.ValueConverterTest Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.026 sec Testsuite: org.jchassis.log.simple.LogTest Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.049 sec Testsuite: org.jchassis.xml.simple.Sax2ParserTest Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.089 sec ===== Sam Stainsby http://careers.yahoo.com.au - Yahoo! Careers - 1,000's of jobs waiting online for you! |
|
From: <sjs...@ya...> - 2002-11-03 22:38:16
|
Hi all, Just to let you know what has been happending with JChassis this week: The basic infrastructure has been coded and is currenly being intensively unit tested. I expect to finish that today. After that, there are a few basic services to implement, the most important of which is the logging service. After that, the command line parsing service is the next important. These should be quite straightforward to implement, so I expect to get them finished this week. That's provided I don't get distracted by teaching activities too much! If I decide to do an I18N service, that will take extra time. I've put together a draft research proposal for my work at QUT. I'll send out a copy later. I don't have access to it until I dial-up to QUT later today. We may also be running a research project using JChassis as the basic for applications executing on Java-enabled robots. Another QUT project may be looking at JChassis running on an embedded system that also involves industry collaboration. This is all just being discussed at the moment. Cheers, Sam. ===== Sam Stainsby http://careers.yahoo.com.au - Yahoo! Careers - 1,000's of jobs waiting online for you! |
|
From: <sjs...@ya...> - 2002-11-03 22:28:53
|
Hi Fredrik, Thankyou for your interest in JChassis. JChassis does not currently meet the requirements you have specified. It is a generic framework at the moment, designed to cover the common needs of applications, whether they be clients, servers, GUIs or non-GUIs. The plan is to add GUI plug-in services in the future, built on top of the generic framework when it is stable. The "basic" framework is currently being unit tested and will be released within the next few weeks. If you are interested in collaborating on the GUI aspects of JChassis, please let me know and we will look at adding you to the team. We will be looking at the following "profiles" of JChassis once the "basic" framework is tested (not in any order): * JChassis for embedded systems * JChassis for servers * JChassis for clients * JChassis for P2P applications * JCHassis for distributed applications * JChassis for user-iterfaces (GUI or non-GUI) * JChassis for desktop applications ***** Again, thanks for your interest, and let us know what you decide. Cheers, Sam Stainsby JChassis Project Manager. --- fre...@pa... wrote: > Hello, > I am looking for a gui framework to use in my project > (tigerdb.sourceforg.net). > JChassis seem to be a good candidate. At the moment my wanted > functionallity > in a gui framewordk is this. > * Window management. Almost all applications have a Window-menu on > the menubar. > I want functionallity for register windows and switching between > different > windows. > * "Dirty"-management. In many applications you have frames and panels > that > have a save-function. When the sav menu item is selected all dirty > windows > should be saved. And if the application is closed the user should be > prompted > if he wants to save or discard changes. > * Editor management. Different java classes have different editors, > Telephone > number may have a JFormattedTextField and a Address may have a > JavaBean consisting > of several JTextFields. > > Does JChassi support anything of this, or should it be implemented as > services? > > > Regards, > Fredrik > > > _______________________________________________________ > Sök företag på Gula Sidorna > http://www.gulasidorna.se > > ===== Sam Stainsby http://careers.yahoo.com.au - Yahoo! Careers - 1,000's of jobs waiting online for you! |
|
From: <sjs...@ya...> - 2002-10-26 02:19:06
|
Hi all, After a brief pause (well, 2 months actually) I'm getting the hang of this lecturing stuff and finding myself with more time to work on JChassis. Even better than that, most of the semester 2 teaching work is over, and I'm not teaching in the summer semster. And, if you thought that was good (or even if you didn't care), as of last Friday, JChassis has become the subject of my research work at QUT, so not only can I work on it at work, but I may get an honours student and/or a research assistant to help me (i.e. slave away for me) next year! I have spent the last week and a bit implementing some of the JChassis "basic" infrastructure. This is coming on well. The XML configuration loader is implemented, but not tested. The basic service context is just a skeleton at the moment, but will probably be less complex to code than the loader was. I'd say I'm roughly half-way toward finishing the basic infrastructure. Of course, then there are the basic services (logging, command line parsing, etc.) to build after this, but they are prety straightforward and self-contained. Each would be an excellent task for a beginner JChassis developer ... hint, hint ;-) . We really need to start designing the technical documentation too if we are to get other developers involved. Will 'Retta and Susan join the team one wonders?? I seem to have lost Susan's email address :-( Anyway, hope you are all happy and well. Cheers, Sam. ===== Sam Stainsby http://careers.yahoo.com.au - Yahoo! Careers - 1,000's of jobs waiting online for you! |
|
From: <sjs...@ya...> - 2002-07-27 00:37:30
|
Hi all, Now things have settled down with my parents no longer staying and me settling into my new job (s.s...@qu... is a quick way of contacting me during a work day), I can get back to the good stuff ... Draft 1 of the designs for the following JChassis services have been finalised: * the command line parser service * the resource location service * the metadata service Please find them at: http://jchassis.sourceforge.net/v1/basic/doc/designs/cmdline-parser-service-design.xml http://jchassis.sourceforge.net/v1/basic/doc/designs/resource-location-service-design.xml http://jchassis.sourceforge.net/v1/basic/doc/designs/metadata-service-design.xml As usual, any review comments are welcome ... Cheers, Sam. ===== Sam Stainsby http://digital.yahoo.com.au - Yahoo! Digital How To - Get the best out of your PC! |
|
From: <sjs...@ya...> - 2002-07-07 22:28:20
|
Add Galeon on to the list of XML/CSS2 capable browsers. Since it has the same rendering engine as Mozilla, the level of support is the same. Doesn't look like CSS2 counters work on either, which makes numbered lists a bit difficult ... Galeon is looking in really good shape lately - and performs much better than Mozilla and my little Pentium 150 :-) ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-07-04 12:15:53
|
Hi all, The following documents are also almost at draft 1 status: "JChassis Basic Services: The Metadata Service Design" http://jchassis.sourceforge.net/v1/basic/doc/designs/metadata-service-design.xml "JChassis Basic Services: The Resource Location Service Design" http://jchassis.sourceforge.net/v1/basic/doc/designs/resource-location-service-design.xml "JChassis Basic Services: The SAX2 Parsing Service Design" http://jchassis.sourceforge.net/v1/basic/doc/designs/sax2-parsing-service-design.xml Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-07-03 22:30:56
|
Hi all, Its come to my attention that Internet Explorer (at least version 5.5) is crap at rendering XML with non-trivial CSS2 properly. If guess that leaves Mozilla, Opera and possible Netscape 6.x as viewers for to new docbook doco. Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-07-03 12:10:10
|
Hi all, The following documents are nearing draft 1 stage: http://jchassis.sourceforge.net/v1/basic/doc/designs/xml-service-configuration-design.xml and http://jchassis.sourceforge.net/v1/basic/doc/designs/xml-service-loader-design.xml plus two new design docs on the way - a resource locator service and a metadata storage service - I just need to format them in the new XML format. Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-07-01 11:07:51
|
Hi all, Work continues on the designs for the "basic services" stage. I am currently finishing the first draft of the XML configuration loader desing. The XML service configuration format is already in first draft form except I haven't written up a DTD for it yet. To see the new look documentation using DocBook XML and CSS2, check out: http://jchassis.sourceforge.net/v1/basic/doc/designs/xml-service-loader-design.xml To view this properly, you will need a browser that can render XML with CSS2 stylesheet support. This includes recent versions of Mozilla and Opera. Recent version of Netscape and IE should work too, but I haven't tried them. Let me know how it goes if you used one of these "untested" browsers. Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-06-20 03:54:35
|
Hi all, The document "Basic service requirements v0.1 draft 1" is attached for your perusal. As usual, any feedback/help/contributions/ideas are encouraged and welcomed ... Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-06-18 10:23:58
|
Just a quick update ... Work on the requirements for the basic set of JChassis services is continuing. I have attached the requirements doc, which can also be found in v1/basic/doc/requirements under CVS. This is still draft 1 in progress, but now includes a lot more than just the XML service configuration requirements ... its got modules and stuff :-)~~~ ANY feedback or help or contribution will be appreciated... Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
|
From: <sjs...@ya...> - 2002-06-15 23:53:20
|
Hi all, I have changed the licensing of JChassis to LGPL (http://www.fsf.org/licenses/lgpl.txt) instead of GPL. This will allow us to compete with other application frameworks that have less restrictive licenses, whilst still maintaining our right of attribution (the right to be recognised as the authors of the code) and our openeness. The main deciding point was that the popularity of open source today is a recognition that open source quality is good enough to compete with proprietary software just based on its superior quality (take Apache and Linux for example), and should not need "protecting" by the GPL. That is, part of the idea of the GPL is to force companies to start making their source open - I now believe they are more likely to do this because of perceived quality and process improvements in this approach, rather than being coerced because they need some GPL software package for their product. Anyway, all source, script and build file headers have been updated, as have the project web site and the Trove categorisation. I have put some templates in the doc/templates area in CVS. I have not bothered changing the prototype code. This is not meant for release anyway. Using the GPL there will help protect anyone from snatching some of the future-oriented code there and going commercial with it before we can release it in JChassis. Eventually, all of that functionality will move to a JChassis release (and hence LGPL) anyway. Other news: I have checked in an update tp the service configuration requirements doc. I have labelled this as draft 1. http://jchassis.sourceforge.net/v1/basic/doc/requirements/xml-service-configuration-v0.1-requirements.txt I expect in the end there will be one big "basic service requirements" doc that will incorporate this plus the requirments for the actual "basic services" (logging, command line parsing, etc.). Cheers, Sam. ===== Sam Stainsby http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
