That looks like a solution, Seth. I think it'll work.
Before I spend a week or so restructuring code and rewriting some of the
critical assignment statements to get the scoping right, I have a couple
questions.
(1) does the following scheme make sense or is there a more sensible way to
pull it to
Daniel,
It doesn't really sound like you're structuring this in the best way.
Your tcltk code should probably be in your /R folder. I don't know why
you're proposing to put it in /data.
Can you also clarify why your code would generating files in the
working directory? This isn't necessary to cre
>
> "For users who don't know anything about R, this solution may work fine.
> But
> for users that do know R, it is unsatisfactory...program changes the
> working directory, fills it with hundreds of alien-looking functions and
> data, and crashes if working directory is changed or variables are m
Thanks, Dirk.
Sorry for my lack of clarity. I do want to create a package and have
created one and it works, but the structure is awkward. I'm hoping someone
can help me straighten out the organization.
In package/R folder, I have several files that define standalone functions
that crunch data.
I
On 11 May 2016 at 12:56, Dalthorp, Daniel wrote:
| I have an R/tcltk application that is designed for use primarily by people
| who don't know R and don't care to learn much about it. I'd like users to
| be able to use the software with a bare minimum interaction with R.
|
| Although the applicat
