0.8.8 service pack 1 available

Dear all,

Service pack 1 for 0.8.8 is available from the download page (all the way to the bottom). The service pack was focused on improving usability and better support for changing texts in the application. Also, the wiki plugin has gotten an upgrade: Wiki pages can be in color, have different font sizes, support arbitrary styles and support linking to most ProjectPier objects. Internal and external communication about your project just got a lot easier and snappier.

Cheers, Reinier

Hi Reinier,
really good how PP develops. To be sure, for patches and upgrades you can just upload everything right into the installation, as long as the config directory remains untouched - is it safe to clean the cache? thx, Dominik

The upgrades will not contain files from /cache, /config, /tmp, /upload etc. Only where code is located: /application, /environment, /library, /public, /language, /tools.

It is safe to clean the cache. It will rebuild automatically.

After deployment you need to 'force refresh" your browser to get new copies of the stylesheets in.

Specific questions to the wiki linking support.
1) how to link to project pier objects?
2) is it possible to have jpg displayed saved within projectpier (in my case database setup)
3) do you have the additionally formatting options available anywhere?

thx, Dominik

re 1) Any project pier object can be linked in with this syntax: [a:b] where a represents the name of any type of object:

a can be: message, task_list, ticket, milestone, file or wiki
b is the id of the object which can be found when viewing the object and checking the url for id=

E.g. [milestone:1], [file:234]

re 2) Currently an icon is displayed representing the image, but I think it should be quite easy to change things as to display an image. I see a couple of solutions:

a) automatically display the image when it is an image type of file
b) introduce a new type like this: [image:234]
c) add additional info in the current syntax like this: [file:234,display]

I will make option a) in your installation.
EDIT: Looks nice. Check out the Wiki in the Platform project.

re 3) https://github.com/phpfreak/Project-Pier/blob/master/library/textile/Textile.class.php

_____________
T E X T I L E

A Humane Web Text Generator

Version 2.0

Copyright (c) 2003-2004, Dean Allen <dean@textism.com>
All rights reserved.

Thanks to Carlo Zottmann <carlo@g-blog.net> for refactoring
Textile's procedural code into a class framework

Additions and fixes Copyright (c) 2006 Alex Shiels http://thresholdstate.com/

_____________
L
I C E N S E

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice,
  this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice,
  this list of conditions and the following disclaimer in the documentation
  and/or other materials provided with the distribution.

* Neither the name Textile nor the names of its contributors may be used to
  endorse or promote products derived from this software without specific
  prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

_________
U S A G E

Block modifier syntax:

Header: h(1-6).
Paragraphs beginning with 'hn. ' (where n is 1-6) are wrapped in header tags.
Example: h1. Header... -> <h1>Header...</h1>

Paragraph: p. (also applied by default)
Example: p. Text -> <p>Text</p>

Blockquote: bq.
Example: bq. Block quotation... -> <blockquote>Block quotation...</blockquote>

Blockquote with citation: bq.:http://citation.url
Example: bq.:http://textism.com/ Text...
-> <blockquote cite="http://textism.com">Text...</blockquote>

Footnote: fn(1-100).
Example: fn1. Footnote... -> <p id="fn1">Footnote...</p>

Numeric list: #, ##
Consecutive paragraphs beginning with # are wrapped in ordered list tags.
Example: <ol><li>ordered list</li></ol>

Bulleted list: *, **
Consecutive paragraphs beginning with * are wrapped in unordered list tags.
Example: <ul><li>unordered list</li></ul>

Phrase modifier syntax:

   _emphasis_ -> <em>emphasis</em>
   __italic__ -> <i>italic</i>
*strong* -> <strong>strong</strong>
**bold** -> <b>bold</b>
??citation?? -> <cite>citation</cite>
   -deleted text- -> <del>deleted</del>
  +inserted text+ -> <ins>inserted</ins>
^superscript^ -> <sup>superscript</sup>
  ~subscript~ -> <sub>subscript</sub>
   @code@ -> &lt;code>computer code&lt;/code&gt;
  %(bob)span% -> <span class="bob">span</span>

==notextile== -> leave text alone (do not format)

   "linktext":url -> <a href="url">linktext</a>
"linktext(title)":url -> <a href="url" title="title">linktext</a>

   !imageurl! -> <img src="imageurl" />
  !imageurl(alt text)! -> <img src="imageurl" alt="alt text" />
!imageurl!:linkurl -> <a href="linkurl"><img src="imageurl" /></a>

ABC(Always Be Closing) -> <acronym title="Always Be Closing">ABC</acronym>

Table syntax:

Simple tables:

|a|simple|table|row|
|And|Another|table|row|

|_. A|_. table|_. header|_.row|
|A|simple|table|row|

Tables with attributes:

table{border:1px solid black}.
{background:#ddd;color:red}. |{}| | | |

Applying Attributes:

Most anywhere Textile code is used, attributes such as arbitrary css style,
css classes, and ids can be applied. The syntax is fairly consistent.

The following characters quickly alter the alignment of block elements:

<  ->  left align ex. p<. left-aligned para
>  ->  right align h3>. right-aligned header 3
=  ->  centred h4=. centred header 4
<> ->  justified p<>. justified paragraph

These will change vertical alignment in table cells:

^  ->  top    ex. |^. top-aligned table cell|
-  ->  middle    |-. middle aligned|
~  ->  bottom    |~. bottom aligned cell|

Plain (parentheses) inserted between block syntax and the closing dot-space
indicate classes and ids:

p(hector). paragraph -> <p class="hector">paragraph</p>

p(#fluid). paragraph -> <p id="fluid">paragraph</p>

(classes and ids can be combined)
p(hector#fluid). paragraph -> <p class="hector" id="fluid">paragraph</p>

Curly {brackets} insert arbitrary css style

p{line-height:18px}. paragraph -> <p style="line-height:18px">paragraph</p>

h3{color:red}. header 3 -> <h3 style="color:red">header 3</h3>

Square [brackets] insert language attributes

p[no]. paragraph -> <p lang="no">paragraph</p>

%[fr]phrase% -> <span lang="fr">phrase</span>

Usually Textile block element syntax requires a dot and space before the block
begins, but since lists don't, they can be styled just using braces

#{color:blue} one  ->  <ol style="color:blue">
# big <li>one</li>
# list <li>big</li>
<li>list</li>
   </ol>

Using the span tag to style a phrase

It goes like this, %{color:red}the fourth the fifth%
  -> It goes like this, <span style="color:red">the fourth the fifth</span>

*/

It´s not a bug it´s a feature :-) - just kidding, thats true on our planes, but PP definitly is better - huge feature, just tried out some of the wiki features - having access to PP objects (pictures) works perfect and gives us a very effective tool to present data from our work to the public, thx

This is really a powerful feature, work very well within one project. Two more questions
1) can you also link to other Projects within the same installation and what would be the synthax (project id:file)
2) you set my display option for graphics, which work great. Which other display options (type of files) are supported and again what would be the synthax (I did not find this in the textile documentation)

Glad you like. It is indeed powerful. Basically you now have a tool to create a "website" for your project.

1) There is no check on the ids but they have to be in the current project. I need to change the code to support linking over projects. At run time we have to check whether the user viewing the page is entitled to view objects from another project (and hide them or make them text) OR we display them and wait for the "access denied" error when they click it (the current solution).
Also, during editing I need to extend the check to allow projects the editor has access to. It does all get a bit more tricky.

2) I simply changed to code to always display images. There are no other options. Let me know what you need.

I think for now it is fine, I think its ok to limit access for objects to the current object. Is it possible to resize pictures automatically (would reduce work to get every picture in a defined resolution)?

The pictures autoresize now dynamically and adjust themselves to the enclosing element (the wiki page). It is not possible yet to set specific sizes (e.g. make them smaller). But it looks quite okay to me.