
Yes I am more concerned with getting the content right [so I can test code that handles the 'submit' buttons] before I worry about a layout.
There is another field to fit on there, which is the 'Ride name is Like' text box.
Although it now fits on one page I have lost some functionality compared with the existing Exchange.
- There are only 3 sort criteria [just above submit buttons]
- It's not possible to filter on 'ranges' of values [For example you can currently filter on excitement being 'less than', 'greater than' and 'between'. This will no longer be possible.
- There are all sorts of possibilities for producing combinations of 'wrong' filters. [The existing exchange prevents this from happening, as you navigate between screens]. For example, I could say that I didn't want to have any RCT1 rides in my searches, but leave all the rides types [including RCT1 rides] selected. I will probably handle this in code by warning users about 'weird' combinatons that they choose, what I have done to get rid of the 'weirdness', but still try to find some results. Essentially, this will mean 'ranking' the filters to decide which take precedence, and I may need to take that into consideration when deciding the final layout of the screen.