I am developing a customization tool for an application.The presentation information, such as text, color code are stored in XML files.
The customization tool, is a tool that it provides friendly user-interface for user to change the value(i.e. text, color) in XML files. XPath was one of my option, however i stumbled upon LINQ to XML! To query multiple value or even a single value with LINQ to XML is really simple, and it is way simple!
For more information, please log on to MSDN, and search for "LINQ to XML", you will find lots of info there!
Have a nice day.
Saturday
Friday
Single Jar Scripts for Packaging JavaFX Applications
Every JavaFX project in the NetBeans IDE has a file called build.xml in its main directory. Open this file and add the following text to the end, just before the < /project> closing tag:
< target name="package-for-store">
<echo message="packaging up ${ant.project.name}"/>
<!-- the name of your app, minus the .jar extension. should not have spaces.
or use the default (the name of your app)
<property name="jar.name" value="MyApp"/>
-->
<attribute name="Main-Class" value="${main.classname}"/>
</manifest>
</jar>
<zip destfile="final/${jar.name}.jar">
<zipfileset src="final/temp_final.jar" excludes="META-INF/*.SF, META-INF/*.DSA, META-INF/*.RSA"/>
</zip>
</target>
To use this, first edit the preceding jar.name and main.classname properties. Then do a clean and build from within NetBeans. From the command line, you can then run ant package-for-store. This will grab the final jar and its support libraries from the dist dir. It will recompress them into a single jar and strip any signatures.
This final jar will be in the final directory, and it will be named based on the properties listed earlier.
< target name="package-for-store">
<echo message="packaging up ${ant.project.name}"/>
<!-- the name of your app, minus the .jar extension. should not have spaces.
or use the default (the name of your app)
<property name="jar.name" value="MyApp"/>
-->
<attribute name="Main-Class" value="${main.classname}"/>
</manifest>
</jar>
<zip destfile="final/${jar.name}.jar">
<zipfileset src="final/temp_final.jar" excludes="META-INF/*.SF, META-INF/*.DSA, META-INF/*.RSA"/>
</zip>
</target>
To use this, first edit the preceding jar.name and main.classname properties. Then do a clean and build from within NetBeans. From the command line, you can then run ant package-for-store. This will grab the final jar and its support libraries from the dist dir. It will recompress them into a single jar and strip any signatures.
This final jar will be in the final directory, and it will be named based on the properties listed earlier.
Google Wave出發！
谷歌剛剛在Google I/O 2009，發布了Google Wave.再一次把云端計算推入高峰！Google Wave,這個由Google的澳洲團隊制造的，整合了文字, 文件, 圖片, 影像, 地圖, 遊戲, 郵件, Gadget 等多種內容
每個人可以同時編輯之前別人或自己說過的話, 並加上連結/圖片/影片, etc
還有能加快輸入, 使用自然語言處理技術的即時拼字建議及校正功能。
另一個重點就是可以透過 API 與其他網路服務互動
像是把 Twitter or Facefook 嵌入 Google Wave中使用。
最重要的是，它是開源的哦！
每個人可以同時編輯之前別人或自己說過的話, 並加上連結/圖片/影片, etc
還有能加快輸入, 使用自然語言處理技術的即時拼字建議及校正功能。
另一個重點就是可以透過 API 與其他網路服務互動
像是把 Twitter or Facefook 嵌入 Google Wave中使用。
最重要的是，它是開源的哦！
Window 7 Managed API
Hello folks, Window 7 RC had been released. Window 7 RC received positive feedbacks from most of the users.
Most Windows 7 APIs are written in native code C, C++, and COM APIs, and have no .Net equivalents.
This makes the life of managed code developers a bit hard, forcing them to create their own interoperability layers for communicating between .NET and the native Windows APIs. Some native APIs are easy to wrap and use from managed code, requiring simple interoperability efforts like adding a reference to a COM type library. However, some are extremely problematic and require a lot of knowledge about the “Win32” programming style. That is exactly why the Windows API Code Pack for Microsoft .NET Framework was created.
Click here for more info.
Happy programming!
Most Windows 7 APIs are written in native code C, C++, and COM APIs, and have no .Net equivalents.
This makes the life of managed code developers a bit hard, forcing them to create their own interoperability layers for communicating between .NET and the native Windows APIs. Some native APIs are easy to wrap and use from managed code, requiring simple interoperability efforts like adding a reference to a COM type library. However, some are extremely problematic and require a lot of knowledge about the “Win32” programming style. That is exactly why the Windows API Code Pack for Microsoft .NET Framework was created.
Click here for more info.
Happy programming!
Subscribe to:
Posts (Atom)
