You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <ben...@id...> - 2004-05-22 12:10:31
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Jonathan F. <jf...@ac...> - 2003-05-05 14:46:39
|
Eric Arnoth wrote: > Jonathan: > >>At Python UK it was recommended that I visit >> http://docutils.sourceforge.net >> >>Highly relevant. > > Wow. I'm very impressed with this module. How do you feel this impacts > PyTeX? Can we tie in with it, does it make this project obsolete (doubt it), > or is it just another tool for a different text-related task...? > > For what I want to see in PyTeX, the ability to create a document by making > function calls, I don't think this is a competing project. The main focus of > it seems to be a simplified way for a human to generate a docuement. I'm > looking for an easier way to make handsome reports in daemons & lengthy > scripts. Granted, I've only spent 30 minutes looking into the docutils stuff > and doing the 'hello world' type stuff... > > What's your take? I think that we can learn a lot from Docutils. I'm a great fan of HML (human markup languages) such as TeX and LaTeX. XML uses the same markup for the small as for the large, which is hard on the eyes. Docutils wish to create HTML, XML and TeX from plain text (i.e. HML). It says so on their Sourceforge home page. Analogy with PostScript may be helpful. Many applications generate PostScript, by using library calls. Put another way, suitable structures can be serialized into PostScript. I'd like a similar interface to TeX. To me, it seems that we have two overlapping projects. Jonathan |
From: Eric A. <ea...@co...> - 2003-04-29 00:10:30
|
Jonathan: Thanks for the links, they are very helpful. =20 On Monday 28 April 2003 13:19, you wrote: > http://www.linuxjournal.com/print.php?sid=3D6800 > reports Guido as saying tabs should not have > allowed for indentation. =09# Tabs should not have been allowed for indentation. Or at the very l= east, =09mixed tabs and spaces should not have been allowed. It's worth pointing out the second half of that statement, but it really = isn't=20 a big deal. A quick Google for 'python tab indent' gave me what I needed= : =20 vi settings to do spaces instead of tabs when I press the 'tab' key. We'= ll=20 use spaces. Done and done. :-) > At Python UK it was recommended that I visit > http://docutils.sourceforge.net > > Highly relevant. Wow. I'm very impressed with this module. How do you feel this impacts=20 PyTeX? Can we tie in with it, does it make this project obsolete (doubt = it),=20 or is it just another tool for a different text-related task...? For what I want to see in PyTeX, the ability to create a document by maki= ng=20 function calls, I don't think this is a competing project. The main focu= s of=20 it seems to be a simplified way for a human to generate a docuement. I'm=20 looking for an easier way to make handsome reports in daemons & lengthy=20 scripts. Granted, I've only spent 30 minutes looking into the docutils s= tuff=20 and doing the 'hello world' type stuff... What's your take? --=20 Eric I. Arnoth CISSP (http://www.isc2.org) =20 ea...@co... =20 http://mywebpages.comcast.net/earnoth =A4=F8,=B8=B8,=F8=A4=BA=B0*=B0=BA=A4=F8,=B8=B8,=F8=A4=F8,=B8=B8,=F8=A4=BA= =B0*=B0=BA=A4=F8,=B8=B8,=F8=A4=F8,=B8=B8,=F8=A4=BA=B0*=B0=BA=A4=F8,=B8=B8= ,=F8=A4=F8,=B8=B8,=F8=A4=BA=B0*=B0=BA=A4=F8,=B8=B8,=F8 |
From: Jonathan F. <jf...@ac...> - 2003-04-22 19:02:32
|
Hello This message describes a prototype socket interface to the TeX daemon. Refer to Lutz, Programming Python (2nd edition) for details and for some examples to follow. The Python Reference Manual is probably just as good, but I like bound printed pages. * Overview To use the TeX daemon, open a connection to the server socket, and send to it a suitable string. The TeX daemon will then process the string. If required, it will send dvi back to the client. At the end of the transaction, the connection is closed. * Opening and closing the socket Client will open connection to server, as in Lutz p528. Client will send the whole string to the server. Client will use shutdown(1) to disallow further sends. Server will read the whole string. Server will use TeX to process the string. Server will read resulting dvi. Server will process dvi as requested by client's string. * Suitable strings A suitable string consists of 3 lines, followed by TeX code. suitable_string = protocol + tex_format + forward + tex_code protocol = 'prototype 001\n' tex_format = 'plain\n' tex_format = 'latex\n' tex_format = '/home/jfine/work/paper03.fmt\n' tex_code = r'''any valid \TeX\ code for the chosen format. ''' forward = command + options + '\n' Some sample commands forward = 'return\n' # send dvi back to client forward = 'preview\n' # send dvi to a previewer forward = 'write /tmp/pic_1234.dvi' # write to file * The forward interface The TeX daemon will split the forward line, look up the command in a dictionary, and call the resulting value, with the options and the dvi as arguments. * Notes I've written this to record and share my thoughts. There ought to be enough detail here to write test code. It also ought to be possible to fairly easily write a dummy server (that contains the framework into which the real live TeX daemon code can be added). It may be that SocketServer provides a suitable starting point. Jonathan |