Hi guys and gals,
XWiki Labs is proud to present an early (but working!) prototype of an Application Development Environment in XWiki.
I want to put out a big congradulations to the Labs team's most recent member Yann Flory for making this great work possible in record time.
We went to great lengths to avoid "nice features" such as syntax highlighting and autocompletion which are likely
sources of bugs so that we could provide a basic workflow which is stable enough to provide you something you can
start using today.
You can install XWebIDE right now from http://extensions.xwiki.org/xwiki/bin/view/Extension/XWebIDE+Application
or by searching for "XWebIDE" on the Extension Manager.
If you're developing extensions or projects on top of XWiki, start playing with XWebIDE and tell us what you think.
If you have ideas for better workflows and user experiences, we want to hear it!
* Should it be integrated in App Within Minutes? If so, how?
* How would you want to create a project? Should there be a wizard? What steps?
* What else would you like this to allow you to do?
You can write your feedback ideas and report bugs on JIRA at http://jira.xwiki.org/browse/XWEBIDE or write to me.
Thanks,
Caleb
--
Caleb James DeLisle
XWiki SAS
calebjamesdelisle(a)xwiki.com
irc.freenode cjd 9:00-18:00 GMT+1 http://bit.ly/1suU0Lh
Satire is the escape hatch from the cycle of sorrow, hatred and violence. #JeSuisCharlie
--
Satire is the escape hatch from the cycle of sorrow, hatred and violence. #JeSuisCharlie
Hello devs,
I'd like a repository on xwiki-contrib and a Jira project for a XWebIDE
Application.
This application provides an IDE for XWiki which allows users to group
pages and spaces in a project. They can then easily navigate between pages
and edit them with wiki, object and class editors.
It is already available for download at
http://extensions.xwiki.org/xwiki/bin/view/Extension/XWebIDE+Application
Name of the repo: application-webide
Thanks,
Yann
Hi,
Now that we are moving to Nested Documents, there is the question of what
do we do with the existing space and page templates[1]? How do we (still)
display them?
In the new create UI we will be showing just the option to create a Nested
Document, but for advanced users, we might also show the option to create a
terminal document (NS-style i.e. document in a space).
Since a ND translates to a space WebHome in the NS approach (or previous
approach), we could reuse any existing space templates and display them
instead of page templates.
Existing page templates were built with the NS approach in mind and I am
concerned that, until the app that provides them does not migrate them to
space templates (i.e. ND-compatible), we risk breaking their functionality
(?). This might now be valid for page templates manually created by the
admins that might have no issues since they are content focused and not
processed by any application.
Until they are migrated, we could just show page templates only when
creating terminal documents, as an advanced user.
So the options I see are:
1) Show both space and page templates when creating ND and only page
templates when creating terminal pages, hoping most of them will work most
of the time.
2) Show only space templates when creating ND and only page templates when
creating terminal pages, but risk hiding a lot of useful page templates
from regular users which would work most of the time.
My +1 goes to 1).
WDYT?
Thanks,
Eduard
----------
[1]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Administration+Applica…
Hi devs,
So after discussing the topic of Nested in several mails, we need to reach
a conclusion in order to start implementing.
There are several open questions that I will summarize. Please cast your
votes in order to advance on some topics and maybe discover what we still
need to agree on.
Q0. **Nested Spaces in model**
No matter the UI decisions we still need to take, we are implementing
Nested Spaces for 7.2 roadmap. The future is still uncertain regarding
changing the model to accommodate Nested Documents, since we can simulate
ND using NS.
Q1. **NS vs ND in the UI**
Q1.1 The majority agreed that since the final purpose are ND, we should
display ND in the UI, since it simplifies the mental model of the user.
This implies removing the Space concept from the UI.
Q1.1.1 A consequence is hiding the 'WebHome' name in the UI.
Q1.2 Although the default should be ND, the question is if we want to give
the option to display NS in the UI. This would be implemented as an
advanced and technical option. The main problem is that we might need to
provide UI alternatives for several components (menus, create step, etc.)
Q2. **Parent/Child**
Q2.1 Deprecate the notion of Parent/Child.
Q2.1.1 Provide a migration to transform the relation into NS/ND. Problem:
the old URLs[A] (bookmarks) are broken + the user is stuck with long
URLs[B] if he wants to keep the hierarchy. Additionally we might need to
provide an extension/configuration to transform into short URLs [B -> C].
Q2.1.2 Don't migrate: the parent/child hierarchy will be lost but the old
URLs[A] (bookmarks) will be kept. The user needs to use NS/ND to create
hierarchies.
Q2.2 Don't deprecate the notion of Parent/Child.
Q2.2.1 Provide a configuration in the Administration to switch the
breadcrumbs between displaying Parent/Child or NS/ND. We might need to
provide UI alternatives for several components (tree, breadcrumb
navigation, create, etc.)
Please cast your votes / add comments.
Thank you,
Caty