KR101368044B1 - Plug­in module based on eclipse platform - Google Patents

Abstract

The present application relates to an Eclipse platform-based plug-in module, and more specifically, it is possible to increase or decrease the number of sorted logs step by step, and to increase the tag to variously filter the log, layout optimization and sequence logic To provide a plug-in module based on the Eclipse platform that can provide a user interface that provides a flow diagram.
The technical configuration of the present application is a log read plug-in that reads log files for Android-based applications and displays log analysis results according to tag names, and logs that display log analysis results according to tag names by reading log files for Android-based devices. And a layout optimization plug-in for displaying a diagnostic result of the layout for the application, and a class array plug-in for displaying the analysis result of the execution sequence for the application.

Description

Eclipse platform-based plug-in module {PLUG­IN MODULE BASED ON ECLIPSE PLATFORM}

The present application relates to an Eclipse platform-based plug-in module, and more specifically, to increase or decrease the number of lines of logs to be sorted stepwise or linearly, and to increase the tag to variously filter the logs, An Eclipse platform-based plug-in module that can provide a user interface that provides layout optimization and sequence logical flow to drawings.

In general, Android is a software platform that combines an operating system for mobile phones, middleware, and applications. Based on the Linux kernel, Android provides a powerful operating system, a comprehensive library set, a rich multimedia user interface, and a phone application.

Here, Android can be compared to Windows, which is an operating system that controls software and hardware on a computer. The mobile phone is equipped with Android to use the Internet and messenger, and can be applied to various information and home appliances as well as mobile phones. Equipped.

What differentiates Android from Microsoft's "Windows Mobile" or Nokia's "Symbian" is that it is a completely open platform. Previously, mobile phone manufacturers and service providers had different operating systems to create applications individually. All Android-based source code has been released, allowing anyone to create and sell software and devices using it.

Therefore, developers can extend, replace, or reuse them to provide users with rich and integrated mobile services. These mobile phones equipped with Android are called "Android Phones". The trading space is called the "Android Market."

It is a mobile-only operating system created by Google that allows you to run programs on your smartphone like Windows, a PC operating system.In contrast to Apple's iPhone content market, “App Store”, you can play games, news, music, etc. Unlike the iPhone system, which is operated by the closed iPhone system, the operating system is released, so it can be adopted not only mobile phone manufacturers but also mobile carriers such as SK Telecom.

Android also enables Android developers to write applications in the Java language, and provides a runtime library that can run compiled byte code, which is developed through the Android Software Development Kit (SDK). It provides various tools and application programming interface (API) needed to do this.

The development environment of Android recommends using Eclipse and the Android Development Tools (ADT), which are integrated with Eclipse. These Android development tools are compatible with device emulators and error correction. It includes debugging tools, profiling to analyze memory and performance.

Here, Eclipse is a development environment that supports various languages, composed of an integrated development environment and an extensible plug-in system, and is mostly configured to develop programs in various languages including Java, and the basic configuration is Java. The Java Development Tool (JDT) is for Java development, and users can extend the functionality by installing plug-ins or writing their own.

These Eclipses can be used on a variety of platforms and started with a programming integrated development environment that supports a variety of languages including Java, but now have evolved into a general-purpose application software platform by introducing the Open Service Gateway Initiative (OSGi). It's a powerful feature, and was developed under the name of IBM's WebShpeare Studio Application Developer (WASD), which has evolved into Eclipse today based on the open source of the engine.

The latest version is 3.6, with various distributions for each purpose (for C / C ++ developers, for Java developers, for web developers, etc.), and Eclipse is based on the Rich Client Platform (RCP), which is a plug-in. The core platform on which Eclipse is running, OSGi, a standard bundling framework, the Standard Widget Toolkit (SWT), a portable GUI widget toolkit, and JFace and Views to simplify the task of configuring advanced components using SWT. It consists of the Eclipse Workbench, which consists of Editors, Perspectives, and Wizards.

And Eclipse uses plug-ins to provide all of the above features, including RCP, as opposed to hard-coding extensions for other Java applications, and this plug-in mechanism is a lightweight software configuration framework. And the plug-in framework, it is not only possible to extend Eclipse into a programming language other than Java, but also to use a typesetting language such as LaTeX, run network applications such as telnet, or manage databases in Eclipse. It is also possible.

The Eclipse Android Software Development Kit (SDK) includes the Eclipse Java Development Tool (JDT), which has a built-in Java compiler, provides a full model of Java source files, and Language-based advanced refactoring techniques and code analysis can be performed.

Currently, Google uses LogCat for error analysis, Dos Command-based layout optimization tools to diagnose inefficient structures of layouts, and processes between classes to identify and correct errors in programs. Provides Android debug monitoring system available.

1 is a diagram illustrating a filter function of a logcat according to the prior art. As shown in Figure 1, Google's logcat is a debugging (ⓓ: Debugging), simple information (ⓘ: Information), warning (ⓦ: Warning), error (ⓔ: Error), detailed information of the program developed by the developer It's a program that displays logs to indicate (ⓥ: Verbose).

In this case, when clicking one of the icons of ⓓ, ⓘ, ⓦ, ⓔ, ⓥ, not only the corresponding log is displayed, but the corresponding log is output first and the lower priority is also displayed. You'll need to make some settings that will help you identify them, and set up your filter by clicking the Add Filter icon.

Then, if you add the source to the file of the application (hereinafter referred to as 'application') of the program that the developer is developing, and press the RUN button, only the log above the priority set when adding the source is displayed. Since the logs are also displayed on the screen, if you add the icon of Add Filter to set the filter, a tab with the added name 'dalvikvm' is created next to the Log tab as shown in the drawing, and the tag is' Only dalvikvm 'will be printed.

Figure 2 is a diagram showing the ultra-edit according to the prior art. As shown in FIG. 2, in order to analyze an Android log, an Ultra edit or Excel, which can edit about 10,000 lines of log, is used.

3 illustrates a layout optimizer according to the prior art. As shown in Figure 3, Layout Optimizer (Layout Optimizer) is a program for Dos provided by Google, a program that analyzes the problems that may occur on the screen structure, similar Android debug monitoring system is between classes for debugging It is used as a program equipped to understand the process.

However, ① logcat only allows 10,000 lines of log, so if a developer concentrates on a lot of debugging work, a large amount of data will be written in the logcat. Logcat dies, or crashes, resulting in a relaunch of Eclipse, and even though filtering the log makes it easier for a developer to see the log, but the log is still piled up and dies. Since it was not changed, it had to be rerun continuously and only one tag was allowed in the filter, so even if the user wanted to filter by various information in the log window, only one could be filtered out, and the log was analyzed to analyze a large number of logs. If you save it to Ultra Edit, you'll get a strange nose It is not easy for a developer to analyze 10,000 logs one by one because they are often displayed. ② When using the layout optimizer, it is easy to analyze problems on the screen structure, but because it is output in a black DOS window. If the user interface is weak and ③ Android debug monitoring system is used, it traces its own development source and the internal source of Android debug monitoring system. Procedures were added indispensably, thus eliminating the developer's development time, making it impossible to focus on development, and the complicated process by the debug monitoring system is difficult for the developer to keep up with a large amount of interclass flows in the program. Debug The time required for there is a problem such as increasing exponentially.

The present application has been made to solve the above problems, by increasing or decreasing the number of lines of the log to be aligned step by step or linearly, the program due to log accumulation, even if the developer does not delete periodically In addition to preventing crashes and data loss, you can create new tabs for sorting one or more tags in a filter, create tags, move tags to another tab, or remove them. By providing an interface familiar to the same user, it aims to provide an Eclipse platform-based plug-in module that can tag various logs and sort them by tab, so that developers can easily analyze tens of thousands of logs.

This application applies to Eclipse, a non-DOS-based, general user interface to diagnose inefficient structures of layouts, automatically shows corrective recommendations on screen when optimization is completed, and information on problematic layouts. It aims to provide Eclipse platform-based plug-in module that can dramatically reduce developer's diagnostic time by automatically moving the area where is displayed to user-friendly interface such as double-click.

This application uses a dummy file instead of the original file to modify and delete it, thereby absolutely reducing the damage of the original file, analyzing the flow between classes, and selecting only the flow desired by the developer among hundreds or thousands of classes. By providing a class sequence flow chart that can be grasped at a glance, when it is difficult to grasp the relationship of source code according to the change of the Android user interface screen, it is aimed to provide an Eclipse platform-based plug-in module that can effectively grasp logical connection between classes. do.

In order to achieve the object as described above, the present application, among the embodiments, reads the log file for the Android-based device and a log docking plug-in that reads the log file for the Android-based application and displays the log analysis result according to the tag name. At least one of a layout optimization plug-in for displaying a log analysis plug-in for displaying a log analysis result according to a name, a layout optimization plug-in for displaying a diagnosis result of a layout for the application, and a class array plug-in for displaying an analysis result of an execution sequence for the application; Eclipse platform-based plug-in module, including the is made to solve the problem.

In one embodiment, the log read plug-in includes a database for storing the Android-based application program and log files; A control unit for controlling each component; A display unit for showing a program according to a command of the controller; A log reading activator which is an icon for analyzing the log; A file loading unit which loads a log file for analyzing the log; A log display unit generating an original of the log output through the file loading unit in a first tab and outputting the log in the first tab; A tag menu display unit configured to display a tag menu in the log display unit when the user input is input to the user interface; And a filter display unit for generating a second tab and rearranging the tag within the second tab when a tag name and a filter are set in the tag menu display unit. It is made to solve the problem using the Eclipse platform-based plug-in module, characterized in that it comprises a.

In one embodiment, the log Puppy plug-in is a database for storing the Android-based application program and log files; A control unit controlling each component; a display unit showing a program according to a command of the control unit; A logpuppy active unit which is an icon for analyzing a log of a connected device; A device selector for selecting a device to be analyzed among the connected devices; A log level setting unit which can adjust the number of logs of the device stepwise or linearly; A log display unit which generates a first tab and outputs the original of the log output through the device selection unit and a log step setting unit in the first tab; A tag menu display unit configured to display a tag menu when a user input is input to the user interface in the log display unit; A filter display unit which generates a second tab and rearranges the tag within the second tab when a tag name and a filter are set in the tag menu display unit; It is made to solve the problem using the Eclipse platform-based plug-in module, characterized in that it comprises a.

In one embodiment, the layout optimization plug-in includes a database for storing the Android-based application program and log files; A control unit for controlling each component; A display unit for showing a program according to a command of the controller; A layout optimization activator for diagnosing the layout of the project in the application program to be optimized; It is made to solve the problem by using the Eclipse platform-based plug-in module, comprising: a layout display unit for displaying a result diagnosed by the layout optimization active unit.

In one embodiment, the class array plug-in includes a database that stores an Android-based application program and logs; A control unit for controlling each component; A display unit for showing a program according to a command of the controller; An array activator for activating a flow between classes of a project in the application program; A dummy generator for generating a copy of the project; An array source unit for displaying a log generated by the application program during runtime; It is possible to solve the problem using the Eclipse platform-based plug-in module, including; class array display unit for graphically displaying the logical flow between classes using the application program and the log of the dummy generator and the array source unit.

As described above, the disclosed technology of the present application having the configuration as described above can be set and allowed step by step or linearly so that the number of rows of logs to be aligned can be increased or decreased, so that the developer does not have to periodically delete the log. You can prevent program-downs and data loss due to accumulation, allow you to create new tabs for sorting one or more tags in a filter, create tags, move tags to another tab, or remove them. By providing a user-friendly interface such as a button, various logs can be tagged and classified by tabs, making it easy for developers to analyze tens of thousands of logs. ② Not using DOS-based to diagnose inefficient structure of layout. Is applied to Eclipse, a common user interface, By showing correction recommendations on the screen and automatically moving the area where information on the problematic layout is displayed to a user-friendly interface such as double-clicking, the diagnostic time of the developer can be dramatically reduced. By using dummy files instead of modifying and deleting, the damage of the original file is absolutely reduced, and the flow between classes is analyzed to select only the desired flow among hundreds or thousands of classes, and the class can be identified at a glance. By providing a sequence flow diagram, it is possible to effectively grasp the logical connection between classes as a picture when it is difficult to grasp the relationship of the source code according to the change of the Android user interface screen.

1 is a diagram illustrating a filter function of a logcat according to the prior art.
Figure 2 is a diagram showing the ultra-edit according to the prior art.
3 illustrates a layout optimizer according to the prior art.
4 is a block diagram illustrating an Eclipse platform based plug-in module of the technology disclosed in this application.
FIG. 5 is a block diagram illustrating a logdog plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application.
FIG. 6 is a program screen on which the log dog plug-in of FIG. 5 is executed.
FIG. 7 is a program screen in which multiple selection of a tag is executed in the log dog plug-in of FIG. 5.
8 is a program screen illustrating a method of reading a log read file by the log read plug-in of FIG. 5.
FIG. 9 is a block diagram illustrating a log Puppy plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application.
FIG. 10 is a program screen on which the logpuff plug-in of FIG. 9 is executed.
FIG. 11 is a program screen on which the logpuff plug-in of FIG. 9 is executed.
12 is a program screen on which the log Puppy plug-in of FIG. 9 is executed.
FIG. 13 is a program screen in which the filter function of the log read and log puppy plug-ins of FIGS. 5 and 9 is executed.
14 is a block diagram illustrating a layout optimization plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application.
FIG. 15 is a program screen on which the layout optimization plug-in of FIG. 14 is executed.
16 is a block diagram illustrating a class array plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application.
17 is a program screen on which the class array plug-in of FIG. 16 is executed.
FIG. 18 is a program screen on which the class array plug-in of FIG. 16 is executed.

The description of the disclosed technique is merely an example for structural or functional explanation and the scope of the disclosed technology should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the disclosed technology should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the disclosed technology should not be construed as being limited thereby, as it does not mean that a particular embodiment must include all such effects or merely include such effects.

Meanwhile, the meaning of the terms described in the present application should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions describing the relationship between the components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring to", should be interpreted as well.

It should be understood that the singular " include "or" have "are to be construed as including a stated feature, number, step, operation, component, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosed technology belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.

Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings.

4 is a block diagram illustrating an Eclipse platform based plug-in module of the technology disclosed in this application. Referring to FIG. 4, the Eclipse platform-based plug-in module 1 according to the present application may include a database 10, a controller 20, a display unit 30, a logdog plug-in 40, and a logpuppy plug-in. (LogPuppy Plug-in, 50), Layout Optimizer (Layout Optimizer, 60), and Class Array Plug-in (Sequencer, 70).

The database 10 is provided to store a program and a log written by an Android application developer, and is also provided to store a program of an Eclipse platform-based plug-in module 1 according to the present application.

The control unit 20 inputs each component such as the database 10, the display unit 30, the log dog plug-in 40, the log Puppy plug-in 50, the layout optimization plug-in 60, and the class array plug-in 70. It is equipped to output, command, and control each component.

The display unit 30 is provided to show a program window of the log dog plug-in 40, the log puppy plug-in 50, the layout optimization plug-in 60, and the class array plug-in 70 according to a command of the controller 20. Looking at each component of the program window provided in the display unit 30, the developer inputs each component with a mouse or the like and displays the respective plug-ins 40, 50, 60, and 70 to the developer.

The log docking plug-in 40 is configured by the developer for debugging logs (ⓓ: Debugging), simple information (ⓘ: Information), warning (Error), error (ⓔ: Error), and detailed information (ⓥ: Verbose). You can sort within tabs formed by a single tag name, and drag and drop without having to open step by step folders within the operating system (Windows OS), which is a step by step folder system, even when you want to open a log file. Drag and drop the file into) to open it.

The logpuppy plug-in 50 can increase or decrease the number of rows of logs sequentially, such as 10,000, 20,000, 30,000, 40,000, Oman, etc., so that more than 10,000 logs can be stacked. More than 10,000 lines of logs, ⓓ: Debugging, Simple Information, Warning, Error, Error, Verbose. In addition, you can sort within the tab formed by the tag name set by the developer.

The layout optimization plug-in 60 is designed to allow users to easily use the layout diagnosis shown in the existing DOS window, to consider users familiar with the Eclipse platform, and to arrange and output the Eclipse platform.

Class array plug-in 70 is provided to show the logic flow of the class in the form of a picture so that the developer can grasp at a glance the logic flow between classes among the classes that can be inserted up to thousands of large programs, Android It can be effectively used when it is difficult to grasp the relationship of source code according to the change of user interface screen, and provides an intuitive user interface for defect tracking and reasoning.

FIG. 5 is a block diagram illustrating a logdog plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application. Referring to FIG. 5, the log read plug-in 40 according to the present application includes a log read activation unit 41, a file loading unit 42, and a log read display unit 43.

Here, although the components of the log dog plug-in 40 are shown as being inside the display unit 30 in the drawing, this is displayed to the developer due to the nature of the program and at the same time a command may be input to an input device such as a mouse and the like. As shown in the figure, the logdog plug-in 40 is not installed in a monitor, which is the display unit 30, and these are components built in the logdog plug-in 40.

The log read activator 41 is an input component in the form of an icon for executing the log read and an output component displayed on the screen. When the developer clicks the icon of the log read activator 41, the log read display 43 is activated. (Launch)

The file loading unit 42 is a component for loading a log file. When the log file is selected, the file loading unit 42 does not need to sequentially open the step by step folder in the Windows OS (Operating System) formed as a step by step folder system. and Drop files are configured to open when dropped.

The log read display unit 43 includes a log display unit 43a, a tag menu display unit 43b, and a filter display unit 43 (1) ... ... 43 (n). The log display unit 43a includes a file loading unit 42. It is provided to form a tab to output the original file itself output through the to be output therein.

When the developer sets the tag name and the filter in the log display unit 43a, the filter display unit 43 (1) ... ... 43 (n) increases the tabs one by one and rearranges them. The number of 43 (1) …… 43 (n)) is determined, i.e., if only one filter is set, the log source files are sorted on the first tab, and the logs according to the first filter are displayed on the first tab. 1)), in the nth tab, logs according to the n-1th filter are arranged in the filter display part 43 (n).

The tag menu display unit 43b is shown due to the user interface adapted to the developer such as the right mouse button in the area where the log is arranged, if the user had to press the green button in the shape of '╋' to form a tag. Is composed of 『NEW』, 『Move Tag』, 『Remove Tag』.

"NEW" is to create a new tab by creating a new filter with the tag as a search condition, "Move Tag" is to move the tag to a filter in another tab, and "Remove Tag" is to move the tag to the current filter. If you want to see the tag at the same time, you can write it by writing an operator like 『,』.

In other words, if you want to see the tag A and the tag B in one tab at the same time, write the comma-like operator and write 『A, B』. The filtered logs will be sorted in one tab within one screen.

In addition, when selecting a log and using a user-adapted user interface such as the right mouse button, "NEW" is displayed. When the icon is pressed, the selected tag is entered without having to enter the tag and filter text. The filter creation window is created automatically, so that logs sorted by the selected filter are sorted in a new tab.

In addition, by selecting one or more logs and using a user-adapted user interface, such as the right mouse button, "NEW" is displayed, and pressing the icon causes multiple selected tags to be entered without the need to enter tags and filter text. The input filter creation window is created automatically, so that logs with multiple tags sorted by the selected filter are sorted in a new tab.

Here, if there are two or more filters, you can move tags with any log between filters at once using 『Move Tag』. If there are less than two filters, there is no filter to move, so you do not activate 『Move Tag』. For convenience, users can activate the 『Move Tag』 only when there are more than two.

In addition, 『Remove Tag』 is used when you want to delete any tagged logs in a filter at once. The removed log is only shown where the original log files are arranged. The Remove Tag is activated only where the logs are gathered, because the original log must be kept unmodified and deleted, after which the logs can be rearranged by various filters.

FIG. 6 is a program screen on which the log dog plug-in of FIG. 5 is executed. As shown in Fig. 6, the "L" icon of ① shows the log reading active part 41, and when this icon is pressed, the log reading display part 43 called "LogDog" of ② is activated. Press to load the log file or drag and drop the file onto the log read display 43, a tab called Log is created in the log read display 43, and the original log file is aligned in the log display 43a of ④. .

Then, if you want to create a filter in the log display unit 43a, or move any tagged logs to another filter at once, or to delete it, press the right mouse button in the log display unit 43a. The tag menu display unit 43b is generated, and a tagged filter for the selected log is generated, moved to another filter, or deleted.

FIG. 7 is a program screen in which multiple selection of a tag is executed in the log dog plug-in of FIG. 5. As shown in Fig. 7, if you want to see the tags A, B, C, D, E at the same time, if you write a comma connected to the tag in the filter and write the A, B, C, D, E in the tab The tagged logs are sorted, and a detailed embodiment of the tag menu is also executed in the logpuppy plug-in, which will be described in detail below.

8 is a program screen illustrating a method of reading a log read file by the log read plug-in of FIG. 5. As shown in FIG. 8, when the file is dragged into the log display unit 43a by dragging and dropping, the log file is opened and may be opened by the same function as the existing file open.

FIG. 9 is a block diagram illustrating a log Puppy plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application. Referring to FIG. 9, the log ppu plug-in 50 according to the present application includes a log ppu activation unit 51, a device selection unit 52, a log step setting unit 53, and a log ppu display unit 54.

Here, although the components of the log-puppy plug-in 50 are shown as inside the display unit 30 in the drawing, this is displayed on the developer due to the nature of the program and at the same time a command can be input to an input device such as a mouse and As shown in the figure, the components of the log puff plug-in 50 are not installed in the monitor, which is the display unit 30, which are components embedded in the log puff plug-in 50.

The logpuppy activator 51 is an input component in the form of an icon for executing the logpuppy and an output component displayed on the screen. When the developer clicks the icon of the logpuppy activator 51, the logpuppy display unit 54 is activated. (Launch)

The device selector 52 connects the log to a developer's computer or the like when the user wants to view the log of the device, and selects a device for which the log is to be viewed as a selection box type for selecting the type of the connected device.

Unlike the existing Eclipse platform where sorting of more than 10,000 logs was not possible, the log level setting unit 53 is configured to sort more logs, thereby preventing the Eclipse platform from crashing due to too many logs. It is provided so as to be able to select the number of sorting logs in steps of 10,000, 20,000, 30,000, 40,000, 50,000, etc., and can be set linearly as the user wants.

The log Puppy display section 54 includes a log display section 54a, a tag menu display section 54b, and a filter display section 54 (1) ...... 54 (n), and the log display section 54a includes a device selector 52. It is provided to form a tab to output the original log file itself of the selected device through the outputted therein.

When the developer sets the tag name and the filter in the log display unit 54a, the filter display unit 54 (1) ... 54 (n) increases and rearranges the tabs one by one, and the filter display unit ( 54 (1) …… 54 (n)) is determined, that is, if only one filter is set, the log source files are sorted on the first tab, and the logs according to the first filter are displayed on the first tab. 1)), in the nth tab, the logs according to the n-1th filter are arranged in the filter display unit 54 (n).

The tag menu display unit 54b is shown due to the user interface adapted to the developer such as the right mouse button in the area where the log is arranged, if the user had to press the green button of the "╋" shape in order to form a tag. Is composed of 『NEW』, 『Move Tag』, 『Remove Tag』.

"NEW" is to create a new tab by creating a new filter with the tag as a search condition, "Move Tag" is to move the tag to a filter in another tab, and "Remove Tag" is to move the tag to the current filter. If you want to see the tag at the same time, you can write it by writing an operator like 『,』.

In other words, if you want to see the tag A and the tag B in one tab at the same time, write the comma-like operator and write 『A, B』. The filtered logs will be sorted in one tab within one screen.

In addition, when selecting a log and using a user-adapted user interface such as the right mouse button, "NEW" is displayed. When the icon is pressed, the selected tag is entered without having to enter the tag and filter text. The filter creation window is created automatically, so that logs sorted by the selected filter are sorted in a new tab.

In addition, by selecting one or more logs and using a user-adapted user interface, such as the right mouse button, "NEW" is displayed, and pressing the icon causes multiple selected tags to be entered without the need to enter tags and filter text. The input filter creation window is created automatically, so that logs with multiple tags sorted by the selected filter are sorted in a new tab.

Here, if there are two or more filters, you can move tags with any log between filters at once using 『Move Tag』. If there are less than two filters, there is no filter to move, so you do not activate 『Move Tag』. For convenience, users can activate the 『Move Tag』 only when there are more than two.

In addition, 『Remove Tag』 is used when you want to delete any tagged logs in a filter at once. The removed log is only shown where the original log files are arranged. The Remove Tag is activated only where the logs are gathered, because the original log must be kept unmodified and deleted, after which the logs can be rearranged by various filters.

FIG. 10 is a program screen on which the logpuff plug-in of FIG. 9 is executed. As shown in Fig. 10, the "E" icon of ① shows the log Puppy activation unit 51, and when this icon is pressed, the log Puppy display unit 54 called "LogPuppy" of ② is activated, When the device is selected in the device selector 52 that can select the device "LG_ANDROID_P500_GB_", a tab called Log is created in the log Puppy display unit 54 and the original log file is arranged in the log display unit 54a of ④. Will be.

Then, if you want to create a filter in the log display section 54a, or move any tagged logs to another filter at once, or to delete it, press the right mouse button in the log display section 54a. The tag menu display unit 54b is generated, and a tagged filter for the selected log is generated, moved to another filter, or deleted.

FIG. 11 is a program screen on which the logpuff plug-in of FIG. 9 is executed. As shown in FIG. 11, in the case where two devices are connected, that is, when emulator-5554 and emulator-5556 are connected in the drawing, the device selector 52 is activated to view a log. One file can be selected, and if selected, the log of the selected device is displayed.

12 is a program screen on which the log Puppy plug-in of FIG. 9 is executed. As illustrated in FIG. 12, when the user wants to view more than 10,000 logs, the logpuppy plug-in may increase or decrease in steps, such as 10,000 Lines, 20,000 Lines, 30,000 Lines, 40,000 Lines, 50,000 Lines, or linearly. It is apparent that the user can set as many numbers as the user wants, and the incremental log line number can be changed as much as the user wants.

FIG. 13 is a program screen in which the filter function of the log read and log puppy plug-ins of FIGS. 5 and 9 is executed. As shown in FIG. 13A, a tag may be multi-selected by dalvikvm and MediaScanner in the filter, so that only logs with a multi-selected tag are sorted in the tab of the Multi Tag Filter.

As shown in FIG. 13B, when the right mouse button is pressed by the developer, a menu is displayed, of which "NEW" indicates that a filter such as a tag attached to the selected log creates a new tab and sorts it within the tab. Logs, such as tags attached to the selected log, are all sorted within that tab. In the drawing, you have selected a log labeled dalvikvm, so all logs tagged dalvikvm are sorted within the tab of dalvikvm.

In addition, as shown in FIG. 13C, when a right mouse button is pressed by a developer, a menu is displayed. Among them, "NEW" indicates that a filter, such as a tag attached to a multi-selected log, creates a new tab and displays the tab. Logs, such as tags attached to multiple selected logs, are all sorted within that tab. In the drawing, multiple logs with ThrottleService, SntpClient, and dalvikvm are selected, so all logs tagged ThrottleService, SntpClient, and dalvikvm are multi-tag. Will be sorted within the Filter.

As shown in FIG. 13D, “Move Tag”, which is a tag movement between filters, activates a menu only when there are one or more other filters besides a tab in which the original log file is sorted, and all logs having a tag attached to the selected log are displayed. In the drawing, the Multi Tag Filter has already been created, and when the left button is pressed within the Log tab, the original log file, the Multi Tag Filter, which is the name of the previously created filter, is activated. All logs attached to the selected tag, MediaScanner, are moved and sorted by the Multi Tag Filter.

If you want to delete the tagged log at a time, as shown in Figure 13e, select one log and press the shortcut key such as the right mouse button to select "Remove Tag", the log tagged with any tag is deleted at once The menu can be activated and deleted only if there are one or more other filters besides the tab in which the original log file is sorted. In the drawing, the Multi Tag Filter has already been created, and within the tab, select the log with the MediaScanner When you click 『Remove Tag』, all logs attached to MediaScanner are deleted in the Multi Tag Filter tab.

The logdog and logpuppy plug-in disclosed in this application are essential elements of the Eclipse platform-based plug-in module according to the present application, and the following layout optimization plug-in and class array plug-in may be selectively mounted in the Eclipse plug-in module, and the number of cases Is shown in Table 1 below.

Eclipse plug-in module components CASE1 Logdog + Logpy + Layout Optimization Plug-in CASE2 Log Dog + Log Puppy + Class Array Plugin CASE3 Log Dog + Log Puppy + Layout Optimization Plug-in + Class Array Plug-in

14 is a block diagram illustrating a layout optimization plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application. Referring to FIG. 14, the layout optimization plug-in 60 according to the present application includes a layout optimization activation unit 61 and a layout display unit 62.

Here, although the components of the layout optimization plug-in 60 are shown as being inside the display unit 30 in the drawing, this is displayed to the developer due to the characteristics of the program and at the same time a command may be input to an input device such as a mouse. As shown in the drawing, the components of the layout optimization plug-in 60 are not installed in the monitor, which is the display unit 30, and the like are the components embedded in the layout optimization plug-in 60.

The layout optimization activator 61 is an input component in the form of an icon for executing layout optimization and an output component displayed on the screen. When the developer clicks on the icon of the layout optimization activator 61, the project exists on the workspace. The list will be visible, and clicking on one of the project lists on the workspace will start the layout diagnosis.

In other words, when the list of application creation programs is selected, layout diagnosis is started on the layout display unit 62, and since the intuitive user interface is provided to the developer who is not DOS-based, the layout display unit (for easy interpretation of the diagnosis result value of the layout) 62) or pop-up window can be displayed to the developer with the explanation, it is obvious that it can be variously changed.

Accordingly, when the diagnosis of the layout optimization plug-in 60 is completed, the result is automatically displayed on the screen, and the layout display unit 62 displays the layout resource name, location, problem, and line number in question, which support the sorting function in a table format. If you double-click the area where the information about the layout in question is displayed, the file is opened and you can automatically move to the problem line.

FIG. 15 is a program screen on which the layout optimization plug-in of FIG. 14 is executed. As shown in FIG. 15, the "O" icon of ① shows the layout optimization activator 61. When this icon is pressed, a list of Android projects existing in the workspace is shown, and one of them is selected. Layout diagnostics begin.

Then, when the diagnosis is completed, the layout display unit 62 called "Layout" of ② is activated and arranged in a table format. When the user double-clicks an area where the information of ③ is displayed, the corresponding file is opened to automatically move to the line having the problem. And, examples of sorting in a table form are shown in Table 1 below, and it is obvious that descriptions of other methods may be added, or may be described in other forms.

Sample results Explanation -11:17 This LinearLayout layout or its FrameLayout parent is useless If you don't need some layout --1: -1 This layout has too many nested layouts: 13 levels, it should have <= 10! The hierarchy is too deep --1: -1 This layout has too many views: 81 views, it should have <= 80! Too many objects in a layout -7:23 The root-level <FrameLayout /> can be replaced with <merge /> If a better way exists for performance

16 is a block diagram illustrating a class array plug-in among Eclipse platform-based plug-in modules of the technology disclosed in the present application. Referring to FIG. 16, the class array plug-in 70 according to the present application includes an array active unit 71, a dummy generator 72, an array source unit 73, and a class array display unit 74.

Here, although the components of the class array plug-in 70 are shown as being inside the display unit 30 in the drawing, this is displayed to the developer due to the characteristics of the program and at the same time a command may be input to an input device such as a mouse. As shown in the drawing, the components of the class array plug-in 70 are not installed in the monitor, which is the display unit 30, and the like are the components embedded in the class array plug-in 70.

The array activator 71 is an input component and an output component displayed on a screen for executing an array activity that can be illustrated in a graphic form so that the developer can analyze the logical flow between classes desired by the developer at a glance. When the developer clicks on the icon of the array activator 71, the windows of the dummy generator 72 and the array source unit 73 are opened.

The dummy generator 72 creates a dummy of the Android project, adds logic for analyzing the flow between classes, and an icon for collecting, starting, stopping, and deleting logs although not shown in the drawing. The interface is further provided, and when this icon is pressed, a task of drawing a flow chart to grasp the flow between classes is performed.

The array source unit 73 is an area in which the collected logs are displayed, and becomes a source of the class array flow chart. The class array display unit 74 is an area in which the logs uploaded to the array source unit 73 are diagrammatically expressed. Clicking a method opens and displays the method in Eclipse, and the drawn object can be moved by dragging the mouse.

In other words, since the existing debug monitoring system traces its own development source and the internal source of the monitoring system itself, it is difficult to see the flow of its own development source, but the technique disclosed in the present application is a copy of its own development. By adding trace code so that only the source can be traced, the logic flows between classes can be summarized at a glance, giving users a breakthrough user interface.

17 is a program screen on which the class array plug-in of FIG. 16 is executed. As shown in Fig. 17A, the "Ｋ" icon of ① shows the array active unit 71. When the icon is pressed, the screen shown in Fig. 17B is shown. Referring to Fig. 17B, Target will show you a list of Android projects in Eclipse's workspace.

② 'Make Project' icon is a dummy generating unit 72, and if pressed, a dummy project, that is, a copy of the original project is created in the original project on the workspace, and the dummy project is a copy of the original project as it is. It is a project with tracking code added later. It is to leave a log for tracking at run time. The reason for inserting tracking code by making a dummy is to prevent modification of the original project.

If you press 『Start』 among 『Start』, 『Stop』, 『Clear Logs』, 『Draw Diagram』 icons of ③, the log of the currently running process for tracking is uploaded. If you press 『Stop』, the log generation is stopped. Logging between start and end is shown in the array source unit 73 which is ④, and when 『Draw Diagram』 is pressed, the flow chart between classes is shown on the class array display unit 74 of ⑤ based on the stacked logs. Done.

FIG. 18 is a program screen on which the class array plug-in of FIG. 16 is executed. As shown in FIG. 18A, a list of Android projects called ApiDemos is displayed by pressing the K icon, and clicking on it sets as a target, and when a button called Make Project is created as shown in FIG. 18B, a copy is created on the workspace. A dummy project named ApiDemos_Sequencer is created.

As shown in FIG. 18C, when the Start button is clicked, the log of the currently running process for tracking is uploaded, and when the Stop button is clicked, the log generation is stopped, and when the button in the Draw Diagram is clicked, the connection between classes is shown in the figure. do.

The Eclipse platform-based plug-in module including at least one of the log dog, log puppy, layout optimization, and class array plug-in disclosed in the present application is created in the same way as the existing interface, and there is no objection to the developer. You can easily create and modify filters on a tag basis using the right mouse button, and incrementally and linearly increase or decrease the maximum number of logs to be sorted. It is easy to re-verify, easy to see by reviewing the results in a table, easy to modify by double-clicking to the corresponding source, and shows the actual process log by operating in the runtime environment. Only the parts you want to check can be expressed in pictures. When you click the array you want to cut and can go directly to that source can provide an intuitive interface for the user.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the following claims It can be understood that

1: Eclipse platform based plug-in module
10: Database 20:
30: display unit 40: log dog plug-in
41: Log reading active unit 42: File loading unit
43: log display unit 43a: log display unit
43b: Tag menu display unit 43 (1): First filter display unit
43 (n): Control filter display section 50: Logpuppy plug-in
51: Log Puppy Activation unit 52: Device selection unit
53: Log step setting unit 54: Log Puppy display unit
54a: log display portion 54b: tag menu display portion
54 (1): First Filter Display 54 (n): nth Filter Display
60: Layout Optimization plug-in 61: Layout Optimization Active Part
62: layout display 70: class array plug-in
71: array active unit 72: dummy generation unit
73: array source portion 74: class array display portion

Claims (21)

In the Eclipse platform-based plug-in device that runs as a computer program,
A log docking plug-in that reads a log file for an Android-based application and displays a log analysis result according to a tag name;
A log-puppy plug-in that reads log files for Android-based devices and displays log analysis results according to tag names;
A layout optimization plug-in for displaying a diagnosis result of a layout for the application; And
Eclipse platform-based plug-in device including a class array plug-in for displaying the analysis result of the execution sequence for the application.
The method of claim 1, wherein the log read plug-in
A database that stores an Android-based application program and log files;
A control unit for controlling each component;
A display unit for showing a program according to a command of the controller;
A log reading activator which is an icon for analyzing the log;
A file loading unit which loads a log file for analyzing the log;
A log display unit generating an original of the log output through the file loading unit in a first tab and outputting the log in the first tab;
A tag menu display unit configured to display a tag menu in the log display unit when the user input is input to the user interface; And
A filter display unit which generates a second tab and rearranges the tag within the second tab when a tag name and a filter are set in the tag menu display unit;
Eclipse platform-based plug-in device comprising a.
The method of claim 2, wherein the tag menu display unit
Eclipse platform-based plug-in device, consisting of "NEW", "Move Tag" and "Remove Tag".
The method of claim 3, wherein the "NEW"
The log display unit generates a new filter having a search condition for a corresponding tag of at least one or more positions in which the user interface is input, and arranges logs arranged in the new filter in the second tab. Plug-in device.
The method of claim 3, wherein the "Move Tag"
It is activated only when at least one filter display unit is formed, and the log including a corresponding tag of at least one position where the user interface is input from the log display unit is arranged in the second tab of the filter display unit. Eclipse platform based plug-in device.
The method of claim 3, wherein the "Remove Tag"
When at least one filter display unit is formed, the filter is activated only in the filter display unit, and the log including the corresponding tag of at least one or more positions where the user interface is input in the filter display unit is deleted in the filter display unit. Eclipse platform-based plug-in device.
The method of claim 2, wherein the file loading unit
Eclipse platform based plug-in device, characterized by being operated by drag and drop.
The method of claim 1, wherein the log Puppy plug-in
A database that stores an Android-based application program and log files;
A control unit for controlling each component;
A display unit for showing a program according to a command of the controller;
A logpuppy active unit which is an icon for analyzing a log of a connected device;
A device selector for selecting a device to be analyzed among the connected devices;
A log level setting unit which can adjust the number of logs of the device stepwise or linearly;
A log display unit which generates a first tab and outputs the original of the log output through the device selection unit and a log step setting unit in the first tab;
A tag menu display unit configured to display a tag menu when a user input is input to the user interface in the log display unit;
A filter display unit which generates a second tab and rearranges the tag within the second tab when a tag name and a filter are set in the tag menu display unit;
Eclipse platform-based plug-in device comprising a.
The method of claim 8, wherein the log step setting unit
Eclipse platform-based plug-in device, characterized in that provided to increase or decrease the number by which the log is sorted.
The method of claim 8, wherein the tag menu display unit
Eclipse platform-based plug-in device, consisting of "NEW", "Move Tag" and "Remove Tag".
The method of claim 10, wherein the "NEW"
The log display unit generates a new filter having a search condition for a corresponding tag of at least one or more positions in which the user interface is input, and arranges logs arranged in the new filter in the second tab. Plug-in device.
The method of claim 10, wherein the "Move Tag"
It is activated only when at least one filter display unit is formed, and the log including a corresponding tag of at least one position where the user interface is input from the log display unit is arranged in the second tab of the filter display unit. Eclipse platform based plug-in device.
The method of claim 10, wherein "Remove Tag"
When at least one filter display unit is formed, the filter is activated only in the filter display unit, and the log including the corresponding tag of at least one or more positions where the user interface is input in the filter display unit is deleted in the filter display unit. Eclipse platform-based plug-in device.
The method of claim 1, wherein the layout optimization plug-in
A database that stores an Android-based application program and log files;
A control unit for controlling each component;
A display unit for showing a program according to a command of the controller;
A layout optimization activator for diagnosing the layout of the project in the application program to be optimized;
A layout display unit displaying a result diagnosed by the layout optimization activator;
Eclipse platform-based plug-in device comprising a.
The method of claim 14, wherein the layout optimization active unit
An Eclipse platform based plug-in device for performing layout diagnosis on one of the project lists present in the workspace.
15. The display device of claim 14, wherein the layout display unit
And sort the results in a pop-up window or a table format, and the results include layout resource names, locations, problems, and line numbers.
The method of claim 16, wherein the layout display unit
If there is a user input in the user interface in the layout display unit, Eclipse platform-based plug-in device, characterized in that for opening and displaying the resource corresponding to the input position.
The method of claim 1, wherein the class array plug-in
A database that stores an Android-based application program and logs;
A control unit for controlling each component;
A display unit for showing a program according to a command of the controller;
An array activator for activating a flow between classes of a project in the application program;
A dummy generator for generating a copy of the project;
An array source unit for displaying a log generated by the application program during runtime;
A class array display unit configured to display and display a logical flow between classes using an application program and a log of the dummy generator and the array source unit;
Eclipse platform-based plug-in device comprising a.
19. The method of claim 18, wherein the class array plug-in
An interface for starting, stopping, and deleting log collection occurring during the runtime;
Eclipse platform-based plug-in device further comprising a.
19. The apparatus of claim 18, wherein the class array display unit
If there is a user input in the user interface in the class array display unit, Eclipse platform-based plug-in device, characterized in that for opening and displaying a method corresponding to the input position.
19. The apparatus of claim 18, wherein the class array display unit
If there is a user input in the user interface in the class array display unit, the graphical platform-based plug-in device is moved to the position where the user input is input.

Images