> >> So, I think xtla-browse full integration with the rest of xtla could
> >> be delayed untill the 1.0 is out.
> >
> > Do you mean we should remove xtla-browse.el from xtla-1.0.tar.gz?  If
> > so, I don't agree with you. I already write much documents based on
> > xtla-browse.el.
> >
> > If tla-browse is bundled to xtla-1.0 as its *optional* part, I agree
> > with you. Another request is to add the latest tree-widget.el to xtla
> > like ewoc.
> 
> I think we should support older emacs versions (21.x) out of the box.
> To make tla-browse usable without any hurdles we should incldue
> tree-widget.el.
> 
> > In stead I will make efforts for
> >
> > 1. Support Emacs 21.3 with the latest tree-widget.el in tla-browse
> > 2. Support XEmacs with the latest tree-widget.el in tla-browse
> 
> Fine.
> 
> To summarize:
> * Add tree-widget.el
> * Keep tla-browse as optional part

My idea is to add only tree-widget.el.
I will not add bitmaps/pixmaps bundled with tree-widget to xtla.
I'll add tree-widget.el and write about it in INSTALL tonight.

> > The biggest question is documentation. Will we fill the texinfo file
> > till 1.0? The documents I'm writing are
> >
> > - XTLA Bootstrap
> > - Start a project with XTLA
> > - Branch the project with XTLA
> > - Run a Project in Anarchy Development Style
> 
> Thanks for the efforts.
> I will add a section about:
> "Tracking a tla project with XTLA"

Good idea.

Different from programming, I think it is not so easy to write
documents collaboratively.

So I propose splitting the documentation process into two stage

- Each developer writes a document about a topic which s/he think
  interesting separately from other developer

- Compile them into a single info file.

BTW, does anyone know a good Free software or Open source magazine?
We can contribute(good term?) articles.

> > xtla-cmd.el: Simple one shot command like tla-commit, 
> >           tla-insert-arch-tag, tla-my-id
> > xtla-bookmarks.el
> > xtla-inventory.el
> > xtla-diff.el
> > xtla-revisions.el
> > xtla-twbrowse.el
> > xtla-bbbrowse.el
> > xtla-gnue.el
> >
> > xtla-middle.el includes middle level functions shared
> > by USER INTERFACE layer. 
> 
> I think you have found a nice way to split the functionality.
> However we need no hurry in doing the split.

Yes. I'm taling about 2.0 in which tla-browse becomes essential part
of xtla.

Masatake

Reply via email to