Saturday, March 28, 2009

Meet us at Cloudcamp Bangalore, 29th March 2009..

CloudCamp is being organised for the first time in Bangalore. Putting together Cloud Computing Vendors, Technologists, Developers and Early adopter Startups to exchange their ideas and experiences regarding Cloud Computing. CloudCamp will be an semi-structured conference with invited speakers from the industry as well as several breakout sessions in unconference style to facilitate discussion amongst participants.

WOLF Frameworks is participating and our CEO is holding a session on, 'Design and run your business application within minutes'. We look forward to making this an interactive and exciting session for all the participants.

Looking forward to seeing you all again @ Cloud camp Bangalore ...

Tuesday, March 24, 2009

Newly added WOLF Screenshots Gallery section

The latest addition to our website is the page which shows you the gallery of screenshots of different WOLF User Interfaces. You can check out the page here.

The screenshots gallery gives you a glimpse into the Wolf Designer, the Runtime user interfaces for admin and application user and also some of the charts and reports built using WOLF. The Screenshots page will be updated regularly to give you an insight into new features and changes in Wolf Platform user interfaces.

P.S. – Please revisit this section soon to get a preview of the upcoming release of the WOLF Chart Control which allows you to design charts and graphs – representing your data as fancy dashboard items in your application.

Thursday, March 19, 2009

Transformation of Coghead customer applications to WOLF Platform...

Welcome to the world of executable XML. Here are a few observations from our Coghead application conversion process for customer applications.

1] Transformation from the Coghead Application XML to Wolf Entity Tree: Coghead used hierarchichal and relational structuring of data which converts into a pure relational model in WOLF. Each of the Collections are identified and the equivalent data structures are created in WOLF. Collections having lists generate separate Entities to hold the data for these lists. All collections of data including lists are treated as entities in Wolf. Collections having Detail Grids are converted into equivalent Gridwidgets in WOLF and Master Detail Relations are established. Linked fields are also created.

The Coghead XML shows that they had the capability of having multiple Collections with the Same Root level names. In WOLF this is an area of conflict and the import transformations fail to distinguish the Entities in such scenarios. The WOLF team here has taken some manual effort to make slight alterations to the Root level names before providing it to the Import Routines.

2] Transformation of Coghead Actions to WOLF Business Rules: Coghead actions convert to business rules easily inside WOLF. The algorithmic structure of the Actions is captured. Expression formats used by Coghead do not import as there is a lot of string manipulation involved in this process. For reasonably sized projects it might be quicker to reconstruct the expressions using the WOLF business rules interface. Simple expressions that can find equivalence in WOLF have been picked up automatically.

3] Transformation of tabs: Each Tab/Form in Coghead is a navigation item for WOLF. WOLF does not create a tab per form but creates multiple screens per entities. The types of screens that we have are Data Views (also referred to as search screens), Edit screens, Report Screens, Chart Screens, Dashboard Screens etc. There could be multiple screens associated to a single Entity. A “Navigation Item” then opens up a single screen. As an output of the transformation, there is a Navigation Item for each View in Coghead. The Editable forms are linked to the Search Screen.

So, in Simple terms: Navigation Item  Linked to Search Screen  Linked to Entity Editable Form Screen.

4] Data Imports: Data imports deal with complex mapping structures. For the import of simple non related data WOLF’s import program generates simple business rules which handles mapping of data when the data XML’s are uploaded.

Monday, March 16, 2009

Basics of a Custom Edit Screen in Wolf

To understand the basics of an Edit screen in Wolf Platform as a Service refer to my previous post here .

As mentioned in my previous post, an Edit Screen in Wolf Platform-as-a-Service allows the visual representation of your Entity.
All the Edit Screens in Wolf are contained inside an Entity. The Default Edit Screen gets created automatically everytime the user creates an Entity. However, a Custom Edit Screen needs to be created by the User.

An Entity can contain only a single Default Edit Screen. However, the user may create any number of Custom Edit Screens in the Entity. A Custom Edit Screen can use the fields defined in the Default Edit Screen allowing for flexible representation of an Entity and its fields/data.
It is important to note that the user cannot create any new fields in a Custom Edit Screen.

Lets consider the Entity below as our initial reference. The Entity "Orange" contains four fields defined inside the the Default Edit Screen - Color, Size, Shape and Price.

To create a Custom Edit Screen for your Entity, Right-click on the Entity name --> Select "New" --> "New Edit Screen"

It is mandatory to specify a name for the Custom Edit Screen.

To start using the fields of the Default Edit Screen in the Custom Edit Screen, you will need to create a tab and a section inside it.

To create a tab inside the Custom Edit Screen, Right-click on the Edit Screen --> Select "New" --> "New Tab"

You may optionally specify a name for this new tab.

To create a new section inside the tab, Right-click on the Tab--> Select "New" --> "New Section"

You may optionally specify a name for this new section.

You can then start adding fields to this Custom Edit Screen. To add fields in the section of the Edit Screen, use the point and click UI to choose the fields.

As you can see, only the fields defined in the Default Edit Screen are accessible as part of the Custom Edit Sceen. The User may only create a label field in the Custom Edit Screen.

The user can create as many Custom Edit Screens as he wants for flexible representation of Entity fields/data. However, there will be only a single Default Edit Screen that acts as the master repository of the fields for the Entity.
As an example, the User may create a Custom Edit Screen for holding all the dimensional data of the Orange Entity such as shape, size, etc. and another Custom Edit Screen for holding other information such as price, color, etc. The User can then link these two Edit Screens to different Navigation Items and restrict the user access to Navigation Items as per requirements.

Go ahead and try the power of the Custom Edit Screens and see how they can help you to design a more complete application.

Monday, March 2, 2009

WOLF Frameworks nominated among the Top 10 Internet companies by The Smart Techie

WOLF Frameworks Eyeing to be a Wolf in the SaaS Market ...

The SmartTechie recognizes the crucial role the Internet companies play and is proud to present "Top 10 Internet Companies Most Likely to Succeed" Merit roll. A distinguished panel comprising accomplished Indian CEOs & CIOs of public companies, VCs, analysts, founders of other VC funded companies including the SmartTechie editorial board decided on the top 10 Internet companies for 2009.

Bangalore based Wolf Frameworks is offering a 100 percent browser based Web application design and development Platform-as-a-Service (PaaS) for creating Software-as-a-Service (SaaS) type business applications on the Internet. Read more about the company.

Read more: