On Mon, Jun 9, 2008 at 9:33 PM, Sachin Mittal <sjmittal(a)gmail.com> wrote:
Thank you Thomas and Guillaume for the help. This helped me a lot.
Firstly our application is just collection of classes, all the velocity code
is written in vm templates, so as to speed the page rendering. Thus this
application would work against a specific skin only. Anyway if all goes well
then we may be able to launch it as a portal by end of the year.
I have some additional queries and would be grateful to you for throwing
some light on these:
1. What is the purpose of Dependencies field of the application?
It contains the plugins your application needs (it is just
informationnal as application does not check it yet).
2. What is the difference between Documents, Documents to include and
Documents to link fields? What is the purpose of each and how to decide
which document goes in which placeholder.
Documents : all the documents your application contains
"Documents to include" and "Documents to link" are used only when
copying an application or a wiki template (which is considered as a
big application by wiki manager) in XEM. you list here which document
content will be replace by a
#includeInContext("sourcewiki:Space.Page") or
#includeTopic("sourcewiki:Space.Page") in place of just copy it.
3. What is the purpose of Applications field of the application?
Application field list all the application your application depends on
and is used when you export "Recursively" your application.
For all thi,s a good example is XEM which has a top application called
"xem" depending on "xapp" (applicatiopn manager) and
"wikimanager"
(wiki manager).
I definitly have to documents all application manager details. Thanks
for the remainder ;)
Regards
Sachin
Thomas Mortagne wrote:
On Wed, Jun 4, 2008 at 12:44 PM, Guillaume Lerouge <guillaume(a)xwiki.com>
wrote:
Hi Sachin,
I recently created an application in xwiki.
Great :-) Will you consider publishing it on
http://code.xwiki.org/ for
the
community to enjoy it ?
[snip]
However, one cannot choose the documents from any
link, one has to type
it.
Now there are many classes and objects I would like to package and it
would
not be possible for me to remember each document's name.
So is there any better way of doing this with or without application
manager
app.
Right now there is no alternative to typing each document name
manually... I
know how annoying it is, I constantly forgot to add one of the 15 pages I
had in the Bulletin Board Application... And I guess it must be the same
for
you, maybe with even more pages.
A good way not to forget any page is to go to the
/xwiki/bin/view/Main/AllDocs page and then use the treeview for the
aeternam
space. Then you can copy all your children docs, paste them in the field,
and start removing those that don't interest you. A bit long, but at
least
you'll forget none of them...
Application Manager also support pattern based on SQL LIKE syntax (see
http://www.techonthenet.com/sql/like.php) :
- [SpaceName.%] will include all pages in the sapce SpaceName
- [%.MyApp%] will include all pages starting with MyApp
You can look at Application Manager application descriptor as an example.
(I'm adding this documentation in the application manager page.)
If you simply need a one shot selective export you can use the groovy
script provided by Admin application. See
http://code.xwiki.org/xwiki/bin/view/Applications/AdminApplication
Guillaume
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context:
http://www.nabble.com/Packaging-application-using-application-manager-plugi…
Sent from the XWiki- Dev mailing list archive at
Nabble.com.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne