@ADefWebserver_twitter could you rewrite this to an blog article that works with Oqtane mod dev?
@thabaum I feel it is too early to document 'granular' issues like that. I am still working on how to document more general issues like configuration and deployment.
I am trying to create a regex or something to make a line stop when it reaches certain characters and if it is a certain length replace the last three characters... anyone follow?
I just need an article possibly that gives some good help. I find all but what I am after doing ;)
@sbwalker fyi I am working with Azure app service installation of the framework and I installed a custom module. First time worked ok but when I attempted to upload a second I am receiving a 500 from the upload function. I installed the files manually onto the app service and had to do a full restart to get it to recognize the module update.
@OrchardSkills I suggest you follow the installation instructions in the framework repo https://github.com/oqtane/oqtane.framework and get familiar with the application. You should also read the philosophy blog: https://www.oqtane.org/Resources/Blog/PostId/538/oqtane-philosophy
Finish first version of template theme package https://github.com/2sic/oqtane-themes-template
Contains everything that a theme should use, and clearly separates js/css, theme parts, build-cycle etc. + checklists and docs to get started.
Would love to hear all your feedback on this.
Contains everything that a theme should use, and clearly separates js/css, theme parts, build-cycle etc. + checklists and docs to get started.
Would love to hear all your feedback on this.
Finish first version of template theme package https://github.com/2sic/oqtane-themes-template
Contains everything that a theme should use, and clearly separates js/css, theme parts, build-cycle etc. + checklists and docs to get started.
Would love to hear all your feedback on this.
@iJungleboy - 👍🏾
Hi everyone, really excited to get using this framework. I'm specifically interested in localization. I'm very aware that Oqtane is not designed to be 'yet another CMS' and fully respect that. However, I was wondering if anyone here had had any luck in implementing it into custom modules? Searching through this room I saw mention of avoiding resx files, etc. but have not found a concrete answer as to what the right way to do this is (it's very possible that there isn't one yet!).
there are 2 different aspects to localization. There is the localization of static text in the application such as labels, helptext, etc... And there is localization of dynamic content. On the roadmap for Oqtane V.Next there is an item for static localization. Microsoft is now offering a solution for static localization in Blazor so we will not have to roll our own. Dynamic content localization is not on the roadmap as it is a CMS feature. I would suggest that if you need dynamic content localization that you should utilize a CMS which was designed for this purpose.
I will try to do some localization stuff for Oqtane in the upcoming days ...
19 replies
maybe can be used for module loading procedure in webassembly mode
public override List<Resource> Resources => new List<Resource>()
{
new Resource { ResourceType = ResourceType.Script, Url = ModulePath() + "script.js" }
};
@chlupac I saw that library a few weeks ago and it looks interesting. It is missing some features we need but there are definitely some concepts we could utilize
I can share all of my thought about localization and open this for discussion
@hishamco currently we are trying to get the 1.0 release stabilized - so we are not integrating substantial new features at this time. I expect this stabilization phase to last ~1 month. In the meantime you can definitely make a proposal of how you think static localization should be integrated.
Could you please to setup a CI/CD a gain ;)
I need to make Oqtane testable
oqtane/oqtane.framework#540 I doctored up a PR here for the notifications. the files are conflicting with probably some changes from when the PR was first created.
but if you take it for a test run check out the notifications let me know if anything functional needs tweaked
I have added a ... to the end of the message on the User Profile index if longer than 100 and added a reply page break along with spaces to put your cursor, and a few other tweaks like taking out the reply message from the messages when showing in the view...
just not sure if I need to redo the changes on the newer files or can those be done in github?
The dashboard PR I created we can chew up in chunks for a while one component at at time to get it ready for a face lift if that works. That PR made the dashboard responsive however it shouldn't be so huge i think 58 files with changes. Nothing special really just getting it ready for the next step I was hoping. Finding out what classes need done up where and how so that theme, mod and framework designers can have a standard workflow we all can understand easily if I am in the right to think so. I look forward to the new UX experiences down the road. For now just making things flow on any device was my intent. However looking back I am sure things can be done so many different ways. Just a perspective on what I am feeling from the community while trying to create acceptable solutions for PR's that help the Oqtane project. I am here to help while I learn :)
I am really just trying to get it ready to throw down the base coat...
love all your past support you guys ROCK!
@sbwalker you mentioned in this previous post:
yes there is support for including third party Blazor components in modules but it is not currently demonstrated or documented anywhere, and it is not fully mature yet as we only achieved the 1.0 release this week
that it is possible to include third party components in a module.
What we want to achieve:
- add third party blazor components to an external module
- without adding any dependencies directly to the oqtane framework
- Run oqtane in WebAssembly mode
What we have reached so far:
- we created a external module and added all needed dependencies to that module. It can be compiled without any impacts.
We also extended the nuspec to include all needed dependent Dlls in the package. - Added the external module to a page
The problem:
Currently the external module can't load correctly because dependent Dlls are missing on client side.
How can we get this to work?
@svreic thank you for raising this item. There were some changes made to assembly loading for WebAssembly just prior to the 1.0.0 release and I was concerned that they may have an impact on assembly dependencies. If you look in the \Oqtane.Server\Controllers\InstallationController.cs class and the Load() method it has logic to determine the list of assemblies which need to be downloaded to the client. It uses GetReferencedAssemblies() to find the dependencies. This is different than the approach which was used previously. Previously it would rely on the module to explicitly declare its dependencies - this was done using the the Dependencies property in the IModule interface.
I am concerned that the new logic does not identify the third party components correctly.
it utilizes the Dependencies property of the IModule and ITheme interface
basically when you are running on WebAssembly you should identify the names of any assemblies which your module or theme depends on, so that Oqtane knows that it needs to download them to the client browser
ie.
public ModuleDefinition ModuleDefinition => new ModuleDefinition
{
Name = "Blog",
Description = "Blog",
Version = "1.0.0",
ServerManagerType = "Oqtane.Blogs.Manager.BlogManager, Oqtane.Blogs.Server.Oqtane",
ReleaseVersions = "1.0.0",
Dependencies = "Oqtane.Blogs.Shared.Oqtane"
};
in the above case it is indicating that the Blog module depends on the Oqtane.Blogs.Shared.Oqtane assembly
if you have multiple dependencies then you should include them all separated by commas