Volunteer github guru for documentation submissions?

classic Classic list List threaded Threaded
185 messages Options
1234 ... 10
Reply | Threaded
Open this post in threaded view
|

Volunteer github guru for documentation submissions?

J. Landman Gay
I'm not keen on trying to learn github but I want to help with the
documentation. I keep finding things. Filling out bug reports is too
much trouble and clutter for things like misspellings or syntax examples.

So I was wondering if there might be a github person who would volunteer
to push changes for us. Anyone with documentation changes could send
them to this kindhearted person who would do the technical part for us.
This person wouldn't need to do any editing or even read the
submissions, just do the actual pushing and pulling or whatever it is.

Is that a feasible suggestion? Without user notes, I think I'm letting a
lot of things just slide because it's too fiddly and takes too much time
to learn what I need to do.

Alternately (and harder) would be someone who could write a LiveCode
plugin that would do the same thing. I suspect a lot more of the docs
would get updated if we had something like this.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Charles Warwick
On 3/04/2016 4:29 pm, J. Landman Gay wrote:

> I'm not keen on trying to learn github but I want to help with the
> documentation. I keep finding things. Filling out bug reports is too
> much trouble and clutter for things like misspellings or syntax examples.
>
> So I was wondering if there might be a github person who would
> volunteer to push changes for us. Anyone with documentation changes
> could send them to this kindhearted person who would do the technical
> part for us. This person wouldn't need to do any editing or even read
> the submissions, just do the actual pushing and pulling or whatever it
> is.

There will be limitations on what I can do depending on the volume of
requests that come through, however, if anyone is in this position where
they have done all the work and simply need a PR submitted on github,
please feel free to contact me directly.

Cheers,

Charles

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Paul Dupuis
In reply to this post by J. Landman Gay
On 4/3/2016 2:29 AM, J. Landman Gay wrote:
> Alternately (and harder) would be someone who could write a LiveCode
> plugin that would do the same thing. I suspect a lot more of the docs
> would get updated if we had something like this.

I second this. I too would contribute more if I didn't need to invest
the time to learn Github and associated tools.

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Kay C Lan
In reply to this post by Charles Warwick
On Sun, Apr 3, 2016 at 3:36 PM, Charles Warwick
<[hidden email]> wrote:
>
> There will be limitations on what I can do depending on the volume of
> requests that come through..., please
> feel free to contact me directly.
>
Charles, THANK YOU so much for offering, but can I suggest that
instead such requests are posted to this List with [DOCS] as a prefix
in the Subject. I think that would have three benefits:

1) You respond here that you're handling a request. If the load gets
too much, then other's might join in and pick up one's you've missed.
I hope I would occasionally be able to help.
2) You respond here that you've completed the PR. The Community here
gets to see that submissions are being made and actioned and hopefully
a snow ball effect will occur - with more people noticing and
submitting errors. No 1 will then become more important ;-)
3) It leaves a very public trail of what has already been picked up
and actioned. Just because a PR has been completed doesn't mean it
instantaneously appears in the Dictionary. So in much the same way
that people should search the QCC to see that a Bug they've noticed
hasn't already been submitted, anyone noticing a Dictionary error
should hopefully be able to search this List and see if a PR has
already been submitted.

Again, thank you for stepping up.

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

J. Landman Gay
On 4/3/2016 7:07 AM, Kay C Lan wrote:

> On Sun, Apr 3, 2016 at 3:36 PM, Charles Warwick
> <[hidden email]> wrote:
>>
>> There will be limitations on what I can do depending on the volume of
>> requests that come through..., please
>> feel free to contact me directly.
>>
> Charles, THANK YOU so much for offering, but can I suggest that
> instead such requests are posted to this List with [DOCS] as a prefix
> in the Subject. I think that would have three benefits:
>
> 1) You respond here that you're handling a request. If the load gets
> too much, then other's might join in and pick up one's you've missed.
> I hope I would occasionally be able to help.
> 2) You respond here that you've completed the PR. The Community here
> gets to see that submissions are being made and actioned and hopefully
> a snow ball effect will occur - with more people noticing and
> submitting errors. No 1 will then become more important ;-)
> 3) It leaves a very public trail of what has already been picked up
> and actioned. Just because a PR has been completed doesn't mean it
> instantaneously appears in the Dictionary. So in much the same way
> that people should search the QCC to see that a Bug they've noticed
> hasn't already been submitted, anyone noticing a Dictionary error
> should hopefully be able to search this List and see if a PR has
> already been submitted.
>
> Again, thank you for stepping up.

Yes, all hail to Charles! But I wonder if posting requests to the list
will add too much irritating noise; I was thinking of something more
private. On the other hand, peer pressure isn't all bad.

Speaking of github, isn't there some kind of "check out" procedure? If
so, I'm not sure how that would work. Asking Charles to do that for us
and then push the changes might be more than he signed up for.

The plugin is sounding better and better to me. Are there shell commands
that a naif like me could just put into a stack without fully
understanding them? If so, maybe I could write one.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Charles Warwick

On 4/04/2016 5:27 am, J. Landman Gay wrote:
> Speaking of github, isn't there some kind of "check out" procedure? If
> so, I'm not sure how that would work. Asking Charles to do that for us
> and then push the changes might be more than he signed up for.
In git terminology, "check out" just means retrieving a particular
version of a file and pulling it into your local repository.  There is
no marking of a file as being "checked out" at the remote end (LC's git
repository).

So you don't _have_ to do anything special to check out a file that you
want to modify.  However, it is obviously best to ensure you are
modifying the latest copy of a file so that any changes you submit won't
be overwriting other already made changes.

The easiest way to retrieve the latest copy of a file from LiveCode's
source is to browse their repository in GitHub (you don't need an
account to do this):

For the latest LC8 code, this link will get you there:

https://github.com/livecode/livecode/tree/develop

Once you browse down the directory tree and have clicked on the file you
want to modify, it will show the contents of the file within the Github
website.  From there, right click on the "Raw" button on the right hand
side just above the top of the contents of the file and choose "Save
As..." to save a copy to your PC.

Then you can make your changes and e-mail them through.

Cheers,

Charles

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

J. Landman Gay
On 4/3/2016 10:55 PM, Charles Warwick wrote:

>
> On 4/04/2016 5:27 am, J. Landman Gay wrote:
>> Speaking of github, isn't there some kind of "check out" procedure? If
>> so, I'm not sure how that would work. Asking Charles to do that for us
>> and then push the changes might be more than he signed up for.
> In git terminology, "check out" just means retrieving a particular
> version of a file and pulling it into your local repository.  There is
> no marking of a file as being "checked out" at the remote end (LC's git
> repository).
>
> So you don't _have_ to do anything special to check out a file that you
> want to modify.  However, it is obviously best to ensure you are
> modifying the latest copy of a file so that any changes you submit won't
> be overwriting other already made changes.
>
> The easiest way to retrieve the latest copy of a file from LiveCode's
> source is to browse their repository in GitHub (you don't need an
> account to do this):
>
> For the latest LC8 code, this link will get you there:
>
> https://github.com/livecode/livecode/tree/develop
>
> Once you browse down the directory tree and have clicked on the file you
> want to modify, it will show the contents of the file within the Github
> website.  From there, right click on the "Raw" button on the right hand
> side just above the top of the contents of the file and choose "Save
> As..." to save a copy to your PC.
>
> Then you can make your changes and e-mail them through.

Thank you for that, you almost make it sound easy. Then I read Mark
Wieder's comments to Kay and decided I was wrong. :)

I'll give it a try.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Charles Warwick

On 4/04/2016 4:04 pm, J. Landman Gay wrote:
>> Then you can make your changes and e-mail them through.
>
> Thank you for that, you almost make it sound easy. Then I read Mark
> Wieder's comments to Kay and decided I was wrong. :)
>
> I'll give it a try.
>
If you just want to get the latest code and send through the changes for
someone else to submit it is easy.

However, if you want to submit your own requests to the LC repository
directly then there is a little bit more to the process. :-)

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Kay C Lan
In reply to this post by J. Landman Gay
On Mon, Apr 4, 2016 at 3:27 AM, J. Landman Gay <[hidden email]> wrote:
>posting requests to the list will
> add too much irritating noise;

That's why I suggested prefixing the subject with [DOC] so as people
can quickly filter out subjects they are not interested in. Thank you
those who use [ANN] [BUG] and [OT] - very helpful. I also envisaged
(maybe wrongly) that you wouldn't be posting the entire document, just
the portion/line/paragraph of relevance; i.e. a stated goal of the new
documents is that the Examples should work for those with Strict
Compilation turned On. Therefore a post to the list might be as simple
as:

-----------------------------------------------

[DOC] Add command - example update

could someone please replace

Example:
add field "New" to tSummaryOfInventory

with

Example:
local tSummaryOfInventory
add field "New" to tSummaryOfInventory

thanks

-----------------------------------------------

>Are there shell commands
> that a naif like me could just put into a stack

yes there are:

http://burnedpixel.com/blog/setting-up-git-and-github-on-your-mac/

BUT

> without fully understanding
> them? If so, maybe I could write one.

is not going to happen. By the time you figured out how to implement
the command line tools in your stack you'd just as easily have figured
out how to use the web interface for Github and done a couple of
amendments!

>Then I read Mark Wieder's comments to Kay and decided I was wrong. :)

I can't for the life of me find a response from Mark - I've checked my
SPAM - but I'll take a stab and agree with him... he's far more
switched on than I am :-)

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

mwieder
On 04/05/2016 12:26 AM, Kay C Lan wrote:

>> Then I read Mark Wieder's comments to Kay and decided I was wrong. :)
>
> I can't for the life of me find a response from Mark - I've checked my
> SPAM - but I'll take a stab and agree with him... he's far more
> switched on than I am :-)

I also have no idea what Jacque's talking about here.

But I do want to say that there's fascinating reading in
https://github.com/livecode/livecode/pull/3518#issuecomment-205199749

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
 Mark Wieder
 ahsoftware@gmail.com
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

J. Landman Gay
On April 5, 2016 10:27:38 AM Mark Wieder <[hidden email]> wrote:

> On 04/05/2016 12:26 AM, Kay C Lan wrote:
>
>>> Then I read Mark Wieder's comments to Kay and decided I was wrong. :)
>>
>> I can't for the life of me find a response from Mark - I've checked my
>> SPAM - but I'll take a stab and agree with him... he's far more
>> switched on than I am :-)
>
> I also have no idea what Jacque's talking about here.

As our glorious ex-leader used to say,,  I misremembered. I'll go out on a
limb and say it was Alex. Or possibly someone else.

Me no think right.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com



_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

mwieder
On 04/05/2016 09:35 AM, J. Landman Gay wrote:

> As our glorious ex-leader used to say,,  I misremembered.

Well, since that lets me off the hook, let me say now that really, it
ain't that hard to do. There's a bit of setup involved, but after that
you're home free.

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
 Mark Wieder
 ahsoftware@gmail.com
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

J. Landman Gay
In reply to this post by Kay C Lan
On 4/5/2016 2:26 AM, Kay C Lan wrote:
> That's why I suggested prefixing the subject with [DOC] so as people
> can quickly filter out subjects they are not interested in. Thank you
> those who use [ANN] [BUG] and [OT] - very helpful. I also envisaged
> (maybe wrongly) that you wouldn't be posting the entire document, just
> the portion/line/paragraph of relevance

I was on a different track, planning to grab the latest file, edit it,
and send it back to github via our Good Deed Doer, that is, Charles.

It would be the same process as anyone else uses who knows github, only
using a proxy person.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Ray Horsley-2
...one other note.  I'm guessing calls to sqLite need drivers. These
drivers are probably built in to Livecode and the OnRev server which
would explain why LC's database commands works so well locally and with
the OnRev based samples.

If this is the problem, does anybody know how I could install these
drivers on my own server?

On 4/5/2016 1:18 PM, Ray wrote:

> I've never worked with sqLite databases before but it appears I should
> be able to access one on a server pretty much the same as I do locally.
>
> Here's what I've done:
>    put revOpenDatabase("sqLite",localPath) into
> theDbId                   -- this creates a zero K local database file
>
>    put "CREATE TABLE bugs(Name char(50), Date char(50))" into myQuery
>    revExecuteSQL theDbId,myQuery -- the local database file is no 2 K
>
>    revCloseDatabase theDbId -- close it or I won't be able to copy it
> to the server
>
> I then copy the local database file to a remote server and make sure
> all 9 permissions are checked (777).
>
> I now load the well-tested server path into the variable dbPath and
> try this:
>    put revOpenDatabase("sqLite",dbPath) into myResult
>
> but all I get back is:
>    Error: Unable to open the database file
>
> Suggestions?

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Devin Asay
Ray,

You may have moved your DB file from a system that is not case sensitive, like MacOS, to one this is case sensitive, like Linux. Do all of your folders and file names have the same exact spelling, including upper and lower case letters, as the string in your path variable?

Devin


> On Apr 5, 2016, at 12:39 PM, Ray <[hidden email]> wrote:
>
> ...one other note.  I'm guessing calls to sqLite need drivers. These drivers are probably built in to Livecode and the OnRev server which would explain why LC's database commands works so well locally and with the OnRev based samples.
>
> If this is the problem, does anybody know how I could install these drivers on my own server?
>
> On 4/5/2016 1:18 PM, Ray wrote:
>> I've never worked with sqLite databases before but it appears I should be able to access one on a server pretty much the same as I do locally.
>>
>> Here's what I've done:
>>   put revOpenDatabase("sqLite",localPath) into theDbId                   -- this creates a zero K local database file
>>
>>   put "CREATE TABLE bugs(Name char(50), Date char(50))" into myQuery
>>   revExecuteSQL theDbId,myQuery -- the local database file is no 2 K
>>
>>   revCloseDatabase theDbId -- close it or I won't be able to copy it to the server
>>
>> I then copy the local database file to a remote server and make sure all 9 permissions are checked (777).
>>
>> I now load the well-tested server path into the variable dbPath and try this:
>>   put revOpenDatabase("sqLite",dbPath) into myResult
>>
>> but all I get back is:
>>   Error: Unable to open the database file
>>
>> Suggestions?
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

Devin Asay
Office of Digital Humanities
Brigham Young University


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Ray Horsley-2
Devin - thanks for the idea but that's not it.  I just checked and
everything on my Windows 8.1 system matches case with the database file
path on the Linux server.  I even tried changing the name of the
database file to all lower case but that didn't work either. Thanks...

On 4/5/2016 3:38 PM, Devin Asay wrote:

> Ray,
>
> You may have moved your DB file from a system that is not case sensitive, like MacOS, to one this is case sensitive, like Linux. Do all of your folders and file names have the same exact spelling, including upper and lower case letters, as the string in your path variable?
>
> Devin
>
>
>> On Apr 5, 2016, at 12:39 PM, Ray <[hidden email]> wrote:
>>
>> ...one other note.  I'm guessing calls to sqLite need drivers. These drivers are probably built in to Livecode and the OnRev server which would explain why LC's database commands works so well locally and with the OnRev based samples.
>>
>> If this is the problem, does anybody know how I could install these drivers on my own server?
>>
>> On 4/5/2016 1:18 PM, Ray wrote:
>>> I've never worked with sqLite databases before but it appears I should be able to access one on a server pretty much the same as I do locally.
>>>
>>> Here's what I've done:
>>>    put revOpenDatabase("sqLite",localPath) into theDbId                   -- this creates a zero K local database file
>>>
>>>    put "CREATE TABLE bugs(Name char(50), Date char(50))" into myQuery
>>>    revExecuteSQL theDbId,myQuery -- the local database file is no 2 K
>>>
>>>    revCloseDatabase theDbId -- close it or I won't be able to copy it to the server
>>>
>>> I then copy the local database file to a remote server and make sure all 9 permissions are checked (777).
>>>
>>> I now load the well-tested server path into the variable dbPath and try this:
>>>    put revOpenDatabase("sqLite",dbPath) into myResult
>>>
>>> but all I get back is:
>>>    Error: Unable to open the database file
>>>
>>> Suggestions?
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> Devin Asay
> Office of Digital Humanities
> Brigham Young University
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Peter Haworth
You might want to try opening the database with something other than
Livecode in hope that you will get a more informative error message.
 sqlite3 is the official sqlite command line tool.  It's distributed with
OSX but not sure if it's included with Windows.

Are you able to access any other files in the same directory as the sqlite
db?

On Tue, Apr 5, 2016 at 1:31 PM Ray <[hidden email]> wrote:

> Devin - thanks for the idea but that's not it.  I just checked and
> everything on my Windows 8.1 system matches case with the database file
> path on the Linux server.  I even tried changing the name of the
> database file to all lower case but that didn't work either. Thanks...
>
> On 4/5/2016 3:38 PM, Devin Asay wrote:
> > Ray,
> >
> > You may have moved your DB file from a system that is not case
> sensitive, like MacOS, to one this is case sensitive, like Linux. Do all of
> your folders and file names have the same exact spelling, including upper
> and lower case letters, as the string in your path variable?
> >
> > Devin
> >
> >
> >> On Apr 5, 2016, at 12:39 PM, Ray <[hidden email]> wrote:
> >>
> >> ...one other note.  I'm guessing calls to sqLite need drivers. These
> drivers are probably built in to Livecode and the OnRev server which would
> explain why LC's database commands works so well locally and with the OnRev
> based samples.
> >>
> >> If this is the problem, does anybody know how I could install these
> drivers on my own server?
> >>
> >> On 4/5/2016 1:18 PM, Ray wrote:
> >>> I've never worked with sqLite databases before but it appears I should
> be able to access one on a server pretty much the same as I do locally.
> >>>
> >>> Here's what I've done:
> >>>    put revOpenDatabase("sqLite",localPath) into theDbId
>    -- this creates a zero K local database file
> >>>
> >>>    put "CREATE TABLE bugs(Name char(50), Date char(50))" into myQuery
> >>>    revExecuteSQL theDbId,myQuery -- the local database file is no 2 K
> >>>
> >>>    revCloseDatabase theDbId -- close it or I won't be able to copy it
> to the server
> >>>
> >>> I then copy the local database file to a remote server and make sure
> all 9 permissions are checked (777).
> >>>
> >>> I now load the well-tested server path into the variable dbPath and
> try this:
> >>>    put revOpenDatabase("sqLite",dbPath) into myResult
> >>>
> >>> but all I get back is:
> >>>    Error: Unable to open the database file
> >>>
> >>> Suggestions?
> >> _______________________________________________
> >> use-livecode mailing list
> >> [hidden email]
> >> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> > Devin Asay
> > Office of Digital Humanities
> > Brigham Young University
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Ray Horsley-2
Peter - thanks for jumping in here.  Yes, I can read and write files to
this location and, as a matter of fact, I can even do a straight read of
the database file on the server and get the same cryptic characters back
I get when I read the local copy.  I just can't establish a connection
to it for the purpose of issuing revDatabase calls.

You're right when you say the "unable to open the database file" is not
very informative.  I get the same message when I try that on an empty
path on the server.

I'll try your sqLite3 suggestion and let you know how it works.

Thanks!

On 4/5/2016 6:34 PM, Peter Haworth wrote:

> You might want to try opening the database with something other than
> Livecode in hope that you will get a more informative error message.
>   sqlite3 is the official sqlite command line tool.  It's distributed with
> OSX but not sure if it's included with Windows.
>
> Are you able to access any other files in the same directory as the sqlite
> db?
>
> On Tue, Apr 5, 2016 at 1:31 PM Ray <[hidden email]> wrote:
>
>> Devin - thanks for the idea but that's not it.  I just checked and
>> everything on my Windows 8.1 system matches case with the database file
>> path on the Linux server.  I even tried changing the name of the
>> database file to all lower case but that didn't work either. Thanks...
>>
>> On 4/5/2016 3:38 PM, Devin Asay wrote:
>>> Ray,
>>>
>>> You may have moved your DB file from a system that is not case
>> sensitive, like MacOS, to one this is case sensitive, like Linux. Do all of
>> your folders and file names have the same exact spelling, including upper
>> and lower case letters, as the string in your path variable?
>>> Devin
>>>
>>>
>>>> On Apr 5, 2016, at 12:39 PM, Ray <[hidden email]> wrote:
>>>>
>>>> ...one other note.  I'm guessing calls to sqLite need drivers. These
>> drivers are probably built in to Livecode and the OnRev server which would
>> explain why LC's database commands works so well locally and with the OnRev
>> based samples.
>>>> If this is the problem, does anybody know how I could install these
>> drivers on my own server?
>>>> On 4/5/2016 1:18 PM, Ray wrote:
>>>>> I've never worked with sqLite databases before but it appears I should
>> be able to access one on a server pretty much the same as I do locally.
>>>>> Here's what I've done:
>>>>>     put revOpenDatabase("sqLite",localPath) into theDbId
>>     -- this creates a zero K local database file
>>>>>     put "CREATE TABLE bugs(Name char(50), Date char(50))" into myQuery
>>>>>     revExecuteSQL theDbId,myQuery -- the local database file is no 2 K
>>>>>
>>>>>     revCloseDatabase theDbId -- close it or I won't be able to copy it
>> to the server
>>>>> I then copy the local database file to a remote server and make sure
>> all 9 permissions are checked (777).
>>>>> I now load the well-tested server path into the variable dbPath and
>> try this:
>>>>>     put revOpenDatabase("sqLite",dbPath) into myResult
>>>>>
>>>>> but all I get back is:
>>>>>     Error: Unable to open the database file
>>>>>
>>>>> Suggestions?
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> [hidden email]
>>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> Devin Asay
>>> Office of Digital Humanities
>>> Brigham Young University
>>>
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> [hidden email]
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Error: Unable to open the database file

Peter Haworth
I suppose I should also mention the usual caveat about using sqlite over a
networked file system, which is that sqlite relies on file system locking
to preserve data integrity and some networked file systems are buggy in
that area according to the sqlite website.

On Tue, Apr 5, 2016, 3:57 PM Ray <[hidden email]> wrote:

> Peter - thanks for jumping in here.  Yes, I can read and write files to
> this location and, as a matter of fact, I can even do a straight read of
> the database file on the server and get the same cryptic characters back
> I get when I read the local copy.  I just can't establish a connection
> to it for the purpose of issuing revDatabase calls.
>
> You're right when you say the "unable to open the database file" is not
> very informative.  I get the same message when I try that on an empty
> path on the server.
>
> I'll try your sqLite3 suggestion and let you know how it works.
>
> Thanks!
>
> On 4/5/2016 6:34 PM, Peter Haworth wrote:
> > You might want to try opening the database with something other than
> > Livecode in hope that you will get a more informative error message.
> >   sqlite3 is the official sqlite command line tool.  It's distributed
> with
> > OSX but not sure if it's included with Windows.
> >
> > Are you able to access any other files in the same directory as the
> sqlite
> > db?
> >
> > On Tue, Apr 5, 2016 at 1:31 PM Ray <[hidden email]> wrote:
> >
> >> Devin - thanks for the idea but that's not it.  I just checked and
> >> everything on my Windows 8.1 system matches case with the database file
> >> path on the Linux server.  I even tried changing the name of the
> >> database file to all lower case but that didn't work either. Thanks...
> >>
> >> On 4/5/2016 3:38 PM, Devin Asay wrote:
> >>> Ray,
> >>>
> >>> You may have moved your DB file from a system that is not case
> >> sensitive, like MacOS, to one this is case sensitive, like Linux. Do
> all of
> >> your folders and file names have the same exact spelling, including
> upper
> >> and lower case letters, as the string in your path variable?
> >>> Devin
> >>>
> >>>
> >>>> On Apr 5, 2016, at 12:39 PM, Ray <[hidden email]> wrote:
> >>>>
> >>>> ...one other note.  I'm guessing calls to sqLite need drivers. These
> >> drivers are probably built in to Livecode and the OnRev server which
> would
> >> explain why LC's database commands works so well locally and with the
> OnRev
> >> based samples.
> >>>> If this is the problem, does anybody know how I could install these
> >> drivers on my own server?
> >>>> On 4/5/2016 1:18 PM, Ray wrote:
> >>>>> I've never worked with sqLite databases before but it appears I
> should
> >> be able to access one on a server pretty much the same as I do locally.
> >>>>> Here's what I've done:
> >>>>>     put revOpenDatabase("sqLite",localPath) into theDbId
> >>     -- this creates a zero K local database file
> >>>>>     put "CREATE TABLE bugs(Name char(50), Date char(50))" into
> myQuery
> >>>>>     revExecuteSQL theDbId,myQuery -- the local database file is no 2
> K
> >>>>>
> >>>>>     revCloseDatabase theDbId -- close it or I won't be able to copy
> it
> >> to the server
> >>>>> I then copy the local database file to a remote server and make sure
> >> all 9 permissions are checked (777).
> >>>>> I now load the well-tested server path into the variable dbPath and
> >> try this:
> >>>>>     put revOpenDatabase("sqLite",dbPath) into myResult
> >>>>>
> >>>>> but all I get back is:
> >>>>>     Error: Unable to open the database file
> >>>>>
> >>>>> Suggestions?
> >>>> _______________________________________________
> >>>> use-livecode mailing list
> >>>> [hidden email]
> >>>> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >>>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>> Devin Asay
> >>> Office of Digital Humanities
> >>> Brigham Young University
> >>>
> >>>
> >>> _______________________________________________
> >>> use-livecode mailing list
> >>> [hidden email]
> >>> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> >> _______________________________________________
> >> use-livecode mailing list
> >> [hidden email]
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Volunteer github guru for documentation submissions?

Alex Tweedly
In reply to this post by mwieder
I fully agree - it ain't that hard, even I could do it.

This is the first time I've used git, or Github, etc.  I followed Ali's
instructions cautiously and slowly, hit one minor bump-in-the-road
(which Mark solved for me within minutes courtesy of the use-list), one
more minor issue which was obvious enough to guess my way round it - and
I got through it all OK.

I even took the opportunity to practice with a real example - and fixed
the minor issues with the instructions, so anyone else following them
now should have an even smoother experience.

So if you haven't done it yet - give it a go. Fill in the Contributors'
Agreement, find some minor issue in the docs to improve, set aside 20-30
minutes and go for it!

If anything does go wrong, either the experts on the use-list or the
helpful guys at Livecode will help you through :-)

-- Alex.

On 05/04/2016 18:31, Mark Wieder wrote:
> On 04/05/2016 09:35 AM, J. Landman Gay wrote:
>
>> As our glorious ex-leader used to say,,  I misremembered.
>
> Well, since that lets me off the hook, let me say now that really, it
> ain't that hard to do. There's a bit of setup involved, but after that
> you're home free.
>


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
1234 ... 10