I'm using Pentaho DI ETL from a few weeks ago, and as in Talend DI ETL, there is the possibility to use a component "Note".
This is quite useful to distinguish the main features of a job, and bring more informations at the first overview when opening it.
MY PROBLEM :
When using a note on the canvas, right-clicking on the component opens a context menu. My problem is that I am unable to use the "Raise" and "Lower" options. May someone has an idea about how those options work ?
Screen of the context menu
Thanks in advance,
Kapusch
REFERENCES :
PDI Documentation link
The feature enables to raise a Note over an another Note. Here is an example :
Hence, it is not possible to cover other components with a Note.
Related
We are working on a React application (using Create React App without ejecting it) and we decided to use Ant as our base component library.
Now that we are near the end of the project, we discover that the application will be integrated into a corporate portal (WebSphere) as a "portlet", so we inherit all the CSS files from the main page.
Both frameworks seem to have their own reset styles, but they use different values.
So far, I have not been able to find a LESS variable in Ant that can be used for prefix all Ant's CSS rules.
Has anyone ever tried to make them live together?
We don't own the parent development, we can only make change on the React part, so only things related to Ant.
We finally go with a specific CSS patch file, and we add rules when needed.
Not really perfect, but none of the suggested path did the job we expected.
Here you can see some of the default antd variables.
One of them is #ant-prefix: ant;. I think you can change it and apply different styles.
That is a tough one, and at the end of development no less!
As #froston mentions, and which you seem to have tried the #ant-prefix: ant; in addition to this you will need to se prefixCls as a prop on every component instance you create, which will definitely be an exercise in self-flagellation.
Even if you set a global CONSTANT and import and use this with your components, you still have to thread it through to all the places, and will need to be appended with the component name.
By way of example, the defaultProps for an anchor is prefixCls: 'ant-anchor'.
Hope this helps and good luck!
Suppose I have two perspective. In which my application has two different org.eclipse.ui.editors as following.
Perpsective1
Editor1
Perspective2
Editor2
When I switch from Perspective1 to Perspective2 My application should hide all the Editor1 opened instances should get invisible and only Editor2 type should be visible and vice versa.
How can I achieve this?
Open editors are not normally affected by perspective changes so you would have to code this yourself.
You can use an IPerspectiveListener (or the extended IPerspectiveListener4) to be notified about perspective changes.
The perspective listener is added using IWorkbenchWindow.addPerspectiveListener
So i have a titanium app, and i just read about single contexts. (Incidentally, somebody here should write a book about programming in titanium... the only one out there doesn't really mention single contexts or any of that new-fangled stuff. Heck, make it an eBook. I'd buy it)
The titanium documentation stresses their use (http://docs.appcelerator.com/titanium/latest/#!/guide/Coding_Strategies-section-29004891_CodingStrategies-Executioncontexts) and then politely forgets how to implement a single context!!
So, question:
Let's say i have the awesomeWidget page - this just shows a button, and when you click on a button a new screen appears.
The aswesomeWidget page is accessed through another page - it is not from the root of the titanium app.
Keeping to single contexts, how do i add the view that the button creates to the current window?
Do I:
keep a global pointer to the current (and only) window?
pass the variable holding the current window down to all the following pages that use it
something else?
First off, Titanium keeps a reference to your current window anyway for you, so this use case is easy. For example:
awesomeWidgetButton.addEventListener('click' function(e) {
var yourView = Ti.UI.createView({...});
Titanium.UI.currentWindow.add(yourView);
});
If you want to dig further, the concept of a single context is closely tied to the use of CommonJS modules and the require keyword. It is very simple to keep a single context, just never open a window with the url component filled out, and liberally use the require() keyword. Other than that, its up to your imagination to keep track of who points to what and vice versa, there are standard patterns and best practices that apply here (MVC, Singletons, just keep it simple) just as in coding in any other language.
I have been googling this subject for hours. Does anyone have an examples of a custom plugin being deployed in Dijit's Editor. I'd be really interested to look at it because I have been following this without much success and of the few examples that exist out there none of them come with working examples :(
(I'm looking to create a pulldown menu like the one for font selection)
There's no difference between a custom plugin and a "builtin" plugin, so I suggest just looking at a small builtin example like TabIndent, and then move on to the font selection itself.
I created a sample plugin which needs to hide the java perspective. For that I used activities. The problems what happends is,it is hiding from the perspectives,but it is there still in the (recent opened perspectives). How can I hide it from there also? Following is my code.
<extension
point="org.eclipse.ui.activities">
<activity
id="com.example.activities.hideperspective"
name="Hide Perspective">
</activity>
<activityPatternBinding
activityId="com.example.activities.hideperspective"
isEqualityPattern="false"
pattern="com.example.activities.hideperspective/org.eclipse.jdt.ui.JavaPerspective">
</activityPatternBinding>
Is this the right way what I have implemented? One more thing, This hiding of perspective I am calling when I click a Button on the toolbar. That the that buttons location is also getting changed. some kind of refresh on the toolbar.
I have attached the screenshot as well.
The activityPatternBinding is plugin.id/perspective.id, where the plugin.id is the ID of the plugin that contributed the perspective, not com.example.activities.hideperspective. Also, it does look like an equality pattern.
Also, activities will show something (like a perspective) if any activity that points to that perspective is enabled. So setting one activity to enabled=false might not get rid of the perspective.
And finally, activities won't shut a perspective that is already open. It just removes it from the "Open Perspective" dialog/shortcuts.