I have a document type which has multiple presentations. Say I want to display the document in an RCP editor with a customizable subset of those presentations, in a layout chosen by the user.
One option that has come up is docking-like behavior for the panels inside an individual editor, with drag-and-drop, resizing, closing, maybe rollover and floating.
Clearly this would need usability testing, but my question here is of feasibility.
Are there any existing libraries or e4 plans to support behavior like this?
In the eclipse magazine 03-2010 is an article about that stuff from lars vogel and others. you can find it using Google with 'Lars Vogel "widget explorer"'. it is written in German.
you can also download the widget explorer. the article says that the widget explorer is only a simple example (it supports moving with dnd, color chosing, minimize and edit). with the wazaabi project or e4 could be done much more.
Related
I haven't worked with dnn very much and for those who also haven't it's basically another CMS tool. I'm working on a mega menu but I am being told that I can't do something because dnn doesn't allow it. I coded a menu idea by myself (html, css, etc.) but have been told this isn't possible or it's never been done so we're not doing it. While I don't have a website example for this kind of menu being used, I know somewhere out there this menu have been used before. My question is have you ever seen this kind of menu used and is dnn really that limiting?
(The idea is that when you hover over an item on the left the information on the right changes)
This is possible with a highly customized DDR menu template.
But a good third-party theme to look at which has a custom menu implementation for DNN is Mandeep's Porto skin. Click on the link to the demonstration site and hover over the Features menu item. This is very similar to you want.
You can get tutorials on Youtube and on Mandeep's website.
I'd like to add extra visual elements inside the Java text editor of Eclipse, more specifically on top of classes and methods declarations. Things like indicators and links.
The best example is what Microsoft has done in Visual Studio with what they call CodeLens:
The closest solution I can think of is using Annotations (displayed in the rulers) but it's far from the user experience I want to have.
Are there any Eclipse plugins that have done this before?
Any pointers to give me somewhere to start?
Annotations are typically shown in the vertical and overview rulers (left and right), but they're not limited to them. Take a closer look at the documentation you linked to, particularly the mentions of AnnotationPainter, and then how it uses drawing strategies. I expect you'd need a rather complicated one, and I haven't even thought through how you'd generate the information in the first place, never mind adding it directly to the Annotation Model if you're not just going to stash it in a Marker on disk.
Of course, some of this looks like information you can already find through Team->Show Annotations (although that does use the ruler to let you find them by line).
Disclaimer, I'm the author of CodeLens Eclipse.
Eclipse doesn't provide Codelens feature, but it exists CodeLens Eclipse.
This project provides a CodeLens extension point to implement your own CodeLens. Today TypeScript, Java JDT CodeLens and lsp4e CodeLens are available. Here a little demo with Java JDT Editor:
I am new to eclipse scout. My question is how do i customise the default application look and feel for an eclipse scout application. I want to be able to change the button colors and replace the default icons with my own. I was able to change some of the colors using the application.css file but i did not archieve much. Also, is there a way of getting the ids, or class names for the various components in the resulting web pages so that i can be more granular in styling them.
Thanks in advance.
How you can style an Eclipse Scout application depends on which front-end you use: RAP, Swing or SWT.
Swing
You can use the Scout Swing Spy to determine the class name of a component in your UI when you have it selected.
If you use the Rayo look and feel, you can use implement the interface ILookAndFeelConfigurator and register it for the extension point org.eclipse.scout.rt.ui.swing.lafconfigurator to change the theming by providing a custom XML. The Rayo concept wiki article explains this in more details.
If you do not use the Rayo LaF...
RAP
The default RAP theme is modelled after the Rayo theme mentioned above.
Changing it involves creating your own theme bundle and create the appropriate CSS file there. Given that it is a RAP theme, you'll have to refer to the RAP RWT Theming guide. See the Scout forum thread "Scout Web App + CSS".
For reference, this is the Rayo CSS file of the Eclipse Scout 5.0 in the eclipse scout git repository (org.eclipse.scout.rt.ui.rap.theme.rayo)
SWT
Given that the SWT UI is designed to be portable and uses the widgets provided by the operating system, the amount of customization is more limited.
You can use the extension point org.eclipse.scout.rt.ui.swt.lookAndFeel to adjust some values of the look and feel (see schema file). See also the Scout thread "Modifying SWT look and feel for disabled elements"
you can make your own button and you own icon by use photoshop first bro
then copy the file into res/drawable of your application project
I'm trying to create several JSPs, and I was told that what most people do, is open notepad and hardcode the whole thing in. I come from the origins of C#, so that option is somewhat foreign to me :)
I did try to do several complex components by hand in Java. It took quite a bit of time (mostly with arrangements) but I was able to do it.
My question is, will I be able to create JSPs inside of Eclipse and will all the UI components that I will implement be there as I positioned them?
I'm asking because I found an Eclipse plugin (http://code.google.com/javadevtools/download-wbpro.html) that allows me to drag and drop components (C# style :D) and I needed to know if it is worth downloading, because if I still have to hardcode the JSP's UI in, the download time will be a waste (slow speed here).
Create a jsp page and right click on the editor and go to open with.
Select Web Page Editor and you will have the design view opened.
On the top right corner you will have an arrow. Click on the arrow and you will have elements to drag and drop on the editor.
I think almost nobody uses notepad to create JSP's. The editing is done in text mode in IDE's or comparable tools.
I agree with #BalusC, JSP's don't have good support for drag and drop development (like Visual Studio), although there tools like Dreamweaver which had some support to create the HTML structure in a WYSYWYG environment. I would not recommend these kind of tools for JSP but it's your choice.
The plugin you mention is not for JSP's and any of the alternatives it does support won't be quick to learn.
As #BalusCmentions, JSF's is an alternative for which there are some visual editors. You might want to look into that but you'd need to do some research as JSF is an standard and there are several implementations and related tools around. There are plugins for JSF support in Eclipse.
All in all I think you need to read further on Java web development and the alternatives that exist.
I'm developing an Eclipse RCP based application, that uses the resource model of eclipse (workspace, projects, resources, etc.). For basic usage of the resource concept, there is no need to depend on the IDE plug-in. But many dialogs, wizards or views I want to use are inside this plug-in. I read about not to have any dependencies on IDE plug-ins in an RCP app.
For example, I want to implement a new project wizard and use the common look and functionality of the existing ones by overriding org.eclipse.ui.dialogs.WizardNewProjectCreationPage and using org.eclipse.ui.wizards.newresource.BasicNewProjectResourceWizard - both inside the IDE plug-in.
Are there any caveats using org.eclipse.ui.ide plug-in in an RCP app?
If so, what is your best practice to not reinvent the wheel?
As you can see with this thread (or that one), since eclipse3.3, most the the components of org.eclipse.ui.ide have been isolated in their own plugin.
So it can be a good practice to include what you need from that package, the only problem being to include to much contributions.
This thread gives a hint as how to remove some of them.
You can, for example, disable export and import wizards.
Both of those examples are based on Activity filtering
An activity is a logical grouping of function that is centered around a certain kind of task.
For example, developing Java software is an activity commonly performed by users of the platform, and the JDT defines many UI contributions (views, editors, perspectives, preferences, etc.) that are only useful when performing this activity.
Activities can be used to implement progressive disclosure of UI elements; when used for this purpose, they are called capabilities in the UI.
The second use for activities, added for Eclipse 3.4, is to filter available UI elements based on other criteria such as the current user's access permissions as defined by the application.
This article "Eclipse Activities – Hide / Display certain UI elements" by Lars Vogel in his "papercut series" gives a good illustration of hiding / displaying certain UI elements.