On 3/22/07, Catalin Hritcu <catalin.hritcu@gmail.com> wrote:
It took me quite a while to understand Sergiu's ideas, but now that I
think I did they seem quite convincing. Here are two points on which I
agree with Sergiu.
It's highly unlikely that we can specify all possible extension points
in any interface using XWiki, especially if we want to keep things
easily extensible in the future. So instead of trying to enumerate the
ones we currently know about, it would make sense to use a more
generic way of specifying extension points. For better understanding,
you can view an extension point as something as simple as a HTML id or
class, so just a string identifier.
Another point is that it should be possible to add such extension
points not only from Java components, but also from Velocity, Groovy
or Xwiki objects etc, so from the user interface itself. First,
because it would be convenient for users. Most users will have the
permissions to add new Velocity code for example, while adding a new
Java component is not an option unless you are an administrator.
Second, if the syntax is simple enough the designers themselves will
be able to add the extension points to their user interface, without
needing a programmer's assistance.
We still need to decide who can add a new extension, and who affects such an extension. My first idea is to allow anybody to add EPs and IEs, but unless such a document is certified somehow, it will only affect the current user. We need to make the distinction between global and user-specific extensions. This complicates a bit the algorithm for fast IE output, but I think we can manage to keep it fast enough.
Regards,
Catalin
On 3/21/07, Luis Arias <
kaaloo@gmail.com> wrote:
> Ok Vincent, sounds cool ! I hope your conference went well !
>
> Luis
>
> On 3/21/07, Vincent Massol <vincent@massol.net
> wrote:
> >
> >
> > Luis, I was only discussing general principles and not details. The
> > page stuff was only one example of one interface. This is why I said:
> >
> > "<example - I'm not asking to vote on this, it's just an example to
> > better visualize what "one Java Interface for each UI contribution"
> > means>"
> >
> > :)
> >
> > Now that said, I need to read Sergiu's emails and answer. That'll
> > take me a bit as I'm talking at conference today and this is not
> > something you read quickly. I'll need to digest it :)
> >
>