28 Oct
2014
28 Oct
'14
9:08 p.m.
On 28 Oct 2014 at 20:28:15, Jeremie BOUSQUET
(jeremie.bousquet@gmail.com(mailto:jeremie.bousquet@gmail.com)) wrote:
Hi,
Le 28 oct. 2014 19:39, "Eduard Moraru" a écrit :
Maybe I did not choose the best words, but the way I understood it (and
tried to reformulate it) was not that the DW explicitly allows you to
select a homepage, but that indirectly, through allowing you to install a
flavor, it will additionally do the job (again, indirectly) of making you
choose a homepage (through the flavor you have selected).
Yes that was the idea, possibly:
- DW doesn't have to know pages or set homepage
- there could be a new wizard, similar to wizards for new page / space from
template, that allows choosing a kind of homepage (empty, wiki concepts,
dashboard, etc)
- a flavor also adds its homepage as a possible "template"
- btw it could be exactly the new space from template page, but with more
choices than current (empty / dashboard)
- following a dw run and a flavor installation, this "new Main space
homepage from template" wizard is triggered and displayed (or just proposed
to user through a button or link), and allows user to either choose default
homepage of the flavor, or use another one
- current (or reworked) homepage is just the default home of the default
flavor (which is the current XE xar)
ok but:
1) it’s complex since it means that a flavor would need to register some kind of post
install script to execute (which is something we don’t really have)
2) it negates a bit the point of a flavor which is to propose a defined “theme” and thus a
defined home page matching that theme
3) it doesn’t solve anything since once you select a default homepage you still need a way
to change it afterwards if you want to change it…
I don’t see how this is much better than having a Admin UI allowing you to change the home
page you wish to have. However it’s a lot more complex (and really marginally better).
Hi Vincent,
On Mon, Oct 27, 2014 at 11:05 AM, vincent(a)massol.net
wrote:
> Hi,
>
> On 24 Oct 2014 at 21:18:31, Eduard Moraru (enygma2002(a)gmail.com(mailto:
> enygma2002(a)gmail.com)) wrote:
>
> > Hi,
> >
> > 2 new proposals (P6 and P7) have been made recently. I did not yet get
> the
> > chance to add comments/analysis on them. Feel free to do it in the
> > meanwhile if anybody wants to.
> >
> > A few notes on Jeremie's "Proposal7: DistrbutionWizard sets the
homepage
> of
> > a flavor and the Help App teaches users" [2]:
> >
> > Personally, I find it a rather elegant solution based on separation of
> > concerns. However, you need to be aware that it is a medium/long term
> > objective.
> >
> > The way I understood it is that we delegate the task of choosing a
> homepage
> > to the DistributionWizard that will most likely be in charge of
offering
> > the user flavor options. At that point,
the homepage of the current
wiki
> > will be the homepage of the user
selected flavor. Optionally, we can
also
> > propose to use a blank page as homepage
if the user wants, however
this
might be a bit of an overkill, since the user can
easily edit the page
and
trash everything.
The DW should not know at all about any page. It should be up to the
flavor to define the wiki pages it will contain and install. Each flavor
should propose its own home page.
Maybe instead of all this, it could be enough to
unrelate the "new space"
and "apply space homepage template" features ?
So I would just have to call "space / apply template" to replace the
homepage of any space already existing (including Main obviously) ?
Yes that’s better already IMO but then it should be a menu option to replace any page
content with a page template.
Thanks
-Vincent
It was just a
high level view on the direction to follow, and not a
specific technical aspect, so no reason to -1 it, right?
since
BTW there’s also another variation for the home
page that hasn’t been
discussed yet:
* Make the home page special by not making it editable (and without any
docextra tabs at the bottom). So no rollback issue/edit weirdness.
* Only admins can change it and only through the Admin UI (basically
decide which space home page to display on the wiki home page).
* Somewhere in the content of the default home page or through the first
time wizard, direct the users to the Sandbox page to try it out editing
(since this is what Sandbox is for!)
Adding this too and I think we`re good for going forward with a vote, we have plenty of proposals.
Thanks,
Eduard
>
> Thanks
> -Vincent
>
> > The task of teaching the user is delegated exclusively to the Help
> > Application, with the note that the application will also be proposed
to
> > the user to be redirected to, as a
final step in the DW (after the
> > installation of the user selected flavor is complete).
> >
> > All of this assumes that we have a properly working Flavors feature
and
> > Help Application. However, what should
we do in the meanwhile for the
> > default XWiki Enterprise UI / Flavor / build? Should we postpone yet
> again
> > any work on the homepage until we have the needed elements to delegate
> the
> > problematic aspects, or should we do something about it in the
meanwhile?
> >
> > Thanks,
> > Eduard
> >
> > ----------
> > [1] http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposals
> > [2]
> >
>
http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposal7Distrbutio…
> >
> > On Tue, Oct 14, 2014 at 12:40 PM, Guillaume "Louis-Marie" Delhumeau
<
> > gdelhumeau(a)xwiki.com> wrote:
> >
> > > Hello.
> > >
> > > I have again a new argument against using the dashboard and the
include
> > > macro in the main page.
> > >
> > > When the user uses the "Inline" editor to change some gadgets,
she
can
> > not
> > > > use the rollback action of the main page to cancel her changes. She
> > has to
> > > > go to the Dashboard page first, and then rollback her changes from
> > there.
> > > >
> > > > Having an include macro in the default page is absolutely not
> > intuitive,
> > > > even if you make it appears more clearly.
> > > >
> > > > Thanks,
> > > > Guillaume