Web Services API

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2006 02:10 PM
Can we expect better documentation for the web services API? The example code that's included with the source helps some. But could you possibly include some comments in the code to explain what is being done? Or could you put some documentation on the Wiki that demontrates and explains how to perform common tasks?
Some common tasks could be:
- Viewing content properties/meta data
- Creatings spaces
- Modifying/Viewing permissions
- etc…
Thanks.
Some common tasks could be:
- Viewing content properties/meta data
- Creatings spaces
- Modifying/Viewing permissions
- etc…
Thanks.
Labels:
- Labels:
-
Archive
8 REPLIES 8

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2006 02:38 PM
We know our documentation is lacking in places and is not necessarily easy to navigate in the WIKI. There's not much point to providing all this capability if we don't inform people how to use it clearly.
To address this, we now have dedicated resource to develop and improve our documentation - not just for the Web Services API, but all APIs and administration, configuration, getting started, user guides etc.
To address this, we now have dedicated resource to develop and improve our documentation - not just for the Web Services API, but all APIs and administration, configuration, getting started, user guides etc.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2006 02:50 PM
This is good news. When can we expect these improvements? Thanks.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2006 03:04 PM
Well, it's going to be a process of continual improvement. One idea we're considering is to provide start-to-end manuals for end-users, administrators and developers (in html, pdf format) rather than lots of linked WIKI pages. Would that help? or do you like the WIKI?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2006 03:40 PM
I rather have the start-to-end manuals (especially PDF so I can easily print a hard copy) because navigating around the wiki is kind of a pain.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2006 10:19 AM
i cant agree with you, if more people were to use alfresco we need a start to end manuals.
when i started using alfresco i couldn't understand a lot of things. it took me quite a while to even understand simple things just because of lace of proper documentation.
alfresco is a great product but if more people were to use it we have to make it easy for them to develop.
if you want to be the defacto standard, my advice is make it as simple as possible for people, so that more people will use it.
cheers prasanth
when i started using alfresco i couldn't understand a lot of things. it took me quite a while to even understand simple things just because of lace of proper documentation.
alfresco is a great product but if more people were to use it we have to make it easy for them to develop.
if you want to be the defacto standard, my advice is make it as simple as possible for people, so that more people will use it.
cheers prasanth

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2006 12:44 PM


Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2006 06:02 AM
It would be great to see start to end docs. I have just starting looking into Alfresco and developing against (I'm coming from a DCTM background), and at the moment it is a up hill struggle; as the wiki is hard to navigate and sometimes hard to find what you are looking for. As an addition to Start to End docs, It would be good to have available the following docs:
- Javadocs for all the api, which are available (maybe they are somewhere, but I can't find them); I've had to download all the src and generate; but unfortunately some methods and params are not documented, so kinda hard to figure out what to do.
- More examples, and tutorials:
- How to create your own Web Service
- How to install and run JCR-RMI, with examples
- Creating and Calling Custom beans from a client.
- Searching and Querying the repository
One of the problems with producing hard format documention like pdf, word etc. Is that the wiki isn't updated, or the documents aren't sync'd, and as result you not sure which is the definitive resource.
Anyway, so far from what I've seen/done, it's looking good. And more docs are a bonus.
Cheers,
Dom
- Javadocs for all the api, which are available (maybe they are somewhere, but I can't find them); I've had to download all the src and generate; but unfortunately some methods and params are not documented, so kinda hard to figure out what to do.
- More examples, and tutorials:
- How to create your own Web Service
- How to install and run JCR-RMI, with examples
- Creating and Calling Custom beans from a client.
- Searching and Querying the repository
One of the problems with producing hard format documention like pdf, word etc. Is that the wiki isn't updated, or the documents aren't sync'd, and as result you not sure which is the definitive resource.
Anyway, so far from what I've seen/done, it's looking good. And more docs are a bonus.
Cheers,
Dom
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2009 01:47 PM
Dom,
I'd really like to develop a framework for creating formal documents with a database back end and a wiki front-end.
Use Case: Given a formal definition of a document (outline and contents) allow a document editor to publish the document framework to a wiki. Document stakeholders can post updates to fill in the required material. The editor can select material from multiple entries and post a top-level entry for the current "truth-state" for the formal document. The editor can also generate the complete formal document for approval and publication. (add polls and other features…)
Joyeaux Noel!
Huet
I'd really like to develop a framework for creating formal documents with a database back end and a wiki front-end.
Use Case: Given a formal definition of a document (outline and contents) allow a document editor to publish the document framework to a wiki. Document stakeholders can post updates to fill in the required material. The editor can select material from multiple entries and post a top-level entry for the current "truth-state" for the formal document. The editor can also generate the complete formal document for approval and publication. (add polls and other features…)
Joyeaux Noel!
Huet
