I am new to BlackBerry. I have experience on Android. Now I want to learn BlackBerry. In Android an application contains res folder in that we add the layout in XML form and we can create the forms easily using views and layouts.
In the same way, is there any facility in BlackBerry? How do I prepare forms in BlackBerry?
I'm not sure about third party tools/packages, but I know there are no first party tools for what you're looking for.
Unfortunately there doesn't exist any 3rd party tool or what you mention in Android. You
must write all from code. Sure you can add layout, etc., but all from code.
Good luck with BlackBerry development :D Just a good idea: learn the MVC pattern very fast if you don't know yet because it helps very much at BlackBerry development (separate the model, view, controller classes and functionalities.)
Related
I am a web developer / programmer that is in my infancy on mobile development on iOS. I would like to start a new project on an mobile app, but usually if i were to develop a web site, I would download some html template on the web with ready made of html and css or CMS like wordpress if my application is complicated or huge, so that i do not need to design the pages from scratch. I would just need to add some php or J2EE programming towards the pages to develop my application.
So now my question is, what about iOS? Is there any ready made iOS templates with good design? I tried searching for templates on the web but doesn't seems to find any. Am I starting at the wrong foot?
Thanks in advance.
I've seen companies that offer such things, but they cost money and I don't think they are worth it. Using storyboards to build an interface and then putting in your logic code is pretty straightforward. If you need some tutorial type help getting started, raywenderlich.com is a great site.
I have a site that's done using ASP.NET MVC and jQuery. Is it possible to modify my existing project without too much of rework so that it can be used in phonegap to create iphone/android apps?
Here's an approach: move your logic to an MVC WebAPI (or other REST/webservice) project, then convert the MVC site into a simple html/javascript/css/image site (Mobile site). Then refactor your Mobile site to use Ajax/JS to query the WebAPI/Rest services you created. Once you've separated your code this way, you can then package the Mobile site with Phonegap. I'm not sure how much work that will be for you or your project. If you're using a lot of Html Helpers or Razor markup in your views it may be too involved.
The core point of my suggestion here is to separate your mobile UI layer and the backend processing layer so you can only package the Html5/UI/Javascript layer with Phonegap and leave the backend processing on your web server. I don't think I need to explain this, but obviously the app packaged with Phonegap is not going to have the MVC/.Net framework available on the mobile device to render views or execute controllers, etc. By migrating your UI to be simple Html5 and Javascript you can use Ajax/Jquery/Javascript calls against your backend, which you will probably want to host in ASP.Net MVC WebAPI.
Edit: Guess there was some confusion about my suggestion. I'm not saying this is the only way to do go, but this is what I'm familiar with as it's how our team builds our desktop/web + mobile + phonegap + mvc4 + webapi + kendoui application. This pattern works well for us so maybe it'll work for you too, or at least give you some ideas on how to structure your solution. Good luck!
I'm not sure but you need a server to compile the ASP.NET right? so I don't think that will work for you. I think you need to work with AJAX to do your ASP.NET work and separate your ASP.NET code and your HTML-jQuery because Phonegap wants a index.html file. You can store your ASP.NET files at a server tough
The answer to your question really depends on the type of site you are trying to convert. Are you just trying to put a native framework around HTML and get your app into an app store?
If it is is mostly or entirely informational in nature and you have simply used MVC to build brochure-ware type pages then it should be fairly easy to move. This assumes that there is little to no logic other than page to page navigation.
If your site instead pushes a lot of data around that relies on a back-end server you will need to re-architect it to store data locally or pre-fetch it via a manifest. Next you will need to implement a strategy that allows you to push your local data back to the server.
Does you app need to run in a disconnected state?
Phonegap is one of the options if you want to target multiple mobile platforms & may be most widely used. Since you are using jQuery, jQueryMobile will be a least learning-curve path to use. Effort is mostly on the front-end UI and will depend on how many screens you want to design to provide a sub-set or the full set of functionality you already have on the web UI. Most likely you will have to redesign your screens using the jquery-mobile UI widgets documented here. It is also a good way to show it to your customer the initial screen design with navigation.
jquery mobile is great for learning and designing , but it's slow in the web browser control that phone gap runs in .
you'll need a more lightweight framework for this .
you can use an inappbrowser control to show your site in case it's responsive , but you wont have the device camera and contacts and so ...
take a look at : http://docs.phonegap.com/en/3.0.0/cordova_inappbrowser_inappbrowser.md.html#InAppBrowser
I'm trying to build a basic website, but that doesn't limit my ability to add complexity later. I am a complete newb and have no prior programming experience. I'm very confused as to the role of web editors (e.g. Kompozer) vs. web frameworks (e.g. Rails, Django). For what purposes are each useful for? What makes sense for quickly building a basic, functional website that can be more professionally developed later on?
Kompozer is a WYSIWYG that allows you to drag and drop HTML elements and create your website with buttons, dropdowns and menus. You can view the code it generates and modify it if you need to.
A web framework you would typically not use a drag and drop type editor, but just type code into something that looked like an advanced Notepad. A web framework typically removes a lot of the grunt work and allows you to organize your logic separately from your design.
Basically, you would use a program like Kompozer if you wanted a simple website that didn't do much in terms of functionality. You would use a web framework for doing some heavy lifting with some custom programming... for example if you wanted to design a web application that did calculations based on the food you ate today and gave you dieting information, or where you could login and manage different types of equipment etc...
I have been developing a simple app using HTML pages that are interlinked. They will be using some form of data persistence. I have not decided yet. They will be displayed on an iPad in both landscape and portrait modes.
I could wrap them in a UIWebView and roll my own app that way, but to me it seems that others must have come across this requirement before and there might be a simple framework to do this.
I don't need any special access to location data, accelerometers etc. Just plain HTML, some CSS and Javascript. The most complex of which will need to store a series of name value pairs (circa. 150 items) that will need to be available to all pages within the application. I have no need to call the Javascript from the app or vis versa.
I will need to insert inApp purchasing in future to the application, whereby I will load a larger set of HTML files. It might be nice to be able to trigger that from inside the HTML pages but that is not necessarily a deal breaker.
There are a number of frameworks for writing apps in HTML5 etc. and converting. I don't really need this either.
But I would rather use some framework that will take the lessons learned by others and let me deploy my app on an iPad with minimal risk.
Can anyone give me advice regarding the best framework for this use case?
Thanking you in advance,
Andrew
I would use phonegap. It works on the iPad no problem.
You can use the camera and accelerometer and all that with phonegap-plugins.
I am using it on a few iPad projects, and since you can use HTML/CSS/JavaScript, you can pretty much just configure phonegap with your web address and your web app is now an iPad app (that or just add static html files to the phonegap project directory). Then it's just 'modify the design and layout HTML/CSS'.
I've been programming for many years and have just recently got the RoR "itch". I'm thinking about how I could utilize a graphic designer and wondered how best to collaborate with them:
1) Do scaffolding and then show them where to place the graphics in the views (seems ugly)
2) Have them do screens and make them keep a certain dir structure for all media links i.e. /public/images public/stylesheets, etc. Will this confuse the graphics designer LOL?
3) Better to just have them build the images (like a header or footer image, etc.) and place them in yourself. But this approach means you have to start thinking about design and layout which seems better left to the graphics specialist.
All of the above seem flawed to me and I was wondering if there are any "best practices" for this problem? Searched for articles, etc., but didn't find much. Suggestions? Thanks all.
i work in a company that works 100% with ruby on rails development. which approach we take to integrate views.
First thing that we develop are views. The design team develop a view, tell us which data will be filled in this view and our development team develop the necessary ERB code. So normally a development process are like:
We develop some views with the client
Our dev team do the spec for functions
The design give to us the application layout
We implement it and start to work in the first models and controllers spec'ed
New whishes and views will be asked by the client, that will be sent by our design team and it will be spec'ed by our dev team.
Normally give them their own rails server, teach them the basics of where they need to add controllers and views (no need for any model stuff) to work with the default route.
I integrate the HTML, they stick in the CSS.
Teaching them how to render partials helps them with consistency. Think that's about it.