The original article is here http://linuxfonts.narod.ru/why.linux.is.not.ready.for.the.desktop.html .
I feel that this post deservers some diggs, However it’s a russian domain, I can not post it to digg, So I wrote this post. All the credit goes to the author.
Post your comments here.
Filed under: technology | Leave a Comment
Tags: linux
Right click on the directory and select properties. check the derived attribute.
That’s it !. All the files and subdirectories are excluded from resource list.
Filed under: eclipse | Leave a Comment
Tags: eclipse
Apache Sling is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content.
Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.
As the first web framework dedicated to JSR-170 Java Content Repositories, Sling makes it very simple to implement simple applications, while providing an enterprise-level framework for more complex applications.
Bertrand Delacretaz and David Nuescheler created a sample site like TSS in Sling in 10 minutes, live on stage at the Jazoon conference. You See the sample here
Bertrand Delacretaz has written a tutorial which helps in getting started with the sling launchpad. the tutorial explains how to:
- get the launchpad
- build the launchpad
- start the launchpad
- create some content
- Render content using server-side java script
And some addition examples of how to create the node with uniqueue path, add page header with sling.include
there are good tutorials on dev.day.com also
I have heard an employee of day software saying that dev.day.com is built on sling
Filed under: Content Management, Java | Leave a Comment
Tags: apache sling, jcr, jsr-170
SnagIt – Now its my favourite
Just before few days when I was editing a screen shot with MS Paint, some one told me about a screen capturing utility SnagIt. When I installed and started using it, I asked my self what the hell was I doing with paint for all these days !!. why was I struggling with Paint when ever client asked for a screen shot of the proposed change in application !!.
If you use paint, than you may know, how frustrating it is, like capture the screen with Print Screen, go to paint and paste, remove the unwanted portions, the list goes on…..
Why SnagIt?
- Easily capture the regions of the screen.
- Capture a window.
- Capture a scrolling window or webpage (How will you do this with paint?)
- Record the screen video.
- Easily outline interested area with various shapes like circles, elipse, square etc.
- Use callouts like arrows, ballons.
- Easy to learn and use.
There are lots of other cool features that I don’t know yet. You can see some of the example screen shots here.
If you need to take screen shots frequently and you use paint for it than I will strongly recommend SnagIt. You can download a trial version of the software from here
Samples
Filed under: General | Leave a Comment
Tags: snagit
I will write an article soon..
But if you are impatience go here
Filed under: Java | Leave a Comment
The Early Draft Review for JSR 294 – Improved Modularity Support in the JavaTM Programming Language is now available for Review
The intention is to deliver this JSR as a component of Java SE 7.
JSR 294 plan to extend the Java programming language with new constructs called “superpackages” that allow hierarchical modular organizatio.
Each superpackage is a collection of one or more packages or superpackages, which helps to organize large programs consisting of many packages. Related packages that are grouped into a superpackage can access each others’ public
types, while unrelated packages outside the superpackage cannot access those types, unless the types are exported
Example declaration
superpackage A {
member package P;
member superpackage B;
}
superpackage B member A {
member superpackage C;
export superpackage C;
}
superpackage C member B {
member package Q;
export Q.X;
}
Find out more about JSR 294 Here and Here
Filed under: Java | Leave a Comment
JSR 308 proposes an extension to Java’s annotation system that permits annotations to appear on any use of a type. (By contrast, Java SE 6 permits annotations to appear only on class/method/field/variable declarations; JSR 308 is backward-compatible and continues to permit those annotations.) Such a generalization removes arbitrary limitations of Java’s annotation system, and it enables new uses of annotations. This proposal also notes a few other possible extensions to annotations
Example
@NonNullDefault
class DAG {
Set<Edge> edges;
List<Vertex> getNeighbors(@Interned @Readonly Vertex v) @Readonly {
List<Vertex> neighbors = new LinkedList<Vertex>();
for (Edge e : edges)
if (e.from() == v)
neighbors.add(e.to());
return neighbors;
}
}
Find out more about JSR 308 here
Filed under: Java | 1 Comment
Easily manage eclipse plugins
Managing multiple eclipse plugins can become difficult, specially when you need to update or remove a particular plugin.
Heres the easy way to manage multiple eclipse plugins.
1) create a folder ‘links’ under eclipse home folder.
2) create a file plugins.link under this folder.
This file can have any name as far as extension is .link, you can create multiple link file for different plugins.
3) edit the link file and put the path of custom plugins folder
example path=D:/customplugins ( use forward slash only).
This custom plugin folder should reflect eclipse plugins directory structure.
create a ecliplse folder within customplugin folder.
create two folders features, and plugins under eclipse folder.
Now you are ready to install plugins in that custom location.
You can repeat this steps to install different plugins in different folders. it will help you when you want to remove/reinstall a particular plugin.
Filed under: eclipse | Leave a Comment
JSR 283 Content Repository for Java Technology API version 2.0 has been approved.
The aim is to produce a content repository API that provides an implementation independent way to access content bi-directionally on a granular level.
A content repository is a high-level information management system that is a superset of traditional data repositories. A content repository implements content services such as: author based versioning, full textual searching, fine grained access control, content categorization and content event monitoring. It is these content services that differentiate a content repository from a data repository. Many of today?s (web) applications interact with content repositories in various ways. This API proposes that content repositories have a dedicated, standard way of interaction with applications that deal with content. This API will focus on transactional read/write access, binary content (stream operations), textual content, full-text searching, filtering, observation, versioning, handling of hard and soft structured content.
Original Specification can be downloaded from
here
Filed under: Content Management, Java | Leave a Comment
Tags: jcr, jsr-283
What’s coming up in Java SE 7
Summary Of Proposed JSRs for Java SE 7 Platform
JSR 277: Java Module System
JSR 294: Improved modularity support in the Java programming language
JSR 295: Beans binding
JSR 303: Bean validation
JSR 292: Supporting Dynamically Typed Languages
JSR 296: Swing application framework
JSR 203: More new I/ O APIs for the Java Platform (NIO.2)
JSR 220: Enterprise JavaBeans™ 3.0
JSR 255: JMX specification, version 2.0
JSR 262: Web services connector for JMX agents
JSR 260: Javadoc™ Tag Technology Update
JSR(s) TBD Java Language changes
JSR 308: Annotations on Java Types
JSR 310: Date and Time API
Fore more detaild information of above JSRs visit JCP
Filed under: Java | Leave a Comment
Recent Entries
- Why Linux is not (yet) Ready for the Desktop
- Eclipse: Open Resource shortcut – Excluding directories
- First Release of Apache Sling: A JCR based web framework
- SnagIt – Now its my favourite
- First look at JSR 303 – Bean validation
- The Early Draft Review for JSR 294 is now available for Review
- Early Draft Review of JSR-308, Annotations on Java Types is available For Review
- Easily manage eclipse plugins
- JSR 283 – Content Repository API version 2.0 Approved
- What’s coming up in Java SE 7
Categories
- Content Management (2)
- eclipse (2)
- General (1)
- Java (6)
- technology (1)
