Intel AppUp developer program adds French language and Java support
The goal of the Intel AppUp developer program Software Development Kit (SDK) is to provide programming framework and libraries that enables the interaction with the Intel AppUp developer program processes and infrastructure.
The Intel AppUp developer program SDK for native Windows* and native Moblin™ application development provides many developer benefits including authorization, crash reporting, and a consumer store client emulator for testing.
Java app support
Continuing with their goal to provide the AppUp community with a choice to work with several operating systems, runtimes and app stores, the Intel AppUp developer program has now added support for Java. This includes a new SDK as well as validation and packaging tools, etc.
Eric Schmidt, Chairman and CEO posted today (12th September 2010) his account of the newest phase of the Chrome OS.
“With Chrome OS, we have in development a viable third choice in desktop operating systems. Before there was no cloud computing alternative—now we have a product which is fast, robust and scalable enough to support powerful platforms. It’s something computer scientists have been dreaming about for a very, very long time. The kind of magic that we could imagine 20 years ago, but couldn’t make real because we lacked the technology. As developers start playing with our beta Cr-48 Chrome OS computer, they’ll see that while it’s still early days it works unbelievably well. You can build everything that you used to mix and match with client software—taking full advantage of the capacity of the web.”
The high profile Google wave projects that started over a year ago is now being committed
into the Apache incubator.
The project has grown over the last year to include many Google and non-Google contributions. The project has picked up steam in recent months as the direction of the standalone Google Wave product has shifted. At this time the Wave in a Box project enjoys very active development, with new features and functionality being added almost daily. The first Wave Protocol Summit was recently held and included developers from a variety of countries, companies, and organizations.
The code base is a mixture of mature core code from Google Wave, and somewhat immature integration code forming WIAB. WIAB is quickly becoming highly functional and is already in a very “demoable” state. The development mailing lists are very active indicating wide community support. We recognize that now is a good time to migrate to the Apache Foundation while the codebase and community is a manageable size. Assuming the current momentum continues, we expect strong growth in the code and community in the near future.
Documentation for this project can be found at: http://waveprotocol.org/
Source is available at: http://code.google.com/p/wave-protocol/source/browse/
The last security update for the Office suite (SP2) may cause for vista users severe problems in computer performance and function.
There are Two phenomena noted:
- The Task Manager Shows multiple instances of the WerFault.exe
- When Attempting to restart in Safe-Mode, the Boot Halts when loading crcdisk.sys
The resolution is to carefully remove these updates:
- Go into “Control Panel”
- Click on the “Programs and Features”
- Select “View Installed Updates”
- Order the Installed update in descending install date order
If your machine is set for automatic updates, each time you uninstall an update, it will automaticly grab and install the newer version of that update. which is enough to do the trick.
The Valueshine AAdmin new version 0.3 is due to release by the end of December 2010.
The AAdmin is a fast add-on with a RoR server side and a Flex client side.
The RoR server side is structured upon the standard Rails scaffolding with a twist. The scaffolding means that setting up the server to connect to any database is a one line command on the consul. The twist is having an alternative controller template that renders XML back to the client instead of the standard redirection to the view.
The Flex AAdmin client side is a dynamic application that adapts itself to the structure it perceives from the server for every entity is handles. This means that in order to have the basic CRUD (Create Read Update and Delete) functionality no change is required on the client side.
On the other hand, the client is capable of handling a verity of display components, that anyone may write and add on in a matter of configuration. Current release is equipped with a table view that supports all CRUD functionality and a graph view for reporting.
This version will be free for download and use at the Valueshine Labs site.
My first program with lisp was so long ago I care not to remember, but now there seems to be a revival to old coding approaches (i.e. functional programming) and languages such as in the new lisp book: “The Land Of Lisp”
Awesome landing page.. though…
A fresh way for supporting multilingual flex interfaces:
Instead of the usual form (from an Adobe development center post):
The label looks more like:
The gS is actually a static object (i.e. hash map) that I load with all the key:value pairs of the language.
Once you declare gS as [Bindable] you can replace the object at runtime with other languages, resulting with the replacement of all the strings in the application.
Note: the compiler issues a warning that since you are using square brackets, the GUI object will not be able to detect changes in the data source. well it does..
original post from giladmanor.com
It appears that there is no official solution for static variables in the rails application since the @@ variables are reset for every thread that is initiated for a response.
To solve this, in a not so elegant manner, I’ve employed the common memory accessible on the Tread.main
if Thread.main[:counter] == nil
counter= Thread.main[:counter] += 1
(originally from giladmanor.com)
Lately i came across a post by Yoshinori Matsunobu on using a community MySQL server as a no-sql solution.
In his post, Matsunobu explains the benefits and the how-to’s of rendering the community MySQL database to a No-SQL implementation thus competing with the popular solution of most high scale web applications that use MySQL with complementary memory cache.
The obvious drawback of using such a local solution is that you code an application with a tight linkage to a particular database provider (i.e. MySQL). To particular implementations and applications this is a real restriction, but MySQL is a literal