public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Nandeep Mali" <n9986.mali@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Progress Report - Setting Beacon Afloat
Date: Wed, 16 Jul 2008 04:35:39 +0530	[thread overview]
Message-ID: <b59c1640807151605x369226fr57d026367f1b2845@mail.gmail.com> (raw)

Hi all,

This report is a matchup of the original timeline and deliverables
with the progress so far.

My original deliverables were:

- Remove Mochikit and replace it with Dojo.
- Provide a GuideXML customized Rich Text Editor in place of normal text-boxes.
- Improve Various User Interface Elements such as the DOM tree and
remove CSS bugs.
- Design a Data Backend as an alternate to temporary file storage.
- Rewrite the drag and drop feature and improve formatting of generated code.

Now to go through them (not in order):

1. Remove Mochikit and replace it with Dojo:
Done. The aim here was to reduce the number of JavaScript libraries
used. I have included the Prototype framework[1] for easy AJAX
handling.

2. Improve Various User Interface Elements such as the DOM tree and
remove CSS bugs:
Done. Created a fluid layout to remove the annoying scroll bars and
will handle different browser sizes and resizing. The original cute
icons are still there. ^_^
The DOM tree can be used to jump to various locations in the document.
Also the different chapters and sections can be referenced in the
document.

3. Design a Data Backend as an alternate to temporary file storage:
Done. Created a wrapper for generic functions like read and write.
Also included a Gmail like auto-save feature. The XML view and save
features are all implemented using AJAX.

4. Provide a GuideXML customized Rich Text Editor in place of normal text-boxes:
& 5. Rewrite the drag and drop feature and improve formatting of
generated code:
The 5th feature has been replaced with the RTE. Now there is no use of
a drag and drop interface. What we had thought of was that the
document would be editable by using the inline text-boxes that Dojo
has. Since the editor will have to be collaborative it'll not be easy
to implement document manipulations on the fly. Therefore I thought of
using the Writely (Google Docs) approach where the entire document is
editable. The RTE is now a big undertaking and will be a continuous
work. The formatting of generated XML has been improved but requires
some more tweaks. The editor does not support some GuideXML elements
but those can be edited directly in the XML and the changes will
reflect back in the WYSIWYG view.

The editor is available at Tux Family[2]. It should run out-of-the-box
if you have:
- A web server
- PHP support (With XSLProcessor)
- The editor uses the system tmp to temporary save files.

Please go ahead and try it out. ^_^

I have also asked mentor-kun to put it up on his server so those of
you don't have a server set up you can soon access it up there.

My post mid-term aim is to implement the collaborative editor and
continue work on the RTE, XML generation and adding/revamping
features.

Kind Regards
Nandeep Mali

[1] http://www.prototypejs.org/
[2] git clone git://git.tuxfamily.org/gitroot/beacon/trunk.git
-- 
gentoo-soc@lists.gentoo.org mailing list



             reply	other threads:[~2008-07-15 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 23:05 Nandeep Mali [this message]
2008-07-16 19:44 ` [gentoo-soc] Progress Report - Setting Beacon Afloat Donnie Berkholz
2008-07-17 20:15   ` Anant Narayanan
2008-07-19  8:27 ` Arun Raghavan
2008-07-20  3:05   ` Alec Warner
2008-07-20 11:18     ` Nandeep Mali
  -- strict thread matches above, loose matches on Subject: below --
2008-08-11 17:58 Nandeep Mali
2008-06-26 12:24 Nandeep Mali
2008-06-26 12:34 ` Luca Barbato
2008-06-27 12:18   ` Nandeep Mali
2008-06-11 14:56 Nandeep Mali

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

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

  git send-email \
    --in-reply-to=b59c1640807151605x369226fr57d026367f1b2845@mail.gmail.com \
    --to=n9986.mali@gmail.com \
    --cc=gentoo-soc@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox