Re: A Responsive Single Page App (SPA) with 3 Issues to Consider

[Booth Martin <booth@xxxxxxxxxxxx>]

My example was written without a code generator.

I understand the point about being responsive and was clear that what I 
was showing was only a starting point.

I just went back and looked at Nathan's example.  I had had my pane too 
narrow and the menubar was not visible.  I see it is set to nowrap and 
uses a 3-bar button on the upper right corner when too narrow.  Since a 
hover didn't drop the menu or display a tooltip, I didn't pick up on 
that element being a clickable image - it looked like a part of the blue 
bar background image.

The severe design limitation I see with a fully responsive solution is 
that the site design is severely limited if there is going to be a 
one-solution-everywhere requirement.  This, to me, is a designer issue, 
not a programmer issue.

As to JQuery... I have no issues with that as a tooling solution.


On 7/13/2015 11:54 PM, Bradley Stone wrote:
> I agree with Nathan here.  I don't see any comparison with your example.
> Was it generated by a WYSIWG tool?
>
> How is using jQuery like building a typewriter?
>
> Brad
> www.bvstools.com
>
> On Mon, Jul 13, 2015 at 11:43 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
>
> > > Would the following be a far neater and more standard starting place?
> > > http://martinvt.com/Menu
> >
> >
> > It has some cool gradients, but is otherwise non-functional.
> >
> >
> > > I understand the concept being pursued but it seems to me that ignoring
> > > the simple tools that are available to us is kind of like writing an
> > essay
> > > on world peace where the first step is to build a typewriter.
> >
> >
> > Again, without you showing us something that is functional, it is hard to
> > compare. You may have a point; a simpler menu perhaps. But it's not readily
> > apparent.