A possible UI toolkit for creating a visualisation of the object graph:
https://pathwaycommons.github.io/cytoscape-sbgn-stylesheet/
There are certainly a lot of js/html tools that will solve this
particular need.
Ari
On 21/12/21 4:11am, Andrus Adamchik wrote:
Is it worth examining DBeaver to see whether Cayenne functionality could be
added on top of the existing ERD
features?https://dbeaver.com/docs/wiki/ER-Diagrams
While I use DBeaver almost daily and appreciate all the work that went into it
and shared
Hi Ari,
I think you are on to something. New functionality and streamlining the ORM
flow is what I am looking for in the rewrite we contemplate. I don't care that
much about directly rewriting what we already have on top of another toolkit.
If we are not planning to drastically change anything,
Hi John,
JavaFX /without/ Scene Builder would be far less interesting to me. SB
shields me from having to learn the FXML semantics, plus I think I'm just
drawn to a more visual editing approach (which is why I want a great
Cayenne Modeler over putting annotations/etc on POJOs).
With something lik
Thanks Michael! I was able to run the JFX version on Java 11 and open the
sample model at "src/test/resources/cayenne-analytic.xml".
For JFX, the existence of a visual editor like Scene Builder is a huge
feature in my opinion. Being able to directly edit the UI in a visual
manner makes it much eas
> Another concern I'd have is
> learning/mastering another language (Kotlin). It might be the right path,
> ultimately, but still a concern.
This is a real concern. Similar to what we previously discussed about writing
the Modeler in JS. At least Kotlin is kinda Java though :)
> Would we be "en
Hi John (and anyone else who is curious),
I think I've got it running again. Pull the changes.
Haven't really updated the docs, so to run:
>From Terminal: mvn clean javafx:run
>From Eclipse/IDE: Set up a Maven build with the "clean javafx:run" goal.
You'll most likely need to load the included
Maybe try to communicate with JGoodies author? It is single-man company
(not huge corporation) and you have an open source non-profit project. Who
knows, maybe he will to support Cayenne...
So you can continue with robust and battle-proven Swing, no need to
transfer to javafx, electron, sciter or s
Yeah, it is likely suffering from bit rot. Was working with I last
committed it, I believe. I think the last thing I was working on was a good
pattern to handle change notifications and undos. I'll see if I can get it
up and running again.
On Thu, Dec 16, 2021 at 11:17 AM John Huss wrote:
> If
If we want to move off Swing I'd say this JavaFX project you started is the
best way to go.
I can't get it to run out of the box. Any chance you could get it running
again?
On Tue, Dec 14, 2021 at 6:49 PM Michael Gentry wrote:
> I've considered an Electron app in the past. One negative is you l
A few random thoughts.
## Integrations
If Modeler changed to another language or UI library, could it leverage
that to better integrate with other tooling?
For example, could making parts of the modeler a js library allow it to
work with existing js database modelers like Vertabelo
https:/
I thought about a web app (non-Electron) in the past, too, and it just
seemed even clunkier. For example, I would really like the ability to have
the same model open in multiple windows, so I could see different parts at
the same time. Doing that in a browser window would be awkward at best and
har
I've thought about this before for apps...what if the app runs a web app
(using whatever stack Andrus decides...maybe Tapestry) as the backend. I
don't know if that's possible.
Also, on JavaFX...I wrote an app in it recently and it's decent. It still
seems to be alive via openjfx.io, but I could
I've considered an Electron app in the past. One negative is you lose
access to existing Java code, but perhaps there is a way around this I've
not seen.
Examples:
- Existing code to read model XML files.
- JDBC drivers.
- Velocity (assuming we want to continue using Velocity templates).
For anyo
What about an Electron app? 😬
On Tue, Dec 14, 2021 at 3:59 PM John Huss wrote:
> My 2 cents is that Java desktop UI is effectively dead. So switching to
> another UI library that is either already dead or is dying isn't a great
> use of time. So I would try to change it as little as possible.
>
My 2 cents is that Java desktop UI is effectively dead. So switching to
another UI library that is either already dead or is dying isn't a great
use of time. So I would try to change it as little as possible.
For the tables with editable cells problem, my recommendation would be to
move editing in
I see a couple of problems with the current UI (beside it being subjectively
old) :
* We are effectively blocked from any significant evolution of the Modeler. Any
time we want to do anything fancy (e.g. improve usability of tables with
editable cells, etc.), we quickly run into the wall with
I believe that compose UI library is used to build the new upcoming IDE
from JetBrains called Fleet. So I expect it will continue to be supported
unless that product completely flops.
I don't mind the current modeler UI. It's good enough for me.
https://www.jetbrains.com/fleet/
On Sat, Dec 11,
I've not heard of it before. It seems that Google is kind of the upstream
provider, but Google is known to drop things all the time, too. If that
happened, I wonder what JetBrains would do? Another concern I'd have is
learning/mastering another language (Kotlin). It might be the right path,
ultimat
A datapoint to our perennial discussion of technology to use for the future
CayenneModeler... With Swing being old and crusty, and JavaFX no longer
supported by Oracle, perhaps we should be looking for something fresh. I just
came across a new "Compose Multiplatform" desktop UI framework by JetB
20 matches
Mail list logo
