Hi Jos,

Thanks for the reply.

On 20 March 2013 20:29, Jos van den Oever <jos.van.den.oever@kogmbh.com> wrote:

Hello Philip,

On 03/20/2013 04:48 AM, Philip Peitsch wrote:

I'm starting to tip-toe into ODF editing, and was looking for a few
pointers.

1. I know there is a collaborative editing effort under way... is there
a roadmap or timeline of features somewhere? Or can someone provide a
quick summary of the delivery time of this?

The patches for collaborative features are landing in the master branch. We are finishing the final touches for the first milestone. That will be a version of WebODF where you can edit text in paragraphs and change paragraph styles. This works for a single user and also when using a collaborative session. The required server for collaborative editing is currently not publicly available, but the protocol is public.

Is there a delivery road-map, or a backlog somewhere of the planned features? I'm in the middle of sorting out the various requirements I have for the editing behaviours and am basically trying to answer where to best start.

The complete features I will need to support in the next few months are:

* Paragraph add / delete

* Page-break add / delete

* Table add/delete (rows & columns as well)

* Character range changes (i.e., modifying the character styles of a selected range of text)

* Paragraph style changes (already covered by your work in some fashion)

* Paragraph alignment changes (create a new style based on an existing, modify the alignment)

* Bulleted & numbered list creation

* Image insertion & removal

* Cut/Copy/Paste (both WebODF => WebODF, external => WebODF, and WebODF => external)

* Page view (as opposed to the "continuous" view currently supported. vandenoever mentioned he had some ideas on how to fix this)

Is the stuff you are doing for the collaborative editing straight-forward enough that I (and you) would benefit if I implement these editing operations using that framework, or is my life going to be much simpler to implement the DOM changing independently?

Ideally, if you have a roadmap and timeline that aligns partially with what I'm going to need to build, I can choose tasks that won't tread on your toes or re-do work you are already scheduling and planning for. It would hopefully also mean there is the best chance that the code I write is useful to the WebODF project in general, rather than a standalone hack branch which I'd prefer to avoid if at all possible :). I'm open to any suggestions on how I might tackle this in a way that will make it possible for you to integrate the work back in if you think it might be useful. Is it possibly a good idea for me to start to plan some of this on a public wiki somewhere if you have specific design suggestions or feedback?

Please don't feel pressured about this either way. If your time is better spent doing things other than helping me design/plan/integrate this, I'll figure something out on my own. I'm just conscious there is a greater risk that the resulting code I produce won't be able to be easily contributed back if I just make it up on my own :)

2. How do I run the things that are currently there? I have found
programs/editor/index.html, as well as cdn-index.html. The
cdn-index.html one appears the work, but I cant figure out how to get
the first going... it appears to be wanting dojo or similar.

Yes, index.html is the version that works with only local files. index-cnd.html uses a cdn (content idstribution network). To use index.html, you have to compile webodf with cmake and make.

cd webodf
mkdir ../build
cd ../build
cmake ../webodf
make

Many thanks. I continue to be impressed by the quality of the webodf
code and functionality.

Thank you very much.

Cheers,
Jos

_______________________________________________
WebODF mailing list
WebODF@nlnet.nl
https://open.nlnet.nl/mailman/listinfo/webodf

Many thanks,

--
Philip Peitsch
Mob: 0439 810 260