[daisy] [GSoC] applying for the development of a .NET library for Daisy

[Steven Noels]

On 21 Mar 2007, at 00:13, Cyberchand wrote:

> Hi,
>
> I am a 21 years old French student applying for the 2007 Google  
> Summer of Code, and I would really love to work on the Daisy  
> project this summer.
> I have a little experience of other CMS (Typo3, Joomla, and much  
> more), and no one convinced me principally because of the lack of  
> interoperability (it is very hard to migrate from one CMS to  
> another, I can tell!). The Daisy project seems to me a very good  
> approach, since it uses XML a lot, which is a guarantee that the  
> documents created with Daisy will be easy to eventually reuse  
> later. Moreover, the physical separation between repository and  
> front-end allows, among other things, the development of third-part  
> GUI editor.
> So, I am getting to the point : I am thinking of developing a .NET  
> library for Daisy, which would encapsulate all the HTTP/XML stuff  
> to communicate with the repository server. Then it would be  
> conceivable to develop whithout to much pain a Windows GUI or an  
> ASP.NET interface for publishing content on a Daisy system.
> I think I could do a great job on this project because, beyond the  
> fact that I am very excited in working on a CMS project which, I  
> think, have a very well-thinked approach, I have a strong  
> experience in .NET programming (especially in C#) and in XML  
> manipulation (XSLT, XPath, XQuery...).
>
> I am looking forward to any comments, feedbacks, proposals, and new  
> ideas !

Hello Cyrille,

interesting proposal. From experiences of last year, I'd suggest that  
you need to seriously define the scope of your project.

* what API parts will you be encapsulating in your Daisy client
* will your focus be editing/modifying Daisy documents or merely  
publishing
* will you be treating the extra services as well (workflow, the  
publisher (the latter I seriously recommend)
* you'll need to think upfront on what libraries you will be using  
inside your client (for HTTP/XML handling, one student last year got  
'bitten' by underperforming unicode handling in his target environment)

But again: excellent idea! Please continue your investigation and let  
this list know your findings.

Register yourself on the scratchpad Wiki so that you can do a write- 
up of your proposal over there.

http://cocoondev.org/daisyscratchpad/

Thanks,

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought                              Open Source Java & XML
stevenn at outerthought.org                stevenn at apache.org