-
- KeldorKatarn
- Posts: 243
- Joined:
Caliburn.Noesis (Caliburn.Micro port)
So I'm editing this first post so people can see it.
Caliburn.Noesis is in prerelease:
Install in the Unity Package Manager via https://github.com/VacuumBreather/Calib ... urn.Noesis
A sample is included, however for it to work, the package needs to be moved from Library/PackageCache to the actual Packages/ folder as an embedded package since the sample references a ResourceDictionary and that can't be done in the PackageCache yet. Otherwise, all features should be working, and I'll look into documenting and more feature samples over the coming days to move towards a 1.0.0 release.
Any feedback and testing is of course very welcome.
Caliburn.Noesis is in prerelease:
Install in the Unity Package Manager via https://github.com/VacuumBreather/Calib ... urn.Noesis
A sample is included, however for it to work, the package needs to be moved from Library/PackageCache to the actual Packages/ folder as an embedded package since the sample references a ResourceDictionary and that can't be done in the PackageCache yet. Otherwise, all features should be working, and I'll look into documenting and more feature samples over the coming days to move towards a 1.0.0 release.
Any feedback and testing is of course very welcome.
Last edited by KeldorKatarn on 16 Jan 2025, 23:37, edited 3 times in total.
-
- KeldorKatarn
- Posts: 243
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
Platform stuff is in place, so is a first rudamentary sample. Next I'll try to get everything working in a WPF solution.
Static LogManager is still in for now, I need to remove that still. I'm still looking for a solution that will work with dependency injection while not being too cumbersome without it.
I also need to adjust some of the API of the DialogViewModel base class. I don't like how the command needs to be re-assigned to asjust the CanExecute state for closing the dialog.
But overall it's already in a state that can be used.
Static LogManager is still in for now, I need to remove that still. I'm still looking for a solution that will work with dependency injection while not being too cumbersome without it.
I also need to adjust some of the API of the DialogViewModel base class. I don't like how the command needs to be re-assigned to asjust the CanExecute state for closing the dialog.
But overall it's already in a state that can be used.
Re: Caliburn.Noesis (Caliburn.Micro port)
This awesome man, I just added it to the Download thread.
Yes, of course, count on that. We are going to be very busy until 3.1 is out (July) but after that we can put resources here. In fact, we would love to have a private call with you.Every bit of feedback is welcome, and when the samples are done I could probably use some help from you Noesis guys to provide some neat styles to make the samples look awesome :)
-
- KeldorKatarn
- Posts: 243
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
We can make something work. I'm currently doing freelance work and still working on my game (well right now this framework kinda IS my game since I need a UI for the editor I'm doing so a good UI integration is my next step. And nothing Unity has to offer comes close to XAML productivity. Especially since I already know it very well)
After this month I'm off my freelance project though and I plan to take a month or two off in summer and just relax and work on my game and do some off-time. I'll very likely just work a bit more on this and add a few neat features and such and add samples. So your July date kinda fits with my plans anyway. I should have time off and some samples in place by then.
If you want to give me a call we can make that work. Send me a PM here and I'll provide you with some contact information. What time zone are you guys in btw? I'm onCentral European time.
After this month I'm off my freelance project though and I plan to take a month or two off in summer and just relax and work on my game and do some off-time. I'll very likely just work a bit more on this and add a few neat features and such and add samples. So your July date kinda fits with my plans anyway. I should have time off and some samples in place by then.
If you want to give me a call we can make that work. Send me a PM here and I'll provide you with some contact information. What time zone are you guys in btw? I'm onCentral European time.
-
- KeldorKatarn
- Posts: 243
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
The code runs in WPF and Unity now. I had to fix some issues with some async code which I stupidly missinterpreted. But now it should work fine. I'm still not happy with the Logger, but I'll deal with that later.
-
- KeldorKatarn
- Posts: 243
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
Edit: Activation logic, draggability and z-order are in place :)
Re: Caliburn.Noesis (Caliburn.Micro port)
😃 Good job! Keep it up!
-
- KeldorKatarn
- Posts: 243
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
I'll probably need this event:
https://www.noesisengine.com/bugs/view.php?id=1041
https://www.noesisengine.com/bugs/view.php?id=1041
-
-
sfernandez
Site Admin
- Posts: 3364
- Joined:
Re: Caliburn.Noesis (Caliburn.Micro port)
We will implement it as soon as possible.
In the meantime, if you need to know when a control initially calculated its layout, you can wait for the Loaded event, that is raised after first measure/arrange is done in the control.
In the meantime, if you need to know when a control initially calculated its layout, you can wait for the Loaded event, that is raised after first measure/arrange is done in the control.
Re: Caliburn.Noesis (Caliburn.Micro port)
I also see this is the last ticket pending to close Caliburn.Micro metaticket (#1038) :)
Who is online
Users browsing this forum: Semrush [Bot] and 3 guests