Re: [ease-dev] Regarding Open Source contribution

[Nikhil Shinde <crenickshinde1996@xxxxxxxxx>]

Hi Christian,

First task would be to provide the user a container in which he can add different components like Input Fields,Message Fields,etc.This container will collectively form a Dynamic Dialog.Task will include to provide user functions to add this component along will all necessary properties(whose number is also varying). eg. In one case the user would like to take normal input and in other case he would like to add certain conditions on input like formatting,length,etc... all of this has to be encapsulated with that component so that when it loads in dialog it must do checks for all the properties stated by dialog creator.Here I consider designing the function which takes input parameters like [ Dialog parentContainer , componentType , (additional component information like name), (additional properties of component as stated above) ]. such function will do work of creating the specified component, binding necessary properties with it and arranging it in the dialog.It will also provide the variables that will store values for that component which can be later accessed by user(dialog creator).  

Second and important task would be arrange the components which dialog creator(user) has asked for. there are simple things that can be done to make automatically-generated components more easily composable such as standardizing widths and heights of components.There are also some heuristics that has to applied such as sorting properties to control type so that all the related components e.g. all combo box, all text fields go together etc.

I have researched about automated layout solution that doesn't require significant guidance and did not get much about it.I would like you to review the above stated process and point me about to the missing points,improvements and wrongs.Also please suggest me the important features/topics that I should be familiar with so as to contribute in this project.

Thank you for clarifying the deliverables in details.

Nikhil Shinde      

On Wed, Mar 15, 2017 at 12:58 PM, <Christian.Pontesegger@xxxxxxxxxxxx> wrote:

Hi Nikhil,

 

not sure if you are on the right track already. I admit I have difficulties following your email.

The task is to provide a script module exposing an API that allows to create dialogs in a dynamic way. Say a user wants to build an address book application with EASE scripts (for whatever reason). Then he might need an input dialog to query for firstname, lastname, …

It would be nice if there were simple script commands available to build a dialog like this.

Now your task would be to come up with such an API and implement it as an EASE module.

 

There are no ‘SWT scripts’, you also should not directly provide ‘dialog generation scripts’. You might need some for testing purposes, but your main task is to enable users to write their own dialog generation scripts. The task also does not include writing of any static dialogs.

 

HTH

Christian

 

 

From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@eclipse.org] On Behalf Of Nikhil Shinde
Sent: Wednesday, March 15, 2017 2:03 AM
To: ease developer discussions
Subject: Re: [ease-dev] Regarding Open Source contribution

 

Hi ,

      Thanks ,.... Now I am aware about the project purpose . It is to provide user the API to generate custom dialogs that includes variable components of his choice. The implementation can be also done by using SWT scripts,but the idea description highlights on not using SWT in scripting layer and custom dialog implementation in jdk. 

      So are we expected to code the dialogs generation scripts from scratch without taking advantage of already available scripts  ?

 

      Please suggest me bugs that would be helpful to get acquainted with the task. I am goint through SWT code base to get idea of its dialog implementation, Please point me if I am missing something.

 

      The static dialogs generation will be easy as we are aware about the results to show in dialogs.For dynamic dialogs we must have previous knowledge about all the possible cases in which the user can ask for. I am confused about how to encapsulate all the cases an d how to provide user ease in this process without much of boilerplate code. Please suggest me some reference that will make this process much clear.

 

Thanks for replying,

Nikhil                

 

_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev