Within the console on a feed layout, we can add tools to the page such as the inline article tool. The feed view setting options with the page layout edit suggest (i.e. help text says "select the tools to make available in the center column of the page") that more than one tool can be created using code and added to the page layout (i.e. within the feed directly below the publisher actions but above the feed items). There is even a multi-select control to move the tools from available to selected, but...
I cannot find any documentation that discusses how to create the tools or how to make them available within the setup menu. Can you provide any insight to if this is possible and if so how to do it?
See example screens below...
thanks
jf
Please chk it - https://resources.docs.salesforce.com/200/10/en-us/sfdc/pdf/salesforce_case_interaction_setup_cheatsheet.pdf
Hope it helps.
Related
I am starting on a new project in WPF with MVVM. As per the Microsoft recommendations, it is advisable to use PRISM for various reasons.
Project requirements:
Dynamic menu with menubar based on roles assigned to user (fetched from database)
Toolbar for commonly used menu items and functionalities (again role based)
Status bar to display general broadcast messages and other information.
Single middle view to load screens as menu items are clicked.
Can someone guide me to a working sample (mainly dynamic menu and multiple views loading in the main region) in this regard.
If you're starting a new project, you might as well consider the latest version of Prism (v6). You can find the official samples for this version on GitHub, together with extensive documentation on how to use Prism with WPF. I suggest you go through these first.
As for the role based menu items, that's something too specific to find any samples on, but it basically comes down to correctly apply authorization and the necessary filtering of your menu items.
In the sencha documentation page, when I click a class, a class tap appears, and there will be a toobar up there usually features two buttons (are they buttons) "properties" and "methods". When the mouse is on these two buttons, a overall properties/methods list will appear.
It seems that list is dynamically generated. Can anyone please help. I'd like to do a similar page on my site, but I don't know how to do this.
Sencha uses JSDuck (https://github.com/senchalabs/jsduck) to generate the documentation. There are instructions in the repo regarding how to add your own classes to it, and it's pretty easy to do. Additionally, you should be able to see the source for how they are handling the menus/dropdowns.
I have been searching for the past 6 hours and I still couldnt figure out yet on how to create licenses that can be used for image uploads in Mediawiki. This is what I understand so far:
1) Add the list of licenses into the Mediawiki:Licenses page. (for this I copied the licenses used in Mediawiki site)
2) Next I then need to create the templates for each licenses. To do that, follow the red template links that appear below the license selection drop down menu on special:upload when you select a license from it and put info boxes in each of those respective template pages.
Step 2 is where I am having trouble with. For example, I copied the Licenses used in MediaWiki site. When I tried to add the Template:PD for public domain images, I copied the template from Mediawiki.org/Template:PD to my site. When I do that,this template is dependent on 3 or 4 other templates that needs to be created, like Mbox template, etc..etc... When I create those, those templates are dependant on even more templates that are yet to be created. Like this its a big massive tree of templates that needs to be created. For the past hour, I have been going through each red links trying to create those template one by one (basically copying it from Mediawiki site) and it seems to be an never ending task. So far I've created these templates:
Template:Mbox
Template:Namespace_detect
Template:Documentation
Template:Template_sandbox_notice
Template:Documentation/start_box2
Template:Documentation/start box
Template:Documentation/docspace
Template:Documentation/template page
Template:Documentation/end_box2
Template:Ombox
Template:Documentation/end box
Template:Fmbox
etc..etc..
Its not even half way by the looks of it. Now this is what I dont know:
1) Am I on the right track? Is this how I do it or am I doing it wrong?
2) How many templates needs to be created like this? Seems like 100s to me...
3) Is there a simpler way to do this?
4) How do I create the license lists for image uploads so the user can choose it from the list? I want a simpler one than what is used in Wikipedia.
Any guidance please.... This license list seems to be more harder than installing the Mediawiki itself!! I just dont understand why some default listings are already provided with the install. Please help...
I was finally able to complete creating the licenses for my site. The method I was doing before was stupid and completely wrong. Thanks to Mir for pointing me out in the right direction. Here is the steps on how I ended up creating licenses for my Mediawiki.
HOW TO CREATE LICENSES: - Tutorial
In order to create licenses you need to do the following steps:
1) First figure out what licenses you want to list in your wiki. Its best to look at some samples to get an idea. Here are a few samples you can have a look at:
Licenses Samples:
MediaWiki Licenses: https://www.mediawiki.org/wiki/MediaWiki:Licenses
Wikipedia Licenses: http://en.wikipedia.org/wiki/MediaWiki:Licenses
https://en.bitcoin.it/wiki/MediaWiki:Licenses
http://qed.princeton.edu/main/MediaWiki:Licenses
2) Next step is to create the list of licenses in Mediawiki:Licenses page. The format used for this is like this: "template name|descriptive label." Once you add the list, the Drop-down list is displayed on Special:Upload.
3) Once you create the license list, when you view it in the Special:upload page by selecting that license, you will see a red link to that template. follow the red template links that appear below the license selection drop down menu on special:upload when you select a license from it and put info boxes in each of those respective template pages. Eg, if one of your license choices is "* Unknown | I don't know" then you want something informative in [[template:unknown]], see template:unknown.
4) Create a template for that license. Here you can have a look at some of the license templates used in wikipedia or other sites and create your own template like that. You can add div tag to add border styles, background colours, padding, etc.. the way you want it. You can also add images for the common licenses like Creative Commons, Public domain, etc.. and most of these images are usually available in default Mediawiki install itself.
5) Once the templates are created, those license templates will be loaded when the license is selected in the Special:Upload page.
Thats it!
In the future when you create new license templates, its better to copy an existing template, look at wikipedia for the sample and just change the license text and image for that new license you are about to add. Its that easy. In the end remeber to add that new license to the Mediawiki:Licenses page.
Hope this makes sense to other newbies like me... :)
There is a category on MediaWiki.org called License templates containing 30 or so templates. You can use the Special:Export page on MediaWiki.org to export this entire category into an XML file. Be sure to tick the box that says "Include templates".
Then, on your wiki, use the Special:Import page (as admin user) to import these templates into your wiki.
More info at https://freephile.org/wiki/Licensing#Licensing_of_Wiki_content
Just want to expand on Neel's answer above.
When you add your list of licenses to the MediaWiki:Licenses page, it's important to include the Bullet List markup.
* Your own work
** cc-by-sa-4.0|Own work, Creative Commons Attribution-Share Alike 4.0
** cc-by-sa-4.0,3.0,2.5,2.0,1.0|Own work, multi-license with CC-BY-SA-4.0 and older
If you do not include the asterisks at the beginning of the line, they will not appear as options in the Licensing drop-down on the Upload page.
More detail in MediaWiki's wiki.
Also, another good source for information on licenses is the Creative Commons site.
We are adding help files to our WPF application in Visual Studio 2010. We have not been able to find so far a method that we have been able to use.
We have some HTML help files, currently they are just in a directory, not added to the WPF project.
We don't have index or search.
I have seen that maybe we can do something with cmh, but this seems quite old and outdated now.
Ideally we would like all this in WPF, but if its not possible we need another solution.
We would like to be able to hit F1, have our main help page displayed (we have this now, it opens in our browser) and additionally add Index and Search to our main help page.
Can anyone point us in the right direction please?
Maybe you should take a look at the Process.Start Method page on MSDN. In particular, the Process.Start Method (String) page has a code example showing how to open web pages from a WPF application.
To do this inside a WPF application, look at the WebBrowser Class page at MSDN. This also provides a code example of loading a web page into your application.
EDIT >>> After re-reading your post, I realise that I missed the bit about searching and indexing. Surely, you can just search through the web pages yourself? Just open each page and use something like
if (webPageContent.Contains(searchTerm)) return webPageContent;
I've searched around for a while today, but I haven't been able to come up with an AutoComplete TextBox code sample for Silverlight 2 Beta 2. The most promising reference was found on nikhilk.net but the online demo doesn't currently render and after downloading a getting the code to compile with Beta 2, I couldn't get the Silverlight plugin it to render either. I think it is fair to say it is a compatibility issue, but I'm not sure. Does anyone have any alternate sample code or implementation suggestions?
You may want to take a look at my blog: http://weblogs.manas.com.ar/ary/2008/09/26/autocomplete-in-silverlight/
You simply write in your XAML:
manas:Autocomplete.Suggest="DoSuggest"
and then in the class file, you need to implement that method, which report suggestions to a delegate. The options can be hardcoded, requested to a web service, or whaterver.
Take a look at the combobox(very close to a autocomplete text box) at worksight's blog Silverlight ComboBox
There is also another good example here:
http://silvermail.com.au
This is a Silverlight based mail client that looks a little like Outlook. When I go to send mail and start typing in the "To" text box, an auto-complete pops up and populates the control for me based on values in a list... I think it automatically stores the addresses in isolated storage, but that's just a guess.
This is a really handy tool for checking mail while away from my home PC... at work for example... and it is loaded with impressive Silverlight functionality.
S.