On Monday 27 January 2003 20:47, Peter Flynn wrote:
> Manos wrote:
> > No, I was talking about Microsoft Office XP not 2k; it does have native
> > XML support. For example "You can save Microsoft Excel 2002 spreadsheets
> > and Microsoft Access 2002 database tables, queries, and views as
> > XML."[
Nice software. Too bad I don't have a thousand Euros to blow to buy it.
-- Robert
- Original Message -
From: "SAXESS - Hussayn Dabbous" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 1:37 PM
Subject: Re: newbies documentatio
Manos wrote:
> No, I was talking about Microsoft Office XP not 2k; it does have native
> XML support. For example "You can save Microsoft Excel 2002 spreadsheets
> and Microsoft Access 2002 database tables, queries, and views as XML."[1].
>
> Please not that I'm *not* an M$ fun ;-)
Office-11 wi
t;
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 1:31 PM
Subject: Re: newbies documentation - yet another wiki?
Star/OpenOffice as well as the new MSOffice.
Then again, WYSIWYG HTML Editors -> Tidy works great too.
Manos
Robert Simmons wrote:
What I don't get i
PROTECTED]>
Sent: Monday, January 27, 2003 1:31 PM
Subject: Re: newbies documentation - yet another wiki?
Star/OpenOffice as well as the new MSOffice.
Then again, WYSIWYG HTML Editors -> Tidy works great too.
Manos
Robert Simmons wrote:
What I don't get is why not put the new docu
Ya, I know MSoffice can save into HTML. I want it to save into XML.
-- Robert
- Original Message -
From: "Emmanuil Batsis (Manos)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 1:31 PM
Subject: Re: newbies documentation - yet another wik
Robert Simmons wrote:
What I don't get is why not put the new documentation in cocoon distribution?
>. . .
Once there *is* new documentation, it will be easy to put it there.
Until then, the wiki is a great way to collaborate on docs until they
are ready for inclusion in the official docs, whe
27, 2003 10:14 AM
Subject: Re: newbies documentation - yet another wiki?
Hi Hussayn,
I mostly agree with your point of view, except on the "separate wiki"
thing. (And by the way, thanks a lot for your "less talking, more doing"
approach!)
What worries me *a lot* with startin
good?
-- Robert
- Original Message -
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 10:14 AM
Subject: Re: newbies documentation - yet another wiki?
> Hi Hussayn,
>
> I mostly agree with your point o
Bertrand
Good points - I think if we first agree on what the real problem
is then it will easier to find a solution for it. Here's my
first draft:
Problem:
* Users cannot get quickly started with Cocoon
Causes (?)
1. The existing Cocoon documentation is poorly written
2. The existing C
Derek Hohls wrote:
Bertrand
I think you are making the same point as me... just proposing
a different solution. I still feel that if we are using a system that
is based on the philisopy of "write once, publish anywhere" we
should be able to create documents in one place and have them
published
Hy, Derek;
Something else crawled into my mind:
I agree with you, that using a wiki as playing
ground for growing knowledge, it makes perfect
sense to extract mature infos from that site and
fill them into the "cocoon information site".
But i would disagree, if this would lead to a newbies
site a
Niclas
What you say makes sense - I think the Wiki has a high value in
"ease of use" for the documenters (that's ALL of us, BTW) to create
and edit documents - then at some point "the editor" (whoever that
is)
needs to pull out the best, structure them, and "submit it to
cocoon-dev"
(whateve
SAXESS - Hussayn Dabbous wrote:
set up 2nd Wiki in the same domain (parallel to the cocoon-wiki)
dedicated to the newbies. this would come close to my thoughts
but would not force us to start with work on the infrastructure.
instead just deploy JSPWiki a secnd time, use different layout,
interlin
On Monday 27 January 2003 17:14, Bertrand Delacretaz wrote:
> Hi Hussayn,
>
> I mostly agree with your point of view, except on the "separate wiki"
> thing. (And by the way, thanks a lot for your "less talking, more doing"
> approach!)
>
> What worries me *a lot* with starting yet another documenta
Bertrand
I think you are making the same point as me... just proposing
a different solution. I still feel that if we are using a system
that
is based on the philisopy of "write once, publish anywhere" we
should be able to create documents in one place and have them
published in more than one
Hy, Bertrand
short answer: join the party of course!
long answer:
when we want to count on newbies efforts they should be given
instant access: edit deploy, online. this is what wiki does.
hence i would consider the work on the cocoon documentation
as secnd step towards the ultimate documentatio
Hi Hussayn,
I mostly agree with your point of view, except on the "separate wiki"
thing. (And by the way, thanks a lot for your "less talking, more doing"
approach!)
What worries me *a lot* with starting yet another documentation site is
the dispersion of resources - wouldn't it be much more e
18 matches
Mail list logo
