<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 06/07/2011 11:43 AM, Pietro Moras wrote:
<blockquote cite="mid:SNT133-w126B1568280BE359AF926FEF5E0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
<p style="margin-bottom: 0cm;" class="western"><font
face="Arial">If you care having Eric (4) Python IDE
documented, here is the URL: </font><a
moz-do-not-send="true"
href="http://www.box.net/shared/k64yenrpey"><font
face="Arial">http://www.box.net/shared/k64yenrpey</font></a><font
face="Arial"> </font></p>
<font face="Arial"> </font>
<p style="margin-bottom: 0cm;" class="western"><font
face="Arial"> where to find a first “open” draft, open to
your questions and remarks. </font></p>
<font face="Arial"> </font>
<p style="margin-bottom: 0cm;" class="western"> </p>
<font face="Arial"> </font>
<p style="margin-bottom: 0cm;" class="western"><font
face="Arial">That is, if you are an active user, eager to
see such documentation improved and updated, you are
encouraged to express your thoughts, posted here, or on the
LinkedIn “Active User Conference” Group; or privately, too.-</font></p>
<font face="Arial"> </font>
<p style="margin-bottom: 0cm;" class="western"><font
face="Arial">You are welcome.</font></p>
<font face="Arial"> </font>
<p style="margin-bottom: 0cm;" class="western"><font
face="Arial"> The Author</font></p>
</div>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Eric mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Eric@riverbankcomputing.com">Eric@riverbankcomputing.com</a>
<a class="moz-txt-link-freetext" href="http://www.riverbankcomputing.com/mailman/listinfo/eric">http://www.riverbankcomputing.com/mailman/listinfo/eric</a>
</pre>
</blockquote>
<blockquote type="cite">> Hi Pietro,<br>
><br>
> I have only had time for a quick skim and generally my
impressions are favourable but I would like to make a couple of
suggestions, hopefully constructive ones:<br>
><br>
> 1. Change your pdf settings to not show crop/registration
marks, (I personally find them a distraction and I am sure that
many others will as well.<br>
> 2. Why no table of contents? Please have one, preferably
with click-able links it makes finding things much easier.<br>
> 3. It would be nice to include an Acknowledgements section<br>
> 4. Second copyright page, (according to the header), does
not contain any copyright, or left, information - it does contain
the Foreward, this should be on its own, correctly headed page.<br>
> 5. Run - page 4 - Eric.bat presumes a windows environment
as Eric is multi-platform this will not always be true.<br>
> 6. As chapter 2 - Menus is over 90 pages it should be
divided into sub-chapters, (possibly one for each top level menu
would be a good starting point, the header should also include at
least the same level of title division.<br>
> 7. It would be nice to include examples of setting up the
following:<br>
> 1. A brand new project,<br>
> 2. A new project for existing source code,<br>
> 3. A multi-project,<br>
> 4. A project debug session.<br>
> 8. Generally add on installation to cover things like
pylint would be useful.<br>
> 9. Please consider supplying your final version, and
possibly later drafts, in a format that is compatible with Eric's
help system, preferably with either install instructions, or
better an install script, to attach it to the help menu.<br>
> 10. I would consider the document less a technical report
than an independent user guide and also think that it would get a,
well deserved, wider readership if re-titled and described as
such.<br>
><br>
> Personally I feel that many, especially new, users will find
it very helpful, (hence suggestion 9 above).<br>
><br>
> Well done!<br>
><br>
> Gadget/Steve</blockquote>
<br>
<br>
On 06/07/2011 7:35 PM, Pietro Moras wrote:<br>
> Hi Gadget/Steve,<br>
> Not bad for a “quick skim”, I've appreciated it.<br>
> As for working on your suggestions, please consider these are
my priorities:<br>
> 1] To get in touch with Eric “Active Users” so to work in team,
to the common benefit. By the way:<br>
> 1.1] I'm already in excellent relations with the Eric's
producer. Now I'd like to extend this collaboration to some users
too.<br>
> 1.2] Is there any reason why you have expressed your thoughts
privately, instead of on the Mail List? Reason for may question is
respect for your preferences, in case our dialogue would get on.<br>
Simply hit the wrong button - should have been reply to list.<br>
><br>
> 2] To Test & Document other unexplored Eric's features,
provided I find experienced users to work with on them. My first
candidate would be the “Source Code Management”, or “Version Control
System”; but I'd welcome other proposals too.<br>
><br>
> 3] To find out a good channel of distribution for the resulting
work, to the benefit of the Eric's user community.<br>
><br>
> 4] To take better care of the “editing” quality of the outcome.
That is: good English, effectiveness, readability, ...<br>
><br>
> To lure you on this adventure consider that there's involved no
money, hard work and little glory.<br>
> See you.<br>
> - P.M.<br>
<br>
Pietro,<br>
<br>
One immediate tip for you is that possibly most users of this list,
like many others, prefer bottom posting, i.e. posting at the end -
this allows people to join in in context rather than having to jump
about the text. The simple reason for the direct reply is hitting
the wrong button - still getting used to Thunderbird.<br>
<br>
While I agree that more content is better I have found that getting
a good structure early on saves a lot of work and also makes it
possible for reviewers to focus on areas that they are familiar
with.<br>
<br>
If you are not looking for lots of money as an outcome possible
distribution channels would include bundling it in with Eric, Simply
publishing it to the web, etc., if you would hope for some
remuneration then take a look at the publishers of other python
books, (<a href="http://wiki.python.org/moin/PythonBooks">PythonBooks
</a>is a good place to start).<br>
<br>
As to the adventure I would be willing to try to assist but have to
warn you that my time is heavily committed.<br>
<br>
Gadget/Steve<br>
<br>
</body>
</html>