[Embedlets-dev] Re: CVS Code tree

[Andrzej J. T. <an...@ch...>]

Chris asks:

> When are you going to post the full source tree to the Embedlets repository?
> Until you do this it is impossible for anyone else to do any code development.
> We will have no revision control until this is done as well.

Soon.....in the meantime, the whole source tree is in the zip file.....so go 
look at it and get the feedback/discussions going!  I see that as the next 
step, since it would be wise to review what currently exists before we go 
building much on top of it.

I may be a decent developer, but I would not suggest that you accept the 
current stuff on face value alone, flattering though this might be.

> I know that it is not your intention to code the complete project yourself!

Nope....not enough time nor interest for that. ;-)

> See my and Bill's post on the CVS repository. We cannot do anything with a zip
> file, without risking overwriting our work.

Sure you can...it's totally self contained so you can review it and provided 
feedback and discussion, which is what I think is needed before we start 
hammering out reams of new code/stuff.

Not gonna post the code base in CVS (since I'm one version ahead) until the 
source code formatting (Jalopy) stuff is in place (coming soon) and I start 
to see some feedback from the group on the current stuff (up to you guys).

Brill chimes in with a similar comment:

> Would you mind posting the source to CVS rather and the zip files (in a
> proper build environment)?

Soon as I start to see some feedback on the current stuff.  The core 
interfaces and design decisions need to be reviewed and agreed before we go 
helter skelter building on top of them.

I also need to get the Jalopy source formatting in place first, to ensure 
that all checked in code is in line with the code conventions.

> At the moment I've got ant set up to check out the zips, decompress them
> into a build dir, etc... but you can't do any diffs, version checking, etc. on
> the zip files ;) If you are willing, I will prepare a build env. for you using
> the current zipped packages, which you can then modify (I have a bit of spare
> time right now).

No need, thanks....this is next on my list with the Jalopy stuff and is part 
way done already.

Keep in mind, I posted these releases for DISCUSSION PURPOSES only....not to 
be used as the basis for further development (yet).  My ideas on the 
interfaces, lifecycle and such are not necessarily the best or the be-all, so 
need to be reviewed.  Besides, before you can start building on new stuff 
(optional services and the like) you need to understand what is already 
there, and how it works (eg. how to you structure an Embedlet Service), which 
should naturally lead to some discussion/review.

Let's not get ahead of ourselves, in our rush to develop our favourite kewl 
component/addition.  This first cut was just intended a proof of concept and 
a kick-start. It SHOULD NOT be accepted as is!

Before we cast it in concrete (by building on top of the current interfaces 
too much, which will make it much harder to change the underlying contracts), 
let's make sure that they are as good as possible, 'cause to do anything else 
will compromise our plan to make Embedlets a defacto and distruptive standard 
that becomes widely adopted.

The bane of many Open Source projects is the tendency to hack too much code 
too early, instead of doing documentation, design review and the like.  We've 
got enough code now (too much probably, since I'm obviously not immune to the 
"let's sling more code" syndrome either ;-) ), and it's time to step back and 
ensure that we are going down the optimal path.

So please go take a look at what's there....pick it apart...make 
suggestions....ask questions....critique the interfaces and design choices, 
as a first step.  This shouldn't take long.....but the effort will pay off 
handsomely down the road.

Then we'll be assured that the platform we are building on is optimal as we 
start to flesh out all the rest of the pieces that need doing (and there are 
many!).

Soon as I get the Jalopy source reformatting tasks running to my 
satisfaction, I will populate the CVS "properly".....but please....in the 
meantime, start the review process!





Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com