Masatake YAMATO <[EMAIL PROTECTED]> writes: >> 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 > 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" > These are rather user manual but not reference manual. tla-browse is > used in the documents. I've written nothing about tla-archives and > friends in the documents. > > BTW, About 2.0, I think we have to split xtla.el more smaller files. > > +-----------------------------------------------+ > | | > | USER INTERFACE | > +-------+---------------------------------------+ > | | | > | | | > | | | > | | xtla-middle | > | | | > | | | > | +---------------------------------------o > | | > | xtla-core | > | | > +-----------------------------------------------+ > > USER INTERFACE includes, > > 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. I like the idea of providing a xtla-cmd.el. It is also a good starting point to split some functionality off. We can order the functions in a way they are listed in "tla help". I there are no objections, I will do that split. Stefan.
