Scroll bar for nuBuilder objects list

[Fundi]

As I am working away and creating my application my nuBuilder objects list is longer then what the window can display. Now I know you can sort by all the columns and you can search with the search function. Still a quick roll down with the mouse would be a nice feature to have. (By the way I just realized it is on all lists)

A real problem with this feature missing is when you add records and you exceed 27 records. Then the list does not indicate that there is another page. nor are these records visible.
So the user would have to assume that there is probably more and enter search criteria of records that he/she has no idea about. Not a nice way of handling it.

I realize that using pages in the first place and not loading all pages on a long record set all have to do with this. But perhaps a discussion on the matter could result on a solution that would improve user experience?

Sorry if this is not the place to discuss this. If not would you be so kind and move the topic and guide me in this.
May I say the application nuBuilder really is nice. All your efforts are greatly appreciated.

Is there a roadmap for future developments (sorry to be nosy).

[admin]

The reason we don't have "Page x of y" is to speed up lists with long record sets.

But with a bit of creative searching you shouldn't need to go past one page.

If you do, you are not making your application scalable enough and should think about more uniqueness to your record sets.

With your example for objects lets say
The Form Name you are dealing with is called "Customer"
The Tab Name you are dealing with is "Details"
and
The Object type is "Text"
and you have 4 columns 10,20,30 and 40.
with a total of 80 fields

Search for "cus det tex 40" it HAS to be quicker than scrolling through 80 fields (which you wont see on one page without scrolling down).

BTW when editing objects, there are short cuts that will make it MUCH easier anyway, take a look at this video..
http://www.youtube.com/watch?v=k4ktuWQfl6o


In other words, if you need to look past the first page your application is wasting time.

If for example, a customer rings up and says they want you to look up an invoice but they cant tell you the invoice number, the order number, the date or anything specific about it, and they have placed 1000 orders with you, how are you going to find it anyway?

regards

Steven

[Fundi]

Hi Steven

Points well taken. There is only one slight problem. When your form (especially a subform) produces a SQL error then you don't get to the screen where the form opens. therefore to fix the problem you have to go in via the object button on the setup tab. Then you have to search for your form. Then fix the problem and try again. This has to be done until you get the sql just right. Now for people who never make mistakes and are very fluent in SQL that is not a problem. For others it is a real slow down.

But I wondered anyway if it would not be a worth while feature that when the SQL error screen pops up to give a button or link to the form in programing mode that contains the offending code. Would that not be something for future versions. Implementation should not be too difficult I guess?

Thank you for your trouble writing back.
Fundi

[admin]

Fundi,

Sometime, what seems like a shortcut actually adds to the complexity of a system.
Especially if it doesn't fit the system's basic pattern.
We are very careful to keep the pattern and simplicity of nuBuilder.

I mention this in my blog. http://nubuilder.blogspot.com/2009/07/n ... icity.html


My suggestion is, make sure a subform works before you close the Object Form for it.
Another thing to do is run the sql in phpmyadmin before you put it on the subform (phpmyadmin has some great ways of showing you where errors actually are)

If this doesn't work then just go back to the object browse and filter to find it (it really is very simple),
This type of error won't pop up much, and even less the better you get.



Steven