emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [GSOC] Bugpile/iOrg weekly update (cont.)
Date: Mon, 04 Jun 2012 10:03:25 +0200	[thread overview]
Message-ID: <87sjeb4i7m.fsf@googlemail.com> (raw)
In-Reply-To: 8762b75xr6.fsf@googlemail.com

Thorsten Jolitz <tjolitz@googlemail.com> writes:

[ups - wrong keystroke and the unfinished mail was sent]

> Hello List, 
>
> following a suggestion from Bastien, I will give a weekly update from
> now on about the state of things in my Google Summer of Code 2012
> project "Bugpile/iOrg".
>
> Just to remind you whats it all about:
>
> ,-----------------------------------------------------------------
> | Bugpile is a bugtracker for GNU Emacs Org-mode written in Emacs
> | Lisp. It will be developed during the Google Summer of Code 2012
> | (GSoC) as an example application for iOrg, a new framework for
> | building dynamic web applications.
> `-----------------------------------------------------------------
>
> Since I have to deal with two things at the same time (the web framework
> iOrg and the example application bugpile), I chose the approach to
> develop bugpile and write the iOrg stuff whenever I feel there should be
> some framework functionality. I write down everything I do as an iOrg
> tutorial on Worg
>  (http://orgmode.org/worg/org-contrib/gsoc2012/student-projects/bugpile/i.html)
>
> I use a software engineering approach for the development, although this
> is rather untypical for the emacs world, but it has two big advantages:
> 1. it guides people step by step through the development process, 

[continuation]

1. it guides people step by step through the development process, so
   even if they don't have a clear idea about how to structure and
   develop a web-application, they will never stare on a blank screen
   without knowing what to do next
2. it gives a clean structure to a project and organizes the sometimes
   many files involved, avoiding to get lost in an unmanageable mess.

I'm finished with the requirements analysis and the software
specification now. Some core functionality of the iOrg framework has
already be written (initialize, rename, update iOrg project), see the
git repo: 

,------------------------------------------
| git clone bugpile@orgmode.org:bugpile.git
`------------------------------------------

Since all the planning has been done using textbased PlantUML as drawing
tool, I want to automize the transformation from the software design to
implementation skeletons. Therefore I have to write functions that parse
the PlantUML source code and write the Elisp and Org files they
'describe' as a last step of the planification phase.

But the most important task for the upcoming week will be to write a
small (minimal) proof of concept that shows how to use Elnode, the Emacs
web-server by Nic Ferrier, to manipulate Org files via a web interface
(with html forms and buttons). 

-- 
cheers,
Thorsten

      reply	other threads:[~2012-06-04  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  7:42 [GSOC] Bugpile/iOrg weekly update Thorsten Jolitz
2012-06-04  8:03 ` Thorsten Jolitz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjeb4i7m.fsf@googlemail.com \
    --to=tjolitz@googlemail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).