Not sure if this is the correct way to represent the flow between the "Home" page button, "Culture" page button and the "Song" page button (as all these buttons are present in all of the pages, where the user is able to click any of these buttons and perform certain activities)
This seems very messy as the arrows are pointing in all direction, which is why I am stuck on how to represent this.
UI of the application:
Why did you choose an activity diagram for this purpose? A state machine diagram is more appropriate. Clicking on a menu option transfers the application to a different state. You can use a superstate to model the transitions that can be made in any application state.
I would use an activity diagram to visualize the paths through a complex use case, not all UI actions.
See my paper 'Which UML models should we make', pages 12 and 13.
Related
I am currently designing my design definition to give the users of my custom controls an idea of what the xpage will look like. The only problem i have in the design panel is that even though a facet is filled with controls i can still see its name. That screws up every design coming from my design definition.
Is there a way to hide the name of the facet once controls are assigned?
I started using Tizen SDK to develop a native app. And I have to make a form into a form. Actually, it works, but I've some bugs with it. I mean, the footer bar is bugged, when I click on an item from the footer. The app crash immediatly...
Do you know how to resolve it ?
Thanks
I don't think it a good choice to make a Form into a Form. If you want reuse UI form, it's better to use Panel instead.
Here is description of Panel from dev guide.
Tizen::Ui::Controls::Panel class is a general rectangular container that you can use to group UI controls, or even other panels. Panels can be used to create a custom background for a defined area, or for organizing and aligning UI controls. However, by default, the look-and-feel of a panel does not differ from its surrounding Tizen::Ui::Controls::Form control.
I am developing a web based back-end application. In this back-end, I can View, Add, Edit, and Delete information. There is a form and a table positioned under the form.
First, the application will load information into the table. When I choose to edit a row, I click an "Edit" link in the row and the information will be loaded into the form. Then I can change the information and save it.
In my Activity Diagram for "Edit", should I start from the user clicking the "Edit" link or start from loading information to the table?
I am a little confused because this loading information step is already included in "View" Activity Diagram.
well i think it depends.if you draw all the roles in partitions then you can use "the loading action" only once and show transition from this to other activities like if you create partitions for view,edit and delete link then you can show loading of the table only once and then show transition from it directly to "edit row" activity in edit link partition and likewise for other activities too.needless to say that you have to use branching accordingly.you could have posted the rough diagram you created so that improvements could be made.
this is not a technical question, but one for advice regarding the best practices in designing an Android tablet UI.
I've got my concept of an Android Phone app pinned down.
The first activity (master view) launched contains a tab bar with three fragments from which the user can launch detail view activities of different sorts.
Both the master-view activity and the detail-view activities have actions in their action bars. Different detail views have different action items.
My question is: How should I organize and display the action items on a tablet, where an activity combines both views side by side?
The problem is the unified action bar for both the master-view fragment and whatever kind of detail fragment is shown. I do not think it is a good idea to start messing with the contents of the action bar whenever a different kind of detail view is opened.
The Android Design Guide does not tell you much on that front. There is a sample of a Contacts app in the "Multi-pane Layouts" section, but it does not actually deal with the problem. It evades it, by putting the single relevant action as an icon inside the detail view fragment.
Any advice with regards to best practices and references are appreciated.
I would suggest leaving your master details icons in the action bar, whilst putting your details view icons in another view/area within the details fragment.
My reasoning would be that icons in the action bar affect / are associated with the whole app / view on screen. Whilst your details icons only affect the details view and therefor should not be in the action menu when showing multiple fragments.
I guess you will have to see how the designs look..
I am not a fan of the action bar icons being changed from within the same activity (even if it contains multiple fragments), however when you load a new activity (like in your phone design) then I say yeah throw them in the action bar.
If I understand your question correctly, which I think is basically a question of how multiple Fragments (i.e. when on a multi-pane layout such as on a tablet) should contribute to the single ActionBar, it's quite straightforward and it is actually briefly discussed in the documentation here. Essentially, you can have the multiple Fragments all contributing their own menu items / action items to the single action bar, via some simple API calls.
I'm workin on my first webpart.
I use some number of user controls as screens. And I have a trouble here.
First screen contains a list of dynamically created options (hyperlinks). After user made a decision with click, I want to change the screen and pass to the new screen some parameters.
My dicision is to load all controls I need on webpart creation. Controls I don't need right now I make invisible.
SomeUserControl1 uc1 = (SomeUserControl1)Page.LoadControl("~/_controltemplates/SomeUserControl1.ascx");
SomeUserControl2 uc2 = (SomeUserControl2)Page.LoadControl("~/_controltemplates/SomeUserControl2.ascx");
uc2.Visible = false;
Controls.Add(uc1);
Controls.Add(uc2);
Option in first user control realized as LinkButtons (serverside). OnClik event calls a special method in the webpart class and in this method i change a visibility of my user controls and pass some parameters to usercontrol2.
I don't like this approach. Are there different ways to realize described functionality?
Thanks!
You need use a ASP.NET Wizard Control, it does what you exactly you want.
From a design standpoint what you are doing looks a little bit frightening. You should think about nesting the various user controls into a single user control that you can use as the face of your webpart. Keep the coupling between the various user controls loose and think about implementing the Observer pattern if you need to do things like playing with control visibility.