Re: [Leaf-devel] developer.xml
Hi Mike At 08:43 30/08/02 -0700, Mike Noyes wrote: On Fri, 2002-08-30 at 08:18, Julian Church wrote: I got a bit confused with editing the log file, so didn't put anything at all, and I don't know what to do to control the version numbers either - the CVS says the file is at 1.1 but I was going to call this version 1.2.1. Log messages are important to let other project members know what you did with your modification/addition. You can see examples of this in our cvs-commits list archive. http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/ Thanks for the link. I see the kind of thing I should have done now. Is there any way to go back and amend my log message? The CVS version numbers are for CVS, and have little or nothing to do with release version numbers. Right - I may have messed up a bit then. I've based my version numbers on those I found in CVS for the original developer guide, developer.rtf. From what you say that might have been a mistake. Tags are used to indicate release versions. Tags? You mean in the XML, or is this another CVS thing? Maybe someone else will have the time to attend to the creation of the other formats. I'm still working on it - I'll let you know if I get anywhere. cheers Julian -- [EMAIL PROTECTED] www.ljchurch.co.uk --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] developer.xml
On Mon, 2002-09-02 at 03:55, Julian Church wrote: At 08:43 30/08/02 -0700, Mike Noyes wrote: Log messages are important to let other project members know what you did with your modification/addition. You can see examples of this in our cvs-commits list archive. http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/ Thanks for the link. I see the kind of thing I should have done now. Is there any way to go back and amend my log message? Julian, Yes. $ cvs admin -m 1.1:your revised commit message developer.xml Changing A Log Message After Commit http://cvsbook.red-bean.com/cvsbook.html#Changing_A_Log_Message_After_Commit The CVS version numbers are for CVS, and have little or nothing to do with release version numbers. Right - I may have messed up a bit then. I've based my version numbers on those I found in CVS for the original developer guide, developer.rtf. From what you say that might have been a mistake. I looked in David's rtf releases, and I was unable to locate revision numbers. I'm fairly certain this document was updated a few times. You should talk with David about the revision history. Tags are used to indicate release versions. Tags? You mean in the XML, or is this another CVS thing? It's another CVS command. $ man cvs tag -- Specify a symbolic tag for files in the repository. By default, tags the revisions that were last synchronized with your working directory. (Changes repository directly; uses working directory without changing it.) Marking A Moment In Time (Tags) http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_ -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [Leaf-devel] Webbased configuration
Everyone, I propose the creation of a config tree in our CVS src tree. All of the components necessary for this project can be placed there, and write access granted to team members. The structure of the config tree is left to the team members discretion. Example: leaf/src/config + | /core | /text | /ncurses | /web | /doc Alternate: leaf/src/config + | /sh-httpd | /weblet | /lrcfg | /acfg | /apkg On Sun, 2002-09-01 at 23:13, Richard Amerman wrote: We can take a look at how far I have gotten and decide if it is on track and ready to put in CVS. I have mainly been working on abstracting everything so that it is easy to construct content in a dynamic way. I'm interested in modules that include the configuration piece, but also inhanced log viewes, live statistics in as much of a dashboard fashion as possible, and other similar ideas. While some of these modules may be sizable, I, like the rest of you wish to keep the base system as small as possible -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] More Docbook XML conversion
Hi All I'm about to start work converting another document to Docbook XML. I think I'm moving onto the install guides for the different distributions that are in the doc/guide part of the cvs tree. My initial instinct was to start with the most recently released distribution, and work back, but the formatting of the Bering guide resembles a lot of guides that I know were originally authored in DocBook, so I'm going to start with the Dachstein Installation guide while I investigate to avoid uselessly duplicating work. I'm still working on getting a Docbook -- PDF/HTML etc system going. Once I've got my full-size Linux (Debian 3.0) box up and running at home things should start to move. thanks all Julian -- [EMAIL PROTECTED] www.ljchurch.co.uk --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] More Docbook XML conversion
On Mon, 2002-09-02 at 10:13, Jacques Nilo wrote: Hi Julian and list FYI the Bering documentation (users and install guides) and my package doc are available in XML from http://leaf.sf.net/devel/jnilo/xml I will move them to CVS when I will have some time. Jacques, I just did this for you. The XML source for both Bering guides is now in our CVS repository. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/doc/guide/install-bering/ http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/doc/guide/user-bering/ -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Webbased Configuration
Hi, some remarks about using forth: - certainly forth is missing all that nice pattern matching like awk or perl, all this has to be coded. - I assume that even arrays are not available in forth - because forth uses very unusual semantics (reverse polish notation) it is not easy to understand and to maintain (you have always to keep in mind, what is in this moment at which position on the stack). mawk is 49K compressed perl4 is 136k compressed Manfred Eric Wolzak schrieb: Hello all, I agree with Erich that it would be wise to get an architecture before thinking about the implementation. IMHO it should be : -easy to configure. -flexible , so adding new packages is possible without much programming. -flexible 2- so it is possible to use the same system on oxygen, bering ,dachstein, Wisp by merely changeing the Tools configuration file. -useable also on slow systems. I thought about it sometime and came up with a kind of a flowchart ( I am afraid , I am not good at Ascii art, so I put it up my webserver: http://wolzak.de/leaf/config1.jpg After some looking at this graphic I noticed that 1. The cgi and the primary Part have a common Trunk Useing a template with the variables to create a html or config file. 2. The intelligenz of this programm is on the firewall. With each call , there is a lot of computeing. 3. The configuration Template is created dynamically, but doesn't change . So why not create it offline or better of the box. So I came up with the next Idea: http://wolzak.de/leaf/config2.jpg The first Action is created on whatever computer under whatever system to create the Parsing rules The HTML Template and the Config Template. The Idea behind this is that as soon as the external Parser is written, it can create any HTML.template , parsing rules or config template just by creating a modules or package config file. What is this parsing rule thing. This is a file build something like `grep -q ^noauth` var1=noauth var2=$NETWORK_INTERFACE var3=`ls /etc/` now after running this shell script or any other (Forth, Java alike) you would have the variables var1, var2, var3 set Those are combined with the HTML template just by catting the template with the variables at the appropriate place. What kind of place is told by the Module configuration file. The kind of field the vars are placed in is destined by the kind of data it expect ( options, filenames, freetext etc) The Modules Config file (which could also be a database can be different formats: 1. xml in that case the template, parsing rules and config template can be generated by merely applying a xsl stylesheet. 2. something with different fields example: field 1 = 0 (optional) /1 demanded field 2 = 0 (single) /1 (repeatedly possible) field 3= variable looks like 1 NAME=value 2 NAME value 3 value 4 filename 5 name= (value1 or value2 or value3) 6 name (value1 or value 2 or value3) 7 ( value1 or value2 or value 3) 8 ... 3 Database. I think I prefer the first option (xml). ... Any Comments , Reactions, flames Eric Wolzak member of the Bering Crew. --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Manfred Schuler Beerenweg 4 31275 Lehrte Tel.: (0 51 75) 66 54 Fax: (07 21) 1 51 22 22 17 E_Mail: mailto:[EMAIL PROTECTED] --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
