See into S60
» Subscribe
» Favorite Links
» What is S60?
» Freeware & Trials
» S60 devices
» Hints and tips

» About this blog
» Blognotes (15)
» Bugs and Workarounds (4)
» Build tools (5)
» Carbide.c++ 1.1 (4)
» Carbide.c++ 1.2 (8)
» Carbide.c++ 1.3.x (9)
» Carbide.c++ 2.0.x (12)
» Carbide Plug-Ins (4)
» CodeWarrior (2)
» FAQ (6)
» Future directions (25)
» General (48)
» Off-topic (5)
» On-device debugging (13)
» Performance Investigator (2)
» Product features (18)
» Product releases (16)
» Screencast (14)
» Support (36)
» Tool setup (6)
» UI Designer (8)
» Usability (18)
» Work in Progress (14)
» Write-build-debug (4)
» Tommi's Reports from Wonderland
» Voice of S60
» Creating Carbide C++
» S60 Multimedia Blog
» The Convergence Zone
» Web Browser for S60 Blog
» Consumed by S60
» Java for S60
» Mobile Web Server
» Mobile Security
» See into S60
» Business2GO
» Nokia Podcasting Application Blog
» New Remote Connections View
» Terminating Multiple Processes
» Agile Tuning of the Austin Team
» Introduction to the workspace screencast
» Adding DLLs while Debugging
» September 2008
» August 2008
» July 2008
» June 2008
» May 2008
» April 2008
» March 2008
» February 2008
» August 2007
» May 2007
» April 2007
» March 2007
» February 2007
» January 2007
» December 2006
» November 2006
» October 2006
» September 2006
» August 2006
» July 2006
» June 2006
Subscribe
Links
July 20, 2006 Platform security -- Capability scanner mockup Posted by Markus Ahonen at 02:46 PM | Categories: Future directions, Work in Progress

capscanner.png
In a previous entry, I mentioned that we were looking into how we could ease the pain of working with platform security. We reviewed the process and the many steps it takes to get a Developer Certificate, as well as how we could help in figuring out what capabilities your app is using. We then developed UI mockups for the proposed solutions. The mockups are:
1) PlatSec Capability Scanner -- for displaying what capabilities are used in the current project
2) Certificate Manager -- to manage developer certificates, including requesting new ones and sharing existing ones

The PlatSec Capability Scanner is simple in UI, but requires quite a bit of underlying work, so the UI proto is really simple. I'm still working on the Certificate Manager presentation, since it's simple to do but has quite a bit of UI elements -- I'll post it later.

capscannerpdf.png

Disclaimer + warning + request: These might never appear in Carbide.c++, and the UI protos may look ugly, because they're protos. Nevertheless, please comment; your comments will impact the final design.


Permalink |

Comments

- how does the user invoke the tool? Is there a command to run the scan, or is it a build step?
- does it retain just the results of the last scan, or can it retain results for each project/build configuration?
- is there a way to apply the results to the build settings, or is the user supposed to manually do that?
- the function entries should have both class name (where present) and function, not just function.
- You might consider a tree presentation, where the top-level nodes are the required capabilities and the children are the source code locations.

Posted by: Anonymous | July 21, 2006 09:14 AM

Thanks for the comments! Quick replies...

- Ideally this would be a build step, turned on by default if the database exists that contains the API/function-->Capability mapping

- So far this would retain only the results for the latest build; I suppose they could be stored, but it would require more elaborate UI so I'd need to see a clear reason to do so

- Currently, the user must add these manually -- the output format is such that you can copy-paste the results into the MMP file. Ideally (in later editions), we should/could be able to pick up the capabilities and add them to the MMP. This may get complicated if the project is complex.

- You're right -- the mockup for the capability-file-etc table is a bit quick. It will contain the classname as well.

- We went with a table view since it allowed sorting multiple ways in a quick and intuitive way -- e.g. list by filename, list by classname.

//markus

Posted by: Markus Ahonen | July 21, 2006 09:37 AM


Post a comment







«Back to previous page