Re: choices / autocomplete with option to create new item

In our custom viewer, we have a specific annotation to identify Factory Methods. We infer from the returned type the associated class they are able to instantiate. That way, we can draw a drop-down menu associated with a button, present in any param requiring an entity of that class. When a

WebServer --port option not working

Hi, while updating a code base to version 1.13, I noticed that starting the WebServer with '--port 12080' doesn't work. Trying to debug it, it seems that on line 159 in WebServer.createJettyServer > final IsisConfiguration configuration = > configurationBuilder.peekConfiguration(); the return

Re: choices / autocomplete with option to create new item

Hi All, Good discussion going on, as usual, my first response to this was that Martin's requirement is just as Oscar describes, to make the new entity/instance a member of the 'options' list and the currently selected member of that list. Then I thought that it just satisifies an edge case, of

Re: choices / autocomplete with option to create new item

Hi Oscar, thanks for this. Could you sketch out what that might look like in terms of (an extension to) Isis' annotations? Cheers Dan On 28 September 2016 at 18:24, Óscar Bou - GOVERTIS wrote: > > In our custom viewer, we have a specific annotation to identify Factory >

Overriding DataNucleus annotation metadata with XML

Hello! I have tried overriding the schema of persistable classes by following the guide [1]. However, it seems that package.jdo totally replaces the annotation metadata, and I get errors on startup due to unrecognized named queries. However, using the ORM XML metadata does perform the expected

Re: choices / autocomplete with option to create new item

Thanks for these ideas, Steve. Which in turn reminds me... we have an existing module for modelling communication channels [1] that could be used/forked as the basis for handling locations. (If you want all the gmap location stuff, that is). Cheers Dan [1]

Re: choices / autocomplete with option to create new item

Thanks for your replies. You are right Dan, if the location was a more complex structure than just a string this would of course clutter up the create dialogue of the concert. Stephen: that's an interesting approach. Let's say the user creates a concert and leaves the location empty. Then per se

Re: choices / autocomplete with option to create new item

Another option to try, assuming that the Concert has been created already, is to have an action on, or contributed to, the Concert that allows creation of a new ConcertLocation. Then the user can either set the concert location by choosing an existing location from the pick list, or by creating an

Re: choices / autocomplete with option to create new item

Hi Martin, This requirement has only come up infrequently so far, not sufficiently to build a particular widget or programming model for it. Where we have required it, we've simply provided two optional parameters, one listing the existing objects, the other for the name of a new object. (This

choices / autocomplete with option to create new item

Let's say we have an entity Concert and an entity ConcertLocation and the model is such that a Concert would reference a ConcertLocation (shared ManyToOne association). In a create dialogue for the Concert entity I would like to offer the possibility to create a new ConcertLocation item if the

Re: choices / autocomplete with option to create new item

On 28 September 2016 at 13:00, Martin wrote: > > > In the last days have caught myself thinking about how my design of the > domain model would affect the usability of the application, especially > since I was taking into account the order in which things would

AW: choices / autocomplete with option to create new item

Hi, one could probably disable certain actions like sending concert announcements until all preconditions are fulfilled (date, artists, location set), but how can the missing data be signaled to the user? Instead of hardcoding the logic into disableAnnouncement, a set of rules could be used

Re: choices / autocomplete with option to create new item

On 28 September 2016 at 14:30, Rade, Joerg / Kuehne + Nagel / Ham GI-DP < joerg.r...@kuehne-nagel.com> wrote: > Hi, > > one could probably disable certain actions like sending concert > announcements until all preconditions are fulfilled (date, artists, > location set), but how can the missing

Re: choices / autocomplete with option to create new item

Hi, I'll briefly give my experiences, but first I have to admit that I've need to break some old habits, but I am still learning. I think the best way to think about Isis is in the OO manner of object methods being messages, that in triggering an action you are telling the object to do something,

Re: choices / autocomplete with option to create new item

Another thought, the pause after each change of parameter state in the modal dialogue is no-doubt part of the Wicket server-side approach and cannot be changed easily, but the slight background dimming with each such change seems an unnecessary distraction, given the background is already