dScribe installation

Thanks for the users of dScribe who noticed some problems with the SQL scripts.

Also maybe because I was to excited to deliver something some of the procedures were the wrong ones.

Come back to GotdotNet in few minutes and you should see the correct Scripts (named this time Scripts SQL 0.1)

I double checked the files so it should be ok now. For the moment the setup is not fully automatic (TBF later).

So click here to read the different steps for a correct installation of dScribe.

Thanks for the support ;-)

1 Comment

  • I've got some feed back for you.



    1) SQL Script

    Since you have to have the SQL Script to install the application, I would just include that with the application files and include a readme that tells a user how to run the Script.



    2) Admin SQL Script

    I would include the SQL Script for creating the default Admin that you mention in your installation instructions with the application files. This makes it much easier for users to install the application and saves time since 99% of the people installing the application will need an administrative account.



    3) Free Text Box

    Now, I don't know what the "legality" of it would be, but if you can include the version of the Free Text Box and it's project file with the solution files. This way if a newer version comes you, you know your application won't break. Also, you tell people it uses it, and where to get it, but there's no installation instructions for it.



    4) Templates / Default Content

    There should be some default content to the CMS so that people can see how it works without spending a lot of time setting it up to see if this is the solution they are looking for. Also, you can mention at the beginning page that the default admin account's password is 1234.



    5) Coding Standards

    In your database you have tables named AccountProperties, SesctionElements, TemplateElts, and Type_params. There should be a standard. If you use an underscore between words, use it in ever table. If you are going to capitalize every word, do so in every table. In the Table Account you have the Primary Key (PK) as AccountID. In Template_Elts you have no PK, and the field that should be a PK is name TemplateEltId (no underscores).



    My standard for database is to have everything CAPS and use underscores between words and only use singluar names. If you use abbreviations, use it everywhere, but make sure they are easily understood. So Template_Elts would be TEMPLATE_ELEMENT with the TemplateEltId as the first field, and named TEMPLATE_ELEMENT_ID.



    The above is my standard. I've found it works really nice. I understand that different people have different standards, and I respect that.. I just suggest picking a standard and sticking to it.



    Now hopefully you will take this as constructive criticism (which is what it is intended to be) and make some improvements in your project to make it easy for you to build upon and for users to use.

Comments have been disabled for this content.