I'm using the zxing javase client library along with the zxing core library to generate QR codes from URLs in a java application. I need to generate custom colored QR codes and looking at the javadocs, using MatrixToImageConfig with MatrixToImageWriter (both in the javase package) seems to be an ideal solution. However, the latest version of zxing(2.0) that I found on the downloads page doesn't have any class named MatrixToImageConfig.
The file is present in the latest code that I downloaded from subversion. Has this been feature been released yet ? If no, is there some other way to achieve this using zxing?
Yes it was added after 2.0. It is in Subversion; you can just use the code / JAR from Subversion or use 2.1-SNAPSHOT in Maven.
Related
I am using Jdeveloper 11g , and wanted to develop a barcode scanner in java, I have found Zxing thru googling and more over its opensource.
I have downloaded the Zxing-2.0.zip and found many folder for different technologies like javase, cpp, android etc, i suppose these folders are intended only for those technologies, if i want to develop in java i find two folder javase and core which have exclusive java code, but I am not sure how to use them in Jedeveloper 11g.
Can some one recommend some tutorial? Some link where I can get useful information on where to start?
You build a library out of all needed jars to work with zxing and af thus to your project. Then you can start working with the zxing classes. I'm sure there are some samples on the zxing site you can refer to.
I tried to add mailcore framework to my project which is existing in my library but it's not getting added into it,can any one pls help me to solve this issue.
Thanks in advance.
One way is to use reMail. remail uses mailcore, and since its acquisition by google, is open source.
Another way is to actually build mailcore.
GETTING STARTED
The best way to start learning MailCore is by reading through
documentation intro (in index.html) and the the included example
projects. To run the example projects:
Copy MailCore.framework to your ~/Library/Frameworks folder.
In each example project, add ~/Library/Frameworks/MailCore.framework to the list of Linked
Frameworks.
Build it!
The documentation isn't as detailed as I'd like. Sorry about that! If
something isn't clear try reading the source included or contact me.
CONTACT INFO
MailCore by Matt Ronge http://www.mronge.com mronge#mronge.com
LICENSE
Licensed under BSD, see LICENSE.txt for more information.
Based on LibEtPan and work done by Dinh Viet Hoa.
From the Getting Started documentation on the project:
IPHONE USE
MailCore has an included iPhone
target, but it requires some
additional compiled binaries (OpenSSL
and CyrusSSL). I am unable to
currently provide these, however the
company Remail is offering the
binaries and a compiled copy of
MailCore for the iPhone. Contact
Remail for more information:
mailcore#remail.com
It seems like you'd need to get those before building against the iPhone target.
After reading the instructions he doesn't say to add the MailCore framework. Just the library. Try it that way.
My clients wants to use some of the already available features in my app into their app. But, i dont want to share my source code with them and vice versa. I found out from some googling that, we can do this by creating some static libraries or frameworks in iOS. Can anyone throw some light on how to create a static library or framework (which ever is better) out of my already available source code.
My preference is to use static libraries over Frameworks. You will provide your customers the library file (.a extension) and the header file(s) for the functions in it. They just need to install the files somewhere in their project tree, set the include path, add the library to the project and they are good to go.
Note that if you want them to use your lib in the Simulator as well as on device you will need to provide them two versions of the library, one for each.
For instructions on how to create and use an iOS static library see this site.
Just for your information:
I created a static framework for iOS according to jverkoey's instruction
A ton of thanks to Diney Bomfim for his excellent article on how to create a framework. This is exactly what i am looking for.
EDIT - The Link is NOT working anymore...
Each C/C++ library has some amount of headers that should be used with that library. And if you're use more than 1-2 libraries, custom header paths is kind of headache.
So I thought: is there a way to compile C libraries as frameworks. Static library + headers + versioning.
I found in XCode template for Cocoa framework but nothing about iPhone framework building. This simple step could allow developers to build and share between each other frameworks with some interesting code.
Also it would be great to use libpng, libjpeg and other libraries packaged as frameworks.
I won't use dynamic libraries in those frameworks. Only static version will be present.
I combined techniques I found here and here into my open source library here (NOTE - I have since removed the relevant scripts from this project. I have updated the link to point to the last revision that included these techniques.). Think that's basically the solution you're looking for.
Basically, it has a target that will build a fat static library (lipo builds for arm6, arm7 and i386). It has another target that takes that library and builds it into a framework.
There's no reason you can't use the same techniques for a C project. In fact I've started work on porting C the VTD XML parser to an Objective C framework using the same techniques.
Frameworks are basically just bundles of dynamic/shared libraries. Since this is not allowed in the App Store, you have to build static libraries and link them with your App's executable at compile time.
However, to ease the pain a little, you can have a Xcode project for each library and compile each library into a static lib. Another way would be to put all required source files into the main Xcode project and configure it appropriately so it all builds at once (I did this with small libraries like Minizip, for instance).
Hope that helps.
the problem you are trying to make already exists - it's called DLL hell
Best way is to stick with plain old static libraries when making small apps and organizing source/headers structure
According to the Core Plot Wiki:
Core Plot is built as a static library
for iPhone, so you'll need to drag the
libCorePlot-CocoaTouch.a static
library from under the
CorePlot-CocoaTouch.xcodeproj group to
your target's Link Binary With
Libraries folder.
I do not see the mentioned library, where might it be?
This is the location referred to in the integration instructions:
(source: sunsetlakesoftware.com)
This will show up as red until the library has been compiled, but you can still drag this library over to the Link Binary With Libraries build phase. If you follow the remainder of the instructions for setting this as a dependency for your application target, it will be built before your application is.
In the future, framework-specific questions like this might receive faster answers on the Core Plot mailing list.