You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by st...@apache.org on 2003/10/30 18:56:05 UTC
cvs commit: cocoon-2.1/src/blocks/linotype TODO.txt README.txt
stefano 2003/10/30 09:56:05
Modified: src/blocks/linotype TODO.txt README.txt
Log:
cleanup
Revision Changes Path
1.3 +16 -10 cocoon-2.1/src/blocks/linotype/TODO.txt
Index: TODO.txt
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/blocks/linotype/TODO.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- TODO.txt 18 Jun 2003 07:18:47 -0000 1.2
+++ TODO.txt 30 Oct 2003 17:56:05 -0000 1.3
@@ -2,18 +2,24 @@
What is left to do?
-------------------
-Tons of stuff, but here is a list of the things that I think are most important at the moment:
+Tons of stuff, but here is a list of the things that I think are most important
+at the moment:
- 1) IE compatibility. Currently linotype works only on Mozilla 1.3 or greater because it needs the Midas editor. IE has an equivalent editing mode since version 5.0. The client-side javascript was written with some portability in mind but there is a long way to go, expecially for non-standard features like image-handling/resizing and a bunch of other UI fanciness. Why should we care about IE? well, if you want to update your blog from an internet cafe', you can bet your ass they won't have mozilla 1.3 installed. that's mostly why.
+ - write different rendering stylesheets for mozilla or IE since IE is *really*
+ poor at CSS2 compatibility. Why? well, again, 90% of the browsers are IE and
+ this is going to take a while to change.
- 2) consider using slide or an alternative content repository instead of plain file system.
+ - allow the ability to write essays and not only news and while you do this,
+ considering adding pagination capabilities, also at the editing level (for
+ example, a button that can trigger the presence of a tag that indicates page
+ break)
- 3) write different rendering stylesheets for mozilla or IE since IE is *really* poor at CSS2 compatibility. Why? well, again, 90% of the browsers are IE and this is going to take a while to change.
+ - improve the ability to redeploy linotype without having to hardwire URLs
+ around the sitemap and flowscript. (probably goes along with
- 4) allow the ability to write essays and not only news and while you do this, considering adding pagination capabilities, also at the editing level (for example, a button that can trigger the presence of a tag that indicates page break)
-
- 5) improve the ability to redeploy linotype without having to hardwire URLs around the sitemap and flowscript.
-
- 6) consider adding the ability to sinchronize two different linotypes. For example, if you have one installed in your laptop and you are offline for a while, you might want to synchronize it with the one online.
+ - consider adding the ability to sinchronize two different linotypes.
+ For example, if you have one installed in your laptop and you are offline
+ for a while, you might want to synchronize it with the one online.
- 7) multi-user setup to host multiple weblogs or weblogs authored by multiple authors.
+ - multi-user setup to host multiple weblogs or weblogs authored by multiple
+ authors.
1.3 +4 -13 cocoon-2.1/src/blocks/linotype/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/blocks/linotype/README.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- README.txt 18 Jun 2003 06:48:32 -0000 1.2
+++ README.txt 30 Oct 2003 17:56:05 -0000 1.3
@@ -5,18 +5,9 @@
What is this?
-------------
-Linotypes were machines that first allowed a single individual to mass-produce content without sacrificing typesetting elegance and text readability. Blogs turned the web into writeable media without sacrificing the ability to remain hypertextual. This is simply an attempt to combine the two concepts together.
+Linotypes were machines that first allowed a single individual to mass-produce
+content without sacrificing typesetting elegance and text readability. Blogs
+turned the web into writeable media without sacrificing the ability to remain
+hypertextual. This is simply an attempt to combine the two concepts together.
- Requirements
- ------------
-
-On the server side, Linotype just depends on Cocoon and saves its edited content on disk, nothing else.
-
-To edit content with Linotype, a browser that supports the Mozilla Midas API is required. For now this means
-Mozilla 1.3 or greater. Note that Midas is *NOT* part of standard Gecko, so Camino and other Gecko-based browser
-won't do it.
-
-Thanks for your interest in Linotype.
-
- Stefano Mazzocchi