Re: v12. I am sure it's me. BUT....
Ok. I did not realize that this was your question. Yes, I already have that. That is the "home"-page of your TUI component. It is in HTML and yes, you can have a picture there without difficulty. Just define your link to the image correctly and think about whether you want/need a fully qualified filename or just the short version (depends on where your app is going to run, if you don't know that because your client installs, then the fully qualified filename will not work!). So this is all possible (and done in my application already since the vid was created).
As I said previously, most reports your customer needs to give some type of parameters for. If he needs ALL horses that might not be needed, but mostly your user will want a more sophisticated report option than just "all". In any case, your TUI button can only open components at present. Which is not a problem since in the majority of cases you will want the user to provide with an option to state parameters anyway. So do it like this: place a button on the TUI, let the button open a small dialog component, and have your input fields for the parameters there with a button to open the pdf or print the report accordingly.
Another angle for you: any app will not just have 1 print button but several. Some are placed in the action button space on any grid, but others could be grouped in functional groups and per group have a dialog housing the appropriate buttons for them. It really all is just a matter of design Govindan. Use your imagination. At some point, Alpha might pick up on the perspective WCD can offer (also from a business point of view!) and develop this a bit further into what could be "more optimal" and maybe create buttons for the TUI that can do more and print directly. At this point however I do not think that the TUI is (from a design point of view) the best place to put a print button on anyway since it is mainly the main menu. I would personally design executing functions rather on grids or dialog components. But that's how I look at it.
Originally posted by GGandhi
View Post
Originally posted by GGandhi
View Post
Another angle for you: any app will not just have 1 print button but several. Some are placed in the action button space on any grid, but others could be grouped in functional groups and per group have a dialog housing the appropriate buttons for them. It really all is just a matter of design Govindan. Use your imagination. At some point, Alpha might pick up on the perspective WCD can offer (also from a business point of view!) and develop this a bit further into what could be "more optimal" and maybe create buttons for the TUI that can do more and print directly. At this point however I do not think that the TUI is (from a design point of view) the best place to put a print button on anyway since it is mainly the main menu. I would personally design executing functions rather on grids or dialog components. But that's how I look at it.
Comment