Hi all,

I'm interested in ways to make installation of SB simpler. As it stands now, you have to unzip the contents to a folder under RB's root and copy the main BAS file to a newly created project folder.

I came up with a new procedure I think simplifies the process.

1. Unzip the downloaded file to the "projects" folder, creating the "SapientBoard_project" subfolder.
   
2. Start the RB IDE in a web browser.
   
3. Create a new project and give it a name of your choosing.
   
4. Paste the following code into the editor, replacing "myboard" with name of the project you chose, and save.

   Code:

   Run "SapientBoard", #sb Head #sb init$("myboard") Render #sb End

   
   
5. Publish the newly created project.

Nix that. Actually I could make installing SB much more streamlined.

The fact that the "app" key is unset when you run a program from the IDE can be used to its advantage. The program simply checks that app is unassigned and if it is, checks for the state of a new install, and if that is the case, it starts the automated install. Otherwise, it just displays a link to start SB in a new window, as it does now.

The installer would potentially need to create a project file and write the above post's code into a file. Then it would need to modify the "prefs.xml" file to publish the app under the desired name.

I hope that doesn't sound too scary to anyone.

Brent it is much simpler.

Your zip already contains a SapientBoard folder, which in turn contains the SapientBoard.BAS

Rename the included SapientBoard folder to SapientBoard_project and instruct the user to unzip into the ProjectsRoot$ folder, that is all what is needed.

RB will immediately list the project.

That is how I added RunBoard and SapientBoard to my projects list.

You need to include the workingversion.xml file to make RB recognise the folder as a real project folder.

Code:

<projectWorkingVersion> <name>SapientBoard</name> <version>unversioned</version> <fromVersion>unversioned</fromVersion> <comment></comment> <hasChanges>false</hasChanges> <iconFullPath></iconFullPath> <resources> </resources> <deployPath></deployPath> </projectWorkingVersion>

Thanks a lot, Stefan. That sounds like a plan.

I hope to have this in v0.1.2 by the following weekend.