skip to main |
skip to sidebar
Don't really know if you have the same problem as i do with my MP3, i have around 15 Gig of files some of them well organized and other not, most of them just says "Track 01" as the filename.
I was goggling for a way to re-organizes my files to have the correct "file-name" based on the ID3 tag, i can do it manually file by file, but it will be a pain.
Then i found this EXCELLENT Free software, MediaMonkey
I must agree it has a funny name, but damn that tool rocks!!!!
The auto-organizes feature and auto-tag from web really helps to organizes your music, so you can browse your Music Collection easily. Even when the file is is not properly tag, it allows you to easily search on the web and then select the correct one.
Hey, i found myself really mad when trying to find out any documentation about something and can't find anything useful due to my bad search skill (I admit, im not as good as i should when trying to create a "good search criteria" on any search engine), then when all the hopes is gone out of the sudden i get the right words on my "google search" and voila get what i was looking for.
This time, im talking about Wicket Framework resources (I wont say again, how great Wicket is). but this post is just for a setting a reminder point where to find right information and good examples in a well organized places for this great framework. Hopefully, i'll keep adding other's resources on this post. So anyone on the net can find them easier than i did :)
For my friends (Yes, i know i'm a "MALETA" when talking about searching criterias).
For those non-spanish reader ("MALETA", gets translate as "SUITCASE", but we aren't talking about travels here :P) in DR (Dominican Republic) we use this term as of referring to someone with bad skill for something in particular in a very non-offensive and joking way.
General
http://cwiki.apache.org/WICKET
Wicket Best practices and Gotcha
http://cwiki.apache.org/WICKET/best-practices-and-gotchas.html
Great Reference Library
http://cwiki.apache.org/WICKET/reference-library.html
How to do things in wicket
http://cwiki.apache.org/WICKET/how-to-do-things-in-wicket.html
Wicket Examples
http://www.wicket-library.com/wicket-examples/
I'll keep adding more link on demands. Happy Wicket!
I recently found a very good article for any java starter, which explain really well how this two Pattern works and why we should use them. You can find the whole article at MartinFowler.comHere is a preview of the article :) Enjoy it!"In the Java community there's been a rush of lightweight containers that help to assemble components from different projects into a cohesive application. Underlying these containers is a common pattern to how they perform the wiring, a concept they refer under the very generic name of "Inversion of Control". In this article I dig into how this pattern works, under the more specific name of "Dependency Injection", and contrast it with the Service Locator alternative. The choice between them is less important than the principle of separating configuration from use."One of the entertaining things about the enterprise Java world is the huge amount of activity in building alternatives to the mainstream J2EE technologies, much of it happening in open source. A lot of this is a reaction to the heavyweight complexity in the mainstream J2EE world, but much of it is also exploring alternatives and coming up with creative ideas. A common issue to deal with is how to wire together different elements: how do you fit together this web controller architecture with that database interface backing when they were built by different teams with little knowledge of each other.A number of frameworks have taken a stab at this problem, and several are branching out to provide a general capability to assemble components from different layers. These are often referred to as lightweight containers, examples include PicoContainer, and Spring.Underlying these containers are a number of interesting design principles, things that go beyond both these specific containers and indeed the Java platform. Here I want to start exploring some of these principles. The examples I use are in Java, but like most of my writing the principles are equally applicable to other OO environments, particularly .NET.Components and ServicesThe topic of wiring elements together drags me almost immediately into the knotty terminology problems that surround the terms service and component. You find long and contradictory articles on the definition of these things with ease. For my purposes here are my current uses of these overloaded terms.I use component to mean a glob of software that's intended to be used, without change, by application that is out of the control of the writers of the component. By 'without change' I mean that the using application doesn't change the source code of the components, although they may alter the component's behavior by extending it in ways allowed by the component writers.A service is similar to a component in that it's used by foreign applications. The main difference is that I expect a component to be used locally (think jar file, assembly, dll, or a source import). A service will be used remotely through some remote interface, either synchronous or asynchronous (eg web service, messaging system, RPC, or socket.)I mostly use service in this article, but much of the same logic can be applied to local components too. Indeed often you need some kind of local component framework to easily access a remote service. But writing "component or service" is tiring to read and write, and services are much more fashionable at the moment.Read the whole article at MartinFowler.com
Posts
