Am learning Play Framework, and i have write a small app in scala. and added some .less file which are not compiled.
the app is from the book's app sample github.com/andypetrella/play2-book-chapters/tree/master/chap3
So does Play framework in Scala support less and how to go about adding them(.less) in application? or is it the same as for java?
The .less files need to be in the app/assets/stylesheets folder. The LESS will be automatically compiled, but only when they are in that folder.
Related
I am using LibVLC v3.0.3 for my application to play WAV sounds from memory.
So far I was able to determine the main plugin folders needed for this (and this is by only testing by deleting one folder at a time and test if the application is working and there is sound in the output).
I want to filter these 5 left folders which are (access, audio_filter, audio_output, codec and demux) to keep only the needed plugin DLLs.
I found out that: the less plugins are loaded, the more the application loads faster.
And, is it possible to link these plugin libraries statically with the application in the compile time !?
Thank you for your understanding.
How to know what are the only plugins needed by my application?
That would depend on what your application is doing. Once you know the features of your application, you can learn about which VLC plugins do what and possibly remove those you do not want using configure if you build yourself https://wiki.videolan.org/Configure/.
I found out that: the less plugins are loaded, the more the application loads faster.
I guess that's true, but not all plugins are loaded by default.
And, is it possible to link these plugin libraries statically with the application in the compile time !?
Depends for which platform. For Windows I don't think so, but current VLC apps for Apple platforms are statically linked.
I'd advise you to have a look at the official apps build scripts from the VideoLAN gitlab https://code.videolan.org/explore/projects/starred
If by any chance you're using the .NET stack (for Windows), that will be easier thanks to https://github.com/mfkl/libvlc-nuget/blob/master/cherry-picking.md
I have created a iOS framework and want to use that framework in one of my application.
My question is about the UnitTesting of the framework.
I have read about the inbuilt xcode unittest framework, but not sure how to get started on testing the framework.
Or do I have to import the framework in one of my apps and then perform the testing of the framework via
Regards,
Nirav
Add a new target to your project, select Others -> Cocoa Touch Unit Testing Bundle, give it a name.
Add to the new target the Compile Sources and the Link Binary. And in your test class write the tests you need.
I have been looking for 2 days now, trying to find a way to get a single iOS framework-file for the ZXing QR reader. The only thing i can find, is a ZXingWidget project to include in my own project. But here, i have to add path's, dependencies etc. for it to work.
Isn't there a way to create one single .framework file that can easily be added to any new projects needing this feature?
I have found a kstenerud iOS framework template to create frameworks, but i can't make it work with the ZXing project.
No, there's no good solution for this for iOS.
Frameworks are generally (always?) dynamically-linked libraries and Apple doesn't allow DLLs on iOS. Note that there are now framework builds for OS X.
It may be possible to hack Xcode to produce a framework with a statically linked library, but that's going against Apple's patterns which means I suspect it will push Xcode into corner cases which fail in subtle and hard to debug ways and which have a high chance of breaking across Xcode versions.
This opinion comes in part from talking to Apple Xcode engineers at WWDC about cleaning up the ZXing project files. There are new project files now that follow all the best practices they recommended but on iOS they still require the same include path and library linkage project customization that the old project files require.
Is it possible to create an own obj-C Cocoa Touch framework which can be used by other developers? And furthermore can you protect this framework?
I've created templates for Xcode 4 that allow you to build universal iOS frameworks (which work in both device and simulator).
Once the templates are installed, you simply select "Static iOS Framework" when creating a new project and it does the rest. It also works with unit tests.
https://github.com/kstenerud/iOS-Universal-Framework
You can create a static library. There is an option in the XCode project chooser to do this. You'll have to distribute the compiled static library file and the header files to users of your library. Your actual implementation files (.m) do not need to be distributed.
GHUnit does a good job of this - packaging up the libraries for both simulator and device - so I recommend looking at this project. (I also recommend using this library for unit testing :-)
The frameworks in Objective C are typically just C / ObjC code and a bunch of classes, nothing amazingly special. As such, you can create your own if you'd like, and then just include that in your project when you build it. The iPhone doesn't care about the difference, it just knows to put all that code into your app, along with everything else.
Have a look at the Framework Programming Guide on Apple's website. It will get you started. Essentially what you'll do is create a Framework project in XCode and then go from there.
As for "protecting" your framework, I assume you mean making your code unreadable. I'm not sure if and how you can do this, but perhaps Apple's guide will say something about it.
Yes you can create frameworks for use with Cocoa Touch.
However there are these caveats:
has to be a statically linked libary, no dynamic loading (dyld) for us
should be a combined (lipo) library for i386 (simulator), arm6 and arm7
you need to hack a bundle project into a framework
you should embed (small and few) images into the library so that the developer does not have to mess around with resources but just drags/drops it into his project
... or if you have large and many images build a bundle with these
I have guides for these things on my site.
1+2 = http://www.drobnik.com/touch/2010/04/universal-static-libraries/
The other links you have to google because this site does not let me post more than one URL.
You could make a static library available as binary (i.e. rudimentary "protection") to third parties, but not a dynamic one, as Apple's App Store policy prevents dynamic linking.
Take a look at a worked example for static libraries given at
this site
If you're going to do it, in my opinion JSON.framework is a great example to follow. To hide/obfuscate the source code is a different story, and a different question entirely,
When creating a new project, navigate to iOS > Framework & Library > Cocoa Touch Framework, it's as simple as that. When you are successfully compile, .framework will be created under Products folder in XCode. Right click to show in Finder, and you can find the output.
It's unlikely this will work the way you want it to because the other developers won't be able to use your framework. This StackOverflow Question explains why.
Having trouble linking the Stomp.framework into an iPhone SDK application.
http://code.google.com/p/stompframework/
I follow the instructions, adding it to the project, adding a Build Phase for Copying the Files, and including it via #import .
I keep getting "image not found".
Anyone try this and/or have a clear idea why?
This may be better:
http://github.com/juretta/objc-stomp
I found it fairly easy to get going.
The iPhone SDK doesn't support embedding frameworks in applications. I believe it supports dylibs, though I'm not certain of that fact. However, the safest thing to do would be to take the source of that framework and compile it directly into your application.
Make sure that whatever folder contains the .framework bundle is listed in the Framework Search Paths setting of your target or project.
There's more you'd need to do if you want to embed the framework in your application but that's another question.
edit: Totally ignored the iPhone requirement there, you'll have to compile the framework as a static library and link against that.