- Convert uDB JavaScript function to use AJAX instead of using hidden frames
- Convert getRecordFromList JavaScript function to use AJAX instead of using hidden frames.
- Convert validateLU JavaScript function to use AJAX instead of using hidden frames.
- Deactivate activity buttons (onblur of objects) on Run Activity screens until zzsys_variable tables have been updated.
Welcome to the nuBuilder forums!
Please register and login to view forums and other content only available to registered users.
Please register and login to view forums and other content only available to registered users.
nuBuilder To Do List
nuBuilder To Do List
Proposed updates for nubuilder.
If you like nuBuilder, how about leaving a nice review on SourceForge?
-
- Posts: 125
- Joined: Thu Feb 18, 2010 5:42 pm
- Contact:
Re: nuBuilder To Do List
Hello, I add this:
cypherinfo wrote:Hello, another good thing to add to nuBuilder would be an intuitive query builder as here:
http://ajax.easyquerydemo.com/
You would be the first cross platform web application to do that!!
Thank you.
Cypherinfo.
-
- Posts: 125
- Joined: Thu Feb 18, 2010 5:42 pm
- Contact:
Re: nuBuilder To Do List
Hello, another good improvement would be to add the [page number/total page number] information as in the attached image.
Thank you.
Cypherinfo.
Thank you.
Cypherinfo.
- Attachments
-
- pagination.JPG (18.17 KiB) Viewed 27920 times
-
- Posts: 17
- Joined: Tue Mar 08, 2011 12:45 am
Re: nuBuilder To Do List
Hi,
Another good improvement is add a "Save and Select" button when we have added a new record when the page was opened from a lookup field.
Example: Some inexperienced users closes the window without return to search screen. Other advantage is three step less to select new customer: save, back to search, search and select.
Evandro
Another good improvement is add a "Save and Select" button when we have added a new record when the page was opened from a lookup field.
Example: Some inexperienced users closes the window without return to search screen. Other advantage is three step less to select new customer: save, back to search, search and select.
Evandro
-
- Site Admin
- Posts: 2786
- Joined: Mon Jun 15, 2009 2:23 am
- nuBuilder Version: 4.5
- Been thanked: 3 times
Re: nuBuilder To Do List
Evandro,
version 2.7.3 will be out soon and will have this feature..
When adding a record from a Lookup's Browse Form, the new record is taken straight back to the Lookup Object when saved.
Steven
version 2.7.3 will be out soon and will have this feature..
When adding a record from a Lookup's Browse Form, the new record is taken straight back to the Lookup Object when saved.
Steven
-
- Posts: 2
- Joined: Wed Sep 12, 2012 1:25 pm
Re: nuBuilder To Do List
One more urgent item - encrypt the password. I see on the forum it's been asked a few times.
-
- Posts: 17
- Joined: Tue Mar 08, 2011 12:45 am
Re: nuBuilder To Do List
Will be interesting if have a way to build a HTML report using a simple select, almost like a "Print" option of form.
The Report Builder is amazing, but position each field for all report is difficult. When we use table, it is not necessary. Fats and easy.
Thanks
The Report Builder is amazing, but position each field for all report is difficult. When we use table, it is not necessary. Fats and easy.
Thanks
-
- Posts: 503
- Joined: Thu May 24, 2012 2:08 am
- Location: Milan, Italy
- Contact:
Re: nuBuilder To Do List
This request arises from the need to have a system in which some rows in Browse Screen are selectable or not selectable, depending on a logic determined by the developer.
I suggest a solution, but I'd like to have the opinion from other developers on the forum and, of course, from nuBuilder Team!
Suppose that there is a field of the system, eg sys_selected (boolean), that the developer can add to their own tables (as sys_changed and sys_added).
In Custom Code > Before Browse it would be possible to run a query and, according to its own logic, the developer could set sys_selected to TRUE/FALSE, for example:
nuBuilder, while building the Browse Screen, should make rows selectable or non-selectable, based on the value contained in this field, basically remove the onclick attribute to all the columns of the row with zzsys_selected = false.
What do you think?
Max
I suggest a solution, but I'd like to have the opinion from other developers on the forum and, of course, from nuBuilder Team!
Suppose that there is a field of the system, eg sys_selected (boolean), that the developer can add to their own tables (as sys_changed and sys_added).
In Custom Code > Before Browse it would be possible to run a query and, according to its own logic, the developer could set sys_selected to TRUE/FALSE, for example:
Code: Select all
$table = nuRunQuery("SELECT * FROM customer");
while ($row = db_fetch_array($table) {
if ($row['cus_discount'] > 0) {
$row['sys_selected'] = true;
} else {
$row['sys_selected'] = false;
}
}
What do you think?
Max