I've some nested UserControls on an MVVM/WPF project using .NET 6.0 and Catel 5.12.22
Google led me to this, all be it an old article https://www.codeproject.com/Articles/129920/Catel-Part-3-of-n-The-MVVM-Framework#mapping
I can't find the UserControl anymore in the Catel 5.12
Lots of dead links to old documentation currently, so please advise where I can find this, or how it works now.
Jeroen
The UserControl still exists in Catel.
Here is the full documentation.
To use it in xaml, use this code:
<catel:UserControl x:Class="Catel.Views.MyControl"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:catel="http://schemas.catelproject.com">
<!-- For the sake of simplicity, content is left out -->
</catel:UserControl>
Related
Please note that I have previously installed Documentation for Android SDK via AS 3.5.2 SDK manager
Consider the following inconsistent behavior whilst editing java source code ...
import android.app.Fragment; // Deprecated!
If I hover over Fragment I get extensive, beautifully-formatted JavaDoc help. Furthermore, at the bottom of the Documentation window there is an option External documentation for Fragment that links to a local file:
file:///home/daz/Android/Sdk/docs/reference/android/app/Fragment.html
Now, moving to androidX ...
import androidx.fragment.app.Fragment;
import androidx.constraintlayout.motion.widget.MotionLayout;
If I hover over Fragment I get an abbreviated help which directs me to the 'framework' documentation. (Less elegant but acceptable)
But if I hover over MotionLayout I get nothing except a reference to
Gradle: androidx.constraintlayout:constraintlayout:2.0.0-beta3#aar
If I go to the declaration I get decompiled source and whenever I try to code a method I have to search the internet for the parameters. All attempts to Choose or Download sources while viewing the decompiled source have failed.
I consider this unacceptable - good documentation exists and I would like to get to it easily!
https://developer.android.com/reference/androidx/constraintlayout/motion/widget/MotionLayout
I appreciate that MotionLayout was a comparatively recent (2018) announcement but it is not an isolated case.
Why is this happening? Why is Android Studio unable to find official Android source code?
Determine if the source .jar was shipped with the .aar:
Example: androidx.fragment.app.Fragment
Assumes External Library: Gradle: androidx.fragment:fragment:1.1.0#aar
EITHER Right-click the external library (from Project view) --> Library Properties ...
OR Navigate to :
.../.gradle/caches/modules-2/files-2.1/androidx.fragment/fragment/1.1.0
Expand the subfolders and confirm something like
b9ebb04df2cb0cad4419af3c658690bc82aa5706/fragment-1.1.0-sources.jar
Example: androidx.constraintlayout.widget.ConstraintLayout
Assumes External Library: Gradle: androidx.constraintlayout:constraintlayout:2.0.0-beta3#aar
By using the above method, you will rapidly determine that no sources.jar exists. (You will only see the .aar and the .pom)
Establishing why not is beyond the scope of this question.
Until some-one provides a more satisfactory answer, you may like to try this grubby hack.
Update 21Nov2019:
If your problem relates to ConstraintLayout or MotionLayout please star this known issue.
I'm busy getting this red-line when trying to use <rich:notifyMessage>. I'm used to primefaces but for this project richfaces is inevitable, hence i'm quite a novice here. I'm using richfaces 3.3.4 final and all required jars are included. What could I be missing? Is there a perfect alternative for a notification message pop-up apart from <rich:message> or <rich:messages>? I'd really appreciate a working example too. Thanks in advance.
This relates to an Xpages project using openNtf's Extension Library for Domino 9.0.1 V 16 (2016-01-28). There is a custom theme applied that extends extLib's Bootstrap3 theme.
Now I also applied Mark Leusink's debugToolbar Plugin (V 4.0.1, 2014-03-10).
Unfortunately all tables that are display inside the toolbar are partially "destroyed", as in this example:
Debugging the resulting html I see that the "label" cells of the debug table are assigned class="label" or class="label wide". Unfortunately bootstrap.css applies a display: inline style to a .label selector.
Currently I solved this by applying my own custom css file to reset toolbar styling; but I wonder whether there might be a more elegant way, maybe some kind of property that I simply missed out here. Or is this something that have to be done within the toolbar's source code?
Please add this as a defect on the project, so the contributor is aware and can resolve.
Alternatively, download the source code from https://github.com/OpenNTF/DebugToolbar, contribute the fix and make a pull request.
Hopefully Paul's and my entries at github and within the openntf.org project will help resolving this issue. Meanwhile my workaround seems to be the only option here;
As I mentioned above I created a custom styleSheet with just one line in it:
div.dBar table.grid td.label{display:table-cell;}
Then I created a cusom control as a container for the debug toolbar so that I could link my custom style sheet as a resource. The debug custom control finally is added to all the xpages where I want to have the toolbar.
Maybe this can help others, too.
Does YUI (3.7)'s DataTable support pagination? It's mentioned in the API docs - but only in the code example. When I try to find any in-depth documentation, I couldn't see anything.
http://yuilibrary.com/yui/docs/api/classes/DataTable.html
But this suggests that it might not be supported yet (although I understand it's referring to a slightly older version)
http://yuilibrary.com/forum/viewtopic.php?p=32211
Thanks
There are a bunch of paginator modules in the gallery, most of which work with YUI DataTable, but there is no official Y.Paginator in YUI yet.
There's a gallery module for datatable pagination: http://yuilibrary.com/gallery/show/datatable-paginator
Also you can use AlloyUI Pagination with DataTable: https://gist.github.com/zenorocha/5032360
Y.Paginator now exists. But it is very low-level and contains no UI components. see.
There's also a very un-documented Datatable.Paginator class. Which I can't figure out at all. Link.
I had a look around on SO to see if someone has asked this question before or not, but couldn't find any posts. My apologizes, if this is a duplicate question.
In Orchard 1.3, there is a module for HTML field that one can use...but there is nothing in Orchard 1.4. How do I go about creating a content type with multiple HTML fields? ( Just adding it in UI and not coding).
Thanks
It's the opposite. There wasn't one out of the box in 1.3, and you had to download one from the gallery, whereas it's built-in 1.4.