OpenNotes Project Idea

I use Microsoft OneNote application to capture my meeting minutes, analysis scraps, rough data, phone numbers, etc. it is handy application but not for free (My company can offer, not me). I understand there are lot of opensource alternatives, but nothing fits my requirements. Decided to start new project to satisfy my needs.

Project : OpenNotes
Platform : Linux
Tools : C++ (Qt 3/4)
Hosting: Google Code
Idea:
- OPTabWidget: Tab widget where notes can be created instantly,
- Tab converts the content into tabular.
- Content starts with * converts the content to list.
- Possibility to move the text inside the editor
- Understanding Links, phonenumber, address etc
- Simplified mind map implementation
- Possibility to insert images in simple shortcut.
- Gestures implementation
- Plugin option, so any new feature can be implemented.
- Custom operation control, were user can define their own action.
- Wiki language support
- Calendar support
- Possibility to convert the control to dairy
- TODO reminders support
- Calculator support, eg: 3,2 + 4,6, * 6,7) = should provide automatic value (for any complex scientific calculation)
- Simple char support , eg LineCart X:10,12,12,15 Y:100,200,300 should convert it to line chart
- Google Notebook API synchronization.
- Video embedding option
- Share the notes (with rights)
- Notes template
- Web Link display
- easy extenstion option with DSL

Hope it is possible to implement above idea , let me give a try and come back to you in another blog.

Bundle Repo Preference

Next step in the osgi-flow-designer project is to implement preference for Bundle Repository commands. Idea is not to recreate the Karaf functionalities in the Eclipse, instead Karaf will be accessed from the eclipse.

Preference has been added to extend the obr:listUrl, obr:addUrl, obr:list, obr:deploy and obr:removeUrl Karaf commands.

Preferences:




Add Bundle Repository URL:



List Bundles:





On double click selected will be deployed. Next step is to identify the services each bundle exports and imports. Once the services are identified using GEF/GMF bundles and services will be rendered in the viewer.

If you are interested in participating in this project development reach me @ rathishraj@gmail.com

Checkout the project from http://code.google.com/a/eclipselabs.org/p/osgi-flow-designer/

Very much interested with the Apache Karaf concept and its kind of useful contribution to the OSGi framework world. In future I can feel that lot of standalone/web/mobile apps will use this Karaf in great extend.

To explore the Karaf functionality and to provide a Graphical interface , tried create eclipse plugin to access Karaf shell from the eclipse view.

Two views are currently created,

- Karaf Admin View
- Karaf Console View

Karaf Admin View:
Access the Karaf shell remotely and provides action for basic OSGi bundle maintenance like list/start/stop/install/uninstall/refresh.



View connects to the Karaf console and gets the bundle list




View allows to stop the bundles.




Karaf Console:

Extended Eclipse console to get Karaf running inside the eclipse.




- Currently implementing the Bundle Repository preference

- Plan is to provide the OSGi flow designer editor with all bundles.

If you are interested in participating this code development, you can reach me rathishraj@gmail.com

Checkout code base in http://code.google.com/a/eclipselabs.org/p/osgi-flow-designer/

Systemtest Framework

Simple Automation Framework for black box systemtesting, with following requirements

• Should be highly configurable


• Should provide plugin option


• Possible to simulate any test scenarios (like GUI testing/Test Report Preparation/etc)


• Tester friendly

I knew there are lot of opensource tools to do this, but each one has it own limitations and not full fill all above requirements . Now days testers are efficient in writing shell scripts then Java Program, so developed simple framework using shell script.

This version framework has been implemented with main 3 artifacts,

1. Datamodel: Test Data, one-to-one mapped with Testgroup.
   
2. Testgroup: Testgroup definition, defines one ore more rules.
   
3. Rules: Simple shell script with 4 life cycle functions.
4. 1 core shell script, to execute the testcases with above artifacts.
   

Rule:
Traditional shell script, with life cycle functions (initialize, execute, cleanup, output).

- initialize function will be invoked before starting executing t.
- execute function will be invoked once the testcase executed.
- cleanup function will be invoked on the testcase end.
- output function will be invoked to get more details (for reporting).

Testdata/Datamodel

Testdata in ":" seprated format, like

• Format

      GROUPNAME_TESTID:ANYTHING1=VALUE:ANYTHING2=VALUE:...

• Example

     SampleCases_Test001:Desc=Sample tescase:A=100

     SampleCases_Test002:Desc=Sample tescase:A=100

Testgroup

Group defines set of RULES.

• Format

        TEST_GROUP:<GROUPNAME>

           RULE:<RuleName1>

           RULE:<RuleName2>

           ....

        END_GROUP

• Example

        TEST_GROUP:SampleCases

           RULE:displayDescription

           RULE:displayAValue

           ...

        END_GROUP

In the above sample, Test001 and Test002 will be executed in the SampleCases? Group.

RULE

Rule is nothing but a shellscript with predefined life-cycle operations "initialize", "execute" and "cleanup"

• Format

       #!/bin/ksh -p

       function initialize

       {

           return 0

       }

       function execute

       {

           return 0

       }

       function cleanup

       {

           return 0

       }

• Example: displayDescription

       #!/bin/ksh -p

       function initialize

       {

         return 0

       }

       function execute

       {

            if [ $DEBUG ]; then set -x; PS4="displayDescription: "; fi

            . ${LIB}/toolsEnv.sh

            arrange "Desc" $*

            echo "TestCase  Desc: $Desc "

            return 0

        }

        function cleanup

        {

          return 0

        }

Where toolsEnv utility extracts the testdata from the input datamodel file.


There were lot of plans to enhance this framework, if you are interested reach me @ rathishraj@gmail.com

You can checkout the code from
http://code.google.com/p/regression-testing-framework/