You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Do users sign on and create an account with a password or do we simply use their email address as the unique identifier? This requires that we save a table of email addresses and the unique IDs that go with them. Then we need the ability to search through the list of email addresses and look up the ID. Perhaps keep an array with a cluster of email address and unique IDs.

We could give each project an ID (the time stamp when the project was created). This could either be part of the file name or it could be a folder. Make the timestamp be a folder. Then when we display the list we can display the project creation date based on the folder name.

We need to make sure that if a user opens an old project and reruns the design algorithms that we don't allow saving the results over the previous files. This is important because we will change the design algorithms. Old designs must be kept as built. Thus the design options must only be available for new projects. The user could load an old project, then select new project (to get a new time stamp) and then the design options would be made available.

Project information is stored at ...DesignData\userid\timestamp\project.acp (AguaClara Project)
User information is stored at ...DesignData\userid\user.acu (AguaClara User)

File name convention: ...DesignData\userid\timestamp\filename.ext

Users should be able to create, open, and delete designs. We could even display a list of projects in the folder for them to select from since we should not give the user access to a real file dialog box.

The project info should be saved using the save anything code that I wrote, but must figure out how to handle data structure updates for backward compatibility

For now, the basis of design will remain in a MathCAD file.

We need the ability to switch languages. I imagine a file containing an array of object identifiers and the text that goes with those objects.

The program needs an initialization step where the AutoCAD and MathCAD references are established and the applications opened. We may need to figure out how to get MathCAD to open from commands from the web browser.

Implement source forge control on LabVIEW code for this project. (also create folder on this computer that is linked with source forge to the MathCAD files)

Learn how projects work in LabVIEW

Learn how versions work in source forge and begin using this for the MathCAD design program.

create toolbar icons for each command that the user can execute

How do we control program flow? For example the autocad file won't exist until after the command is sent to autocad. If the user tries to email the attachments before running autocad the autocad file won't yet exist. One possibility is to dissable booleans that shouldn't be used.

Do dialog boxes work in the web environment?

Program defaults such as message sent along with email, file path to saved projects, file path to mathcad file, are saved in an ini file.

  • No labels