dScribe GUI - A lot of improvements

Thanks to all who gave me some advice on the best practices for a complex GUI like the one below.

So now I have no more hidden boxes made visible on demand. Everything is done by Disable/Enable.
I still have to figure out (later) how to code a good Disable/Enable switch as a generic class helper.

But hey it's working now fine. As you can see also I keeped the headline of the datagrid always visible whatever the scrolling position.

I have also to include a function to keep the focus on the selected row. Do you know a good one (server side if possible but client side why not). I have my own code for that but surely somebody brighter than me has something great ;-)

So I will publish a new article tomorrow (if I find some time ;-) about this screen Editing Content for approval

 

4 Comments

  • Problems w/ dScribe.



    I've downloaded the project from GotDotNet workspaces. And I've tried to install it. However, I have run accross several problems:



    1) The FreeTextBox Project Cannot be found.



    2) No default admin user. It would be quite helpful to include a default user and some default content.



    3) I get the following errors when the SQL script is run:



    Server: Msg 207, Level 16, State 3, Procedure Details_Page, Line 7

    Invalid column name 'Template_Id'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'T_Id'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Id'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Name'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'T_Name'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'T_Nb_elts'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Name'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'T_Name'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'T_Nb_elts'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Active'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Active'.

    Server: Msg 207, Level 16, State 1, Procedure Details_Page, Line 7

    Invalid column name 'Page_Name'.

    Server: Msg 2714, Level 16, State 5, Procedure Element_Update, Line 28

    There is already an object named 'Element_Update' in the database.

    Server: Msg 207, Level 16, State 3, Procedure Image_Insert, Line 8

    Invalid column name 'Page_Id'.

    Server: Msg 207, Level 16, State 1, Procedure Image_Insert, Line 8

    Invalid column name 'Page_Name'.



  • Apologies if you find some errors. I will have a look now and post something asap.

    Thanks for your feedback ... and your support

  • I've implemented some Gui like you before.

    I've handled the selected row like this.

    Everytime you call the details "edit":

    -save the index of the datagrid in the viewstate

    -you color "the indexed row"



    If you want to retrieve the selected index on another page, you might use the session.

  • I am trying to figure out how to eliminate 207 invalid column message

Comments have been disabled for this content.