Hello,
Stephen is right, using Python's os.sep is much better than using
DIR-SEPARATOR.
On Mon, Feb 24, 2014 at 9:36 PM, Pat David wrote:
> Could someone with a better grasp of the material chime in to help iron
> this out so that we can possibly include it as either a tutorial or wiki
> mater
On Mon, Feb 24, 2014 at 02:36:56PM -0600, Pat David wrote:
> Could someone with a better grasp of the material chime in to help iron
> this out so that we can possibly include it as either a tutorial or wiki
> material? I have to confess to not being familiar enough with the material
> to be able
Could someone with a better grasp of the material chime in to help iron
this out so that we can possibly include it as either a tutorial or wiki
material? I have to confess to not being familiar enough with the material
to be able to add anything meaningful beyond helping to translate to the
prope
Pat,
I did look into the DIR-SEPARATOR (DIR_SEPARATOR on python?) constant.
It did not appear to be documented anywhere in the gimp docs that I
could find with a search engine. From an old scheme script I found
posted I was able to find the following:
The DIR-SEPARATOR constant appears to b
Thanks so much for your contribution! I downloaded the PDF and ODT copy.
I plan on going through it and learning about it :D
On Wed, Feb 19, 2014 at 9:19 PM, Stephen Kiel wrote:
> Pat,
>
> I finally finished the tutorial that I was talking about with you a couple
> of months ago. You mentione
Pat,
The conversion to compatible HTML went much faster than I imagined. It
looks like getting everybody comfortable with the tutorial is going to
be the longer part of the process.
I looked at the notes, if we need to make some changes we can, I would
rather not make a lot of changes if the
Stephen,
Just a couple of notes. There are some concerns about the introduction of
the term "macro" in the tutorial and the sense with which it's used.
Also, saul has asked me to relay to you: "have him look into the
DIR-SEPARATOR constant. Using it would obviate about half of his code."
If you
Hi Stephen!
You can just leave it as an ODT file. I'll make the stylistic changes
required to fit the website HTML.
Give me a little time and I'll make the conversion and get it up to test.
Thanks for the contribution!
--
pat david
http://blog.patdavid.net
Pat,
I finally finished the tutorial that I was talking about with you a couple
of months ago. You mentioned then that I could either send it in Word
Processor format or take attempt to convert it to HTML.
Which of the two methods would be easiest for you? I am not sure if it is
easier to fix a
If you want to keep it in a word processor, I can just translate it from
there.
You can also use google docs if you want to share it with my acct through
there.
On Wednesday, October 16, 2013, Stephen Kiel wrote:
> Pat,
>
> That sounds great. I will plan to write in a word processor (with a spe
Pat,
That sounds great. I will plan to write in a word processor (with a spell
checker) & then dump it into bluefish to add the html tags. If that works
it should make the whole authoring process pretty straightforward. I would
prefer to stay in a word processor form rough to final draft & mini
Just stick to clean, plain HTML and you should be fine. Style inline if you
want, I'll move it to an external style sheet anyway.
You can publish screen grabs if gimp non problem I believe. Someone may
correct me.
I'll be out of town for a few days, but just hit me up when you're ready
for testin
On Wed, Jul 24, 2013 at 08:10:09AM +0200, Marco Ciampa wrote:
> BTW I think that it is better for you to just create a patch and post it
> here to someone that have write permissions to "push" it into master
> branch ...
Ok I'll try to push your tutorial ... let me check it ...
--
Marco Ciampa
First of all, I am not a git expert.
I am trying to help you in the hope to do and say not too much errors...
On Mon, Jul 22, 2013 at 07:22:07AM -0700, Stephen Kiel wrote:
> [stephen@localhost gimp-web-staging]$ which git
> /usr/bin/git
> [stephen@localhost gimp-web-staging]$ git config --global
On Mon, Jul 22, 2013 at 07:22:07AM -0700, Stephen Kiel wrote:
> Roman and Pat,
>
> I have made some progress toward getting my tutorial ready for release, but
> I am at a point now where I have hit a wall, and I would like to ask for
> some advice on how to proceed.
>
> I did do a final edit of t
Roman & Pat,
I spent quite a bit of time fiddling round with git-bz and after
downloading it, configuring it, and trying to use it to send in the
differences from checking my tutorial into git (local check out / check in
*seems* OK), I have come to the conclusion that this is probably not what
yo
Dear Stephen,
On Tue, Jul 02, 2013 at 12:37:33PM -0700, Stephen Kiel wrote:
> Roman,
>
> I did browse through some of the tutorials & looked at they way they were
> marked up. I don't think porting my tutorials into a markup language will
> be any problem. The part that I don't really understan
Roman,
Thanks for getting back to me, your feedback wasn't discouraging, I just
didn't really know how to proceed (so no worries).
I completely understand peoples limited time, I am in the same boat, I did
not want to invest hours in writing, learning the nuances of a particular
markup language,
On Wed, Jun 26, 2013 at 09:53:53AM -0500, Pat David wrote:
> > the best way to go with this is to become a maintainer of your content.
>
> This is actually the step I am at currently while trying to contribute
> at least some time in updating and creating new tutorial content.
>
> Stephen, I'll h
> the best way to go with this is to become a maintainer of your content.
This is actually the step I am at currently while trying to contribute
at least some time in updating and creating new tutorial content.
Stephen, I'll have some free time in a week or two if you want to send
me the .odt fil
20 matches
Mail list logo