1. Obtaining the Aspirin jar files and adding them to the classpath,
https://aspirin.dev.java.net/files/documents/1407/6519/aspirin-0.6.6.zip
2. Downloading and running witl 0.1 to test it out,
http://sourceforge.net/project/showfiles.php?group_id=143099&package_id=157141&release_id=340223
3. Opening the witl project in eclipse using the cvs repository, and,
http://witl.sourceforge.net/2005/07/using-cvs-in-eclipse.html
4. Improving, compiling, and running the witl code.
Thank you very much!
Isaac4given
isAAc4.com
Let the Lord Jesus be magnified!
Thanks for accepting me into the team. I've been looking over the
code, and wanted to post my thoughts.
It looks like at this point we've been figuring out how the peices
actually work, and have gotten a working prototype up and running.
I'd like to propose moving into an architecture, so that we can write
plugins and stuff easier.
In particular, the piece that I think would be most helpful right now
would be a scheduler. At present, it looks like we're just setting the
next time on a thread, and letting the thing run.
Besides the proposal below, I was also wondering if there a roadmap
of features and stuff that we're looking to add? Or is it pretty much
ad hoc right now?
My proposal:
WitlApp
Kicks off Scheduler thread
Adds tasks
Scheduler thread
Manages task list
Poll each task to see if it should execute.
ITask(Interface)
execute()
shouldExecute(Date currTime)
Generic task interface. Then we can extend to do other stuff too.
Basically, has functionality to check if it should execute, and then
function to execute.
Mailer implements ITask
Text,dummy, aspirin extends Mailer
ScreenCamera
Does screen captures.
What do you guys think?
Koby
good changes to witl, discussed in this group, are committed to the
repository by members of the SourceForge.net witl team. These
trustworthy members have "commit" access to the repository, in which
all real development work is done.
if you would like to become a team member, please see the witl "Help
Wanted" page:
http://sourceforge.net/people/?group_id=143099
notice: please include a concise and informative comment with every
change committed to the repository. changes submitted without good
comments may be rolled back. please review the existing comments in the
repository for examples of good comments.
repository id:
:extssh:<username>@users.sourceforge.net:/cvsroot/witl
cvs host server:
cvs.sourceforge.net
path to repository:
/cvsroot/witl
authentication:
ext
connection type:
extssh
*the cvs login and password is the same as your SourceForge.net login
and password.*
for more information, please see:
Basic Introduction to CVS and SourceForge.net (SF.net) Project CVS
Services:
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
Introduction to SourceForge.net Project CVS Services for Developers:
http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1
Instructions for installing and configuring a variety of CVS clients
may be found in:
http://sourceforge.net/docman/?group_id=1
Here is a screenshot of witl cvs access setup in Eclipse for the sf.net
login name "i4g":
http://witl.sourceforge.net/2005/07/using-cvs-in-eclipse.html
(Click on the little picture for a bigger picture.)
Don't worry too much about the versions.
witl 0.1 requires Aspirin version 0.6.6.
I've been using Windows XP, and Java Standard Edition Version
1.5.0-beta2 (build 1.5.0-beta2-b51.)
I'm sure older Java will work because witl uses few advanced features
of the language (it does use the JavaMail APIs.)
I'm also sure other Operating Systems will work, because witl is pure
Java.
I happen to be using Eclipse Platform Version: 3.0.1 Build id:
200409161125.
Eclipse Java Development Tools Version: 3.0.1 Build id: 200409161125
Eclipse Modeling Framework (EMF) Version: 2.0.1.M200409161148 Build id:
200409161148
Eclipse Graphical Editing Framework Version: 3.0 Build id: 200408311615
Java EMF Model Version: 1.0.2 Build id: 200412091401
Visual Editor Version: 1.0.2 Build id: 200409191449
I'm using the CVS client built into that version of Eclipse, and the
CVS server hosted on SourceForge.net. CVS version are pretty standard.
Thank you.
Let the Lord be magnified!
We mostly use the discussion group for communication. This way we can
publicly discuss questions suggestions and everything.
Let's use email for important alerts when people aren't checking the
discussion group, and for personal communication instead of public
communication.
We mostly use the blog to announce and state facts like bugs:
The blog is more for announcements which don't really require
discussion, and real chatter is done in the discussion group.