Could someone tell me what is the maximum # of properties for an Object or Class in U2 Web Designer? I can't seem to find that in the documentation.
Related
I am still new to Papyrus, but have been following along with some tutorials.
I am working on a C++ class model and was trying to add some stereotypes to some class properties. But when I go to the class Profile, Apply Stereotypes option, or even the class property Apply Stereotype option, the list of available stereotypes is always empty. I added the AnsiClibrary and the STD packages already, so those data types and such are there. But for some reason my list of available stereotypes is always empty.
I there something I am missing in getting the stereotype list to populate?
I included a picture.
It seems, from your image, that you do not have the C_Cpp profile applied.
Did you instal the Designer-CPP (Incubation) additional component? That's the component that provides the CPP stereotypes.
Once you have that component installed, you will be able to add the "C/C++ profile" (a.k.a, "C_Cpp") to your model (by using the [+] button in the Profile tab of the Properties view for the model) and then apply the stereotypes it provides to your model elements. At that point, the stereotypes should be visible. If not, you can use the "Appearance" tab of the properties view for the element to make the stereotype visible.
I had the same problem as of December 2019 and found a solution. For those who are having the same problem, might find a solution like this:
Copy latest Papyrus link, by visiting here.
Open Eclipse. Help->Install New Software, paste your link here and install Papyrus.
Copy this link directly.
Go to Help->Install New Software, paste your link here.
Make sure you check Papyrus C++ profile, ... as in the image. (I am not sure if the other checks are required.)
At the end of the installation you should have both Papyrus and its C++ available for code generation out of UML.
References:
https://wiki.eclipse.org/Java_Code_Generation
The project I'm working on is a new Sitecore 8 site build using MVC and with a demand for page-editor support. The simple fields are being addressed with the FieldRenderer.render() method, but there are also some droplink and multilist fields that need to be available in page editor.
In webforms you could use the sc:editframe control for that, but how can I get the same functionality while using Sitecore MVC?
Just an FYI in Sitecore 8.2 there is support for edit frames:
#using Sitecore.Mvc.Extensions
Then
#using(Html.EditFrame(...)) {...}
If not already, I highly recommend using GlassMapper to map your Sitecoce object to strongly typed objects in your code.
With Glass, you can then use the BeginEditFrame concept to replace the sc:EditFrame functionality of WebForms.
To take it a step further, look to implement edit frame buttons (this link is not Sitecore 8 specific, but the method to implement edit frame buttons is the same) in the core database to allow a very-friendly Experience Editor experience.
I am trying to implement a faceted navigation search using Sitecore 7.5, Solr and Glass Mapper. Currently I am using code generation using TDS and Glass to auto-generate classes for every data template in my project. I have read tutorial 25 on the Glass Mapper site but I am very confused. The Glass tutorial seems to suggest that I need to create a completely new class to represent a search result. Let's say that I have a data template called Product. If I am building a Product Search page, ideally I would like to be able to have my search code return back a list of Product objects.
Is there any way of doing that? Or do I have to create a separate class that inherits from SearchResultItem? Seems strange that I can't use my auto-generated data classes for my search results.
You can either edit the T4 GlassV3Header.tt template to make the GlassBase inherits from SearchResultItem. Or you can follow the "Using custom result class" section in tutorial #25 to use the generated classes directly with the search.
Check out this link for more details:
https://stackoverflow.com/questions/28429752/sitecore-glass-mapper-tds-code-generation-and-searchresultitem
I am using DataGrid for displaying table. One of the columns in Datagrid consists of XamFormulaEditor. Also, there are some custom variables that are assigned to XamCalculationManager's Named references so that they are visible to user when he types formula in XamFormulaEditor. I have couple of problems with ContextualHelp:
For Eg. if the custom variable name is "a", then in ContextualHelp list it looks like [//a]. Isnt't there any settings to make it look like [a] ?
Is there any way to filter the contextual help to not display standard functions and only display variables that we want ?
After looking into this and doing some research, ContextualHelp on Infragistics XamFormulaEditor for custom variables has been determined to be a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at Infragistics new site for features:
http://ideas.infragistics.com.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
I'm developing an application which displays items on a QGraphicsScene. These
items have properties, which I would like to display in a tree-view, if the
item is selected. If possible, I would like to stick with the property system
implemented by QObject. However, this does not fit all my needs because I need
to store some meta-data along the properties, e.g.
a category used for grouping (e.g. "System properties" and "User properties")
a tooltip text which is shown when the mouse hovers over the property in
the tree-view.
Inspired by Qt Property Browser and by Qt's object framework, I have thought to
implement the following system:
All items in the scene are derived from PropertyItem (which itself inherits
QGraphicsItem or QGraphicsObject). It contains
the logic to get and set the value of a property.
Every class derived from PropertyItem has a static MetaPropertyItem.
A MetaPropertyItem holds instances of the class MetaProperty in order
to store meta-data about the properties of such as the category, the
tooltip string and the type of the property.
Whenever an item is selected in the scene, instances of the Property class
are created for every MetaProperty from the associated MetaPropertyItem.
These properties are then shown in the tree-view and deleted when the item
is deselected.
The more I think about this design, the more I get the feeling that I'm doing
something wrong. It seems that I'm just duplicating what is already part of Qt:
PropertyItem <--> QObject
MetaPropertyItem <--> QMetaObject
MetaProperty <--> QMetaProperty
Property <--> needs to be implemented
I also found this bug ticket, which proposes to add meta-data to a Qt property.
Unfortunately, it did not get any attention so far.
Looking for alternatives, I also stumbled upon QMetaPropertyBuilder which
will (probably?) be part of Qt 5. Unfortunately, documentation about this class is sparse
and what I understood from reading the sources it would not solve my problem.
Thus, my question: Is there actually a better way to achieve what I'm
looking for without re-implementing another Qt framework?