Drupal 7.x

Hi all,
I have a heavily Dojo-ed (Dojo Toolkit) webpage that want to turn it into a Drupal module. But drupal does not seem to support Dojo. What's the right way to load dojo into drupal?

1- Does my page work if I simply load dojo .js files inside my module?
2- If not, is there a certain way to load dojo into drupal pages?
3- As jQuery will also be loaded for drupal client-side activities, will there be any conflict between Dojo and jQuery on the client side?
4- Is there any sample drupal module that uses Dojo?

Thanks
Navid

So I have a module that adds a new field type to the database. The field consists of two things, a bonus category which is just the ID of a taxonomy term, and a bonus amount, which is an integer. Everything works fine, but I'd like to change the field entry form to something a little less default. I followed the code given in the poll module, and it seemed to me that I had to do three things:

1. Add (hook)_theme
2. Add template_preprocess_(some_name)
3. Add a template

The trouble I'm having is that template_preprocess is never called, so my template is never used. I suspect that I'm missing something, like how to tell Drupal that my widget is themed. Can you spot what I need? Here's my module info, code, and template:

category_bonus.info

name = Category Bonus
description = "Creates a custom field for entering and displying project bonus data for categories."
package = Fields
core = 7.x
files[] = category_bonus.module
php = 5.2

category_bonus.module:

<?php

/**
* @file
* A category bonus field using the Field API.
*
*/

/**
* Implements hook_theme().
*/

function category_bonus_theme() {
dpm("category_bonus_theme called");
return array(
'bonus_entry' => array(
'template' => 'bonus-entry',
'render element' => 'form'
)
);
}

Not sure if this question fits here, and I'm not a programmer so I don't know what should I do to fix this.

I added the simple "Magic line" effect to menu but it's causing problems in Admin interface. Button doesn't open inline settings: http://screencast.com/t/HxTs3ZLlT

Firebug shows error:

$("#main-menu-links .active a").position() is null
http://rosic.lan/sites/default/themes/green_carbon/scripts/jquery.magic-...
Line 16

Screenshot of console is here: http://screencast.com/t/im1NKS025gJ9

Code is included with scripts[] = scripts/jquery.magic-line.js

(function ($) {

Drupal.behaviors.magicLine = {
attach: function(context) {

// Lava Lamp Meny Effect

var $el, leftPos, newWidth,
$mainNav = $("#main-menu-links");

$mainNav.append("

");
var $magicLine = $("#magic-line", context);

$magicLine
.width($("#main-menu-links li.active").width())
.css("left", $("#main-menu-links li.active a").position().left)
.data("origLeft", $magicLine.position().left)
.data("origWidth", $magicLine.width());

$("#main-menu-links li a").hover(function() {
$el = $(this);
leftPos = $el.position().left;

Theme used: Genesis.

I've been struggling with this for the past few hours and am extremely frustrated and my "newness" is showing through.

How do I disable the "readmore link” to allow a full posting to show and then make the link invisible. I actually made the link invisible, but because of it not being disabled my post also disappeared and I was not able to view it. This is for the front page of a website.
All help appreciated, and thanks for your patience.

Thanks in advance,

PChuprina

While logged in as Admin, in Drupal 7, when you click on a menu option on the Administration Bar (top black bar).. it opens up a framed menu/window.

What is that window called?

Can that be adopted to a module that takes over the login functions which would allow the user to click the Login link, then a small (configurable size?) pop-out login window would appear?

Is this pop-out window functionality only in the Drupal 7 code?

Say you have a large, three year old Drupal 6 site with 10,000 nodes and close to 100,000 comments spread out over 10 content types, including a couple of forum content types. And all those content types are configured to have threaded comments, with 300 comments per page (the maximum). Because pagination on threaded comments suck (the links to and theming for new comments get broken), my current practice is to close comments right before a thread hits 300, and start a second thread.