I am looking for a CalendarView control in JavaFX 8. Is there any built-in control like that or to use the popup calendar from DatePicker control.
My idea is to display a calendar for the user to choose a date from.
I've implemented some controls using the new Data and Time API.
The library is Open Source.
You can read more about it here:
http://puces-blog.blogspot.ch/2013/12/drombler-commons-date-and-time-controls.html
http://puces-blog.blogspot.ch/2013/04/drombler-commons-javafx-controls-for.html
The library is available from Maven Central (requires Java SE 8):
<dependency>
<groupId>org.drombler.commons</groupId>
<artifactId>drombler-commons-fx-time</artifactId>
<version>0.2</version>
</dependency>
If you find some bugs or have some enhancement requests, you can file them here: http://issues.drombler.org/
Related
I have been trying to find an answer since a week now. I have compiled and copied the DAL plugin to /Library/CoreMediaIO/Plug-Ins/DAL but simply cannot find a way I can send the buffer to the plugin from an application that will let user selct an image that can be sent to plugin.(swift or C++). this is the plugin I am using https://github.com/seanchas116/SimpleDALPlugin
I have tried to call the Plugin methods from a swift application. But so far unable to call the PluginInterface API.
I have asked questions to every DAL Plugin repository but no answer so far.
I am trying to obtain information about the system configuration in RCP 4 application. I got a link RCP3 System Configuration which implemented in RCP3 for getting the system configuration. WorkbenchMessages properties and WorkbenchPlugin are used to get the system configuration in RCP3 application but in RCP4 those are not available. How can I implement to get the system configuration?
The ConfigurationInfo class you reference is using the org.eclipse.ui.systemSummarySection extension point and calling the ISystemSummarySection interfaces it defines to get the system summary.
This extension point and the ISystemSummarySection interface do not exist in a plain e4 app so this information is not available using this code.
You may be able to get some of the information by looking at the individual classes that implement ISystemSummarySection and copying the code for those parts that don't use 3.x compatibility mode classes.
For example the ConfigurationLogDefaultSection class just uses System.getProperties() to list the system properties section.
In AEM 6.3,The JSONArray API is deprecated ,so what is the alternative in place of JSONArray API?
Due to license issues these classes were removed with Sling 9. It simply was the json.org library. Sling itself used it for a few things only, so Sling was refactored to get along without it.
I afraid, there is no replacement. You have to choose a different JSON library, include it into your project and port your code. As the JSON lib is pretty straight forward, it should be doable.
Here some links with the mailing lists:
https://lists.apache.org/thread.html/ee51bace078681765d5dcfeda1939628ccefb9b4261b1d7f6a56d420#%3Cdev.sling.apache.org%3E
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201611.mbox/browser
https://issues.apache.org/jira/browse/SLING-6536
Here is the license in question. It contains the ambiguous sentence "The Software shall be used for Good, not Evil."
https://github.com/stleary/JSON-java/blob/master/LICENSE
The best way forward is to change your Json API from org.apache.sling.commons.json to com.google.gson. Since it is already being used in AEM elsewhere.
You can use any json API depending upon your requirement. I will suggest using Gson as its quite easy to use as one can map a json object directly to a pojo class and then use the object of the pojo class. It removes a lot of boilerplate code for reading the json objects one by one.
Another way forward which avoids (most) code changes is to replace the Sling Commons JSON library with Org.Json if you can live with the license change that caused it be deprecated in the first place.
Add to the pom.xml dependencies:
You can add the org.json dependency to the pom.xml:
<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20180813</version>
</dependency>
<!-- Or depending on version of AEM
use the granite bundled version instead -->
<dependency>
<artifactId>json</artifactId>
<version>20090211_1</version>
<groupId>com.adobe.granite.bundles</groupId>
<scope>provided</scope>
</dependency>
OR use Open-JSON, a clean-room reimplementation by the Android team which has a standard Apache 2.0 license without the 'evil' clause:
<dependency>
<groupId>com.tdunning</groupId>
<artifactId>json</artifactId>
<version>1.8</version>
</dependency>
Update Import statements
The Apache Sling Commons JSON is mostly a repackaged org.json parser, and appears to be compatible aside from package path differences. To change to the org.json or Open-Json parser, alter these imports:
import org.apache.sling.commons.json.JSONArray;
import org.apache.sling.commons.json.JSONException;
import org.apache.sling.commons.json.JSONObject;
import org.apache.sling.commons.json.io.JSONWriter;
to
import org.json.JSONArray;
import org.json.JSONException;
import org.json.JSONObject;
import org.json.JSONWriter;
For many this will be an acceptable and clean solution that doesn't require reworking all the code to use GSON or Jackson (both available in AEM).
Caveat: I've only tested this compiles... You might need to embed the parser in your bundle. Neither of these parsers claim to be OSGi aware.
I am using JS Overlay objects in my GWT application. When Debugging the application, I am not able to see the value of Overlay object. Is it a limitation of Using GWT overlay objects.?
Is it because Overlay object is a native Object..? If it is a limitation, Is there any future plan to bring debugging support for Overlay objects in GWT.?
[I am not able to upload images. So typing what I see in the debug window]
> customer= JavaScriptObject$ (id=52)
> hostedmodeReference= JsValusOOPHM (id=183)
> value= BrowserChannel$JsObjectRef (id=188)
refId= 2
GWT version 2.5.1
Overlay types in GWT are a very special beast and are implemented using bytecode rewriting. See https://code.google.com/p/google-web-toolkit/wiki/OverlayTypes for (maybe a bit outdated) details.
As Suresh points out in the comments, there's low-level support for it in GWT but then IDEs have to use it for a seamless integration.
Pending that integration, you can use the utility class directly in the “watch” view (or similar) in your IDE during a debugging session:
com.google.gwt.core.ext.debug.JsoEval.call(MyJso.class, myJso, "myMethod")
This will print the json string from the JavscriptObject.
// Print it to the log
GWT.log(new JSONObject(customer).toString());
// Popup window
Window.alert(new JSONObject(customer).toString());
I'm wondering is there a similar framework like Vaadin built on top of GWT which wraps the original GWT components but with server-side only event handling? (I know that Vaadin is built on top of GWT. I'm looking for an alternative solution.)
Vaadin is nice because of it's precompiled nature. I found compile times with GWT horrific the last time i've worked with it. Also it's a bit easier to maintain security if event handling code runs on the server. It would be nice if the standard GWT could be used in a similar way.
I don't think there is another like vaadin. and vaadin is already server-side..
see this http://vaadin.com/learn for more info
Have you seen this? - http://code.google.com/p/gwteventservice/
For server-side alternative, you might take at a look at ZK too.
Notice that its client side is based on jQuery, not GWT. However, you won't notice it at all since they both are server-side solutions and using pure Java.
Event handlers that you normally deal with are in server-side Java code. Consider this:
final Button testButton = new Button("Test Button");
testButton.addListener(new Button.ClickListener()
{
#Override
public void buttonClick(ClickEvent event)
{
mainWindow.showNotification("I am server-side code!");
}
});
As you said, you need to compile GWT code only when adding a custom component to your code. Vaadin's built in components are already compiled and put in the jar file. Although sometimes your IDE might detect your project as a GWT project and try to compile the widgetsets every time you change the code, when you might want to ask it to ignore.
If you look for alternatives to Vaadin you might have a look at Echo2.