On Wed, 4 Feb 2004 14:29:21 -0500, Gerard Cote <[EMAIL PROTECTED]>
wrote:
> But I can ensure you Robert that nobody will be left aside during the
> process - since this is firstly done for the whole
> international REBOL community. I simply favor French as my own support
> tool since it will be easier to me.
Hi, ok we will see.
> I can send you what I already did about easy-vid.r and we could help
> each other to better understand what is needed and how it can
> be done.
I once had a quick look at easy-vid but I don't remember its internal data
structure to store the parsed input. IMO it makes sense to define a
data/block structure that can be used by the player to create the layout
dynamically from the content and where the navigation stuff is included as
well.
> In fact I also looked back at the way you're emitting your HTML related
> tags inside make-doc-pro. Since in your case the
> output can be produced for the Internet browser to manage the display
> you don't have to add overhead to the produced document as to
> support navigational features like is the case in the easy-VID or
> VID-usage products.
I have a make-site script (thanks to Chris) that uses MDP to create
complete web-sites. My homepage is created with it. This script supports
navigational stuff already. I think this combination can be extended to
support VID emitter as well. That would be my starting point.
> When are you ready to start with ?
Any time but expect a slow progress as I'm doing a more-than-full-time-job
in parallel. As said, first step would be to look at the input data
structure for the player. If this one is defined, adding an emitter should
be easy.
> May be we can start working without any further consideration and we'll
> simply replace any additional or updated modules when
> completed. At least it would become feasible to create self-running
> REBOL Lessons without having to dig inside each time to replace
> manually any old content by a new one.
My idea is to create one output file that contains the input for the
player from a set of input files. The player could become an encapped
standalone version, so people don't have to install anything.
Having the input files separated makes it possible to work with a group of
people in paralle. The input structure is as follow:
\topic1
menu.txt
content1.txt
\topic2
menu.txt
content2.txt
menu.txt
index.txt
topic1.txt
topic2.txt
The first level is the main level. Every sublevel is a separate directory.
For each level exists a menu.txt file, specifying the available
navigation. Robert
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
