[FM Discuss] Quick booki development update

[Aleksandar Erkalovic]

dear flossmanuals mailinglist subscribers,

i decided to send quick development update. will try to write more
about this in the future and for now please feel free to bother me
with your specific questions :)

as adam already said, we will migrate flossmanuals from twiki platform
to new booki platform. if you tried to use
new platform you would see it is missing a lot of features current
platform has. so... the general idea is to make
it suck less and make migration less painful for all of us.

one of the things you will like in new version is "versioning". book
maintainer will be able to freeze current version
of the book. as always, when i was planning this i did not realise how
complex this will be at the end. but in general,
we are allllmmmmooost there. there are some issues with attachments
and html editor for now.

if you tried to use booki you could see "history" tab does not really
work. now... it kind of works :) you can see
book history, chapter history, you can revert to previous revisions,
you can compare different revisions and etc.
i need to make diff visually nicer, but in general we are almost there
with this feature.

not everyone likes to talk about deadlines. that is why i will ignore
deadlines in this mail.

some of the issues with "migration". basicly, we already have some
books in current booki. new changes require new
internal book structure, changes in edited text, changes with
attachments and etc... it means i will have to write
scripts for migrating current booki books to new booki. even thinking
about it makes me sick and curse "why did
i ever let people use beta booki!" :) also, i have to work on older
structure and code at the same time. this will take
some time and i will start writing migration scripts when i feel
confident there will be less big internal changes.
there will be separate installation of new booki. only after some
testing it will replace current booki install.

also, new booki is far more complex then twiki architecture. it always
means more problems, but it also means some
really cool features and benefits. one of the major problems with
current booki is in communication layer with redis database.
this causes booki to randomly freeze sometimes (and i have to erase
redis database and restart it again). fixing
this problem will be my next step after finishing versioning. and when
i say fixing i mean fixing in new booki, current
booki will continue to break and require restart from time to time.
don't feel like fighting on two different fronts
for now with this issue.

ok.. will write more in the future.

aco



-- 
 http://www.binarni.net/