reStructeredText (ReST) default type on Vasudevaservice.com

reStructeredText (ReST) is now the default content format for all the standard ATCT objects (Pages, News, Events) and EasyBlog, for all sites on this server.

For now, if you still have Kupu as your editor then the default will be overriden by Kupu to html.

Be aware though, that since we are going to use Vasudevaservice.com as testbed for reStructuredText, Kupu has been uninstalled there.

Two directives: sidebar and figure

ReStructuredtext has a "sidebar" directive. See a good example of a sidebar here: http://en.wikipedia.org/wiki/Gorbachev

Sidebars are like miniature, parallel documents that occur inside other documents, providing related or reference material. A sidebar is typically offset by a border and "floats" to the side of the page; the document’s main text may flow around it. Sidebars can also be likened to super-footnotes; their content is outside of the flow of the document’s main text.

Sidebars may occur anywhere a section or transition may occur. Body elements (including sidebars) may not contain nested sidebars.

If you would have the following css inside your Plone skin:

.sidebar
{
color: red;
font-weight: bold;
float: right;
width: 10em;
}

The following code:

.. sidebar:: Sidebar Title
   :subtitle: Optional Sidebar Subtitle

   Subsequent indented lines comprise
   the body of the sidebar, and are
   interpreted as body elements...

   .. image::  /images/vasudevaserver.gif

Would be rendered as a sidebar of text floating on the right.

Now, for what concerns images, reStructuredText has a wonderful directive, "figure", which also support a "class" attribute.

Let’s assume we also have this css:

.float-right
{
float: right;
border-style: dashed;
border-width: 1px;
border-color: red;
}

The following reStructuredText:

.. figure:: /images/vasudevaserver.gif
   :alt: logo
   :figwidth: image
   :figclass: float-right
   :align: right

    This is the caption.

Would produce the following:

logo

This is the caption.

That is for today! We saw how easy it is to employ the two powerful directives "sidebar" and "figure".

See you next time!

change color tabs vscore

vsCore which is used on Vasudevaserver has a few new features. Firstly colors of tabs can be changed through ZMI.

when caching has expired the tabs will change at top.

  • subskin feature – Very useful, when you want to have many plone instances and still keep the same main_template

These features are not included in the current vsCore tarball; a new tarball will be uploaded shortly…..

Evaluating Plone form mailer

With Plone Form mailer, you can design email forms through the web. We at Vasudeva Server have had occasion to use them a lot.

Their best point is the ease with which you can actually get a form drummed up and ready on your site. The ‘edit’ tab lets you enter text before and after the form, configure who to send it to, sort out what the email is going to look like, and design a ‘thank-you’ page. The ‘modify form(zmi)’ tab lets you work on the form itself.

The edit tab

The fields to enter in the ‘edit’ tab are pretty intuitive (and have
been made more so in recent versions). There are a couple of times
where you have to enter a TALES expression, like the mail recipient or
the email address of recipient. For example, if your name is Mr Happy
and your email address is happy@happy.com then enter string:Mr Happy and string:happy@happy.com in the relevant fields. One nice feature is they warn you what bits not to touch if you haven’t a clue what youre doing!

The ‘modify form’ tab
By default, the form has a field for name, email and message. One
recent improvement to Plone Form mailer is that the whole form doesnt
fall apart if for some reason you delete the email field. Clicking on
the tab takes you to a ZMI interface where you can see a menu
containing each of the fields. You can add more fields by clicking on
the top right, including checkboxes, radiofields, you name it.

Issues
Sometimes we have had problems implementing PloneFormMailer using
scripts other than Roman (eg Cyrillic). Sometimes the checkboxes dont
work and the characters are not correctly interpreted in the email.

One issue is that form mailers invariably always present problems when migrating Plone, and usually have to be deleted and recreated again. However PloneFormMailer is quite young and we would expect this to be sorted out in the future.

You can read more about Plone Form Mailer on their section  of  the Plone site

Owner permissions in Plone

Factoid of the day: Owners can add images and files in Plone but by default they can’t edit them once the save button is pressed.

ATImage tips

The default Image type in Plone (ATImage from the ATCT Product) is capable of scaling:

large : (768, 768)

preview : (400, 400)

mini : (200, 200)

thumb : (128, 128)

tile : (64, 64)

icon : (32, 32)

listing : (16, 16)

To access these sizes, append /image_XXX to the URL, where XXX is one of the above sizes.

Choosing ‘photoalbum view’ in the new ‘display’ menu when inside a folder containing images will result in a different view.

Example: if you reference /images/EasyBlog-Logo-1.gif on this site you will have:

Listing: /images/EasyBlog-Logo-1.gif/image_listing

/images/EasyBlog-Logo-1.gif/image_listing

Icon: /images/EasyBlog-Logo-1.gif/image_icon

/images/EasyBlog-Logo-1.gif/image_icon

Tile: /images/EasyBlog-Logo-1.gif/image_tile

/images/EasyBlog-Logo-1.gif/image_tile

Thumb: /images/EasyBlog-Logo-1.gif/image_thumb

/images/EasyBlog-Logo-1.gif/image_thumb

Mini: /images/EasyBlog-Logo-1.gif/image_mini

/images/EasyBlog-Logo-1.gif/image_mini

Preview: /images/EasyBlog-Logo-1.gif/image_preview

/images/EasyBlog-Logo-1.gif/image_preview

Large: /images/EasyBlog-Logo-1.gif/image_large

/images/EasyBlog-Logo-1.gif/image_large

An EasyBlog screencast

EasyBlog is probably the best blogging tool available on the Plone platform.

Our very own Richard Pettinger has recorded today a very nice EasyBlog screencast.

It is targeted to beginners who have never used EasyBlog before.

More screencasts will come for more advanced functions soon.

EasyBlog screenshot

EasyBlog, the best blogging on Plone

Plone byline issues

One of the bees that’s been buzzing around in my bonnet recently is the issue of bylines in plone.

To me, any text that appears on a Plone page should be editable via a UI rather than having to edit a template. Ever since 2.1 the byline has been right at the top, so it might be one of the first things a new Plone user will wish to modify. An option to turn on/off the last modified date would be welcomed, some of our content contributors find it ugly and also a little misinformative if you have a site with contributors from all around the globe. At least it’s simple enough to remove the byline entirely, see here.

The same issue also applies to the colophon, the bit at the very bottom….

But to me the main issue is that to move the byline somewhere else requires a main template modification. I know its only cut and paste, but when you’re using other products with modified templates you kind of want to keep the clutter to a minimum. Since there’s only four places where 99% of sane Plone users will want to put their byline why not just have the ability to make that choice in a UI also?

Until things change, we are modifying the main template of our vsCore product to put the byline on the bottom right. We are also working on skin changes so that a photo of the page creator appears on the bottom right.

Lisp and dinosaurs

I really like Philip Greenspun’s contributions to the developer’s community and Internet world at large. His posts are usually witty and have about them a sharp vision that is quite rare to find.

Here is a post I liked about LISP. It is not really concerning Plone, but I think it concerns us as seekers of beauty and simplicity in our project.

From "Lisp diehards = Holocaust deniers"

Hmm… it seems that the “Java = SUV of programming languages” posting has stirred up a bit of controversy over at Slashdot and right here on this server. Some people read it as a personal endorsement of PHP, VB, and other semi-baked programming languages. Actually my personal preference is a much darker, uglier, and more shameful secret: Common Lisp, CLOS, plus an ML-like type inferencing compiler/error checker (with some things done in a sublanguage with Haskell semantics and Lisp syntax). Common Lisp dates from around 1982 and ML from 1984.

I try to keep this preference concealed from young people who’ve been raised on a diet of C, Java, C#, Perl, etc. They just wouldn’t find it credible that 20-year-old systems and ideas are actually better than the latest and greatest from Microsoft and Sun.

Imagine my delight in running into a friend yesterday. She’s a 23-year-old graduate student in computer science at Harvard. Conversation rolled around to programming tools. Unprompted she said “What I think would be best is Common Lisp Object System with a modern type system”. I was stunned. I thought it was only dinosaurs like me that clung to Lisp.

I had a second ephiphany for the week… Believing that Lisp circa 1982 plus some mid-1980s ML tricks thrown in is better than all of the new programming tools (C#, Java) that have been built since then is sort of like being a Holocaust denier.

It is also interesting to read the numerous comments to that post:

http://blogs.law.harvard.edu/philg/2003/09/22/lisp-diehards-holocaust-deniers/