Peter Rust wrote:
I see where you're coming from, but my sentiments are that it is a needed
bit of stretching. The iUI framework (as it stands) doesn't "play very nice"
with other frameworks
In my experience iUI plays well with other JavaScript frameworks at the
code level, but...
or with previous code that wasn't written with iUI in
mind
... it does assume a certain structure to your pages that you will
typically be creating from scratch. It also works really well for sites
that have clear separation of content from presentation using a
template-driven approach (so you can create an entirely new set of
templates for iUI)
This is what some call a "convention over configuration" approach and
is, I believe, a major selling point of iUI. jQTouch uses the same
approach. Neither framework (correct me if I'm wrong about jQTouch)
really supports adding itself in to an existing page.
Creating the iScroll integration and iPad integration has forced the
codebase to do a little much-needed maturing so it can handle some of these
situations (and it still needs some more maturing).
This is absolutely true. By the time iUI fully supports iScroll and
iPad it will be much more flexible. One of the big changes will be to
no longer require that all iUI views (aka "pages" or "fragments") be
direct descendants of the root.
I do agree that we should separate the code that iPad-specific (and
iPhone-specific, if there is any). Segregating the code in this way
(separate classes or a function prefix or something) would be smart both for
device optimization (no need to send iPad-specific code to the phone) and
for code organization (single-responsibility principle).
I'm not sure it is going to work out that way or if that is desirable.
Sometimes an "if" is all you need and creating separate classes or
functions is overkill. There may be some CSS that is iPad/tablet
specific that could be placed in a separate file -- but let's see how
many lines it is first. At one point it was suggested to put Mozilla
(-moz) CSS in separate files. I tried that and quickly decided it was
much more of a hassle than it was worth and rolled the -moz stuff back
in to iui-css.
But this is an implementation detail and something we can look at once
we have a working "dev" level release. Beyond the 0.40 release we might
do some restructuring/refactoring of the iUI core and I'm very open to
suggestions on how to do that, bu that again is a topic for the
iui-developers list.
-- Sean
--
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en.
