Setting : resize widget for windows

Change-Id: I352f6f7e81bc7dc56808d10d7cef76e927293f91
Signed-off-by: heeyoung <heeyoung1008.hwang@samsung.com>

diff --git a/org.tizen.dynamicanalyzer.workbench/dynamic-analyzer/config/template b/org.tizen.dynamicanalyzer.workbench/dynamic-analyzer/config/template
index b07f380..16272a8 100644 (file)
--- a/org.tizen.dynamicanalyzer.workbench/dynamic-analyzer/config/template
+++ b/org.tizen.dynamicanalyzer.workbench/dynamic-analyzer/config/template
@@ -1,6 +1,6 @@
 mobile-2.3|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 mobile-2.3|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
-mobile-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+mobile-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process's CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 mobile-2.3|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
 mobile-2.3|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
 mobile-2.3|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
@@ -10,7 +10,7 @@ mobile-2.3|Energy|This template inform you of power consumption of target device
 mobile-2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
 wearable-2.3|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 wearable-2.3|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
-wearable-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+wearable-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process's CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 wearable-2.3|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
 wearable-2.3|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
 wearable-2.3|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
@@ -20,7 +20,7 @@ wearable-2.3|Energy|This template inform you of power consumption of target devi
 wearable-2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
 tv-1.0|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 tv-1.0|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
-tv-1.0|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+tv-1.0|Process Activity|This template shows the overall activities of your concerning processes, which are process's CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
 tv-1.0|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
 tv-1.0|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
 tv-1.0|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis

diff --git a/org.tizen.dynamicanalyzer/src/org/tizen/dynamicanalyzer/ui/toolbar/setting/SettingDialogBinarySettingsPage.java b/org.tizen.dynamicanalyzer/src/org/tizen/dynamicanalyzer/ui/toolbar/setting/SettingDialogBinarySettingsPage.java
index aa92949..6a33708 100644 (file)
--- a/org.tizen.dynamicanalyzer/src/org/tizen/dynamicanalyzer/ui/toolbar/setting/SettingDialogBinarySettingsPage.java
+++ b/org.tizen.dynamicanalyzer/src/org/tizen/dynamicanalyzer/ui/toolbar/setting/SettingDialogBinarySettingsPage.java
@@ -277,7 +277,8 @@ public class SettingDialogBinarySettingsPage extends DAPageComposite {
                data.top = new FormAttachment(librariesLabel, 4);
                data.left = new FormAttachment(0, 6);
                data.right = new FormAttachment(100, -6);
-               data.height = 310;
+               data.bottom = new FormAttachment(100, -45);
+
                // data.width = 590;
                scrolledComposite.setLayoutData(data);
                scrolledComposite.setLayout(new FormLayout());