future sample example

[JD Kromkowski]

I am working on a sample example, that I’d like to post: :”a baby payroll system”. (There things that still need to be “worked out” but that might be done as a group FORUM activity.) However, I’d like to know the protocol that’s being followed. In your tutorial examples; you put the form(s) and .sbm(s) in the bin directory under the project in question. What I have been doing is creating two directories C:SIMPOLData where I put all the .sbm files and C:SIMPOLForms where I put all the .sfx files. Obviously, everybody can program the way they want. But it might be nice to have a “standard” way of doing things, to facilitate the flow of learning. Since this is a “new thing”, it might be useful for the Forum and/or SIMPOL LTD to agree on the way things normal should be done. E.g., where do you normally put the forms and the data. As another organizational method, I follow something similar to the SBAIR example. I have the ProgramName.sma but which includes only function main() function quit() Then, I have MainForm.sma SecondaryForm.sma (This is how I’m handing the deficiencies of the current detailblock) Menu.sma ToolBar.sma Then, so that I can follow the functions better I have an sma for each Menu, e.g. FileMenuFunctions.sma EditMenuFunctions.sma ViewMenuFunctions.sma SortByMenuFunctions.sma NavigationMenuFunctions.sma Since all form buttons or toolbaritems have a corresponding menu equivalent. These functions handle the function whether it is called from the menu, the toolbar, or a form button. There is quite a bit of rummaging around (at least for me) in the SBAIR example to find out how the functionality is working. My way sort of cuts down on this for me. I sometimes have trouble following my own code much less code from somebody else. Guidance? Suggestions? Thoughts?

[Michael]

JDK wrote:
> I am working on a sample example, that I'd like to post: :"a baby
> payroll system". (There things that still need to be "worked out" but
> that might be done as a group FORUM activity.)
>
> However, I'd like to know the protocol that's being followed.
>
> In your tutorial examples; you put the form(s) and .sbm(s) in the bin
> directory under the project in question.
>
> What I have been doing is creating two directories C:SIMPOLData
> where I put all the .sbm files and C:SIMPOLForms where I put all
> the .sfx files.

That might be ok if you only have one project on your system. What I
tend to do is create a directory for a project. Then if that project has
multiple sub-projects (see the Projectsssp directory), I then place
each project in that directory. If there is only one code project, then
I put everything required in that projects bin directory. Otherwise, I
create a secondary bin directory below the main project directory, as
well as an include and a lib directory, and I put things that are
project-specific into those directories.

By using this approach, I can move a project and all its important
pieces around as a unit without worrying about missing something.

> Obviously, everybody can program the way they want. But it might be
> nice to have a "standard" way of doing things, to facilitate the flow
> of learning. Since this is a "new thing", it might be useful for the
> Forum and/or SIMPOL LTD to agree on the way things normal should be
> done. E.g., where do you normally put the forms and the data.
>
> As another organizational method, I follow something similar to the
> SBAIR example.
>
> I have the ProgramName.sma but which includes only function main()
> function quit()
>
> Then, I have
>
> MainForm.sma SecondaryForm.sma (This is how I'm handing the
> deficiencies of the current detailblock) Menu.sma ToolBar.sma
>
> Then, so that I can follow the functions better I have an sma for
> each Menu, e.g.
>
> FileMenuFunctions.sma EditMenuFunctions.sma ViewMenuFunctions.sma
> SortByMenuFunctions.sma NavigationMenuFunctions.sma
>
> Since all form buttons or toolbaritems have a corresponding menu
> equivalent. These functions handle the function whether it is called
> from the menu, the toolbar, or a form button.
>
> There is quite a bit of rummaging around (at least for me) in the
> SBAIR example to find out how the functionality is working. My way
> sort of cuts down on this for me. I sometimes have trouble following
> my own code much less code from somebody else.
>
> Guidance? Suggestions? Thoughts?

In the SBAir example, all the functions from the menu would best be
loacted in the menu sma, but I think they are not, yet. All the toolbar
code is in the toolbar.sma, except the code for the tool bar combos,
which is in the tbcombos.sma. Much of the real working code is, of
course, in the appframework project.

If you have a really huge menu, it might be useful to break things up
the way that you describe. I think that this will end up being an issue
of personal choice, really.

Ciao, Neil

[Author]

Posts