Nice work, joerg, I'll check it out! By the way, Seb Slutzky (who I think you met back in Amsterdam a while back) has also developed an ro viewer, his in typescript. I'll make sure both implementations are referenced from the new V2 site.
Cheers, Dan On Sun, 22 Sep 2019, 15:55 Rade, Joerg / Kuehne + Nagel / HAM GI-DP, < [email protected]> wrote: > Hi Andi, > > thanks for taking the time to comment! > > A couple of years ago I looked into Vaadin as well and liked it's > approach. > IIRC back then the UI programming model was more server side. > > The approach I took for kroviz is a client side model - I ended up in > reinventing Redux. > Requests to the server are sent asynchronously and response events are > stored. > As soon as layout information is available, views are rendered. As more > data comes in, it will be added to the lists. > [3] has an overview diagram. > > The parts that are platform specific should be replaced easily. > I'll check the current Vaadin model and will get back on it. > > -j > -----Ursprüngliche Nachricht----- > Von: Andi Huber [mailto:[email protected]] > Gesendet: Sonntag, 22. September 2019 12:45 > An: [email protected] > Betreff: Re: Restful Objects Viewer in Kotlin/JS > > Hi Jörg, > > I only got a glimpse at your screenshots, and must say it looks awesome! > > We had thoughts to do something similar: starting a new viewer from > scratch, maybe utilizing WebComponents with Vaadin > > While the Apache Isis Wicket Viewer currently acts as the UI > reference-implementation, this might change in the future. > > So I'm looking forward to exchange experiences on this alternative viewer > topic or to even somehow join forces. > > Cheers, Andi > > On 2019/09/20 15:37:55, "Rade, Joerg / Kuehne + Nagel / HAM GI-DP" > <[email protected]> wrote: > > Hi all, > > > > during the last months I've implemented a RO viewer in Kotlin/JS. > > The major parts are in place and I hope to have it ready for users by > the end of the year. > > > > The code is available at [1] , binaries yet to come. > > > > Thanks to the Tabulator widget, ObjectLists are pretty comfortable > already (see sample screens in the README). > > Next on my list is parsing layout.xml's and building Object forms based > on it. > > > > Open issues are at [2], if you are adventurous and want to run it, see > [3], especially the section on CORS. > > > > All comments welcome! > > > > Have fun -j > > > > [1] https://github.com/joerg-rade/kroviz > > [2] https://github.com/joerg-rade/kroviz/issues > > [3] > https://github.com/joerg-rade/kroviz/blob/master/docs/DevelopmentGuide.md > > > > Kühne + Nagel (AG & Co.) KG > > Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE > 812773878. > > Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Holger Ketz (Vors. ), > Martin Brinkmann, Lars-Olof Grün, Matthias Knicky, Nicholas Minde, Johannes > Trimborn, Lars Wedel, Matthias Weiner. > > Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform: > Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745, > Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt. > > Geschäftsleitung Region Europa: Dr. Hansjörg Rodi (Vors.), Mart Ambur, > Tom Ban, Dominic Edmonds, Thierry Held, Uwe Hött, Richard Huhn, Jan-Hendrik > Köstergarten, Heiko Schuhmacher. > > > > Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen > Spediteurbedingungen 2017 (ADSp 2017). Hinweis: Die ADSp 2017 weichen in > Ziffer 23 hinsichtlich des Haftungshöchstbetrages für Güterschäden (§ 431 > HGB) vom Gesetz ab, indem sie die Haftung bei multimodalen Transporten > unter Einschluss einer Seebeförderung und bei unbekanntem Schadenort auf 2 > SZR/kg und im Übrigen die Regelhaftung von 8,33 SZR/kg zusätzlich auf 1,25 > Millionen Euro je Schadenfall sowie 2,5 Millionen Euro je Schadenereignis, > mindestens aber 2 SZR/kg, beschränken. Die ADSp sind auf unserer Webseite > als Download erhältlich. Auf Anfrage senden wir Ihnen diese auch gerne zu. > > >
