|
|
|
Posted
2 days
ago
Gaia Transparence is a software vendor specialized in financial markets. It is a pioneer in the open source community for financial markets. The Gaia Transparence team is building an open source solution for the finance industry based on the NetBeans
... [More]
Platform.
The Gaia Transparence open source financial platform will address new regulatory requirements, including central counterparty (CCP) margining, credit value adjustment (CVA), Markets in Financial Instruments Directive revision (MIFID2), and Basle3.
On the open source motivations of the team, Benjamin Frerejean (Director of R&D) explains the following:
A key benefit of open source is "transparency". As the source code is available, it can easily be audited by either users or auditors. Along with Gaia Transparence turnkey applications, we deliver "generic trades", "positions", and underlying objects. Users pilot the development and share all the specific instance types, while user group members can mutualize enhancement costs.
We, the Gaia Transparence team, believe that open source is the solution for financial institutions to cope with the challenges they are faced with since the 2008 crunch. On the one hand, the market needs to regain "trust", whilst on the other the new regulatory environment imposes new trading standards and reporting. IT budgets are tight in this time of crisis. Trust can only be gained with transparency and standardization. Open source is transparent by nature. Open source solutions become standards when the community is active. By enabling mutualization of development costs, open source solutions help contain IT budgets. The rapid acceptance of the open source CDS pricer published by ISDA in April 2009, as part of the "Big Bang" initiative, proves the market is ready. [Less]
|
|
Posted
3 days
ago
Last week I blogged about the free and open source EPUB Open Toolbox which I am creating for publishers and authors. Officially, it is now known as Fosfor, since it is initially being developed for the Fosfor Uitgeverij, that is, an on-line e-book
... [More]
publisher based in Amsterdam, as a replacement for Sigil. And this is yet another example of how the web and mobile worlds need the desktop—just for fun you should ask a publisher or author some time: "Do you ever see yourself editing and managing books on your mobile phone?"
At the time, when I started working on this, I was using the SHEF framework as the basis of a WYSIWYG editor. That had its shortcomings and I couldn't help thinking that the JavaFX WebView would be a more natural fit.
So, here we are a week later, with the JavaFX WebView doing a superb job rendering the XHTML pages of EPUB projects:
It simply looks awesome. No credit whatsoever for me on that score, since I'm simply reusing the JavaFX WebView, the creation of which I had nothing to do with. Images are rendered, which wasn't the case with SHEF, the performance is great, and the whole thing just looks professional, like a commercial off the shelf product that took years to develop, rather than days. Aside from the rendering, there's a lot of functionality built into the JavaFX WebView, e.g., when you right-click on an image, you get popup menus for opening the image in a new view, when you right-click on a URL, you can open the URL in a new view, etc.
But, I don't want a web browser. I want a WYSIWYG editor. The start is clearly there, i.e., there's a JavaFX toolbar containing JavaFX buttons, each of which will be, once the prototyping phase is over, provided by different NetBeans modules. For example, here's the color chooser in action—select a piece of text, invoke the color chooser, select a color, and immediately the font of the selected text is changed to the selected color:
Still many things to do. Especially, synchronizing changes back into the source file. Once that's done, all the rest should be relatively painless. Not possible, right now, to type in the WebView, but I have a pretty good idea how to solve that. My insight on this is that there's no difference between adding characters and adding colors to selected text. And it's also possible to get hold of the cursor in the JavaFX WebView, so the basics for typing are already included in the app. With that solved, its all about adding more tools, e.g., a bold tool, italics tool, font size, and so on.
I've shared the above pics with Sean Phillips who works on NASA software (he's been mentioned in this blog several times, has a lot of JavaFX/NetBeans Platform articles on NetBeans Zone, and hopefully will be at JavaOne this year) and he responded pretty positively from his perspective at NASA:
Based on what you have said and the limited images I've seen, this could be used as a technical document markup tool. Several of the Ground System missions I am associated with have home brew tools that generate documentation. Office tools like MS Word and the like can't really be used because a significant portion of the documentation is based around data produced by custom mission specific software systems. As a result, someone ends up writing code that generates Latex or HTML as a custom one off. I wonder if there could be a future in a tool like what you are developing that could be used towards a goal like what I have just described.
Part of my reason for blogging about this is to ask—are there developers out there who have tools written in JavaFX (or who would like to start doing so) that are relevant to the above and could be contributed to the free and open source Fosfor project? [Less]
|
|
Posted
4 days
ago
Let's say you have a NetBeans Platform application that puts a premium on vertical space. Maybe a Heads Up Display on a Touch Screen? Wouldn't it be great to have the menu slide out from the edge of the screen only when you need it? Well the
... [More]
NetBeans Platform provides slide-in TopComponents, of course, but a JMenu just isn't going to work out so well inside one.
Preview... [Less]
|
|
Posted
4 days
ago
qSim is a computer network simulator with emphasis on Quality of Service (QoS) mechanisms. It lets you observe how computer networks react to different QoS mechanisms, including network node usage (input/output queues, RX/TX buffers usage), data flow
... [More]
delay time, and packet drop statistics.
13 QoS mechanisms are supported, which can be divided in three groups: packet classification & marking, active queue management, and packet scheduling algorithms.
The network topology is fully customizable, including:
link bit rate and length (in meters)
link reliability
simulation of input/output queues
simulation of RX/TX buffers
size of all buffers/queues
different data flows (TCP/UDP/ICMP protocols supported, various packet sizes, realistic packet generation delays)
The simulations have been tested and compared with real CISCO devices, with positive results.
qSim was developed at the Faculty of Informatics and Information Technologies, Slovak University of Technology, in Bratislava. [Less]
|
|
Posted
5 days
ago
Knockout4Java takes the best of two words: The type safety of Java and Knockout.js ability to alter any HTML page in any browser. Write your models in Java (using JSON4Brwsr library) and render them as HTML with the help of Knockout4Java!
--JaroslavTulach 21:32, 16 May 2013 (UTC)
|
|
Posted
5 days
ago
SimuQuest is a Michigan-based software development company that specializes in working with electronic hardware companies that produce electronic controls for such things as car engines or wind turbine generators. UniPhi is one of
... [More]
SimuQuest's software tools. It is created on the NetBeans Platform. It is a model-based development tool for data management and dependency visualization, enabling consistent, version-controlled management of data (signals and parameters) and rapid visualization of object dependencies (modeled features, signals and parameters). UniPhi is deployed to develop embedded systems using model-based design within a variety of industries such as aerospace, automotive, consumer appliance, and alternative energy.
Further info:
http://www.simuquest.com/products/uniphi [Less]
|
|
Posted
6 days
ago
Most modern automation installations, such as controlers of machinery on factory assembly lines, amusement rides, or light fixtures, are driven by Programmable Logic Controllers (PLCs). Low level programming languages that have been used
... [More]
for decades, such as Ladder Diagrams (LD), are still being
used to develop new PLC software. Together with the ageing techniques inherent in such programming constructs, there are hidden penalties, such as the fact that
PLC software is brand dependent.
PLC-PROG is the first tool for PLC programming to enable a completely brand independent and user-friendly object oriented approach, resulting in a reduction of development cost and an increase in the reliability of developed programs. It is valid for all PLC brands which comply with the IEC 611131-3 standard, is based on graphical programming methodologies, requires no specific programming skills, and makes it possible to perform both monitoring and visualization from the tool.
PLC-PROG has been developed using the NetBeans Platform, to take advantage of the benefits that its libraries offer. Below you see the PLC-Prog Visual Editor with the rack concept, which is a base element on top of which fuctions and input/output modules can be dragged:
Other tools, such as a Tree View for tracking programming flow, is shown below:
Further info:
http://www.plc-prog.eu/ [Less]
|
|
Posted
6 days
ago
Most of the popular acronyms are wrong: SOAP (Simple Object Access Protocol): is neither simple nor object oriented. "SOAP originally stood for 'Simple Object Access Protocol' but this acronym was dropped with Version 1.2 of the standard.[2]
... [More]
Version 1.2 became a W3C recommendation on June 24, 2003. The acronym is sometimes confused with SOA, which stands for Service-oriented architecture, but the acronyms are unrelated…" http://en.wikipedia.org/wiki/SOAP
AJAX (Asynchronous JavaScript and XML): Most of AJAX applications are using JSON, not XML. AJAX' core component is the XMLHttpRequest JavaScript object / browser API. Without XMLHttpRequest would be hard to implement an AJAX application...
NoSQL: "… Some authors refer to them as "Not only SQL" to emphasize that some NoSQL systems do allow SQL-like query language to be used…" https://en.wikipedia.org/wiki/NoSQL. …and often the offered NoSQL query language is structured and very similar to SQL :-)
EJB (Enterprise Java Beans): Well designed JavaBeans are actually not well designed EJBs.
YAGNI there should be no acronym for that. Thinking about that may cause endless loops :-)
See you at Java EE Workshops at MUC Airport!
Real World Java EE Workshops [Airport Munich]> [Less]
|
|
Posted
7 days
ago
Project News NetBeans IDE 7.3: Power Tools for HTML5 & JavaScript From NetBeans IDE 7.3 onwards, released earlier this year, new features have been introduced to enhance the development experience for HTML5/JavaScript/CSS3 Web
... [More]
applications. In this article, an overview is provided of all the new features encompassing the new tools for HTML5 and JavaScript developers.Legacy
... [Less]
|
|
Posted
7 days
ago
This blog post introduces another exciting new feature in the upcoming NetBeans IDE 7.4. Namely, JavaScript debugging and visual CSS editing on Android devices. So without further ado, let's see how it works. As a prerequisite, you will need
... [More]
an Android 4.x device. Let's do some setup steps that you only need to do once. First, install the Chrome browser on the device. The Chrome browser is available in the Play store.
Next, you will need to turn on USB debugging both at the system level and in the Chrome browser, which can be done in Android's Developer options in the phone settings. Note that on Android 4.2 and newer, Developer options is hidden by default, so we need to unhide it first. To do that, go to Settings > About phone option in settings, and tap Build number seven (7) times. Then return to the previous screen, and you will find Developer options.
Once Developer options are present, you will see the USB debugging checkbox inside this category. Make sure it is checked.
Next, open the Chrome browser, go to Chrome settings, and under Advanced > Developer tools, check the Enable USB Web debugging checkbox.
We will also need to set up the Android SDK and point NetBeans to it. In NetBeans, go to Tools > Options (or NetBeans > Preferences on Mac OS X), choose Miscellaneous > Mobile Platforms, and specify the location of the Android SDK. In case you don't have the Android SDK installed on your machine, the dialog provides a convenient link to the SDK's download page. This completes the one-time setup.
Now, to start developing your web application on your Android device:
Connect your machine and the Android device with a USB cable
Connect your developer machine and the Android device to the same Wi-Fi network (this is necessary so the device can access the web server running on your computer)
As our testing application, we will use the AngularJS Phone Catalog application that is bundled as a sample in NetBeans, but you could of course use any HTML5 application - or a Java web application or a PHP application, as described in a prior blog post.
To run the application in Chrome on your Android device, click the new browser switcher icon in the main NetBeans toolbar, and select Android Device (Chrome).
Next, just run the application, and the application will open in Chrome on your device.
Let's now see how we can tweak the style of this application directly on the device. You will notice that in the IDE, a couple more windows opened: Browser DOM and CSS Styles. The Browser DOM window displays the real DOM tree as rendered by the browser on your device. When you select elements in this window, the CSS Styles window refreshes to show the CSS styling information for the currently selected element.
More interestingly, as you select (or hover over) elements in the Browser DOM, the current element will be highlighted in the page on your device.
Next, we will want to select elements on the device in order to change them. If we were using the desktop version of Chrome, we could do this by turning on Inspect in NetBeans Mode using the menu item provided by the NetBeans Connector for Chrome. But as Chrome for Android does not support extensions, we will do this using the Inspect Mode in the Browser toggle button at the top right of the CSS Styles window.
Once Inspect Mode is on, the interaction now works in the other direction: tap elements in the page on your device, and both Browser DOM and CSS Styles windows will be synchronized. Once we have selected the element whose style we'd like to modify, we can just do so using the bottom part of the CSS Styles window (Property sheet), and the change will be reflected live on the device. For example, this is the result of increasing the font size of the description text from 13px to 22px.
Note that this example is illustrative only - in a real world example we would likely use media queries to achieve good appearance on both mobile and desktop clients. Speaking of which, media queries (as the main tool to do responsive web design) are supported in NetBeans' visual CSS editor.
Next, we may want to debug the application. For example, to see what happens when we click on an individual item in the list of phones in our application, we will place a breakpoint on line 16 in controllers.js. But in order to tap the item, we first need to turn off Inspect Mode using the toggle button in the CSS Styles window. Then after tapping the item on your device, the IDE will stop on the breakpoint.
Now we can inspect the variables, step through the code, see the call stack, and in general use all the features of the NetBeans JavaScript debugger.
All this support will be included in NetBeans IDE 7.4, which will be released later in 2013. However, you can already try this out now in a recent nightly build of NetBeans 7.4. [Less]
|
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.