<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>
    
    <title>Classics Unlocked</title>
    <link>http://www.classicsunlocked.net/index.php/site/news/</link>
    <description>Reading instead of deciphering</description>
    <dc:language>en</dc:language>
    <dc:creator>saugos@gmail.com</dc:creator>
    <dc:rights>Copyright 2011</dc:rights>
    <dc:date>2011-12-27T09:33:02+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />

   

    <item>
      <title>The new roadmap</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/the_new_roadmap/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/the_new_roadmap/#When:08:33:02Z</guid>
      <description><![CDATA[
At the end of the year 2010 I published the roadmap for ClassicsUnlocked website. 
Now, after finishing just 1 of the 6 steps of that roadmap I feel the need to rethink it.
Three main ideas I find important. 



First, during the last couple of years the version 2 of
ExpressionEngine CMS has matured and leaving ClassicsUnlocked website based on the outdated version 1 of this CMS
does not seem a good way to ensure its long&#45;time viability. 



Second, I came to conclusion that basing projects&#39; workflow around Control Panel is wrong. I.e. it&#39;s wrong that all publishing and editing should be done in Control Panel.
Now I think that projects&#39; workflow should be based on SAEF (stand&#45;alone entry forms), since this approach allows for more flexibility and usability.  



Third, architecture of ClassicsUnlocked website required saving certain HTML code in database together with content.
That&#39;s obviously wrong. It seems that only certain most primitive text&#45;formatting markup can be allowed into database.



These are important consirerations which do not allow to continue executing the former roadmap and do not allow merely revising it.
Some radically new roadmap is needed which involves switching to ExpressionEngine version 2 and new architecture of ClassicsUnlocked website.
So, here it is, now consisting only of 2 steps:



1) Writing of about 10 add&#45;ons which provide needed functionality, such as multi&#45;language,
online keyboard, keyboard mapping, combined RSS feed, flexible member administration, flexible entries administration,
new forum posts widget, new comment entries widget, control panel admin comments add&#45;ons.
Most of them, unfortunately, are quite complicated to write.



2) When these add&#45;ons will be ready, recreating ClassicsUnlocked website based on the version 2 of
ExpressionEngine CMS at the same time changing its architecture so that publishing will be based on SAEF and
saving certain HTML code in database together with content will be avoided.



Adopting such roadmap means the end of the development of current ClassicsUnlocked website. The only thing that will be done
untill needed add&#45;ons will be ready and recreating of the website based on ExpressionEngine version 2 begins is publishing news
articles.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2011-12-27T08:33:02+00:00</dc:date>
    </item>

    <item>
      <title>Images in ebooks</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/images_in_ebooks/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/images_in_ebooks/#When:07:30:55Z</guid>
      <description><![CDATA[
After several moth of coding image gallery functionality has been added to ebooks. 
An ebook in Classics Unlocked format now can contain author portraits as here, 
illustrations as here and a list of all its illustrations as here.

Each picture can be clicked to view it in full&#45;size. Clicking a picture opens a window 
containing the picture, its caption and the Previous/Next links for viewing other pictures
placed on the same page. That&#39;s is usual functionality of javascript image galleries. 


The script used is Floatbox. It was chosen because of its usability and one feature 
which is rare in javascript image galleries &amp;mdash; zooming. 
In Floatbox each picture can be zoomed in and out. This is very important for pictures displaying
ancient artefacts and scholarly reconstructions &amp;mdash; viewing them you often want not only get 
a general impresion but to study the tiny details as well.

Images currently added to the pages of started projects only demostrates the capabilities 
of the templates and image gallery script. Later these images will be replaced with those who
are really needed for the relevant projects.

So, the first stage of the roadmap described in my latest post I consider completed. Now I begin
the work on the second stage &amp;mdash; removing any hardcoding of the autoincrements from templates and scripts.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2011-05-26T07:30:55+00:00</dc:date>
    </item>

    <item>
      <title>Roundup of the year 2010 and a roadmap</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/roundup_of_2010_and_roadmap/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/roundup_of_2010_and_roadmap/#When:13:47:23Z</guid>
      <description><![CDATA[
In the last news article written about a year ago I expressed the hope that the year 2010 will be the year when it will be possible to move from solving technical problems to publishing content. I was wrong. Although the year was quite productive for Classics Unlocked, I&#39;m still preoccupied with solving various technical problems and will in the foreseeable future.



So, what has been done and what technical problems remain? 



During the year I did complete overhaul of the commenting with the aim of making reading of Classics Unlocked ebooks social. Now visiting any page of the ebook, e.g. this one, you will find &quot;Comment pane&quot; button in the menu bar. Clicking it right pane will be opened where you can log in, submit comments and get info about comment authors and commented pages.



On each page of the ebook it is possible submit both general comments, i.e. comments concerning ebook as a whole, and comments related to that particular page (except title page on which it is possible submit only general comments). On analysis pages such as this one it is possible to comment on sections of the page: on Basic Analysis, Morphology, Syntax, Dictionary, Commentary and Prosody. Recently submitted comments can be seen in the right pane by clicking &quot;Latest comments&quot; menu item. Info about commented pages and sections and info about comment authors is accessible by clicking, respectively, &quot;List of commented sections&quot; and &quot;List of commenters&quot; menu items. Submitting comments and displaying info about comment authors and commented pages is being done by AJAX, i.e. without reloading of the current page. That&#39;s quite rich functionality which should be wholy adequate for the needs of both ebook compilers and readers.



The new commenting system can be seen by visiting the website. There are other changes which can be seen only from the backend. This year Classics Unlocked website experienced much of spamming activity (comment spamming and member profile spamming). To stop it several spam prevention and spam filtering measureas were implemented. Also several website&#39;s Control Panel enhancements were implemented which aim to enhance the workflow of editors and contributors working on ebook publishing projects.



All that involved writing new and new add&#45;ons for ExpressionEngine, a CMS which powers Classics Unlocked. If judged from the number of add&#45;ons used Classics Unlocked is now arguably the most complex ExpressionEngine website.



Still, much remains to be done. As the work proceeds the concept of ebooks in Classics Unlocked format and of the website becomes more and more distilled and now I can formulate a roadmap consisting of the technical problems which should be solved in the near future (without venturing to say when transitioning to conten creation will happen). So, the roadmap:



1. Introducing possibility to add pictures. It should be possible to add portraits of the authors of classical texts and it should be possible to add illustrations at proper pages in the ebooks.



2. Any hardcoding of autoincrement values should be removed from templates and scripts. Database tables often have colums whose values serve as keys and are incremented automatically when new data is being inserted. Hardcoding of autoincrements in templates and scripts is architectural mistake which if lefts as it is would prevent fetching data of one or several project on one website and restoring those project on another website. This architectural flaw should be corrected.



3. Writing of ePUB generator module for ExpressionEngine. Ebooks in Classics Unlocked format will be compiled online and will be available for reading either online or offline in ePUB format. Generating of ePUB publication should be done using current online content and that means that generation should be done also online ExpressionEngine&#39;s add&#45;on.



4. Adding certain functionality to ePUBReader. ePUBReader is perhaps the best reader of ePUB publications. It is Firefox extension enabling the reader to use whole power of this amazing browser. I believe that electronic books should be read in full&#45;fledged browsers, not using special software which integrates some crippled browser engine, as Adobe&#39;s Digital Editions. In essence, ePUBReader gets reading of ebooks right, but it lacks some features essential for ebooks in Classics Unlocked format. More specifically, in ePUBReader right&#45;clicking on publication&#39;s inner URLs leads to opening publication&#39;s pages without ePUBReader&#39;s interface. That&#39;s OK for recreational reading, but for any serious reading of electronic publication full support of right&#45;clicking on inner links is a must.



5. Website redesign. New, more professional site theme, new front page, site&#39;s logo, Twitter stream integration etc.



6. Forum redesign. New forum theme.



That&#39;s quite much work to be done. I hope that the year 2011 will be productive.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2010-12-30T13:47:23+00:00</dc:date>
    </item>

    <item>
      <title>Enabling cooperation on projects</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/enabling_cooperation_on_projects/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/enabling_cooperation_on_projects/#When:10:24:43Z</guid>
      <description><![CDATA[
The year 2009 went through and there was almost no new content published at the
website. Visitors might have thought that the website and the project of publishing
First Book of Homer&#39;s Iliad in Classics Unlocked format were abandoned.



The truth is contrary to this. The year was very productive for the website.
Missing parts of both the Platform and Ebook application were added and now these sections
of the website are fully functional. If the aim of the website were to be the place of the publishing
efforts of one individual, then it would be possible to continue with he project of publishing
First Book of Homer&#39;s Iliad in Classics Unlocked format. But the aim of the website is more ambitious &#45; 
to enable cooperative work of the groups of individuals on different projects. 
During first project &#45;
First Book of Homer&#39;s Iliad in Classics Unlocked format &#45; although being pursued by one individual, the ways how such cooperation will proceed should
be explored.



Enabling cooperation on projects is in essence support for several different roles. It seems that 
at least two roles should be introduced: Project admins who would be responsible for certain project, 
e.g. for the project of publishing First Book of Homer&#39;s Iliad in Classics Unlocked format, 
and Project contributors who would be responsible for one or a couple of aspects of the project, 
e.g. for Commentary 
or Dictionary. 
In&#45;built role management functionality of ExpressionEngine CMS
which powers Classics Unlocked website does not satisfy the needs of cooperative workflow on our
publishing projects. It means that the only way to achieve needed role management functionality
is using add&#45;ons for ExpressionEngine.



Writing add&#45;ons enabling role management is what I have been doing for the last couple of months. 
At least four new add&#45;ons need to be written and one adapted to the needs of the website. This will
bring the number of add&#45;ons used on Classics Unlocked website to more than sixty! That&#39;s a very big number
which illustrates pretty well the sheer complexity of the backend. I have never thought that
supporting the publishing of ebooks in Classics Unlocked format might be such techically complex 
undertaking. Here some good words should be said about ExpressionEngine CMS. If not for its flexibility
and extensibility hardly anything like website&#39;s Platform 
and Ebook application sections would be 
possible.



Building Classics Unlocked website proceeds slowly but has clear aims and vision. I hope that the comming 2010 year
will be the one when it will be possible to switch from solving technical problems to publishing content.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2009-12-28T10:24:43+00:00</dc:date>
    </item>

    <item>
      <title>Backend restructured</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/backend_restructured/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/backend_restructured/#When:13:39:11Z</guid>
      <description><![CDATA[
I am happy to tell that the aim announced in my previous 
post &amp;mdash; to radically restructure the website&#39;s backend 
&amp;mdash; was achieved. The number of templates, other backend 
constructs and the size of the database were significantly reduced; 
the website is now much more easily scalable and maintainable. 
Perhaps the most important aspect of all this is that starting of a 
new project became as easy as adding a new category and filling one 
simple form and that Classics Unlocked website can now accommodate as 
many projects as there would be. 

 Achieving this scalability and maintainability was quite 
complicated undertaking. It&#39;s enough to say that in order to get 
needed functionality 25 add&#45;ons to  ExpressionEngine CMS were 
used; 11 of them I was forced to develop by myself since nothing of 
the kind existed. 

 After restructuring of its backend the Classics Unlocked website 
has three distinct parts or areas:

 1) website proper; here belong all those pages whose URL 
addresses begin with www.classicsunlocked.net/index.php/site/, e.g 
this page or that one, the 
homepage serving as the gateway to such pages;

 2) ebook application; here belong all those pages whose URL 
addresses begin with www.classicsunlocked.net/index.php/ebook/, e.g 
this page or that one,  
Ebooks and Projects pages 
serving as the gateways;

 3) platform for compiling Classics Unlocked ebooks; here belong all 
those pages whose URL addresses begin with 
www.classicsunlocked.net/index.php/platform/, e.g this 
page or that one,  
Platform page serving as the gateway. 

 These three parts or areas seems to be quite reasonable 
structure for Classics Unlocked website: website proper being used for 
representing ideas, aims, opinions ans news; the platform being used 
to aid in compiling ebooks in Classics Unlocked format; ebook 
application being used to display ongoing and finished projects. 

 Nice unintended result of the resorganizing of the 
backend was that for the first time since starting Classics Unlocked I 
got a clear vision how complete and fully functional platform and 
ebook application should look like. With that vision in mind I am 
very excited and impatient to get hands on the next task.

 The next things to be done are: 

 1) smoothing many rough edges left after restructuring of the 
backend;

 2) adding missing parts to both the platform and ebook 
application.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2008-09-11T13:39:11+00:00</dc:date>
    </item>

    <item>
      <title>Frontend and backend changes</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/frontend_and_backend_changes/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/frontend_and_backend_changes/#When:17:10:10Z</guid>
      <description><![CDATA[
Although I was not posting any articles for several months, there was much of activity on Classics Unlocked
website during this time. Myriad of bugs were fixed and many small features added. To the visitors 
most of these changes are not perceptible, but collectively they result into smooth functioning of the entire website.

One change is easily noticeable &amp;mdash; renewed design of the website&#39;s main sections, such as &quot;Home&quot;, &quot;Projects&quot;, &quot;For authors&quot;. 
Older design of these sections with it&#39;s old&#45;fashioned three&#45;column layout and brownish color&#45;scheme was conspicuously inconsistent with 
blue and violet theme of ebook and Analysis assets pages. New design features two&#45;column layout and the same blue and violet color&#45;scheme 
as in all other pages. As previously, the design is intended to be as simple and distraction&#45;free as possible. I hope you will like it.

Another noticeable change is removal of &quot;Blog&quot; item from navigation; you will find &quot;News&quot; instead. Website&#39;s raison d&#39;être is publishing 
of classics, not blogging about it. There are news and opinions about current projects and activities, but no abundance of events or points of view
suitable to blog about.

Developing Classics Unlocked website I learned much about ExpressionEngine, 
a CMS which powers it. Now I see clearly that many architectural decisions 
I made in initial stages of the website&#39;s development were wrong, that the management of the website and 
starting of new projects is much more complicated than it should be. In order to improve management of Classics Unlocked website
I will undertake in the next several weeks or months a radical reorganization of it&#39;s entire backend. Number of templates and
other backend constructs will be reduced several times and  starting of new projects will be as easy as adding a few new categories.
No new materials will be added until these changes will be completed.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2008-05-13T17:10:10+00:00</dc:date>
    </item>

    <item>
      <title>New version of Date picker tool</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/new_version_of_date_picker_tool/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/new_version_of_date_picker_tool/#When:17:46:15Z</guid>
      <description><![CDATA[
Date picker script matured into version 2.0. 



The aims which were pursued with the release of the new version are as follows:
To make possible to use Date picker script for those who post pieces of analysis, such as 
available on this page.
Titles of such pages often contain two numbers as e.g. &quot;Verses 1&#45;2&quot;, &quot;Verses 3&#45;5&quot; and both 
numbers must be considered by calculating the date (previous version of the script allowed only
one number to be contained in a title). Making possible to use of Date picker script for those 
who post pieces of analysis means standardizing of setting of dates for all posts which have
titles containing numbers and that in its turn makes it possible in some future to automate setting
of dates for such posts completely via 
ExpressionEngine&#39;s 
extension.



With the version 2.0 of Date picker script it is possible to order by date posts which have titles containing
one or two numbers. E.g. posts can be ordered as here: &quot;Verse 528&quot;, &quot;Verse 529&#45;530&quot;, &quot;Verse 531&quot;, &quot;Verses 531&#45;533&quot;, 
&quot;Verses 533&#45;535&quot; etc.



This version is not compatible with the previous one. Incompatibility with the previous version has two aspects:
1. Version 2.0 accepts as an input a string containing one or two numbers in a range from 1 to 9999 
(earlier version accepted string containing one number in a range from 1 to 99999).
2. For the string containing some number version 2.0 outputs later date than previous version.


UPDATE Mon, December 28, 2009
Date picker tool was removed from the Platform section because more advanced way of ordering of entries was adopted.
Now ordering of entries is done using Seeries add&#45;on which is based on series of entries concept &#45; pipe delimited string of entry ID numbers.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2008-01-18T17:46:15+00:00</dc:date>
    </item>

    <item>
      <title>Small tool called Date picker</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/small_tool_called_date_picker/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/small_tool_called_date_picker/#When:17:45:44Z</guid>
      <description><![CDATA[
New tool is available in authors&#39; section of our website &#8212; 
Date picker.
It is a tool for those who post excerpts from grammars and commentaries. 
Excerpts from grammars have standard titles, such as &quot;§ 589&quot;, &quot;§ 712&quot;, &quot;§ 335&quot;,  etc.
Titles of excerpts from commentaries are also standard: &quot;Verse 1&quot;, &quot;Verse 2&quot;, &quot;Verse 3&quot; etc.
These titles should be ordered according their numerical values, as here: &quot;§ 1&quot;, &quot;§ 2&quot;, &quot;§ 3&quot;, ...
&quot;§ 10&quot;, &quot;§ 11&quot;, &quot;§ 12&quot;, etc. But instead ExpressionEngine, 
a CMS which powers Classics Unlocked website,
orders titles which include numbers alphabetically, 
so that we get &quot;§ 1&quot;, &quot;§ 11&quot;, &quot;§ 12&quot;, &quot;§ 13&quot;, ... &quot;§ 2&quot;, &quot;§ 21&quot;, &quot;§ 22&quot; etc.


Two solutions are possible here. The first is writing PHP script. The other is ordering titles by date &#8212;
since the dates on which excerpts from grammars and commentaries are posted does not matter,
you can order entries properly by setting dates manually so that every entry with a bigger number has later date.
The latter solution not only is less complicated to achieve, but also has a serious advantage: ordering by date 
will be retained on search results page in cases when 
search outputs many results.

Calculating and formatting a date for every particular entry is dull and time&#45;consuming job. Here comes Date picker script.
Date picker script takes as input a string, parses from it a number, and for any number in a range between 1 and 99999 it picks a date
which is later than any date it picks for any lesser number and earlier than any date it picks for any bigger number in that range. The dates 
the script picks are formatted as in ExpressionEngine&#39;s PUBLISH page. So, enter title containing number or only a number, push the button
and you will get a date ready to be pasted into ExpressionEngine&#39;s PUBLISH page.

UPDATE Mon, December 28, 2009
Date picker tool was removed from the Platform section because more advanced way of ordering of entries was adopted.
Now ordering of entries is done using Seeries add&#45;on which is based on series of entries concept &#45; pipe delimited string of entry ID numbers.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2007-10-16T17:45:44+00:00</dc:date>
    </item>

    <item>
      <title>The text of the first book of Iliad published</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/text_of_iliad_1_published/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/text_of_iliad_1_published/#When:17:33:30Z</guid>
      <description><![CDATA[
As I wrote in my previous 
post,
the compiling of the 
First Book of Homer&#39;s Iliad in Classics Unlocked format
will proceed in six steps and the first of them will be publishing of the text of this book.
I am happy to announce that the text is already published. You can see it 
here.


The text is based on Walter Leaf&#39;s edition of Iliad. One could ask &quot;Why Leaf&#39;s? 
Why not Monro and Allen&#39;s edition which is used by both 
Perseus and 
Chicago Homer?&quot; The main reason 
is punctuation. Punctuation in Monro and Allen&#39;s edition is very scarse and this does not
aid understanding of the work. In Leaf&#39;s edition punctuation is rich enough and Leaf 
is very careful about it.

The biggest change I introduced to the Leaf&#39;s edition is the change of iota adscript to 
iota subscript throughout the text. Perseus and Chicago Homer websites did the same with 
Monro and Allen&#39;s edition. Other changes are as follows:
Verse 8. τίς τάρ changed to τίς τ&#39; ἄρ 
Verse 65. εἴ ταρ changed to εἴ τ&#39; ἄρ&#39; 
Verse 93. οὔ ταρ changed to οὔτ&#39; ἄρ 
Verse 123. πῶς τάρ changed to πῶς γάρ

The text is devided into smaller meaningful chunks. Each chunk is prefaced by a sentence or two 
sentences long synopsis which is based on the one found in 
Allen Rogers Benner&#39;s Selections from Homer&#39;s 
Iliad. 

The text can be read in two modes: not scanned and scanned. By default you will see the text
without scansion. If you switch to scanned mode you will see only some lines, since as yet 
the scansion is entered only for a handful of verses.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2007-10-16T17:33:30+00:00</dc:date>
    </item>

    <item>
      <title>Analysis assets opened</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/analysis_assets_opened/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/analysis_assets_opened/#When:17:25:10Z</guid>
      <description><![CDATA[
For some time I was quite busy thinking and experimenting in order to find out what
could be the best way of collecting text and code which is produced in the process
of compiling a Classics Unlocked edition, distributing it between 
participators in the particular project, and making it reusable in different projects.
The result is Analysis 
assets section of the website.

The concept I have adopted is as follows. Someone, probably project admin, logs into 
control panel of Classics Unlocked website and using special form enters the text of some classics work.
Then the server generates following sets of HTML tables:
1) Text tables
2) Scanned text tables
3) Basic Analysis tables
4) Morphology tables
5) Syntax tables
6) Dictionary tables
7) Commentary tables
8) Prosody tables
These tables I call &quot;Container tables&quot;. They display lines of classics text and 
serve as as containers into which analysis of these lines can be inserted. For example, dictionary tables serve as
containers into which dictionary articles explaining meaning of the words of one or more lines can be inserted.


Each participator in the project visits the pages containing the code of the table he needs, copies the
code into clipboard, saves it as a file and opens in his favorite text editor. The code of the table contains
special Classics Unlocked tags marking the places in code which can be modified and explanations which show 
more exactly what modification is expected. For example, 
one dictionary table 
 contains such marks: 
&amp;lt;!&#45;&#45; {line13_word4_dictionary} [φέρων] &#45;&#45;&amp;gt; &amp;lt;!&#45;&#45; {/line13_word4_dictionary} [φέρων] &#45;&#45;&amp;gt; 
These marks contain opening tag {line13_word4_dictionary} and closing tag {/line13_word4_dictionary} which together show 
the place in the code where dictionary article explaining the fourth word from the verse 13 can be inserted. [φέρων]  
indicates the word which should be explained. After filling the places marked by 
Classics Unlocked tags each participator logs into Control Panel and 
posts the table he modified. Posting is done by entering several parameters, such as title, URL title, date, which 
were copied together with the code of the container table. The analysis submitted is instantly accessible for viewing and commenting. 

There are pieces of analysis, such as 
dictionary articles, grammar paragraphs, inflection charts and explanations of the syntax of constructions,
that need to be inserted into several different container tables. To enable easy finding and reuse of such pieces of analysis 
they are posted using special forms in Control Panel and 
are collected in Analysis assets section of the website. 
Dictionary articles and inflection charts are grouped together as
&quot;Dictionary and morphology assets&quot;; grammar paragraphs and explanations of the syntax of constructions are grouped together as
&quot;Grammar assets&quot;.

UPDATE Mon, October 13, 2008
Since this post Analysis Assets section of the website has grown into kind of a platform for compiling ebooks in Classics Unlocked format. Accordingly, the gateway page no more has the title &quot;Analysis Assets&quot;; it is titled now The platform.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2007-10-16T17:25:10+00:00</dc:date>
    </item>

    <item>
      <title>Changes in ebook&#8217;s user interface</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/changes_in_ebooks_user_interface/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/changes_in_ebooks_user_interface/#When:14:44:46Z</guid>
      <description><![CDATA[
The ebook First Book of Homer&#39;s Iliad in Classics Unlocked format has a new less cluttered and more usable interface.

Until now the pages of the ebook  were by default displayed with all navigation of the website. There was a &quot;Site off/Site on&quot; button on the right top corner of the screen using which the reader could choose to display the page with or without site&#39;s navigation. There are no more site&#39;s navigation and  &quot;Site off/Site on&quot; button in ebook&#39;s pages. Instead you will see narrow menubar on top of the screen with links &quot;CU home&quot; (Classics Unlocked home page), &quot;Previous page&quot;, &quot;Next page&quot;, &quot;Advanced search&quot; and menus &quot;Ebook contents&quot;, &quot;Page contents&quot;, &quot;Links&quot;, &quot;Simple search&quot;.

&quot;Links&quot; and &quot;Ebook contents&quot; menus were not present in earlier version of ebook&#39;s interface. To see ebook&#39;s contents the reader was forced to open the separate page. Now ebook&#39;s contents are displayed on  each page.
 &quot;Links&quot; menu on each page contains two links: one to the page in Perseus website dedicated to the same verses as the ebook&#39;s page and the second one to the home page of Chicago Homer website. Of course, it would be better to link to particular pages, but Chicago Homer website does not allow doing it.
 
 
The menubar is fixed on top of the screen, so you can use it without any scrolling of the page. Fixed menubar is especially usable for navigating within long ebook&#39;s pages: you can jump forth and back between page sections such as &quot;Basic Analysis&quot;, &quot;Morphology&quot;, &quot;Dictionary&quot; instead of scrolling the page. (Menubar will not stay fixed for users of Internet Explorer 6 or below; within these browsers the menubar is fully functional, but it will scroll with the page and lack some small nifty features, such as changing color of downward arrows. If you are using Internet Explorer,  please consider upgrading to Firefox or other modern browser &#8212; you will get better and safer browsing experience.)     

One more change of ebook&#39;s user interface is being considered. It seems that for such projects as compiling ebooks in Classics Unlocked format it would be a great advantage to have paragraph commenting system, such as Commentpress. Commentpress is a plugin for Wordpress blogging engine, and that means that it is not possible to use it on the non&#45;Wordpress website without substantial rewriting of the code. As soon I will have some time available, I will try to do rewriting of Commentpress code for use with ExpressionEngine, which powers our Classics Unlocked website.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2007-08-29T14:44:46+00:00</dc:date>
    </item>

    <item>
      <title>First project started</title>
      <link>http://www.classicsunlocked.net/index.php/site/news/first_project_started/</link>
      <guid>http://www.classicsunlocked.net/index.php/site/first_project_started/#When:16:18:15Z</guid>
      <description><![CDATA[
The first project to produce a compilation of classics work in Classics Unlocked format started! Some pages of the First Book of Homer&#39;s Iliad in Classics Unlocked format already published; you can read and comment them.
 
 During the work of compiling the idea of Classics Unlocked format is slowly taking more concrete forms. As for now, it seems that the analysis of the classics text according this format should contain following parts:
 
 
 1. Basic Analysis
 2. Morphology
 3. Syntax
 4. Dictionary
 5. Commentary
 6. Prosody
 
 
 Most fundamental part is, of course, Basic Analysis, which as it seems,  should in its turn contain following parts:
 
 
 1. Line of text
 2. Main forms of particular words
 3. Main meanings of particular words
 4. Morphological parsing of particular words
 5. Syntax of particular words
 6. Syntax of constructions
 7. Verbatim translation of sentence
 8. Rephrasing of sentence to match english word order
 9. Grammatical translation
 
 
 The work of compiling proceeds quite slowly. Project as this is essentially the project to be done by a group, where someone compiles dictionary, another one — commentary, the third — prosody, the fourth — morphology, and the most experienced in the group — Basic Analysis and Syntax. Now, the project to compile the First Book of Homer&#39;s Iliad in Classics Unlocked format is the idea and work of only one man, so be patient.
 
 The compilation of the first pages was done by analyzing line after line all aspects mentioned above. Proceeding this way the character of the work being done constantly changes: one set of skills is applied doing Basic Analysis, another set of skills — compiling Morphology, the third — compiling Dictionary etc. This accounts for considerable loss of productivity. To increase productivity the workflow will be changed. From now the compiling will proceed in such steps:
 
 
 1. the text of the first book of Iliad will be published; then
 2. Commentary entries will be published; then
 3. Prosody entries will be published; then
 4. Dictionary entries will be published; then
 5. Morphology entries will be published; then
 6. Basic Analysis and Syntax entries will be published.
 
 
Express your opinions on this project by commenting particular pages and participating in forums.
]]></description>
      <dc:subject>News article</dc:subject>
      <dc:date>2007-03-23T16:18:15+00:00</dc:date>
    </item>


    
    </channel>
</rss>
