|
From: Rainer S. <rs...@ba...> - 2020-07-27 11:30:17
|
Dear Bernard, Nice, Windows working now - I mean at least it got past that initial hurdle! ;-) I hope to be trying out stuff in a few days, can’t do it justice right now. Having both a MAMP install and a bare Apache-php side by side is actually quite interesting, as one can see which additional modules are required that are tacitly provided by the MAMP distribution. Ideally you could suggest a few test steps similar to what Anthony did for “trying out/testing” his binary - sort of 10 things (ununderstandingly) to do to make reasonably sure it does what is expected (or at least it tells us what is going wrong). As to the readme: you haven’t provided a download-link to the “php-folder” yet - so maybe you’d like to add that, and make those amendments explaining document-root and path structure yourself? Your snapshot always contains a binary and a “BP2_help.txt” - I left the binary away (it’s ignored anyways by git) but added the help.txt, because I wasn’t sure if it contained something useful/changing. I guess now just the php-folder would be enough, right? Generally speaking It’s a bit counter intuitive to suggest the workflow you describe for a repo that has already folded Anthony’s and your repos into each other. After all, the simplest way to download your php folder would be to simply clone that repo - but that would give us Anthony’s files as well (which I am monitoring in that repo as well). My strategy is to try to gradually entangle you more and more in the use of this git/repo stuff - so that at some point the switch to actually doing something like that yourself will be trivial and welcome. But as long as Anthony and you keep separate repos, there will be different requirements between you keeping a "bp-php-repo", and me, bringing both development trees together in order to quickly sync multiple testsystems for building and testing/trying out. Maybe I should create a separate bp-php repo exclusively for your code? (And I can join them in another one I use privately)? Or do you already feel ready to set it up yourself? I think your readme would fit such a repo much better than the current one. Best .r. PS: bp-php on Windows ;) : > On 27. Jul 2020, at 11:52, Bernard Bel <ber...@gm...> wrote: > > Dear Rainer, > > Don't bother, your AMP installations are certainly working! I fixed the problem as follows: > > Having developed the PHP interface with MAMP on Mac, I had assumed that every user would place the "bolprocessor" folder at the root of the site which is named "htdocs" in that configuration. > > Now I have modified "_basic_tasks.php" to detect the actual location of the "root" and fix the path accordingly. I am now running the application under /htdocs/try/ and it works. So it should also work immediately in your case. > > When you tried with MAMP the location was correct but you got an empty list because your "bolprocessor" folder did not contain any data. You should have at least, for instance, the "ctests" folder containing examples. I uploaded the one I am working with. > > Remember that the "php" folder is supposed to be placed in the "bolprocessor" folder supplied by Anthony with the server application, and that folder contains "ctest" andf "data" example sets. > > I check sound-object prototypes in the "-mi.abc1" file. Be careful that the file is autosaved every 20 seconds, therefore it is safe to work on copies. I am going to program an "undo" command for edits in the MIDI contents of prototypes. > > True, the ReadMe.txt could be copied to the face-page of the GitHub repository. It will require a small edit because if the user is not using MAMP then the entry URL won't be "http://localhost/bolprocessor/php/" <http://localhost/bolprocessor/php/>. Just tell the user to point a browser at the "index.php" file… Maybe no need to markdown the text as we might modify it from time to time. > > GD Libary is very good news! I am going to check it. > > All new material on my site: > https://leti.lt/bolprocessor/ <https://leti.lt/bolprocessor/> > > Bernard > _______________________________________________ > bolprocessor-devel mailing list > bol...@li... > https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel |
