add a jump menu field populated from a sql list

You can look at the code here...

http://drupal.org/node/34237

But that is plain code. It would be better in a field with a structure...

Field label:
Description:
Query Table :
Select fields (at least one):
Add search conditions (body of the "where" clause):

Or Do a "query by example" (wildcard: "%")
Field Type Operator Value

Required field
Show in teaser
Show in table

Theses fields where taken from phpMyadmin... do a search and you will see :)

Comments

Bèr Kessels’s picture

Bèr Kessels commented
Priority: Normal » Minor

I don't understand at all what a "jump menu" is, nor why we would want to have it.

stevryn’s picture

stevryn commented

I think..and I may be waaaaaaaaaaaaay off, what they are looking for is a way to limit "results" using a drop down menu (jump menu)

In other words, I have a flexinode content type called "Tasks".

I would like to have a page, that lists ALL the submitted "Tasks", and then, be able to select from my "jump menu" to limit it to whatever is in that dropdown, for example, in my case I would like it to be users.

The dropdown (ie jump menu) would be populated by another table, in my case... users.

I have been looking for a way to do this, but instead of a page, using the flexinode "table view". I think being able to limit the results of that table could prove to be an invaluable feature!

Bèr Kessels’s picture

Bèr Kessels commented

I still don't get what a "jump field" is. Can you not give an example URL or a screenshot?

alexandreracine’s picture

alexandreracine commented

Hi Bèr,

here is a example of a jump menu.
http://javascript.internet.com/navigation/jump-menu.html

This one is a simple one, with only 2 choices.

A real world example would be to have ....mmm.... a list of different Drupal websites (in alphabetical order) and the jump would go to the node describing the website.

Bèr Kessels’s picture

Bèr Kessels commented

Ah those. Those are considered extremely bad usability and break on a lot of browsers.

But okay,
* Why do we need this in /flexinode. This belongs in a theme. Or even a contrib module.
* How do you plan to use this in flexinode.

stevryn’s picture

stevryn commented

Ahh so I was way off! :)

Thanks for the example alexandreracine.

It seems like that it would be just as easy to have a "collapsible menu" to take care of cluttering a page...

alexandreracine’s picture

alexandreracine commented
Status: Active » Closed (fixed)

But okay,
* Why do we need this in /flexinode. This belongs in a theme. Or even a contrib module.

I think you are right, this is something that would be better in a theme.