Bug getting group name, plse check

[Mike Bonner]

Its pretty easy to set up a custom search engine in google.  I created a
cse restricted to 4 sites. www.livecode.com forums.livecode.com
lessons.livecode.com and the nabble site.  I'm sure there are settings that
might help it work better.

Like all google search, you can improve results with quoted phrases etc.
Heres a link to the one I set up.
https://cse.google.com/cse/publicurl?cx=002762050828011275793:09mnfq5cmmy


On Mon, Aug 17, 2015 at 9:19 AM, William Prothero <prothero at earthednet.org>
wrote:

> Folks:
> My initial comment arose because I, through searching the dictionary,
> couldn’t find how to get the group name of a control that was in a group.
> The best result I had was by searching with google. I could enter something
> like: “How do I get the group name of the group that a control is within?”
> I got pointed to a forum post which got me started. Then Richard provided
> the final answer that let me know the critical word was “owner”.
>
> I think it’s critical that every statement, property, command, be
> correctly entered in a dictionary. But, it  can be impossible to guess the
> command that might be relevant for a specific operation and often it’s not
> intuitive. Google is my friend in this case, as is this list.
>
> Regarding tagging, searching, etc, I’ve experienced very primitive search
> boxes and they can be extremely primitive. (read useless almost). It is
> very difficult to build a great search system. Google has done that. It is
> possible to get Google to index web pages. Perhaps there should be thought
> given to taking advantage of Google search to get the context information
> that we need from the dictionary.
>
> I don’t know what would be involved in creating this, but it could be made
> much more useful than what we have now.
>
> BTW, for search phrases, the topic heading of emails to this list would be
> a great resource. However, unless there is some flexibility for variations
> in the search phrase in the search engine, the situation won’t improve.
> Everybody says things differently.
>
> Regards,
> Bill
>
> > On Aug 16, 2015, at 9:04 AM, Richard Gaskin <ambassador at fourthworld.com>
> wrote:
> >
> > William Prothero wrote:
> > > Richard:
> > > This is an example of how difficult it can be to find docs on an
> > > operation that isn’t commonly used and that doesn’t have “obvious”
> > > syntax.
> > ...
> > > Perhaps if there was a dictionary based, not on livecode commands,
> > > but on operations that the user wants to perform, with great search,
> > > it would be helpful.
> >
> > We definitely need tagging in the Dictionary, something I'll be pushing
> for as we finally get the ball rolling with the Community Documentation
> Team soon.
> >
> > With searchable tags anyone can add terms that will help others find
> relevant tokens.
> >
> > If you were able to add tags to the "owner" Dictionary entry, what would
> those be?  What sorts of terms and concepts come to find when looking for
> ways to refer to objects in the message path?
> >
> >
> > > Then again, this list is a great source of this kind of info too.
> >
> > This list is great, and so are the forums, but IMO people rely on them
> sooner in the process than would be ideal.
> >
> > LiveCode is a very unusual language so it requires much care in how it's
> presented, and more importantly in it's indexed, so searches can be made
> for concepts and not just keywords.
> >
> > --
> > Richard Gaskin
> > LiveCode Community Manager
> > richard at livecode.org
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>