user interface

TITLE: Web Developer (LAMP/Drupal)
COMPENSATION: Fair market price.
TERM: Part-time, flexible schedule, potential for full time, work at home.

DESCRIPTION: We are looking for a self-motivated, reliable, responsible web developer who takes their work seriously, is obsessed with clean, well-commented, rock solid code, and who has an excellent work ethic. Should have superior skills in a Linux environment, an astonishing ability to be present online seemingly at all times (at least during business hours), willingness to respond quickly, and a proactive attitude. Must play well with others.

I run a group of tech entrepreneurs called Ultra Light Startups (http://ultralightstartups.com/) and I'm interested in the use of Drupal in startups for several reasons. Many of our members' startups are either already built on Drupal or they are evaluating use of Drupal for a project. Several of our members are also active in the NYC Drupal community. Also, after hosting an event on Open Source CMS's last fall, I became convinced that Drupal was the right platform for several of my own projects, including a planned major upgrade to the Ultra Light Startups site.

Is anyone aware of a good guide for creative agencies with regard to creating user interfaces/web site designs that are easly implemented with drupal?

We’re looking for a great Drupal developer to join our fast-growing team. The role will focus on coding the user-interface; with opportunities to contribute to innovative module development too.

Primary Responsibilities

Development of innovative web user-interfaces on Drupal

We’re looking for someone with experience of…

• Drupal (6x is ideal, 5.1 ok), PHP, MySQL development experience – must be able to reference deployed projects and detail involvement on each project
• Extremely proficient in AJAX and JQuery

Hey gang,
started today on an idea for a new idea for the future of the interface of quiz creation. The current problem is that the interface for quiz right now is really hard to follow and complicated for most users. Result Options are unclear. No body can figure out how to create a personality quiz, etc. This is a first attempt to make the interface much easier to use. And much more straightforward. So far this is basically an idea, and not a reality, but feel free to post your ideas. I can't tell you a timeline on this as my time is very limited, but here is my initial idea for a new interface.

This is only the first few steps, there is more to come.

Step 1: Quiz Creation - The initial create quiz node
Step 2a: Scored Quiz Options (simple summaries) - The default view for scored quizzes
Step 2a: Scored Quiz Options (advanced summaries) - The view that is seen when advanced summaries is checked for a scored quiz
Step 2b: Personality Quiz Options - The default view for a personality quiz
Step 3: Not done yet... More to come

.

.

As some of you know, I've recently taken over maintenance of Inline and Image Assist, and initiated the Wysiwyg project. That was not only caused by personal interest, but also to take the necessary steps to realize the long awaited Inline API. You might ask yourself, what those three modules have in common or to do with each other at all: They deal with user input, allow to embed complex contents into a content, and provide an interactive GUI for that. If you already had the chance to work with them, you already know that there is a rather hidden, non-obvious hard-dependency between them.

Although I'd really like to discuss both topics (Inline and Wysiwyg support) separately, the gained experience on these topics enforces us to discuss them concurrently. The following mockup hopefully explains why: (see attachment to view in full size)

One of my main problems with Drupal UI was the module install page. The checkboxes are very small, especially considering that is the interacting part in the form, and there is way too much information in the description column. The length of the list is another issue too.

To solve the first pair of my problems i added some minimal hacking to system.module, and created a script that checks the module checkbox when the row of the module is clicked. I attach the screenshots, javascript and diff file for Drupal 5.3. What do you think?