My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 55: Long load time for admin interface
2 people starred this issue and may be notified of changes. Back to list
 
Project Member Reported by rj...@student.aau.dk, May 16, 2011
The load time for the admin interface is so long that in some cases the phone will lock before the interface is shown. The problem seems to be with the main interface, as it will also take a long time to load when going back to it from an applications settings, or the girafplace client.

This happens with the newest version (r1142), on my personal phone, a Galaxy S
May 26, 2011
Project Member #1 steffa...@gmail.com
Marked as future improment
Status: WontFix
May 26, 2011
Project Member #2 steffa...@gmail.com
This is what we wrote as future impromenet:

On older Android devices made for Android 2.1, and on some few devices running Android 2.2 natively, the GUI of the administration module loads slowly. The reason for this poor performance is found in the great  amount of tasks that are executed when loading the root menu of the administration module GUI. Here, the list of all GIRAF applications are traversed and it is determined whether the application contains a settings.xml file or not. Furthermore, as the GUI only lists GIRAF applications with visible settings declared in the settings.xml file, the GUI is also responsible for parsing through each settings.xml file, and count the number of visible settings. If the count is greater than zero, the application can be shown, otherwise, it will not be shown. The process of counting the number of visible settings utilizes a parsing method originally build and currently used for GUI generation based on a single settings.xml file - for instance, when a single application is selected, the GUI for this application's visible settings is generated. The parser builds an object structure reflecting the menu structure in the selected application's settings.xml file. By using the same parsing method to determine the number of visible settings, a large overhead occurs, as there is no need for a representation of the menu structure at this point. Therefore, to solve this issue, different solutions could be considered.
Status: Accepted

Powered by Google Project Hosting