% $Header: /cvsroot/latex-beamer/latex-beamer/solutions/conference-talks/conference-ornate-20min.en.tex,v 1.7 2007/01/28 20:48:23 tantau Exp $

\documentclass{beamer}

% This file is a solution template for:

% - Talk at a conference/colloquium.

% - Talk length is about 20min.

% - Style is ornate.

% Copyright 2004 by Till Tantau <tantau@users.sourceforge.net>.

%

% In principle, this file can be redistributed and/or modified under

% the terms of the GNU Public License, version 2.

%

% However, this file is supposed to be a template to be modified

% for your own needs. For this reason, if you use this file as a

% template and not specifically distribute it as part of a another

% package/program, I grant the extra permission to freely copy and

% modify this file as you see fit and even to delete this copyright

% notice.

\mode<presentation>

{

  \usetheme{Hannover}

  % or ...

  \setbeamercovered{transparent}

  % or whatever (possibly just delete it)

}

\usepackage[english]{babel}

% or whatever

\usepackage[utf8]{inputenc}

% or whatever

\usepackage{times}

\usepackage[T1]{fontenc}

% Or whatever. Note that the encoding and the font should match. If T1

% does not look nice, try deleting the line with the fontenc.

\def\isac{${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$}

\def\sisac{{\footnotesize${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$}}

\title[\isac: Computation \& Deduction] % (optional, use only with long paper titles)

{Integrating Computation and Deduction\\

  in the \isac-System}

\subtitle{Projektpraktikum: Introducing Isabelle's Contexts}

\author[Lehnfeld, Neuper] % (optional, use only with lots of authors)

{Mathias~Lehnfeld\inst{1} \and Walther~Neuper\inst{2}}

% - Give the names in the same order as the appear in the paper.

% - Use the \inst{?} command only if the authors have different

%   affiliation.

\institute % (optional, but mostly needed)

{

  \inst{1}%

  Vienna University of Technology

  \and

  \inst{2}%

  Institute of Software Technology\\

  Graz University of Technology

}

% - Use the \inst command only if there are several affiliations.

% - Keep it simple, no one is interested in your street address.

% \date[CFP 2003] % (optional, should be abbreviation of conference name)

% {Conference on Fabulous Presentations, 2003}

% - Either use conference name or its abbreviation.

% - Not really informative to the audience, more for people (including

%   yourself) who are reading the slides online

% \subject{Theoretical Computer Science}

% This is only inserted into the PDF information catalog. Can be left

% out.

% If you have a file called "university-logo-filename.xxx", where xxx

% is a graphic format that can be processed by latex or pdflatex,

% resp., then you can add a logo as follows:

% \pgfdeclareimage[height=0.5cm]{university-logo}{university-logo-filename}

% \logo{\pgfuseimage{university-logo}}

% Delete this, if you do not want the table of contents to pop up at

% the beginning of each subsection:

\AtBeginSubsection[]

{

  \begin{frame}<beamer>{Outline}

    \tableofcontents[currentsection,currentsubsection]

  \end{frame}

}

% If you wish to uncover everything in a step-wise fashion, uncomment

% the following command:

%\beamerdefaultoverlayspecification{<+->}

\begin{document}

\begin{frame}

  \titlepage

\end{frame}

\begin{frame}{Outline}

  \tableofcontents

  % You might wish to add the option [pausesections]

\end{frame}

% Structuring a talk is a difficult task and the following structure

% may not be suitable. Here are some rules that apply for this

% solution:

% - Exactly two or three sections (other than the summary).

% - At *most* three subsections per section.

% - Talk about 30s to 2min per frame. So there should be between about

%   15 and 30 frames, all told.

% - A conference audience is likely to know very little of what you

%   are going to talk about. So *simplify*!

% - In a 20min talk, getting the main ideas across is hard

%   enough. Leave out details, even if it means being less precise than

%   you think necessary.

% - If you omit details that are vital to the proof/implementation,

%   just say so once. Everybody will be happy with that.

\section[Introduction]{Introduction}

\subsection[TODO]{Isabelle and \isac}

\begin{frame}

  \frametitle{Isabelle and \isac}

TODO

\end{frame}

\subsection[TODO]{Computation and deduction in a Lucas-Interpreter}

\begin{frame}

  \frametitle{Computation and deduction in a Lucas-Interpreter}

TODO

\end{frame}

\section[Contributions]{Contributions of the project}

\subsection[TODO]{Introduction of Isabelle Contexts}

\begin{frame}

  \frametitle{TODO}

TODO

\end{frame}

\subsection[TODO]{Redesign of type inference in \isac}

\begin{frame}

  \frametitle{TODO}

TODO

\end{frame}

\subsection[TODO]{Improvement of functional code}

\begin{frame}

  \frametitle{TODO}

Demo

\end{frame}

\subsection[TODO]{Preparation of future development}

\begin{frame}

  \frametitle{TODO}

TODO

\end{frame}

\section[Problems]{Problems encountered in the project}

%\subsection[TODO]{TODO}

\begin{frame}

  \frametitle{TODO}

\begin{itemize}

\item Publication of new Isabelle release

\item Amount of code in Isabelle and \isac

\item Changes scattered throughout the code

\end{itemize}

\end{frame}

\section{Summary}

\begin{frame}

  \frametitle{TODO}

TODO

\end{frame}

\end{document}