You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Eli Baram (JIRA)" <ji...@apache.org> on 2009/07/01 10:48:47 UTC
[jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Posted by Jason Dillon <ja...@planet57.com>.
On Jul 7, 2009, at 7:20 PM, Nicholas L Gallardo wrote:
> I agree with Jason's point below that the ability to edit the docs
> should be generally accessible. Jason, can you think of any examples
> of PDFs that have been generated from cwiki content? I'd be curious
> to see how much it resembles the wiki itself.
>
Off hand, no, but I can generate one for you if you like from
something in the GMOx* spaces. It does a good job, but has some warts.
> Eli made good points earlier too about not wanting to have a single
> page that became the doc. It needs to be a well-organized tree that
> can then have a PDF generated from there. Don't know if that's
> possible though.
>
In Confluence-lang a section of a PDF tends to become its own page,
sub-sections could be their own-page depending on complexity and
size. Chapters would be their own page, blah, blah, blah.
You could even have a single page, which includes all of the other
pages if you really wanted that huge massive single-page doc.
> Another point to consider. For the online docs, it would be nice to
> keep them versioned under link that correspond to the release
> (separate docs for 0.1, 0.2, 1.0, etc.)
>
Geronimo handles with with a GMOxDOC<VERSION> space. You can see them
all here:
http://cwiki.apache.org/confluence/dashboard.action
Just search for GMOx and see all the spaces that Geronimo has.
* * *
I would recommend limiting the number of spaces for now to two... one
for the site, one for the docs until incubation has finished, I don't
think infra would have a problem with that.
--jason
PS. exporting the GMOxDOC21 space now as PDF... hope it doesn't crash
Confluence ;-)
Re: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and
its content need to refer to Wink instead of Symphony
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Thanks for chiming in folks. Glad to hear others are interested in moving
that way as well.
I agree with Jason's point below that the ability to edit the docs should
be generally accessible. Jason, can you think of any examples of PDFs that
have been generated from cwiki content? I'd be curious to see how much it
resembles the wiki itself.
Eli made good points earlier too about not wanting to have a single page
that became the doc. It needs to be a well-organized tree that can then
have a PDF generated from there. Don't know if that's possible though.
Another point to consider. For the online docs, it would be nice to keep
them versioned under link that correspond to the release (separate docs for
0.1, 0.2, 1.0, etc.)
-Nick
Nicholas Gallardo
WebSphere - REST & WebServices Development
nlgallar@us.ibm.com
Phone: 512-286-6258
Building: 903 / 5G-016
Jason Dillon
<jason@planet57.c
om> To
Sent by: Jason wink-dev@incubator.apache.org
Dillon cc
<jason.dillon@gma
il.com> Subject
Re: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf
07/07/2009 06:44 and its content need to refer to
AM Wink instead of Symphony
Please respond to
wink-dev@incubato
r.apache.org
I actually think moving this to the wiki is not a bad idea... that is
what we have done for all the Geronimo docs. If needed we can create
additional spaces in Confluence to hold the pure-docs aside from the
website.
I am not really sure how many Apache projects use Word to generate
docs, I can't think of any of the top of my head (doesn't mean there
aren't any). But generally more open and accessible formats are
preferred, so that if I want to help with the docs I don't have to go
out and buy Microsoft Word/Office to do it. I suppose OpenOffice
would work as long as the format is compatible.
I have not tried recently, but in the past changes to a Word doc, even
the xml flavors often make scm change logs very difficult to grok and
comprehend what was actually changed. This can be easier with formats
like docbook, or using Confluence's change notification emails.
BTW, a Confluence space can be exported as a PDF file, so you'd get
html and PDF (plus wiki markup) versions of the docs. The only thing
is that the "root source document" would be a Confluence space, not a
single file on a file system.
* * *
I'm pro-Confluence for docs.
--jason
On Jul 7, 2009, at 6:32 PM, Bruggeman, Michael wrote:
> In my opinion the best solution is to generate all of the
> documentation from a root source document, such as a word document
> and from that root doc. HTML and PDF formats can easily be generated.
>
> Michael
>
> -----Original Message-----
> From: Baram, Eliezer
> Sent: Tuesday, July 07, 2009 2:24 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> The thanks are to Michael Bruggeman who updated the docs.
> I think the best solution would be if we have both, a html version
> for the reasons you mentioned and also a pdf version that can be
> part of the distribution zip so people who download Wink would be
> able to work with and print. It would also help us bundle the
> documentation per a specific version, so people with older version
> then the latest (once we have older versions :)) will be able to
> easily find the documentation of the version they have.
>
> I do not want to manage the two instances of the same document (wiki
> and pdf) so the best solution IMO would be if we could generate one
> instance out of the other. Wiki provides an option to generate a
> pdf format out of it, but I'm not sure if it gives the full
> capabilities we would like to have in the pdf like cross references,
> index, etc and I'm afraid we would need to keep all the
> documentation in one wiki page in order to be able to generate pdf
> out of it, a page that can grow to several hundreds of "pages".
> I do not have experience in managing documents in several formats
> and I'll be happy to hear good practices.
>
> --Eli
>
>
>
> From: Nicholas L Gallardo [mailto:nlgallar@us.ibm.com]
> Sent: Monday, July 06, 2009 7:11 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
>
> Thanks for updating the doc Eli. There's still some HP branding on
> the first page that we should probably change to Apache at some point.
>
> So, I'm just going to throw this out there. What would you guys
> think about taking the content in the PDF and getting it on the
> wiki? I'm not saying that it has to be done immediately, or that you
> in particular should do it. But want to see what others think about
> that.
>
> Here's my reasoning... The content in the document in excellent, but
> as a user my primary problem solving tool is Google. When I go to
> search for information related to Wink that probably exists in that
> doc, I won't find it. The harder it is to find the necessary
> information, the less likely it is for people to a) help themselves
> in terms of development and debugging and b) it's less likely for
> people to use the project when they can't find what's supported
> easily.
>
> Just a thought...
>
> -Nick
>
>
>
> Nicholas Gallardo
> WebSphere - REST & WebServices Development
> nlgallar@us.ibm.com
> Phone: 512-286-6258
> Building: 903 / 5G-016
> [cid:1__=08BBFF78DFCBE10F8f9e8a93df938@us.ibm.com]"Baram, Eliezer"
<ebaram@hp.com
> >
>
> "Baram, Eliezer" <eb...@hp.com>
>
> 07/05/2009 06:58 AM
> Please respond to
> wink-dev@incubator.apache.org
>
>
>
> To
>
>
> "wink-dev@incubator.apache.org" <wi...@incubator.apache.org>
>
>
> cc
>
>
>
>
> Subject
>
>
> RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
> and its content need to refer to Wink instead of Symphony
>
>
>
>
>
>
>
>
> Hi Michael
> All the "symphony" references including the those who are part of
> parameter or a property name should be changed to wink.
> For those who are parameter or a property we should also do code
> changes, part of them where already been changed (WINK-14).
> Regards,
> Eli
>
>
> -----Original Message-----
> From: Bruggeman, Michael
> Sent: Sunday, July 05, 2009 2:36 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> Hi Eli,
> What about all of these instances of the "Symphony word used in the
> code.
>
> symphony.serviceDocumentCssPath
>
>
>
>
>
>
> -----Original Message-----
> From: Eli Baram (JIRA) [mailto:jira@apache.org]
> Sent: Wednesday, July 01, 2009 11:49 AM
> To: wink-dev@incubator.apache.org
> Subject: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> The Symphony_SDK_2.0_Features_List.pdf and its content need to refer
> to Wink instead of Symphony
>
------------------------------------------------------------------------------------------------
>
> Key: WINK-25
> URL: https://issues.apache.org/jira/browse/WINK-25
> Project: Wink
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.1
> Reporter: Eli Baram
>
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Re: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Posted by Jason Dillon <ja...@planet57.com>.
I actually think moving this to the wiki is not a bad idea... that is
what we have done for all the Geronimo docs. If needed we can create
additional spaces in Confluence to hold the pure-docs aside from the
website.
I am not really sure how many Apache projects use Word to generate
docs, I can't think of any of the top of my head (doesn't mean there
aren't any). But generally more open and accessible formats are
preferred, so that if I want to help with the docs I don't have to go
out and buy Microsoft Word/Office to do it. I suppose OpenOffice
would work as long as the format is compatible.
I have not tried recently, but in the past changes to a Word doc, even
the xml flavors often make scm change logs very difficult to grok and
comprehend what was actually changed. This can be easier with formats
like docbook, or using Confluence's change notification emails.
BTW, a Confluence space can be exported as a PDF file, so you'd get
html and PDF (plus wiki markup) versions of the docs. The only thing
is that the "root source document" would be a Confluence space, not a
single file on a file system.
* * *
I'm pro-Confluence for docs.
--jason
On Jul 7, 2009, at 6:32 PM, Bruggeman, Michael wrote:
> In my opinion the best solution is to generate all of the
> documentation from a root source document, such as a word document
> and from that root doc. HTML and PDF formats can easily be generated.
>
> Michael
>
> -----Original Message-----
> From: Baram, Eliezer
> Sent: Tuesday, July 07, 2009 2:24 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> The thanks are to Michael Bruggeman who updated the docs.
> I think the best solution would be if we have both, a html version
> for the reasons you mentioned and also a pdf version that can be
> part of the distribution zip so people who download Wink would be
> able to work with and print. It would also help us bundle the
> documentation per a specific version, so people with older version
> then the latest (once we have older versions :)) will be able to
> easily find the documentation of the version they have.
>
> I do not want to manage the two instances of the same document (wiki
> and pdf) so the best solution IMO would be if we could generate one
> instance out of the other. Wiki provides an option to generate a
> pdf format out of it, but I'm not sure if it gives the full
> capabilities we would like to have in the pdf like cross references,
> index, etc and I'm afraid we would need to keep all the
> documentation in one wiki page in order to be able to generate pdf
> out of it, a page that can grow to several hundreds of "pages".
> I do not have experience in managing documents in several formats
> and I'll be happy to hear good practices.
>
> --Eli
>
>
>
> From: Nicholas L Gallardo [mailto:nlgallar@us.ibm.com]
> Sent: Monday, July 06, 2009 7:11 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
>
> Thanks for updating the doc Eli. There's still some HP branding on
> the first page that we should probably change to Apache at some point.
>
> So, I'm just going to throw this out there. What would you guys
> think about taking the content in the PDF and getting it on the
> wiki? I'm not saying that it has to be done immediately, or that you
> in particular should do it. But want to see what others think about
> that.
>
> Here's my reasoning... The content in the document in excellent, but
> as a user my primary problem solving tool is Google. When I go to
> search for information related to Wink that probably exists in that
> doc, I won't find it. The harder it is to find the necessary
> information, the less likely it is for people to a) help themselves
> in terms of development and debugging and b) it's less likely for
> people to use the project when they can't find what's supported
> easily.
>
> Just a thought...
>
> -Nick
>
>
>
> Nicholas Gallardo
> WebSphere - REST & WebServices Development
> nlgallar@us.ibm.com
> Phone: 512-286-6258
> Building: 903 / 5G-016
> [cid:1__=08BBFF78DFCBE10F8f9e8a93df938@us.ibm.com]"Baram, Eliezer" <ebaram@hp.com
> >
>
> "Baram, Eliezer" <eb...@hp.com>
>
> 07/05/2009 06:58 AM
> Please respond to
> wink-dev@incubator.apache.org
>
>
>
> To
>
>
> "wink-dev@incubator.apache.org" <wi...@incubator.apache.org>
>
>
> cc
>
>
>
>
> Subject
>
>
> RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
> and its content need to refer to Wink instead of Symphony
>
>
>
>
>
>
>
>
> Hi Michael
> All the "symphony" references including the those who are part of
> parameter or a property name should be changed to wink.
> For those who are parameter or a property we should also do code
> changes, part of them where already been changed (WINK-14).
> Regards,
> Eli
>
>
> -----Original Message-----
> From: Bruggeman, Michael
> Sent: Sunday, July 05, 2009 2:36 PM
> To: wink-dev@incubator.apache.org
> Subject: RE: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> Hi Eli,
> What about all of these instances of the "Symphony word used in the
> code.
>
> symphony.serviceDocumentCssPath
>
>
>
>
>
>
> -----Original Message-----
> From: Eli Baram (JIRA) [mailto:jira@apache.org]
> Sent: Wednesday, July 01, 2009 11:49 AM
> To: wink-dev@incubator.apache.org
> Subject: [jira] Created: (WINK-25) The
> Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
> Wink instead of Symphony
>
> The Symphony_SDK_2.0_Features_List.pdf and its content need to refer
> to Wink instead of Symphony
> ------------------------------------------------------------------------------------------------
>
> Key: WINK-25
> URL: https://issues.apache.org/jira/browse/WINK-25
> Project: Wink
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.1
> Reporter: Eli Baram
>
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
RE: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink
instead of Symphony
Posted by "Bruggeman, Michael" <mi...@hp.com>.
In my opinion the best solution is to generate all of the documentation from a root source document, such as a word document and from that root doc. HTML and PDF formats can easily be generated.
Michael
-----Original Message-----
From: Baram, Eliezer
Sent: Tuesday, July 07, 2009 2:24 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
The thanks are to Michael Bruggeman who updated the docs.
I think the best solution would be if we have both, a html version for the reasons you mentioned and also a pdf version that can be part of the distribution zip so people who download Wink would be able to work with and print. It would also help us bundle the documentation per a specific version, so people with older version then the latest (once we have older versions :)) will be able to easily find the documentation of the version they have.
I do not want to manage the two instances of the same document (wiki and pdf) so the best solution IMO would be if we could generate one instance out of the other. Wiki provides an option to generate a pdf format out of it, but I'm not sure if it gives the full capabilities we would like to have in the pdf like cross references, index, etc and I'm afraid we would need to keep all the documentation in one wiki page in order to be able to generate pdf out of it, a page that can grow to several hundreds of "pages".
I do not have experience in managing documents in several formats and I'll be happy to hear good practices.
--Eli
From: Nicholas L Gallardo [mailto:nlgallar@us.ibm.com]
Sent: Monday, July 06, 2009 7:11 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Thanks for updating the doc Eli. There's still some HP branding on the first page that we should probably change to Apache at some point.
So, I'm just going to throw this out there. What would you guys think about taking the content in the PDF and getting it on the wiki? I'm not saying that it has to be done immediately, or that you in particular should do it. But want to see what others think about that.
Here's my reasoning... The content in the document in excellent, but as a user my primary problem solving tool is Google. When I go to search for information related to Wink that probably exists in that doc, I won't find it. The harder it is to find the necessary information, the less likely it is for people to a) help themselves in terms of development and debugging and b) it's less likely for people to use the project when they can't find what's supported easily.
Just a thought...
-Nick
Nicholas Gallardo
WebSphere - REST & WebServices Development
nlgallar@us.ibm.com
Phone: 512-286-6258
Building: 903 / 5G-016
[cid:1__=08BBFF78DFCBE10F8f9e8a93df938@us.ibm.com]"Baram, Eliezer" <eb...@hp.com>
"Baram, Eliezer" <eb...@hp.com>
07/05/2009 06:58 AM
Please respond to
wink-dev@incubator.apache.org
To
"wink-dev@incubator.apache.org" <wi...@incubator.apache.org>
cc
Subject
RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Hi Michael
All the "symphony" references including the those who are part of parameter or a property name should be changed to wink.
For those who are parameter or a property we should also do code changes, part of them where already been changed (WINK-14).
Regards,
Eli
-----Original Message-----
From: Bruggeman, Michael
Sent: Sunday, July 05, 2009 2:36 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Hi Eli,
What about all of these instances of the "Symphony word used in the code.
symphony.serviceDocumentCssPath
-----Original Message-----
From: Eli Baram (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, July 01, 2009 11:49 AM
To: wink-dev@incubator.apache.org
Subject: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink
instead of Symphony
Posted by "Baram, Eliezer" <eb...@hp.com>.
The thanks are to Michael Bruggeman who updated the docs.
I think the best solution would be if we have both, a html version for the reasons you mentioned and also a pdf version that can be part of the distribution zip so people who download Wink would be able to work with and print. It would also help us bundle the documentation per a specific version, so people with older version then the latest (once we have older versions :)) will be able to easily find the documentation of the version they have.
I do not want to manage the two instances of the same document (wiki and pdf) so the best solution IMO would be if we could generate one instance out of the other. Wiki provides an option to generate a pdf format out of it, but I'm not sure if it gives the full capabilities we would like to have in the pdf like cross references, index, etc and I'm afraid we would need to keep all the documentation in one wiki page in order to be able to generate pdf out of it, a page that can grow to several hundreds of "pages".
I do not have experience in managing documents in several formats and I'll be happy to hear good practices.
--Eli
From: Nicholas L Gallardo [mailto:nlgallar@us.ibm.com]
Sent: Monday, July 06, 2009 7:11 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Thanks for updating the doc Eli. There's still some HP branding on the first page that we should probably change to Apache at some point.
So, I'm just going to throw this out there. What would you guys think about taking the content in the PDF and getting it on the wiki? I'm not saying that it has to be done immediately, or that you in particular should do it. But want to see what others think about that.
Here's my reasoning... The content in the document in excellent, but as a user my primary problem solving tool is Google. When I go to search for information related to Wink that probably exists in that doc, I won't find it. The harder it is to find the necessary information, the less likely it is for people to a) help themselves in terms of development and debugging and b) it's less likely for people to use the project when they can't find what's supported easily.
Just a thought...
-Nick
Nicholas Gallardo
WebSphere - REST & WebServices Development
nlgallar@us.ibm.com
Phone: 512-286-6258
Building: 903 / 5G-016
[cid:1__=08BBFF78DFCBE10F8f9e8a93df938@us.ibm.com]"Baram, Eliezer" <eb...@hp.com>
"Baram, Eliezer" <eb...@hp.com>
07/05/2009 06:58 AM
Please respond to
wink-dev@incubator.apache.org
To
"wink-dev@incubator.apache.org" <wi...@incubator.apache.org>
cc
Subject
RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Hi Michael
All the "symphony" references including the those who are part of parameter or a property name should be changed to wink.
For those who are parameter or a property we should also do code changes, part of them where already been changed (WINK-14).
Regards,
Eli
-----Original Message-----
From: Bruggeman, Michael
Sent: Sunday, July 05, 2009 2:36 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Hi Eli,
What about all of these instances of the "Symphony word used in the code.
symphony.serviceDocumentCssPath
-----Original Message-----
From: Eli Baram (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, July 01, 2009 11:49 AM
To: wink-dev@incubator.apache.org
Subject: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and
its content need to refer to Wink instead of Symphony
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Thanks for updating the doc Eli. There's still some HP branding on the
first page that we should probably change to Apache at some point.
So, I'm just going to throw this out there. What would you guys think
about taking the content in the PDF and getting it on the wiki? I'm not
saying that it has to be done immediately, or that you in particular should
do it. But want to see what others think about that.
Here's my reasoning... The content in the document in excellent, but as a
user my primary problem solving tool is Google. When I go to search for
information related to Wink that probably exists in that doc, I won't find
it. The harder it is to find the necessary information, the less likely it
is for people to a) help themselves in terms of development and debugging
and b) it's less likely for people to use the project when they can't find
what's supported easily.
Just a thought...
-Nick
Nicholas Gallardo
WebSphere - REST & WebServices Development
nlgallar@us.ibm.com
Phone: 512-286-6258
Building: 903 / 5G-016
"Baram, Eliezer"
<eb...@hp.com>
To
07/05/2009 06:58 "wink-dev@incubator.apache.org"
AM <wi...@incubator.apache.org>
cc
Please respond to Subject
wink-dev@incubato RE: [jira] Created: (WINK-25) The
r.apache.org Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to
Wink instead of Symphony
Hi Michael
All the "symphony" references including the those who are part of parameter
or a property name should be changed to wink.
For those who are parameter or a property we should also do code changes,
part of them where already been changed (WINK-14).
Regards,
Eli
-----Original Message-----
From: Bruggeman, Michael
Sent: Sunday, July 05, 2009 2:36 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink
instead of Symphony
Hi Eli,
What about all of these instances of the "Symphony word used in the code.
symphony.serviceDocumentCssPath
-----Original Message-----
From: Eli Baram (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, July 01, 2009 11:49 AM
To: wink-dev@incubator.apache.org
Subject: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to
Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink
instead of Symphony
Posted by "Baram, Eliezer" <eb...@hp.com>.
Hi Michael
All the "symphony" references including the those who are part of parameter or a property name should be changed to wink.
For those who are parameter or a property we should also do code changes, part of them where already been changed (WINK-14).
Regards,
Eli
-----Original Message-----
From: Bruggeman, Michael
Sent: Sunday, July 05, 2009 2:36 PM
To: wink-dev@incubator.apache.org
Subject: RE: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
Hi Eli,
What about all of these instances of the "Symphony word used in the code.
symphony.serviceDocumentCssPath
-----Original Message-----
From: Eli Baram (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, July 01, 2009 11:49 AM
To: wink-dev@incubator.apache.org
Subject: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Created: (WINK-25) The
Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink
instead of Symphony
Posted by "Bruggeman, Michael" <mi...@hp.com>.
Hi Eli,
What about all of these instances of the "Symphony word used in the code.
symphony.serviceDocumentCssPath
-----Original Message-----
From: Eli Baram (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, July 01, 2009 11:49 AM
To: wink-dev@incubator.apache.org
Subject: [jira] Created: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
------------------------------------------------------------------------------------------------
Key: WINK-25
URL: https://issues.apache.org/jira/browse/WINK-25
Project: Wink
Issue Type: Task
Components: Documentation
Affects Versions: 0.1
Reporter: Eli Baram
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to Wink instead of Symphony
Posted by "Michael Bruggeman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bruggeman updated WINK-25:
----------------------------------
Attachment: Apache Wink 0.1 Runtime Features List.docx
Apache Wink 0.1 Runtime Features List.pdf
I have attached the updated version of the Apache Wink 0.1 Feature Set preliminary documentation draft.
> The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
> ------------------------------------------------------------------------------------------------
>
> Key: WINK-25
> URL: https://issues.apache.org/jira/browse/WINK-25
> Project: Wink
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.1
> Reporter: Eli Baram
> Attachments: Apache Wink 0.1 Runtime Features List.docx, Apache Wink 0.1 Runtime Features List.pdf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to Wink instead of Symphony
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729266#action_12729266 ]
Hudson commented on WINK-25:
----------------------------
Integrated in Wink-Trunk-JDK15 #17 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK15/17/])
> The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
> ------------------------------------------------------------------------------------------------
>
> Key: WINK-25
> URL: https://issues.apache.org/jira/browse/WINK-25
> Project: Wink
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.1
> Reporter: Eli Baram
> Attachments: Apache Wink 0.1 Runtime Features List.docx, Apache Wink 0.1 Runtime Features List.pdf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WINK-25) The Symphony_SDK_2.0_Features_List.pdf
and its content need to refer to Wink instead of Symphony
Posted by "Eli Baram (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Baram resolved WINK-25.
---------------------------
Resolution: Fixed
Fix Version/s: 0.1
Assignee: Eli Baram
> The Symphony_SDK_2.0_Features_List.pdf and its content need to refer to Wink instead of Symphony
> ------------------------------------------------------------------------------------------------
>
> Key: WINK-25
> URL: https://issues.apache.org/jira/browse/WINK-25
> Project: Wink
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.1
> Reporter: Eli Baram
> Assignee: Eli Baram
> Fix For: 0.1
>
> Attachments: Apache Wink 0.1 Runtime Features List.docx, Apache Wink 0.1 Runtime Features List.pdf
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.