[ 
https://issues.apache.org/jira/browse/SLING-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988020#action_12988020
 ] 

Federico Paparoni commented on SLING-1438:
------------------------------------------

I tried Apache FOP in order to replace iText. The flow to create a PDF is 
HTML->XHTML->XML->XML-FO->PDF, it's the only way using this library.
Unfortunately it isn't very easy to create a bundle for Apache FOP that works 
on Felix, I'm currently trying to build it.
If you think it make sense a version without the creation of PDF, I can remove 
it.

> GSoC 2010: create a mini-CMS to demonstrate Sling
> -------------------------------------------------
>
>                 Key: SLING-1438
>                 URL: https://issues.apache.org/jira/browse/SLING-1438
>             Project: Sling
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Bertrand Delacretaz
>            Assignee: Federico Paparoni
>         Attachments: david.rar, david16092010.zip
>
>
> This is a suggested project for Google Summer of Code 2010.
> The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
> practices.
> The emphasis is on the quality and readability of the demo code, and we 
> expect to have to go through several iterations to refine it and the 
> corresponding JCR content model so that they demonstrate Sling best 
> practices. We will not necessarily create a full-fledged CMS, the goal is for 
> the result to be educational and help Sling newcomers understand how to 
> create web applications with it.
> Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
> server-side scripting, and Java code in OSGi bundles for back-end 
> functionality.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to