requirements. Agree that the import/export is not needed for our first
On Oct 6, 9:48 am, Adam Ross <
adam.r...@priocept.com> wrote:
> Agreed. Though we can launch without this IMO as the core functionality is browsing/editing/moving/deleting etc, some of which is far more usable than CRX.
>
>
>
> -----Original Message-----
> From:
jackrabbitexp...@googlegroups.com [mailto:
jackrabbitexp...@googlegroups.com] On Behalf Of
matthew.skel...@priocept.com
> Sent: 05 October 2010 14:39
> To: Jackrabbit Explorer Discussion
> Subject: [jackrabbitexplorer-discuss:0] Defining and editing inheritance and mixins for node types
>
> Chris J and I were talking about this yesterday - the possible need to
> support definition and editing of inheritance and mixin relationships
> within Jackrabbit Explorer.
>
> Is that an appropriate goal for Jackrabbit Explorer? I seem to
> remember discussing the possibility of Jackrabbit Explorer becoming an
> open-source replacement for the CRX browser. If that's still the case,
> then I definitely think we need a way to define new node types with
> inheritance and mixin options.
>
> Thoughts?
>
> Matthew
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jackrabbit Explorer Discussion" group.
>