Just like the previous one, the inclusion of table / field names is something "I" normally wouldn't include as part of the wireframe. I would have normally come up with an idea on possible DB schemas after the prototype, during the application phase.
Keeping inline with allowing the user of the tool ability to keep their wireframe up to date as they progress through the different phases of FLiP, we should certainly allow this request to proceed. And, again, just like your HTML hyperlink task, several other people have requested this feature.
I have assigned the task to you in the interim, because if you're going to add in the HTML hyperlink field, then the DB fields could be added in, in-concert with the HTML fields.
Please let me know what assistance I can give you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1479959
Originator: NO
Hi Kevin,
Just like the previous one, the inclusion of table / field names is something "I" normally wouldn't include as part of the wireframe. I would have normally come up with an idea on possible DB schemas after the prototype, during the application phase.
Keeping inline with allowing the user of the tool ability to keep their wireframe up to date as they progress through the different phases of FLiP, we should certainly allow this request to proceed. And, again, just like your HTML hyperlink task, several other people have requested this feature.
I have assigned the task to you in the interim, because if you're going to add in the HTML hyperlink field, then the DB fields could be added in, in-concert with the HTML fields.
Please let me know what assistance I can give you.