Bernie Pursley wrote:

> You pose that either (1) there is not enough specificity in my
> comments for you to respond to or (2) I can take the open source code
> and do my own thing.

#1 is correct. #2 would be difficult for newbies, like myself, who do
not know Python.

However, I don't think the documentation is getting enough credit. I
was impressed when I first starting reading the documentation because
it does try to be a thorough, definitive resource on Leo. In many
ways, I do believe it succeeds.

Edward K. Ream wrote:

> I think what some people are asking for is a way to understand Leo
> without doing much work, and without carefully studying the
> documentation that is there, and without trying it out.  That's not
> likely to work.  Otoh, many people *have* "gotten" Leo, despite
> less-than-perfect docs.

Leo isn't Notepad so yeah, it's going to take some work to learn.

Studying the documentation will work if it's organized and easy to
find answers after the basics are covered. Really crappy documentation
could be carefully studied for years, and probably end up causing
brain damage in the process. :D

> In fact, aside from the installation critique, which I have
> incorporated into Leo's web site,  the criticisms here have not been
> specific:  *this* sentence or paragraph is unclear; *this* question is
> nowhere addressed.

Getting specifics (examples) is an entirely reasonable expectation to
have of the individuals doing the critiquing. Otherwise, complaints
are ineffectual. A person writing documentation can only be so
psychic. :D

I hope the suggestions I've made in other threads have been detailed
and clear. I =want= to know if they are not, so I ask for in-kind
specific feedback in return. :D

And, just so I make sure I say it, they are "suggestions" and not
"expectations" on my part that they will be incorporated. I've only
scratched the surface of Leo, and my suggestions are made without
knowing Leo or its documentation 100%.

Gour wrote:

> E.g. The top of the Leo Homepage has 'Leo at Google Groups' link
> which is later referenced again in the 'Links' session.

When I first looked at the Leo Homepage and saw the 'Leo at Google
Groups' link at the top, I mistakenly thought, because of its
prominent position, that it is the starting place to ask for help. The
link title 'Leo at Google Groups' is a little vague in describing it's
purpose compared to the 'Leo's help forum' link on the left side. In
addition, the left side also lists the same 'Leo at Google Groups'
=above= the 'Leo's help forum' link, further seeming to give it higher
prominence, where as for newbies like myself I'd rather the help forum
link stand out more. I realize that the Leo Editor Users group was
likely added later and that may be why the purposes are not clearly
distinguished.

Suggestion #1: Remove 'Leo at Google Groups' link at the top.

Suggestion #2: Move the 'mind-mapping.org' link to the 'More links'
page (http://webpages.charter.net/edreamleo/leoLinks.html). I =do=
know what mind mapping is and use it, but I don't think it needs such
prominence.

Suggestion #3: OK, well, not much of a suggestion, but because of #1
and #2 there'll be a big white space where the links used to be. I'm
too tired to think of a creative "filler" at the moment.

Suggestion #4: Move the 'Quotes' link from the Documentation section
to the Links section. Keep the download link first under the Links
section, but you could put the Quotes link below it, or maybe above
'More links'. It's very good to have the Quotes, but I don't think it
qualifies as Documentation.

Suggestion #5: Move 'Leo's help forum' to be above 'Leo at Google
Groups' and capitalize H and F: Leo's Help Forum.

Suggestion #6: Change 'Leo at Google Groups' to 'Leo's Developer [or
maybe 'Technical'?] Forum' (note title case). If this makes the column
width to wide, perhaps you could drop the 'Leo's' and have 'Help
Forum' and 'Developer's Forum'. I don't think it's that critical to
say they are hosted at Google Groups.

Then in the main/right hand section of the page ('Leo is...'):

Suggestion #7: Change 'Portable' to be 'Cross platform'. When I first
saw the word 'Portable' I thought that meant I'd be able to run it on
a flash drive.

Suggestion #8: Instead of, "Please use the leo-editor group to ask
questions and make suggestions" how about replacing it with two
sentences (of course, also put links in):

Please use the Leo Help Forum to ask questions and make suggestions.

If you want to know more about Leo's Python scripting feature and
other technical aspects , please use the Leo Developer's Forum.

> Maybe the 'poll' can be created about merging leo-editor &
> leo-editor-users into one group? (I must confess that until today I
> was not aware there are two mailing lists since I follow 'leo-editor'
> via gmane.)

If there is a poll to merge the two lists, I would vote an emphatic
NO. In fact, I'd likely break the mouse from clicking so hard. The leo-
editor list is often WAY over my head, but still fascinating at times
just to read.

> I propose to change name of 2) into leo-devel mailing list or
> something depending whether the two mailing list are going to be
> merged or not.

I like the 'leo-devel' list idea very much and is why I've
incorporated it into the suggestions above.

> What do you think about having some dedicated domain for Leo?

This would be nice as it would be easier to remember, but if it
doesn't happen, I'll just keeping using the bookmarks I've already
made. :D

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.

Reply via email to