Re: Search engine (was Wiki)
On Wednesday 05 May 2004 2:28, Derek Atkins wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > The archives are in a sub-domain of gnucash.org but how is that > > configured? > > machine1 is "gnucash.org", "www.gnucash.org", and "mail.gnucash.org" > machine2 is "cvs.gnucash.org" and "lists.gnucash.org" > Machine2 (cvs,lists) hosts cvsweb and mailman/pipermail > (the latter being the list archives). Right now machine1 (www) has > very limited disk space (at least until Linas upgrades his machine). > Machine2 is also SIGNIFICANTLY faster! So I'd like to have the search engine on machine 2 under lists.gnucash.org using local filesystem access - read, no write access required for the script except to upload new versions. > So, in terms of performance and disk space, using machine2 is the much > better option (also, it's the one I maintain ;) However it means it's > not at www.gnucash.org. As with the doxygen docs, it's only a link away. Besides, I can easily give the search engine the look and feel of the main GnuCash site - you'll only be able to tell the difference from the URL. I might be learning QOF but HTML, CSS, SSI and PHP are second nature, even if I say so myself. I don't do Flash and I'm no artist but if you want strict compliance HTML, XHTML, CSS, CSS2, SSI, PHP, Perl, XML, WML then take a look at codehelp.co.uk and www.dclug.org.uk - it's all my own code, most hand-crafted in Vi. I'd be lying if I said it was hard to do. > IMHO it would be "easier" for the docs to be generated on the same > machine where the cvs archives are kept. It's a local matter to > update the tree, so there's no network usage, and that machine is > significantly more powerful. Same applies for the search engine - the faster the script can access the HTML archive, the faster the search returns the answer. > But I agree with you.. Having the docs live at http://cvs.gnucash.org/... > is just fine, so long as there's a link off the main gnucash site. > Linas may not agree, however, if he wants to keep the "gnucash look at > feel" of the docs. But I don't know how hard that would be to get > doxygen to use SSI. It might be easier with frames. As with all other 'machine-produced' HTML, I've always found it better to use a Perl script AFTER generation, not to dabble in the config. The machine output is very standard and very predictable - ideal country for a pattern match that replaces the default doxygen or
additional doxygen pages (was: Re: QOF help!)
Josh Sled wrote: I'm not sure how to use doxygen for architectural docs... Could you provide an example or pointers to docs that describe it? http://www.stack.nl/~dimitri/doxygen/commands.html Using \defgroup , \addtogroup , \example , \mainpage and \file , and a bit of convention, one could build higher-level structural docs along-side the lower level file/function/variable docs. Just a thought about how I usually add "extra" documentation pages (the result is similar to the pages shown here http://simthetic.sourceforge.net/simthetic/api-doc/html/pages.html ): 1. Create a new text file with your documentation text 2. At the beginning and end of this text file, insert the c comments for doxygen, i.e. /** \page page_label My extra documentation page [... text goes here ... ] */ 3. Add the file name of the text file to the INPUT tag of the doxygen configuration file (Doxyfile). That's it. 4. Potentially, use more doxygen commands inside that text file, e.g. \section and \subsection. Christian ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
DAMMIT! I checked all the .scm files, but not additional stuff that didn't have a .scm ending. Damn Damn Damn! Thanks, let me fix this. -derek Herbert Thoma <[EMAIL PROTECTED]> writes: > Derek Atkins schrieb: >> Yes, SuSE decided to build guppi inside the gnucash package. Don't >> ask me why. Ask them. > > Presumably because GnuCash is the only application that uses guppi ...? > >> > OK, I compiled this >> >>From source like I did in the old 1.6 days ... There was another problem >> > with slib: slib comes as version 3a1 and caused a compilation error. I >> > installed 2d4 and this worked fine. >> >> The slib3 issue should be fixed in 1.8.9. > > Nope. I have a fresh checkout from CVS and get the following error: > > make[3]: Entering directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src/engine' > chmod u+x ./iso-currencies-to-c > GUILE_LOAD_PATH=: srcdir=. ./iso-currencies-to-c > ERROR: slib:require unsupported feature format > make[3]: *** [iso-4217-currencies.c] Fehler 2 > make[3]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src/engine' > make[2]: *** [all-recursive] Fehler 1 > make[2]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src' > make[1]: *** [all-recursive] Fehler 1 > make[1]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work' > make: *** [all] Fehler 2 > > Herbert. > -- > Herbert Thoma > Group Manager Video > Multimedia Realtime Systems Department > Fraunhofer IIS > Am Wolfsmantel 33, 91058 Erlangen, Germany > Phone: +49-9131-776-323 > Fax: +49-9131-776-399 > email: [EMAIL PROTECTED] > www: http://www.iis.fhg.de/ > > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
Derek Atkins schrieb: > Yes, SuSE decided to build guppi inside the gnucash package. Don't > ask me why. Ask them. Presumably because GnuCash is the only application that uses guppi ...? > > OK, I compiled this > >>From source like I did in the old 1.6 days ... There was another problem > > with slib: slib comes as version 3a1 and caused a compilation error. I > > installed 2d4 and this worked fine. > > The slib3 issue should be fixed in 1.8.9. Nope. I have a fresh checkout from CVS and get the following error: make[3]: Entering directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src/engine' chmod u+x ./iso-currencies-to-c GUILE_LOAD_PATH=: srcdir=. ./iso-currencies-to-c ERROR: slib:require unsupported feature format make[3]: *** [iso-4217-currencies.c] Fehler 2 make[3]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src/engine' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/home/TMA/gnucash/gnucash_cvs/gnucash_work' make: *** [all] Fehler 2 Herbert. -- Herbert Thoma Group Manager Video Multimedia Realtime Systems Department Fraunhofer IIS Am Wolfsmantel 33, 91058 Erlangen, Germany Phone: +49-9131-776-323 Fax: +49-9131-776-399 email: [EMAIL PROTECTED] www: http://www.iis.fhg.de/ ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Search engine
Neil Williams <[EMAIL PROTECTED]> writes: > So I'd like to have the search engine on machine 2 under lists.gnucash.org > using local filesystem access - read, no write access required for the script > except to upload new versions. Yep, that's what I think, too. Both the doxygen docs and search engine should be on cvs/lists. I'm planning to work on the doxygen scripts relatively soon. > Same applies for the search engine - the faster the script can access the HTML > archive, the faster the search returns the answer. Ahh, so it's doing a real-time grep, effectively? Ok, that makes sense. That also explains why you don't think you need an index. Honestly, I don't know much about search engines, but I was under the impression that you could make multiple indices that speed up searches. But.. eh. That explains the disconnect. We're on the same page, now. > Yuk! I may be good at PHP but I know when I need testing and speedy updates to > my code!! Sorry, I've done this before and it simply did NOT work. I really > do not want to get involved in that morass again. Ok, how about this: CVS access to a "search engine" module which gets pulled out into the web server? This way: 1) you can make changes to the server in near-real-time 2) we get a change history of the script 3) it still keeps the server protected Would this be "good enough" for you? >> Let me know what other information you need. > > absolute path names, the mail archives are /var/mailman/archives/public//... What other paths do you need? > ability to use phpinfo() as and when required (without > leaving it there for the entire world to see), I have no idea what this implies or how to grant you this access. > and access. Would CVS be sufficient? Assume that your commits are auto-pushed into some area. This way you can still upload changes to your script to fix bugs. > Sorry, I really > cannot work without FTP or preferably SSH. I'm NOT going to sit and download > the archive page by page to create a test site and I don't work without being > able to do my own updates. FTP allows me to download an accurate copy quickly > and upload script updates simply, SSH allows me to compress the copy into a > tarball, download that and delete the temporary tarball. Either way, I really > have tried to do this without access and it is a process WORSE than learning > QOF. We really, really, truthfully do NOT want to do go there! This is a > simple job that can be done today, IF some sort of FTP or SSH user access is > available. Just an ordinary user, but if this isn't available then sorry, I > really can't help with the search engine. > >> No offence, but right now not >> even the developers have shell access to the server. > > Pity. I've got a script that is just waiting to be adapted but I really cannot > proceed without some access. With the timezone differences as well, I will > not be able to fix bugs unless I can update in real time from my own box. > (Yes, there may well be bugs, nobody writes perfect code first time!) If you send me an ssh key I can set up CVS access in a matter of minutes, and then I can set up a job to pull out the search script whenever there are changes made to CVS, allowing easy updates. One reason I'd like to audit the scripts and limit access is that I'm a bit paranoid about system security. PHP has never been a strong winner in that area. So I'm obviously a bit concerned. >> > With regard to: >> > http://www.gnucash.org/en/contribute.phtml >> > We even need someone to make sure that the mail archives are running >> > correctly, and that recent mail is getting indexed & is searchable. >> > (webmaster selected) >> > >> > Is that bit about checking the operation of the mail archives still a >> > problem? From only a casual use of the archive, recent messages seem to >> > be added very quickly. The 'searchable' I can solve for you. >> >> No, it is not a problem any more. The lists are running fine, and the >> archives are running fine. > > So the contribute script is to be updated . . . . ? Well, it needs to be updated.. Whether it WILL be is something different.. Access to www.gnucash.org is rather limited. :( -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: additional doxygen pages (was: Re: QOF help!)
Ok, the docs are now auto-generated every night from CVS and are available on the web: http://cvs.gnucash.org/docs/HEAD/ Enjoy, -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Search engine
On Wednesday 05 May 2004 7:05, Derek Atkins wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > Same applies for the search engine - the faster the script can access the > > HTML archive, the faster the search returns the answer. > > Ahh, so it's doing a real-time grep, effectively? Yes. PHP uses readdir() and then fopen() in a loop. > Ok, that makes sense. > That also explains why you don't think you need an index. Honestly, > I don't know much about search engines, but I was under the impression > that you could make multiple indices that speed up searches. I think that's more for database backend searches or where the search terms are strictly defined: price between X and Y or catalogue ID etc. Creating and maintaining indices outside a database is not fun! > But.. eh. > That explains the disconnect. We're on the same page, now. Great - I was getting a tad confused. :-) > Ok, how about this: CVS access to a "search engine" module which gets > pulled out into the web server? This way: > > 1) you can make changes to the server in near-real-time > 2) we get a change history of the script > 3) it still keeps the server protected > > Would this be "good enough" for you? Novel idea! It'll work with one proviso - could you make a tarball of: https://lists.gnucash.org/pipermail/gnucash-devel/2004-April/ https://lists.gnucash.org/pipermail/gnucash-user/2004-April/ please? I need some real files to test the adapted script. If you could put the tarball somewhere (any site will do) and let me know the URL, it'll be easier than sending by email - I'm aware these are not small archives. > >> Let me know what other information you need. > > > > absolute path names, > > the mail archives are /var/mailman/archives/public//... Great, thanks. I'll reproduce the same structure locally. > What other paths do you need? > > > ability to use phpinfo() as and when required (without > > leaving it there for the entire world to see), > > I have no idea what this implies or how to grant you this > access. That's OK. It's a simple file that PHP treats as a special function. It simply outputs the entire list of PHP and server environment variables, PHP config and status messages. That's why it isn't good to have around all the time! One way round this is simple - the info doesn't really change, so if you create this single line file: and call it phpinfo.php then put that somewhere in the webspace for the lists site (so that it picks up the correct environment for my script), send me the HTML output and delete the file. > > and access. > > Would CVS be sufficient? Assume that your commits are auto-pushed > into some area. This way you can still upload changes to your script > to fix bugs. OK. > If you send me an ssh key I can set up CVS access in a matter of > minutes, and then I can set up a job to pull out the search script > whenever there are changes made to CVS, allowing easy updates. You should have just received that. > One reason I'd like to audit the scripts and limit access is that I'm > a bit paranoid about system security. PHP has never been a strong > winner in that area. So I'm obviously a bit concerned. I can use Perl if you prefer. That script is the one running www.codehelp.co.uk searches and was used on dclug - it needs the time-aware code added and it was easier to do that with a new one in PHP for the dclug site. It's too late this side of the pond to finish the script now (the problems of international development eh?) so let me know the CVS commands / URL's and I'll start work on it on Friday (more paid work tomorrow). Let me know if you want me to do this in Perl asap. Ta. > > So the contribute script is to be updated . . . . ? > > Well, it needs to be updated.. Whether it WILL be is something > different.. Access to www.gnucash.org is rather limited. :( :-( -- Neil Williams = http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3 pgp0.pgp Description: signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Search engine
Neil Williams <[EMAIL PROTECTED]> writes: > Novel idea! It'll work with one proviso - could you make a tarball of: > https://lists.gnucash.org/pipermail/gnucash-devel/2004-April/ > https://lists.gnucash.org/pipermail/gnucash-user/2004-April/ > please? I need some real files to test the adapted script. If you could put > the tarball somewhere (any site will do) and let me know the URL, it'll be > easier than sending by email - I'm aware these are not small archives. Done. I'll send it in a private mail. The Archives aren't actually THAT large. The -user and -devel archives for 2004 are a total of about 2.5MB uncompressed. The gzipped tarball is only 250KB. > One way round this is simple - the info doesn't really change, so if you > create this single line file: > > and call it phpinfo.php then put that somewhere in the webspace for the lists > site (so that it picks up the correct environment for my script), send me the > HTML output and delete the file. Done. I'll send this in another private email. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Welcome to the GnuCash Developer gene pool
Welcome to cvs.gnucash.org. You now have an account, codehelp, which you can use to access the CVS sources. You can now access the sources by: cvs -d :ext:[EMAIL PROTECTED]:/home/cvs/cvsroot ... You will also have mail forward automatically. Good Luck, The GnuCash Server Maintainers ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
developer account created
This is an automated e-mail via the add-new-developer script ($Revision: 1.6 $). Developer account Neil Williams has been created: <[EMAIL PROTECTED]>. Admins (root) should update CVS access for this user. Welcome to the team. -- (script run by root). ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
