Bill Keese | 1 Nov 2005 01:42
Picon

Re: Re: Portlet like widget

>
> It's movable and resizable?  I looked at the floating pane test html page and 
> it's not movable and resizable.  I am talking about moving it like the a 
> DragMoveSource and resizing it by dragging the corner of the pane.
>   
Try this link:

http://archive.dojotoolkit.org/nightly/tests/widget/test_ResizeHandle.html

You can move it by grabbing the blue title bar, and draggable from the 
bottom right striped triangle thing.

>   
Bill Keese | 1 Nov 2005 01:43
Picon

Re: The weird behavior of nested DragMoveSource

>
> I want to be able to move the children of an element freely inside the parent 
> element but not outside of it.  Please let me know if I am missing some widget 
> that does that already.  From the code, the floating pane looks like it may do 
> that, but I haven't gotten it to do it.
>   
Yeah, that's the floating pane, and it's demonstrated on the demo page.  
The inner floating pane can't move outside the outer floating pane.

http://archive.dojotoolkit.org/nightly/tests/widget/test_FloatingPane.html

>   
Bill Keese | 1 Nov 2005 01:48
Picon

Re: HtmlComboBox

>
> morning as the last nightly snapshot to include HtmlComboBox.js is 10-27-05. 
> Does anyone know why this is??  Thank you again.
>   
Hmm, that's strange.  The file still appears to be in SVN.  At some 
point the file contents will be split into widget/Combobox.js and 
widget/htmlCombobox.js, but not yet, apparently.  So it should be 
working...
>   
Bill Keese | 1 Nov 2005 01:52
Picon

Re: Portlet like widget

Ah, I see.

I'd like to use the toggle stuff in my widgets too, so when I get a 
chance I will move it to Widget like you suggested.

Jason Carreira wrote:
> It depends on how you use it. Check out the way the tree uses it. The 
> body of a tree node (which includes all of the child nodes) can be 
> toggled open and closed, but the title (which includes the icon that's 
> clicked for opening and closing) is not hidden. It's all in how the 
> template is defined and the DOM nodes wired...
>
> On 10/31/05, *Bill Keese* <billk <at> beacon-it.co.jp 
> <mailto:billk <at> beacon-it.co.jp>> wrote:
>
>     That's probably a good idea, but I'm not sure what it has to do with
>     Portlet stuff.  Are you saying that minimize-window can be implemented
>     using the toggle stuff?  I thought the toggle stuff makes the element
>     completely disappear, which is different than minimizing it... or
>     did I
>     miss something?
>
>     Jason Carreira wrote:
>     > I'd like to suggest that the Toggle stuff I put into the tree widget
>     > be made top level and make any / all widgets able to be toggled like
>     > this. You can then specify the toggle type between "wipe",
>     "fade", and
>     > "default" (which just does display=block|none). Then widgets which
>     > want to make that functionality available to users can just show a
>     > button which is linked to the toggle method.
(Continue reading)

Martin Cooper | 1 Nov 2005 02:04
Picon
Favicon

Re: The weird behavior of nested DragMoveSource



On 10/31/05, Bill Keese <billk <at> beacon-it.co.jp> wrote:
>
> I want to be able to move the children of an element freely inside the parent
> element but not outside of it.  Please let me know if I am missing some widget
> that does that already.  From the code, the floating pane looks like it may do
> that, but I haven't gotten it to do it.
>
Yeah, that's the floating pane, and it's demonstrated on the demo page.
The inner floating pane can't move outside the outer floating pane.

http://archive.dojotoolkit.org/nightly/tests/widget/test_FloatingPane.html

Doesn't work at all on IE. ;-(

--
Martin Cooper
 

>
_______________________________________________
Dojo-interest mailing list
Dojo-interest <at> dojotoolkit.org
http://dojotoolkit.org/mailman/listinfo/dojo-interest

_______________________________________________
Dojo-interest mailing list
Dojo-interest <at> dojotoolkit.org
http://dojotoolkit.org/mailman/listinfo/dojo-interest
Bill Keese | 1 Nov 2005 02:09
Picon

Re: The weird behavior of nested DragMoveSource

>
>
> [Floating pane] Doesn't work at all on IE. ;-(
>
Ah, that explains the confusion.    OK, that floating pane stuff is not 
my code, but I'm modifying it now anyway, so let me see if I can fix 
that.  In the meantime, try it in firefox.
Marius Hanganu | 1 Nov 2005 03:11
Picon

Re: Context menu

Tested your fixes. It works quite neat now.

One small exception though: tried the following:

<div dojoType="contextMenu" targetNodesId="test2"><!--Note no spaces between nodeIds-->
  <div dojoType="menuitem">
     <img height="15" align="middle" src="images/fisheye_1.png"> Item 1
  </div>
  <div dojoType="menuitem">
     <img height="15" align="middle" src="images/fisheye_4.png"> Item 2
  </div>
</div>

<div dojoType="contextMenu" targetNodesId="test1"><!--Note no spaces between nodeIds-->
  <div dojoType="menuitem">
     <img height="15" align="middle" src="images/fisheye_1.png"> MENU2-Item 1
  </div>
  <div dojoType="menuitem">
     <img height="15" align="middle" src="images/fisheye_4.png"> MENU2-Item 2
  </div>
</div>

And what I get is both menus displayed - when clicking on one after clicking on the other. Maybe all the other dojoType="contextMenu" should be made invisible.

Nice job, I will definitely use it in my projects
Marius

Fredrik Johansson wrote:
måndag 31 oktober 2005 06.50 skrev Marius Hanganu:
Yeah, attaching context menus to specific dom nodes is a MUST. Besides that, I also added a ticket about context menu getting out of the page: http://dojotoolkit.org/trac/ticket/179
Well I worked on my file ContextMenu.js in the html folder a bit more. You can test position changed code on: http://www.vaxjorc.com/Test/test_dojo/dojo/tests/widget/test_ContextMenu2.html and node connect code on: http://www.vaxjorc.com/Test/test_dojo/dojo/tests/widget/test_ContextMenu1.html The bug that made context menu disapear as soon as I released right mousebutton in Konq is also fixed, at least it works on my machine. / Fredrik Johansson
Fredrik - I also tested your patch in Firefox 1.0.7 and it doesn't seem to be working. Regards, Marius Fredrik Johansson wrote: söndag 30 oktober 2005 18.02 skrev Alex Russell: On Sunday 30 October 2005 3:32 am, Marius Hanganu wrote: Hello, In dojo 0.1 it seems that the context menu is not working. Any ideas on how can I make it work? (tried Firefox and IE) Yeah, there are a lot of b0rken widgets in the 0.1 package. Give one of the nightlies a try, and if it's not working there, please file a bug against the 0.2 release. http://archive.dojotoolkit.org/nightly-profiles/ Regards Funny, I was just about to post bugfix for ContextMenu that makes it work in konqueror and it allows you to set contextmenu to specific dom nodes, not just the hole page. It still is a bit buggy in Konqueror, you need to hold right mousebutton down for half a sec for it to stick, but I thought that was better than no contextmenu att all. For the changed files go to http://dojotoolkit.org/trac/ticket/180 Hope find the changes useful. / Fredrik Johansson _______________________________________________ Dojo-interest mailing list Dojo-interest <at> dojotoolkit.org http://dojotoolkit.org/mailman/listinfo/dojo-interest
_______________________________________________ Dojo-interest mailing list Dojo-interest <at> dojotoolkit.org http://dojotoolkit.org/mailman/listinfo/dojo-interest

_______________________________________________
Dojo-interest mailing list
Dojo-interest <at> dojotoolkit.org
http://dojotoolkit.org/mailman/listinfo/dojo-interest
Kamen Vitanov | 1 Nov 2005 04:15
Picon

Re: keyboard support

I agree that as a first step one action per key would be enough. But I suggest to leave the doors open for KeyDown and KeyUp events. If one wants to provide some more sophisticated keyboard control - like moving objects using the keyboard or some smart scrolling though multiple items - then they'll need KeyDown and KeyUp events.
 
Kamen

 
On 10/31/05, Tom Short <tshort <at> eprisolutions.com> wrote:

Most dhtml/ajax apps have poor keyboard support (one exception is
jotlive.com ). A number of dojo widgets are just crying for keyboard
usage (menus, the new tree widget, ...). Better keyboard support would
also help with accessibility. One thing that would make things easier
is to have better toolkit keyboard support, and dojo's event system
seems like it would be a good fit for that. In my own app
(www.rpad.org), the keyboard code is quite a pile of spaghetti. Dojo
does have some keyboard improvements already, such as being able to do
e.KEY_LEFT_ARROW, but I think more is needed. From the toolkit user
point of view, I would like to be able to do something like the
following when defining a widget:

dojo.require("dojo.keyboard.*");

dojo.keyboard.bind(this, "UP", moveUp)
dojo.keyboard.bind(this, "DOWN", moveDown)
dojo.keyboard.bind(this, "Ctrl-C", doInterrupt)
dojo.keyboard.bind(this, "F9", doCalculate)

If you want to remove some key event, I suppose that would be:
dojo.keyboard.remove(this, "F9")

I think you'd only want one action per keypress.

This would be much easier than messing with keypress/keydown/
keyup. The keyboard routines would need to handle the different
Alt/Ctrl/Shft key modifier combinations.

Does anyone have some tips on where to start to develop this sort of
functionality (for an amateur)? How about any roadblocks?

Some steps that I think are needed are:

* Install a keypress event.
* Keep a table of "active keys".
* Parse the keyboard entries to populate the table.
* Have the onKeyPress handler look up on the table of active keys.

Any suggestions or code that might be useful?

- Tom


_______________________________________________
Dojo-interest mailing list
Dojo-interest <at> dojotoolkit.org
http://dojotoolkit.org/mailman/listinfo/dojo-interest

_______________________________________________
Dojo-interest mailing list
Dojo-interest <at> dojotoolkit.org
http://dojotoolkit.org/mailman/listinfo/dojo-interest
Bill Keese | 1 Nov 2005 04:16
Picon

Re: The weird behavior of nested DragMoveSource

OK, try it now (from SVN head).  I think I got it all working.  Plus I 
added a simple drop shadow effect.

Bill Keese wrote:
>>
>>
>> [Floating pane] Doesn't work at all on IE. ;-(
>>
> Ah, that explains the confusion.    OK, that floating pane stuff is 
> not my code, but I'm modifying it now anyway, so let me see if I can 
> fix that.  In the meantime, try it in firefox.
> _______________________________________________
> Dojo-interest mailing list
> Dojo-interest <at> dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-interest
>
>
Alex Russell | 1 Nov 2005 04:29
Favicon
Gravatar

Re: The weird behavior of nested DragMoveSource

On Monday 31 October 2005 7:16 pm, Bill Keese wrote:
> OK, try it now (from SVN head).  I think I got it all working.  Plus
> I added a simple drop shadow effect.

Wow.

If you guys don't slow down, we'll have a full-blown component library 
before 0.2. Then what'll we do for 0.3?

;-)

--

-- 
Alex Russell
alex <at> dojotoolkit.org BE03 E88D EABB 2116 CC49 8259 CF78 E242 59C3 9723
alex <at> netWindows.org  F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46

Gmane