or push admin UI might use" vs stuff we recommend to end-users via our
quickstarts, ticketmonster, JBoss Tools palettes, etc.
I care deeply about the later, less so about the former. :-)
For the later, we must have a recommended UI component/widget set.
On Jul 9, 2013, at 10:39 AM, Kris Borchers wrote:
On Jul 9, 2013, at 8:42 AM, Hylke Bons <hbons(a)redhat.com> wrote:
> Hi,
>
> I can't judge the implementation or performance. I'll take people's word
on that, though I don't think it's the most important thing.
On mobile, performance is one of the most important things both in terms of perceived
performance from the user (i.e. does this app "feel" fast and react to my
interaction appropriately) and actual performance (i.e. draining the battery). That will
be more important than having a fancy menu or a date picker any day.
>
> The default style will be overridden with our own, no matter what framework we'll
be using. So style is irrelevant here really. I agree that people should stop using the
Bootstrap style everywhere, it looks lame (but the same can be said for Topcoat once it
gets adopted more).
>
> I've downloaded Topcoat and had a look inside. I don't see any components,
just a few simple element stylings.
What components do we (AeroGear) "need" that we can't just use a little
plugin for or roll our own? I feel like a base of some nicely styled native components is
perfect, not to mention much leaner.
> If that all Topcoat is, it probably makes more sense to do all the CSS custom, as it
will be almost as much work as retheming everything and there's not really a
point having a CSS framework at all then.
This makes no sense to me. Topcoat has a complete, and easy to use theming system based
on Stylus and built with Grunt. You change a few variables for colors, font sizes, etc.,
then add some of your own custom styles on top to make it your own.
> We can grab our missing components from Bootstrap (or something else), and make some
components from scratch where the Bootstrap components are suboptimal.
>
> So the style elements being equal, I think Bootstrap would give us a head start due
to a better selection of components that we need. So I want to vouch for that one.
I think a selection of components is one of the least important items on the list in
terms of what AeroGear needs as a project.
>
> Thanks,
>
> Hylke
>
>
>
> On 08/07/2013 21:55, Matthias Wessendorf wrote:
>> If Luke/Kris want to use Topcoat for a good number of reasons, I am +9001 on
that.
>>
>>
>>
>> On Mon, Jul 8, 2013 at 9:34 PM, Kris Borchers <kris(a)redhat.com> wrote:
>> Topcoat is a nice and clean CSS framework.
>>
>> Bootstrap is a messy framework dirtied by some half-assed JS based widgets that
don't work well in most cases.
>>
>> The few widgets we may need could probably be done with pure CSS, or a small
jQuery plugin. No need for the bootstrap mess. Also, every site using bootstrap, for the
most part, still looks like bootstrap and that's annoying.
>>
>> On Jul 8, 2013, at 2:24 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
>>
>> > I'm not a UI specialist, but I do like Topcoat
>> >
>> > Lucas Holmquist wrote:
>> >> Starting a new thread for this:
>> >>
>> >>
>> >>> I would like to reboot the discussion of css frameworks
>> >>>
>> >>> the 2 that are in question are bootstrap and topcoat.
>> >>>
>> >>> i would like to here why one is "better" than the other.
or why the
>> >>> preference.
>> >>>
>> >>> Ready, Go.
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev(a)lists.jboss.org
>> >>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> > --
>> > abstractj
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev(a)lists.jboss.org
>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog:
http://matthiaswessendorf.wordpress.com/
>> sessions:
http://www.slideshare.net/mwessendorf
>> twitter:
http://twitter.com/mwessendorf
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev