by jbardi » Sat Sep 05, 2009 11:28 am
tarnfeld, I don't understand. You said in another post that you are a mod on the iWebkit forum, yet you keep posting questions about interface objects that we have already discussed as being best achieved by using either iWebkit or iUi. If you are a mod on their forum, why on earth are you not using iWebkit but instead you expect the Nimblekit team to keep including redundant interface objects that are more easily implemented with existing projects?
What you are talking about is part of the Tableview style referred to as the classic list view, only inside individual white, rounded bubbles instead of being the full width of the screen. These types of interface objects are not going to be implemented into Nimblekit as they would be too limited in their visual style, while using the CSS files and image files from iWebkit or iUi gives you more freedom to display them how you like, such as Music View and Store View which would display with thumbnails and descriptions or standard Classic List view like you are looking for.
Honestly, the majority of the Interface with Nimblekit should be achieved through straight HTML and CSS and not by using a whole slew of custom Nimblekit created objects. That would only serve to make Nimblekit bulky and too large to implement into every project without manually removing references to objects you are not useing from the javascript file to slim it down for each separate project.
Nimblekit should be a functional, light weight API to access features of the iPhone, not a recreation of the Interface Builder of XCode. All of these visuals can be achieved very easily without having to add buttons and lists and checkboxes and all of this bloated code inside of the Nimblekit libraries.
I personally do not even us NKButton, nor do I really think it should have been included, as I see it as a duplication of an HTML form button that is better styled through CSS rather than as a static object.
