How can we switch from classic UI to Touch UI in AEM 6.2. I see documentation to switch from touch ui to classic but not other way round.
Site Wide
In system console (http://localhost:4502/system/console/configMgr) there is an OSGi configuration for WCM Authoring UI Mode Service. You can change the property of Default authoring UI mode to TOUCH.
Per User
Login as the user, navigate to Projects (http://localhost:4502/projects.html/content/projects), select the user icon in the top right hand corner, select the settings icon, ensure that Authoring Mode has Touch-Optimized selected.
Other Items
You should also ensure the OSGi config for Day CQ Root Mapping has the property Target Path set to /projects.html
Here is a short cut to switch between the two UI modes:
Open any page from Site Admin by default it will load in Touch UI Mode. The URL will be say http://localhost:4502/cf#/content/test.html. Now to switch to classic UI you would write http://localhost:4502/editor.html/content/test.html. Replace 'cf#' in the URL with 'editor.html'.
Three methods to do so are:-
[User Level]
[Global Level]Go to:-http://localhost:4502/system/console/configMgr
and choose WCM Authoring UI Mode Service
using cf# or editor.html
If your site is :- http://localhost:4502/content/geometrixx-outdoors/en.html
then
Classic UI :- http://localhost:4502/cf#/content/geometrixx-outdoors/en.html
Touch UI :- http://localhost:4502/editor.html/content/geometrixx-outdoors/en.html
Reference Adobe AEM Community posts:-
Link:-http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__isbp-hi_i_want_toope.html
Link:-http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__7rmk-i_was_askedtoconfi.html
I hope this will help you.
Thanks and Regards
Kautuk Sahni
Unfortunately, Classic UI has been more or less abandoned since 6.1 and won't likely be updated anymore as Adobe is trying to move away from ExtJS.
That said what you could do is add a custom button to the sidekick that would navigate to the TouchUI, which would involves adding the editor.html at the root of the URL of the page (and removing the #cf if it's there)
You can follow this link that gives an example on how to add a new function to the Classic UI sidekick.
https://helpx.adobe.com/experience-manager/using/creating-touchui-component1.html
Nate Yolles has produced a Chrome Extension that allows switching between modes amongst other things
https://chrome.google.com/webstore/detail/aem-developer/hgjhcngmldfpgpakbnffnbnmcmohfmfc?utm_source=chrome-app-launcher-info-dialog
Related
I'd like to be able to add an option to the download dialog that pops-up in Firefox when starting a file download. Is it possible to do so using the new add-on SDK or do I have to do it the old way?
edit: Obviously, if the new option is selected, I need a way to know it and execute code based on it.
That's something you would use XUL overlays for. I guess that the dialog you are talking about is chrome://mozapps/content/downloads/downloads.xul - the download manager. AFAIK doing this isn't possible with the Add-on SDK, it only provides the most common UI integration points. You could create a traditional extension however, it can overlay any dialog.
There is no existing module that will help you that I know of, so you would have to create one, or wait for one to be made by someone else. But the main idea to extending browser UI is simple, and goes like this:
When the addon is loaded, scan for open windows of the type that you wish to extend.
extend the open windows by adding xul elements and javascript to the page.
listen for newly opened windows, and test that they are the type that you are looking for once they open
extend newly opened windows while your addon is active
Clean up after yourself when windows close or when your addon is disabled/uninstalled.
The last step is the most important and never matter with old school extensions which were not restartless.
Some for the built-in modules that you can look at that do this are the widget module, the context menu module, and the hotkeys module, all of which you can find here.
I've made a couple myself which are the toolbar button module, the xulkeys module, the menuitems module, and a few others, all of which you can find here.
Recently I wrote an extension do the same things. A bootstrap extension, not using addon-sdk.
I already submit it on AMO, but wait for review
https://addons.mozilla.org/en-US/firefox/addon/download-dialog-tweak/
And the source code
https://github.com/muzuiget/download_dialog_tweak
First of all, when to use what and the overall differences between them has already been answered before. But I couldn't find an answer to this question:
Where can I check if my Visual Studio project is a Web Application or a Web Site?
The easiest way to differentiate between Web Site and Web Application is to look at the project's icons.
Web Site
has an icon without the used language
displays its physical root path
does not have a Properties folder
Web Application
has an icon including the used language
displays the project's name
has a Properties folder
To find out more about the technical differences between them ...
ASP.NET Web Site or ASP.NET Web Application?
Personally, one tell tale sign for me is whether the project folder actually contains a project file, or not.
You can see the icons differ slightly in VS - a web application has a layered world->docs->language icon and a web site just consists of world->docs.
Also, once opened within VS, right-clicking will display Properties and Property Pages for web applications and web sites respectively; further, on clicking this option you will be greeted with a dialog for the former and MDI tabbed form for the latter - the latter also exposes more functionality to control pre and post build steps and so forth.
A a web application will also display Properties and References special folders as part of the project tree in the Solution Explorer, whereas a web site does not necessarily; unless manually created for some reason (but they still won't be special - web sites use the bin folder for their references).
I recently found out (painfully) that web applications do not support Profiles which is not fun. Web sites however do support them and make life much easier. I noticed here people saying there are no major differences. This one is quite major and can make your life difficult if you select to make a web application instead of a web site.
Web application and Web Site are VS templates, nothing more. I doubt you will find this information directly somewhere in project. You can try to go through template differences list and guess how this particular project was created.
For Web Site project, once run (F5) you can change the code in the code-behind, the solution will allow it and it will compile on the fly when saved.
A Web Application project, however, will not allow this. This is the simplest way of being able to tell between the two.
I am looking at ASP.NET membership controls (2008) and have been dropping them onto web pages to see how it all works. In some ASP.NET starter kit web site examples that I downloaded, I notice that between the asp:control tags I can see all the tags of the constituent parts like the textboxes, labels and buttons etc. However with the membership control that I am using in 2008 I do not see these other tags. Is this because the starter kit examples are from an older version or is it possible to expose these inner tags? It seems that this would make it possible to customize the controls. Thanks
pbmoss#hotmail.com
Let's say if you have added a login control to your project's page, if you click on the smart-tag at top right corner of the control, you will find an option convert to template that will allow you to see the same things that you can see in the starter kit project
i hope this helps
regards
I want to display a "folderview" which I can drag and drop files into but via WebForm. I am doing this via a webbrowser control pointing at local drive. The code works in a win form user control but what I want is to embed this control in web form. This is an intranet so security etc is less of an issue. However when I add things like AllowDrop or the webbrowser control to my control it stops working - I get the image placeholder which I take to mean an error. Can anyone give me an idea what is wrong or perhaps suggest a different solution.
Hi I figured it out when you deploy a new version of your user control you need to clear the GAC download cache - gacutil /clc but I think versioning your dll may work. I don't think web browser control work at all but I may be wrong. I've managed to drag and drop msg files with Outlook Automation see http://bytes.com/groups/net-vb/527320-drag-drop-outlook-vb-net-richtextbox
I've looked around, and not found much documentation on this, so I thought I'd ask where all the experts hang out.
I would like to create a new start page, with bug tracking and source control interfaces, rather than the standard MSDN feed. I seem to remember that one can do more than just supply a different URL, but can actually implement a component to run as the start page, which needn't use web content. I may be wrong. Can anyone please give me some tips?
You can do is to create a DTE ToolWindow (read: Creating a ToolWindow hosting a .NET user control) and host your controls there, then its pretty easy to create an addin that will show the tool window as a document at runtime. (The same way that the start-up page looks)
Go to Tools > Options > Environment > Startup and put your RSS URL in the Start Page news channel field.
That should give you enough, but if you want to do more you can select open home page in the at startup dropdown and point it at a URL with the appropriate content. If you use an intranet with Windows authentication you could display user specific stuff.
This will be completely customizable in VS 2010. You'll be able to do anything you want to on the start page.