On 21 November 2015 at 20:25, Vladimir Nišević <[email protected]> wrote:
> Hi Dan, thank you, this is a really cool feature! The applications I'm > building, have often legacy systems and some parts of my domain models are > built on service calls to that legacy systems - in that case we build > domain models with view models to hold the data from multiple backends and > implement the core domain logic in them. Until now we have primarily used > this domain models to expose REST services to other systems, but I believe > this could be the way to implement some wicket based UI's. > > Glad you like it :-) > Additionaly, here some ideas I'd like to share, maybe to see some of them > in the future in the Apache Isis framework: > > 1. Search capability based on e.g. Elasticsearch [1], where the > Elasticsearch could act as a kind of "external index" for the parts of > domain model. Developer could mark which fields should be searchable, this > fields would be updated in elasticsearch instance after database > insert/update/delete. User can search thru Elasticsearch and retreive the > entity OID's as results and in the second step use them to retreive the > entities from main repository (thru datanucleus container). I could > contribute to this feature since we have integrated Elasticsearch with > Apache Isis. > > This has come up several times, and we do have a ticket for it [4]. I think that as of 1.10.0 all the infrastructure is now in place to make this really very easy to implement. I've updated that ticket with some implementation details. I do think though that it'd be better implemented as an isisaddon rather than baked into the framework. The isisaddons site has a template project [5] that one can use as a starting point. > 2. An add-on to support system-wide and/or user-specific notifications > (similar to Atlassian Confluence [2}). An Isis user could receive such > "notifications" - they would appear on his desktop, he could mark them > "readed". Some notifications could be system-wide and controlled by e.g. > system without a possibility to remove them until e.g. administrator > decides that. We use such features to e.g. notify application users there > is a newer version of the application and they should finish their work and > log off /logon in order to switch to that new version. > > Again, we have a ticket for this already [6]; I've updated it to add your ideas (which are probably several related tickets). Kevin and I did a spike on this a while back, and got a little clock ticking in the corner of the Wicket viewer. So it's definitely doable. I think this one would probably be "baked into" the framework. > 3. In a world of collaboration systems there could be an interest extension > to your incode-module-note feature, the capability not only to add the > notes to an entity, but also to add infinite comments to that note (in > other words to add the comment threads to the entity). In combination with > text search capability (idea #1) I thinks we could build really great > features. > > That does sound like an interesting feature. I've raised a ticket in the incode-module-note repo [7]. What can I say other than "pull requests" gratefully received! Cheers Dan > > Vladimir > > > [1] https://www.elastic.co > [2] > > https://confluence.atlassian.com/display/CONF43/Managing+Notifications+in+Confluence > > [3] https://github.com/incodehq > > [4] https://issues.apache.org/jira/browse/ISIS-383 [5] github.com/isisaddons/template [6] https://issues.apache.org/jira/browse/ISIS-1176 [7] https://github.com/incodehq/incode-module-note/issues/1
