Showing posts with label technical. Show all posts
Showing posts with label technical. Show all posts

Monday, October 03, 2011

To allow good Appendix table of content view and writing professional documents, follow this piece of code:

Note that , appendix1 and appendix2 is a normal .tex files like any chapter files start with \chapter and contains sections

\usepackage[titletoc]{appendix}

\begin{document}  
\begin{appendices}

\include{appendix1}

\include{appendix2}
\end{appendices}

\end{document}

To allow code Listing in Latex, follow this block of code , like a professional books

\documentclass{unlthesis} 
\usepackage{color}
\usepackage{xcolor}
\usepackage{listings}
\usepackage{caption}
\DeclareCaptionFont{white}{\color{white}}
\DeclareCaptionFormat{listing}{\colorbox{gray}{\parbox{\textwidth}{#1#2#3}}}
\captionsetup[lstlisting]{format=listing,labelfont=white,textfont=white}

\begin{document}

\begin{lstlisting}[language=java,
caption=XYZ.java, label=code:XYZ_Code, frame=b,
breaklines=true, showstringspaces=false,
basicstyle=\footnotesize]

class Doing
{
public static void main(string [] args)
{
int x = 0 ;
}
}
\end{lstlisting}
\end{document}


Friday, June 10, 2011

My Resume

To see my Resume in Google Docs , Please Click Here

Friday, June 03, 2011

I happy to announce from my small space of internet that my first technical publication will be 7 July 2011 in SEKE 2011 Conference. The tile is "An Approach for Identifying and Implementing Aspectual Features in Software Product Lines". The abstract :

"Software Product Lines (SPL) exploits reuse by identifying,modeling, and systemically reusing software features to develop different but related software systems. Successful reuse of a product line depends greatly on the modularity of the features that characterize the product line. Traditionally, features in SPL are grouped along the dimension of commonality and variability. However, this single dimension grouping overlooks the crosscutting nature of some features in the system, which negatively impacts the reusability and modularity of the product line architecture. In this paper we address this particular problem by investigating
the concept of Aspectual Feature (AF) as another grouping dimension that can be used in SPLs. To this end,the paper proposes the Aspectual Product Line Engineering (APPLE) approach for identifying, modeling, and implementing AFs to enhance the reuse of SPLs. A tool support for implementing the APPLE approach is also presented and demonstrated through a case study."

Wednesday, April 13, 2011

I wasted a lot of time to try passing Data between workflow activities, so i find it at last very easy.

simply you need to create WF Variable of the type you want to pass ( in my case this was a primitive string ) and called it for example TMP.

Then come to the sender activity properties where the data is settled by and type in output VB expression "TMP". Open the receiver activity and write TMP in its input.

WF Engine is smart enough to understand that TMP is a local variable inside the Workflow and get the value of it.

Very Easy HUH !!!!