Thanks for the feedback, & don't worry , I think that people who ask for
feedback and want to shoot the messenger are pretty ridiculous.
It is interesting that the <pre> code was the one that you had trouble
with. I used the "bluefish" editor (open source) to format the HTML. I
noticed that their tag for preformatted text was simpler than that used on
previously published tutorials. I tried editing those tags to make them
like the published tutorials, apparently I missed the quotes. It would be
interesting to see if the code right out of an editor like bluefish would
work, it would be nice to be able to use an editor that would produce code
that is essentially correct by construction.
About the scheme code & style, I guess I would say that I am not a
programmer, so the criticism does not hurt my feelings. My goal was to
write code that is clear and avoid writing bad code (to have it called kind
of 'C' like actually seems like kind of a compliment). I think it is
better to avoid opening up a debate on coding style, I have seen them
consume a lot of energy and often fail to resolve much. If I do write
another tutorial, the one that I am thinking about be just gimp-python
anyway (it would be harder to write in scheme).
Anyway thanks again for all of the help and feedback,
On Mon, Oct 14, 2013 at 3:59 AM, Marco Ciampa <ciam...@libero.it> wrote:
> On Fri, Oct 11, 2013 at 08:59:04PM -0700, Stephen Kiel wrote:
> > Marco,
> > Thanks for all of your help! Getting the tutorial published was more
> > complicated than I originally anticipated, but it was definitely worth
> > I do have a question for you:
> > If I were to write another tutorial, is there anything that I could do to
> > make the release or publication process easier? I am not sure if there
> > were things that you had to fix in order to publish the tutorial. If I
> > made some mistakes, it would be a good time for me to take note of them
> > I don't repeat them.
> > Stephen Kiel
> Right question, I do not really know the answer(s).
> I myself have had some difficoulties to have your tutorial published.
> I asked help to a friend of mine for testing in local the gimp site pages
> before publication.
> I successfully tested your tutorial using the nginx web server instead of
> I was NOT able to test it under Apache btw...
> Even when local testing went well (without errors) the publication went
> Automatic compilation was blocked by a couple of errors in the tutorial
> It seems that my version of python is less picky about small errors in the
> htrw pages so it was not so easy to find the errors in the first place.
> Specifically the code into the web pages, the text in <pre class="code">
> MUST BE QUOTED since there are a couple of "<" and ">" inside it that
> confuse it a bit. Once quoted compilation and consequently site update went
> Some developers complained about the scheme code. They say that it
> is a bit "C like" and not really "scheme/lisp like" and since it
> should be a teaching example, it should be rewritten to be a better
> code for beginners and students.
> Please forgive my bad english and ... don't shoot the messenger! :-)
> Marco Ciampa
> | Linux User #78271 |
> | FSFE fellow #364 |
Mission Viejo, CA 92692
*Mobile/SMS (949) 702-1993*
Home (949) 367-2915
gimp-docs-list mailing list