[mochikit] Re: MochiKit Development
On 18 juil, 17:16, Jason Bunting [EMAIL PROTECTED] wrote: I *am* curious as to the effort to get us to an official '1.4' release - seemed like there was a bit of momentum a few weeks/months back to get all bugs fixed and get it shipped, but then it seemed to die. It's all about voluntary work, so anything can happen :). Anyway I closed 2 bugs and did a bit of cleaning tonight. There's still one issue (http://trac.mochikit.com/ticket/248) but I don't manage to reproduce it and it doesn't seem very important. I also moved Controls.js out of trunk, in the autocompleter branch, until someone decides to revive it. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: onmouseleave and Firefox
On 29 mar, 13:59, Darren Beale [EMAIL PROTECTED] wrote: Hi When the mouse leaves an element which is next to the edges of the browser - so it leaves both the element and the window at the same time - it looks as if onmouseleave is not triggered in Firefox. Seems OK in IE/Opera. Is this a known issue? If so is there a workaround? You have to use 'onmouseout'. MochiKit will then take care of making it works everywhere. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Future of MochiKit
On 2 mar, 04:39, Karl Guertin [EMAIL PROTECTED] wrote: On 2/28/07, Bob Ippolito [EMAIL PROTECTED] wrote: (e.g. I don't currently use anything in DragAndDrop, Sortable, or Visual) so it's harder to know what the overall status of everything is and it makes it harder for me to confidently do a release. The amusing thing about this is that you're listed on the blame for the majority of the lines in these files, though I know Thomas maintains them. I guess that mainly comes from automatic changes (like the id* stuff) or the merge itself. Not that I want to claim any proud for this code :). I was one of the people pushing for Scriptaculous stuff to be included, but a year later I no longer feel that the Scriptaculous implementations are the best approach to the problems they solve*. There would be little love lost from me if they were dropped from the framework and turned into an extension. * yui/yui-ext (preferring yui-ext) is my favorite solution for widgets and I like animator for animation. Yes, today animator is a *great* solution, especially for doing custom effects. Scriptaculous is very useful if you just want to put a quick effect, and that works well (be fair, very well for me, with lots of feedback from different browsers). Unfortunately the API is not so good. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: element positioning, fixed only?
On 15 fév, 08:15, iain duncan [EMAIL PROTECTED] wrote: are the get/setElementPosition functions intended to be used only with and within fixed position elements? I am getting very different behaviour between firefox and ie6 if any of the elements are absolute ( container or the moving elements ). Is this the correct behaviour? And if so, is the recommended procedure to just used fixed position for everything in the document? I don't think you meant 'fixed'. Fixed position doesn't even work under IE. getElementPosition should give you the absolute position of the element in the page. If not it's a bug. setElementPosition is a bit tricker because it's intended to be used on absolute positioned elements. The documentation could be clearer on this. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Visual.Move
On 8 fév, 12:40, Aaron Faanes [EMAIL PROTECTED] wrote:
In Visual.Move.prototype.setup, there's the following (line 869)
var s = this.element.style;
var originalVisibility = s.visibility;
var originalDisplay = s.display;
if (originalDisplay == 'none') {
s.visibility = 'hidden';
s.display = '';
}
// some code that doesn't change originalDisplay
if (originalDisplay == 'none') {
s.visibility = originalVisibility;
s.display = originalDisplay;
}
So there's no real change.
That was the intended behaviour. If I remember correctly (I should
have made a comment :/), elements with display:none are not positioned
in the document, so left/top are 0. By using visibility:hidden, the
element is repositioned in the document and you can get a value for
left/top.
So yes, it's dumb, but it's actually useful :).
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
[mochikit] Re: problem with Effect.fade (opacity) in IE7 with scriptaculous, test included
mwaschkowski a écrit : Ya, that works great, problem is gone (so there IS a problem with Mochikit's $ function clobbering Prototype and impacting scriptaculous). Or there's a problem with scriptaculous using $ function. It depends of the point of view :). The best way to handle this is to set MochiKit.__export__ to false (unless there's a side effect, but it should do the trick). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Regressions in MochiKit.Sortable
Peter Russell a écrit : Hi, Hi, I've been using MochiKit.Sortable for a web page, There seems to be a bug with these sortables - but that's not the bug I'm writing about. It'd be great to have some details about this :). In trying to produce a test case to demonstrate the problem, I updated the SVN version of MochiKit. Unfortunately I don't have a record of the version I had been using before. There seem to be some regressions in the intervening time. There's no tests for Sortable unfortunately. It makes regression more likely to happen. Using the code below, in IE 6 (running under Wine) elements can be dragged, but not dropped, also dropping on the empty list does not work. I don't reproduce the problem with dropping in the full list (it works for me under IE/Firefox). For the empty list problem, well, the problem is that it's empty: you should use css to set a minimum height, otherwise you can't point the zone with the mouse. A couple of other bugs: The Sortable documentation lists Effect as a dependency, but it does not exist, and Position is a dependency of Visual, but is not listed as such. Thanks, it has been corrected. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Drag and Drop
SanderElias a écrit :
Hi,
Hi,
1. on a successful drop, the draggable does a revert. I only want a
revert, when it's dropped outside an dropzone.
To do this, just remove the element in your ondrop function.
2. Somehow connecting to the draggable fails.
connect(aDrag[x],onstart,function(){log('dragging!!');})
//connect(aDrag[x],start,function(){log('dragging!!');}) //did
not work too
//connect(lis[x],onstart,function(){log('dragging!!');})//did
not work too
//connect(lis[x],start,function(){log('dragging!!');})
//did not work too
The signals generated are generated on the Draggables
(MochiKit.DragAndDrop.Draggables). You connect to it *one* time for all
your draggable items. You'll get the draggable as first argument.
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
[mochikit] Re: Drag and Drop
SanderElias a écrit : Hi Thomas, Tanks for the quick reply You're welcome. 1. on a successful drop, the draggable does a revert. I only want a revert, when it's dropped outside an dropzone. To do this, just remove the element in your ondrop function. but I'm moving it to a new parent, would that not remove that too? Or do I have it backwards, and to I have to set the new parent/owner by hand? OK forget what I said. You'll have to do something trickier. I see two options: * personalize the reverteffect option to do the revert only when you want * the other is not documented: you can pass a function to revert, that takes the element as argument and returns whether it should be reverted or not. Hint: to make this work, connect to the end signal on Draggables, and change the class of your element. Then in your revert function check the value of your element class. 2. Somehow connecting to the draggable fails. The signals generated are generated on the Draggables (MochiKit.DragAndDrop.Draggables). You connect to it *one* time for all your draggable items. You'll get the draggable as first argument. this did the trick! :) Great :). Don't hesitate to say if the documentation is not clear on that part. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Some news from the VIsual front
Jason Bunting a écrit : I had a comment/question: The puff, squish, grow and shrink effects all change the font size to make it looks like the text is being affected in the same way as the container thereof - sometimes the overall effect is not so smooth because the text starts to wrap differently as the container changes size. I don't know what, if anything, can be done about that, but I do wonder if it would be possible to pass an additional parameter to these to turn off the font scaling. Basically, I want to have the effect on the container, but not the text/elements within it, just like the fold effect, for example. Does any of that make any sense? Yes, it does ! There's a scaleContent option in the Scale class, I've made it available in puff/shrink/grow in revision 1242. I hope it's that you needed. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Some news from the VIsual front
Hi, I've added a new full-featured example of Visual effects in the trunk, with the MochiKit site style: http://mochikit.com/examples/effects/full.html. Among others, it shows the new Morph effect adapted from Scriptaculous (with some differences). Every feedback will be welcome :). Thanks, -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Calling the rounding function after the page has loaded
The first problem I see is that you call roundClass with the option border at true, whereas it takes a color as argument. It should be in the documentation though. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Calling the rounding function after the page has loaded
[EMAIL PROTECTED] a écrit : Thomas Hervé wrote: The first problem I see is that you call roundClass with the option border at true, whereas it takes a color as argument. It should be in the documentation though. No, the documentation says that the default value for border is false. That would indicate it is a boolean value, not a color string. Yes, that's what I meant: the documentation isn't clear on that point. But it *is* a color expected. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit.Position.cumulativeOffset and the scrolling DIV
Martyn Smith a écrit : [snip] Can anyone see a better way of dealing with this? You could call realOffset and make the substraction. It should do the trick. and what are the chances we could include this patch in upstream MochiKit.Position? If you can provide an example showing your problem, relatively high :). I'd be particulary interested if you can show an example with DragAndDrop. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: insertSiblingNodesBefore question
My guess is that it has nothing to do with insertSiblingNodesBefore. Where's your rowCount variable ? Does your table has an initial line ? Try to reduce it to a full reproductible example. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Forcing animations to finish
You should look at the scope notion in Effects, and the ScopedQueue class. You probably only have to add the option 'queue', and set the scope to 'global'. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: setOpacity not working in new revision
Not working is not a information precise enough. What's your problem exactly ? Under which browser ? For me it works perfectly. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Color.fromBackground broken in IE 7?
I checked in a workaround in revision 1225. Can you verify it corrects your problem ? Thanks. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: mochikit cache prevention
Diez B. Roggisch a écrit :
So - is there any chance such a thing could be made (optionally) part of the
Async-package?
If a patch is provided, why not. Until then, you have several options:
* define the cache control in your web server (with pragma no-cache and
cache-control).
* Add an argument to loadJSONdoc(): loadJSONdoc('http://toto',
{'no-cache': new Date().getTime()})
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
[mochikit] Re: How to automatically init start a Draggable object?
Kevin Kaiser wrote: Assuming you MochiKit.Signal.connect() an event to an element, how do you then programmatically create the custom event object, set its parameters and then use it to signal the DOM element via MochiKit.Signal.signal() to fire the event and pass the custom event object to the connect()'d function? I think you take the problem from the wrong side. Drag an item without the mouse is not dragging, it's just moving. I'd try with Visual.Move. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: Problems changing label's text when using HTTPS
Jorge Godoy wrote: It was a valid URL and the code was perfectly fine. It worked when using only HTTP (development server) but not on HTTPS (production server). I changed the HTML element to an input field and the code ran perfectly. As a solution to this problem I: - changed from .innerHTML to .value (because label has no .value I had to use .innerHTML) On label you have to define its text content. - changed from label to input type=text disabled=1 class=borderless / (my input fields have a 1px border by default, so I had to override that with a special class) These were the only changes to make the code work. So, at least Firefox has a restriction on changing labels when on a HTTPS page. You haven't convinced me :). Try to find a small reproductible example; if it's true, you should report this to mozilla. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Sortable woes
Am I doing something wrong, or is this a bug? You're doing something wrong: don't create the Draggables, Sortable handles that alone, and the containment option (which you specified well) handles the dragging between the 2 Sortables. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit.Visual - correct way to immediately stop an effect
I forgot yet another method: cancel. It should do the trick. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: enhancement proposal for drag and drop
First thanks because I spotted a problem in DD with your code :). I'm not very sure you used the good solution, and this part of the code is pretty sensitive. Anyway your use case seems reasonable, so I'll try to find a solution. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: enhancement proposal for drag and drop
Hi, It's interesting, but it'd be hard to say if it's pertinent without an example. Anyway you could send your patch (unified diff please, against trunk if possible) and I'll have a look. You can also open a ticket in the tracker. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Errors on Sortable.create
Please post a full reproductible example, it'll be easier to find out what's the problem. Regards, -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Back Button
What do you mean by 'back button support' ? There are many ways to support back button in a ajax webapp, so it'd be good if you say what you'd want. Generally MochiKit tries to be not too much intrusive, and I don't see how you can support back buttons without modifying server code. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Back Button
m_waschkowski a écrit : Well, it seems to me that concept of 'Back Button Support' is pretty straightforward - you press the back button, and then go to the last visited page. ie. just what people expect the back button to do. Yes, but the concept of page in an Ajax app is somewhat unclear, because it depends of what you do at each user inputs. Here you can see a good solution: http://www.contentwithstyle.co.uk/Articles/38/. But it's difficult to find a generic solution to this problem. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Deferred fails with no content on Safari
Could you post a reproductible example ? There are several ways for a Deferred to fail (via loadJSONDoc ? doSimpleXMLHttpRequest directly ?). The reason of the failure could also help (errback should be launch with an error as argument). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Minor documentation error in Signal.rst
Thanks applied in [1119] in the trunk. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Dynamic Draggables
Captain Phalanx wrote: Hi all, i'm trying to dynamicly add starteffects and endeffects to draggables. The adding works, but the fade effects are using the wrong variable, so only the last one fades... Here is my code: http://pastie.caboo.se/12725 Does anyone have any idea how to fix this? starteffect and endeffect take a parameter which is the dragged element. Just add the parameter in your function definition and use it instead of ElementID in your effects and it should work. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: fade, error getInlineOpacity
There are probably conflicts with the function namespace. Why do you want to use scriptaculous ? -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: blindUp glitches and #176
Leonardo Soto a écrit : After being able to reproduce the problem I figured out why it happens :). I've posted a simple workaround on #177. That seemed reasonable, I applied it to trunk. But I will insist that setElementDimensions still suffers this problem No setElementDimensions doesn't suffer, IE suffer from this. We can't make workaround every little quirks: it happens for IE, on height=0 and width!=0, and overflow hidden. It looks like a very specific problem to be handled in the code. and there should be a workaround or a note on the documentation to avoid people fall on this trap. I agree a documentation note can be useful. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: fade, error getInlineOpacity
Visual effects only work with the trunk version. Don't forget the New.js file. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: blindUp glitches and #176
OK I've tried to look at this using IE. To reproduce your accordion example I used the file effects_slide.html from the examples/effects and used blindUp/blindDown instead. It doesn't make the 'ugly glintches' you seem to have. I think the workaround is to use a div container. Could you try this and see if it works for you ? Otherwise, can you provide a simple example without ui4w and with blindUp that reproduces the problem ? Thanks, -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Simple MochiKit-based ComboBox
ericwaldheim a écrit : I hacked together a simple MochiKit-based ComboBox and am posting it in case it could be useful to anyone. If there's a better way to attach source here than cut and paste, please let me know. You could post the code in the wiki: http://trac.mochikit.com/ -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: DragAndDrop in packed Mochikit.js?
You should give a full example. My crystal ball feels rather dusty :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: drag and drop, rubberband/resize/stretch example, cleanup question.
Eric Waldheim a écrit :
Thanks again, I appreciate your input, your time, and DragAndDrop.js.
Thanks for your feedback.
My actual application makes use of starteffect, endeffect, and snap
(for actually snapping) for numerous types of dragging (create/resize/
move shifts and breaks) so I suspect I end up writing and maintaining
less code by using Draggable.
Here's one more swag at the same thing. I know that reaching into
the internals of MochiKit.DragAndDrop.Draggable is not a good thing,
but this solution cleans up up my application code and avoids
circular references, so it's a tradeoff I suspect I'll be willing to
make.
OK that's your choice. But some of these internals methods may change,
especially until 1.4 release.
And one additional piece: I added a check at the start of
my_mouse_down to end any currently active dragging (caused by mouse
up outside the document). Is that a reasonable approach?
Comments below.
var p = MochiKit.DragAndDrop.Draggable.prototype;
p.realEndDrag = p.endDrag;
p.endDrag = function (event)
{
this.realEndDrag(event);
this.cleanupDrag();
}
p.cleanupDrag = function ()
{
if (this.options.removeElementsOnMouseUp)
forEach(this.options.removeElementsOnMouseUp,
removeElement);
if (this.options.destroyOnMouseUp)
this.destroy();
}
Arg. Don't do this :). You can use inheritance, that would be better.
The best thing to use in this case is the observer. You call
MochiKit.DragAndDrop.Draggables.addObserver with an object with an
onEnd method. See Sortable for an example.
function my_mouse_down(event)
{
var ds = MochiKit.DragAndDrop.Draggables;
if (ds.activeDraggable)
{
ds.endDrag(event);
return;
}
I think that's OK, but why do you return ? I'd just replace this code
with:
MochiKit.DragAndDrop.Draggables.endDrag(event);
and I think it will make what you want (check active, and clean
current).
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Fwd: Re: Effects 'conflicting' on the same element
Leonardo Soto a écrit : I see. But AFAICS, that queue let me put the new effect to be executed 'soon' or 'later', and lets both effects to finish. Yes, you're right. I want to stop the running effect, but don't see how could that be done using toggle. I think the behaviour of toggle is sane, as it waits the precedent effect before running the new one. But I guess you want another behaviour. For what you want, another option of the queue functionnality can make it works (like 'break'). I'll try to have a look at this. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: getFirstElementByTagAndClassName | New.js
Thanks, it's fixed in the trunk. Be careful, this function is not part of the public API and may be removed at any moment. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: DragAndDrop in packed Mochikit.js?
[EMAIL PROTECTED] a écrit : I checked out the latest trunk this morning (Revision 1074). I noticed that the DragAndDrop.js is not being built into the packed version of MochiKit.js. Is there a reason for this or is just not being done? Yes, DD is still in developpement, so it's not put by default in the packed version. Furthermore, due to its size, it may not be in the packed version in the stable release. So then I manually included the DragAndDrop.js. In my test page, I got the error: d.makePositioned is not defined (DragAndDrop.js line 499). You have to include New.js. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Concurrent Highlight effects have side effects and restorecolor not utilised patch
Thanks for your feedback, it's been done in the trunk (1071). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: drag and drop, rubberband/resize/stretch example, cleanup question.
It's interesting, here's some comments:
* The hack with snap (and the drag_x/drag_y variables) is not very
good. You should use getElementPosition(draggable.element,
$('container')) in onchange and remove the snap option.
* For the endeffect option, I really don't know. The best is to try
with a memory tracker and see what happens.
* I don't really see the point of DD for this example. You don't use
Droppable and you destroy the draggable very quickly. I think it might
not be the good thing for this. Have you looked at the draggable
example using Signal ? It's pretty simple and thus very customizable.
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Safari initial slideDown does not work
I did the patch and it seemed to correct the problem you have (under Konqueror). I don't have Safari to test so I can't make anything for this :/. May you try some things to find where the problem is ? I think it's around getElementDimensions, but I can only suppose. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Sortable objects with textarea... textarea not editable
Dee a écrit : If you create a sortable that contains a textarea, the textarea is not editable. Any ideas on how to get around this? Is this a bug? I'm using mk 1.4. OK, there was a bug in the initDrag function that prevent the event from reaching input elements. It should be fixed in the trunk. Thanks for your report. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: on-the-fly DD element creation problem
Some comments: - Don't use display: none in your css class, use visibility: hidden instead. You have to do this because you can't set the position of an element with display:none. - Don't use window.onload with MochiKit. Use addLoadEvent, or better connect(window, 'onload'). - I think event.mouse().page is better suited to what you want to do - After a few tests, it seems you may have to set some positions to absolute to prevent some side effects. Good luck :) -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Is anyone working on autocomplete for MochiKit?
As you seem to have spotted, Controls.js is not supported at all. It's here by accident, and there're very few chances that it'll be in the next MochiKit release, or even in a release one day. Bob would be a better judge, but I don't think autocomplete/ajax editor is a feature suited for MochiKit. For now, there are no docs, no examples, and no maintainer for this file. There's a lot of work needed for removing Prototype stuff and using MochiKit instead. Every volunteer are welcome, though :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Problem with tbody and blindUp et al
You have to include the file New.js to use the Visual effects. The error is relatively clear, no ? It means the function makeClipping is not defined (because it's defined in New.js). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: problem slideDown effect | Safari | MK 1.4
bartb a écrit : Hi all, The function slideDown of Visual.js does not work properly on Safari (2.0.4). The slideUp function behaves as expected, but the slideDown only shows the endresult and not the transition effect. See http://212.238.141.176/polarisnow.com/testmk.php for an example. Thanks for your report, I've posted a solution in http://trac.mochikit.com/ticket/149, it should be soon in the trunk. Btw, should I post bugs to the MochiKit google-groups first to see if it really is a bug, or can I create a bugticket at trac.mochikit.com right away? For me, I post a ticket when I have a more advanced diagnostic. But every report is welcome, so you can use the tracker if you prefer. The group tends to be more responsive. Also, if you use the tracker, it's better to post complete code examples than URLs (tests' URLs generally disappear after a short period of time). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: fade-effect on iexplore, problem
This a known IE problem. See here for an explanation and the solution: http://jszen.blogspot.com/2005/04/ie-bold-text-opacity-problem.html -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Submitting documentation patches?
Fred Drake a écrit : What's the best way to submit dcumentation patches for MochiKit? I'm sure there's a link to a tracker or something on the website, but I wasn't able to find it after just a few minutes of searching. It seems the link was forgotten in the new website. You can find the tracker here: http://trac.mochikit.com. Are the reStructuredText versions of the documentation the definitive versions? Yes, they are compiled into HTML using the make_docs.py file in the scripts directory. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Proposed Patch for Sortable
It's interesting, but I think you may run into other problems with so many sortables. Have you checked the performance of your solution ? I suspect the page become very slow, because Sortable is not designed to handle so many items. Again, I think Sortable is mainly a proof of concept for DragAndDrop, and fits for simple cases. If you have lots of items or a complex layout, a hand made system (based on DD) will definitely be better. For example, you may try to define your Draggable on the fly ? -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Dollar shortcut for document.getElementById?
Kevin Francis a écrit :
Is there anything akin to the $('id') shortcut seen in prototype
available for MochiKit?
Yes, there is $('id'), though not advised, getElement('id') is a
preferred form.
I've looked through the documentation, but have
been unable to find anything remotely similar...
http://mochikit.com/doc/html/MochiKit/DOM.html#fn-$
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Newbie - How to avoid dropping of the draggable items in free space?
Please post an example showing your problem, that'd be easier to help you. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Generating Table rows on the fly with TR(), TD() in I.E. x.x
http://groups.google.com/group/mochikit/search?group=mochikitq=ie+table+row -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Sortable checkboxs and IE
Wouhou, another insane IE bug. It seems the check value is reset during the insertBefore call (method onHover of Sortable). I'll try to look at this, but I don't really know what to do. I haven't found reference about this on the web. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Sortable checkboxs and IE
Scott Chapman a écrit : Thomas Hervé wrote: Wouhou, another insane IE bug. It seems the check value is reset during the insertBefore call (method onHover of Sortable). I'll try to look at this, but I don't really know what to do. I haven't found reference about this on the web. Here is a sortable table implementation that takes care of the problem. It may be useful as a reference. http://webfx.eae.net/dhtml/sortabletable/sortabletable.html It doesn't look the same: Sortable uses a DD facility to sort items, whereas this one uses a sort on columns value. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: DD bug in trunk?
Tim Stebbing a écrit : there does not seem to be a makePositioned in DOM? DD is still in development, until 1.4 release you have to include the file New.js which contains the functions needed. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Sortable bugs?
I didn't realize that DragAndDrop/Sortables were so new. Well there's no release with these elements yet :). Here's a quick and dirty test page that I put together to illustrate. Trying to add scroll:true or ghosting:true to the options in the init script will really make things weird/ugly. OK I've add quick look at the page: I don't think Sortable is your solution. The page is *really* slow so I don't see how you can adapt Sortable to work with your goals. Sortable is really made to have one create for a page, with a list of elements. If you have multiple Sortable.create, this may not be the good solution (it should not be actually). I advise you to use Draggable/Droppable directly, maybe with some inspiration from Sortable. I'll try to see if I can tweak your example but it's not for now. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: DragAndDrop.Draggable onchange function 'element' parameter
Thomas Sandor a écrit : Can somebody tell me what is this element? Yes, the draggable object itself is passed to the function. You can access the DOM element in the attribute 'element'. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: ondrop on Mochikit.Sortable
Luciano Ruete a écrit :
Take me a while to figure out that i need to generate an explicit match
(ussing '()') to make serialize work, but no complains about no docs, couse
im ussing svn code here :-).
Yes there's a lot to do in the documentation field. Every contribution
is welcome :).
Ok, simple example attached, error reproduced on firefox 1.5 with firebug
extenstion.
Maybe it is because my use of javascript, maybe not, im relative new to
javascript.
[snip]
for (node in getElement(e).childNodes){
child = getElement(node);
if (! isUndefinedOrNull(child)) {
log (child.id);
}
}
Your problem is here, you can't iterate through childNodes like this.
You can try this:
map(function (child) {
if (! isUndefinedOrNull(child.id)) {
log (child.id);
}
}, getElement(e).childNodes);
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Help: how to start effects_slide.html example with div's hidden?
[EMAIL PROTECTED] wrote: Hi -- thx to all you MochiKit developers: it is *great* Simple question by a noob: I'd like to start the effects_slide.html example with the divs hidden (i.e. closed) instead of open. How can I do this? You just have to customize the CSS of your elements (by adding 'style=display:none;' for example in your div declaration). slideDown should do the job after that. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: ondrop on Mochikit.Sortable
luciano a écrit : Hi all! Im trying to use Mochikit.Sortable but i want to trigger my actions when i finally drop the element, because if i use onchange, the function is called each time the element is surfing betwen the other sortable elements. AFAICsee there is a ondrop function in a dropp'able element, so im wondering if it is possible to Mochikit.Sortable.Sortable.create to set this ondrop function as an option. This is not exactly (I think) what you want. You should look at the 'onUpdate' option of create, it's called every time the serialization of the Sortable change. To customize the serialization, use the format option (it's a regexp checking id of items). Aditionally im ussing divs instead off lis, and affter sorting, i was not aviable to find the new order trougth childNodes nor nodeWalk(), both returns me the divs in the original order, but visually sort works ok. Strange... I see no reason why it should not work with childNodes. If you can make a simple example reproducing the problem it would be great. Im ussing the svn versión of Mochikit (i update almost every day) Thanks to mochikit developers, it cracks the earth. Glad to see a happy user :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: adding rows to a table, but table.rows.length is still 0
Don't append TR directly into the TABLE. You must insert a TBODY/THEAD/TFOOT element before, and then append into it, to make it work under IE. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Nested Draggables and Sortables
Brian Granger a écrit :
Hi there,
I am using MochiKit to develop a web-based frontend for a
Twisted/Python Servers. Coming from the Twisted/Python/OjbC world, I
am really enjoying MochiKit. I have a question about Sortables.
Is it possible to nest sortables? I have a layout that consists of
nested divs:
div id='dnd1'
div id='dnd2'
divstuff/div
divmorestufff/div
/div
div id='dnd3'
divstuff/div
divmorestufff/div
/div
/div
script type=text/javascript
MochiKit.Sortable.Sortable.create('dnd1',{ 'tag':'div'});
MochiKit.Sortable.Sortable.create('dnd2',{ 'tag':'div'});
MochiKit.Sortable.Sortable.create('dnd3',{'tag':'div'});
/script
I would like to be able have the inner most div's be sortable _and_ the
outer divs to be sortable as well. Is this possible?
Yes it's possible, even though not really the main point of Sortable.
The only thing you need is something where the user can click to drag
your sortable:
div id='dnd1'
div id='dnd2'foo
divstuff/div
divmorestufff/div
/div
div id='dnd3'bar
divstuff/div
divmorestufff/div
/div
/div
With this, 'foo' and 'bar' will move 'dnd-2' and 'dnd-3' with all their
children inside dnd-1.
I did see that
in Sortable.js, there was an unimplemented tree option. Does this mean
that this type of thing might be possible. Any thoughts on how to go
about this?
It's another functionnality comin from Scriptaculous 1.6. It should not
too complicated too import, I'll try it soon.
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: MochiKit.DOM class* functions not working in this situation.
Sam Sutch wrote: Sure, here: http://kalispellcopycenter.com/t/ is what I was talking about (view source, obviously). toggleElementClass works perfectly, it's just that your tabHover class doesn't modify the look of your elements (it conflicts with the definition of your styles in styles.css). Just modify the stylesheet to see that it works. Note: be careful with roundElement/roundClass, it modifies the elements statically; it doesn't seem you expect that in your code. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Chained Deferreds
Thank you for your reply. You're welcome :). I should have seen that, but if I change it to return result; , I still get the same error. What am I missing? Well, for correcting your problem, I did like that: * copy/paste your code in a file * create the json files in the directory * change the path to MochiKit.js (I used the one of trunk) * remove the objectToString call as it's not defined for me * remove the maybeDeferred call So maybe you should try the packed version from trunk (I don't really see why ? maybe DeferredList has improved ?). Otherwise you're not posting the good code :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Chained Deferreds
[EMAIL PROTECTED] a écrit :
You're right, of course I should have supplied a runnable example.
Here goes, it's not beautiful, but it illustrates my problem:
[snip]
/*var serverMsgCallback = function(result) {
alert(objectToString(result));
return maybeDeferred(result);
^
Your problem is here: maybeDeferred works with a function, not a value.
Here you just have to make 'return result' to pass your result to
following callback.
Note: if you want to pass value using a Deferred (not useful in this
case), you'll have to use 'succeed(result)'.
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: transfer data to server via POST Request
There a ticket for that in the tracker: http://trac.mochikit.com/ticket/56. Maybe soon in MochiKit :). -- Thomas X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.11.88.14 with SMTP id l14mr40767cwb; Mon, 22 May 2006 06:42:07 -0700 (PDT) X-Google-Token: vNjbZwwAAACGTmovf31qcGI__5meerXQ Received: from 62.39.9.251 by 38g2000cwa.googlegroups.com with HTTP; Mon, 22 May 2006 13:42:07 + (UTC) From: =?iso-8859-1?q?Thomas_Herv=E9?= [EMAIL PROTECTED] To: MochiKit mochikit@googlegroups.com Subject: Re: transfer data to server via POST Request Date: Mon, 22 May 2006 06:42:07 -0700 Message-ID: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.0.2) Gecko/20060502 Ubuntu/dapper Firefox/1.5.0.2,gzip(gfe),gzip(gfe) Mime-Version: 1.0 Content-Type: text/plain There a ticket for that in the tracker: http://trac.mochikit.com/ticket/56. Maybe soon in MochiKit :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: transfer data to server via POST Request
The issue with POST is that there isn't one standard way to do it, and there are often a few custom headers that need to be set depending on the application. The current recommendation is to write your own function that satisfies your requirements. I agree, but today we don't have a simple wrapper in MochiKit to build POST requests. In the ticket, the method 'doXMLHttpRequest' in the second patch offers that (you can specify method GET or POST and add content to the XmlHTTPRequest send). The equivalent of loadJsonDoc is probably unnecessary. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: MOCHIKIT VISUAL
information is basic and if the information is wrong... better dont have the info Information is a the level of the question. Launching posts every two seconds with caps words and '!!' won't help you to get good anwsers. i think if all we wanna make of this library compete with prototype, mochikit developers have not only to emulate or copy prototype functionallity (as with visual effects module in mochikit) you have to be better than it! We don't copy anything. scriptaculous has done a great work on the compatibility field, so we ported it. It's a work in progress, there's still no MochiKit release with this code. You can use it if you're a developper and if you're likely to help. Quick opinions like 'Be better ! You should work more' won't make us go anywhere. And there's no point to compare with prototype as it's not the same work, that's all. i think prototype with visual effects extensions (rico / scriptaculous) are best option for production applications for now If you had started by that... DISCLAIMER: don't use Visual Effects in any application if you're not willing to see things break and api changes. It will be marked as stable when MochiKit 1.4 will be released. Finally, I remember you there are mainly voluntary developpers here. I'm not paid to code on MochiKit, and I'm not paid to answer your questions. If you're not happy with MochiKit, and are not ready to help, please go away. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: blockOn( DeferredList )
The differences between updating the prototype and using an instance of a prototype: 1. Using an instance allows instanceof to work 2. Using an instance utilizes the prototype chain (changes to the parent prototype propagate to instances of the subclass too) 3. Creating the instance executes the parent's constructor, where just doing the update doesn't execute anything. OK, thanks a lot for these clarifications. I could make another little modification to clean up the implementation, and apply your advices in Effects. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: How can I to use MochiKit in my bew-page?
Control.js is in trunk by accident and there's no plan to really support it at the moment. Howere if you want to try it, include first MochiKit.js, then New.js and Control.js. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Signal changes prior to MochiKit 1.3 release
Beau and I are here making some last minute changes to Signal. We've hacked it apart and put it back together in the interest of ease of use, performance, and plugging up leaks. Great work, the svn has burned :). PLEASE let us know if you have existing MochiKit.Signal code that doesn't work against the trunk given this hack. I'll try to test scriptaculous port against it ASAP, but I don't see any problem for now. Just as a side note, I launch the tests against a few browsers (Firefox/Opera/IE/Konqueror). I only spotted a little problem in the new printfire function on Konqueror, which doesn't known dispatchEvent. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] gatherResults and maybeDeferred
Bob, could you http://trac.mochikit.com/ticket/87 ? Just a simple implementation of gatherResults and maybeDeferred, with tests. It would be great to have those in 1.3. Note: the 'cc' keyword doesn't seem to send mails. Did you activate the smtp functionnality of Trac ? -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Combining two getXMLHttpRequests
Could you merge this to trunk, or do you want me to? I can, no problem. I'll send you a note when finished for review. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Combining two getXMLHttpRequests
OK it's in trunk (code, tests, and doc). I just didn't generate the packed version because I didn't have java on my machine. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Combining two getXMLHttpRequests
That's a good use-case for DeferredList. I've made a primary implementation here: http://trac.mochikit.com/changeset/548. To use it, simply get the 2 deferred from sendXMLHttpRequest, create a DeferredList with these 2 deferreds, and add your function as callback to the DeferredList. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Signals status?
I think Beau makes it this way for compatibility purpose (keypress works very bad on Safari; actually some like prototype refuse to register keypress events on it). It's actually well documented in Signal : if you want to filter Special Keys, use keydown. This said, you have access to everything you might need with the event() method, so I don't think it's a Signal problem --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Request: MochiKit.Signals event().currentTarget()
See here someone who got the same problem as you: http://groups.google.fr/group/mochikit/browse_frm/thread/1f83acd42a1cd4e0/5a64c7c40769ccd1?q=targetrnum=1#5a64c7c40769ccd1 To make it quick, I think the simplest way to handle it is in your code, by passing the element you connect to with a partial (IE doesn't have currentTarget). This said, if Beau is motivated to add it it might be good :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Perf suggestions with large numbers of connect()s and addLoadEvents?
You shouldn't add a listener for each link: add a global listener to your document and filter in your event function. Even if the function is a little more complex, the performance will be much better. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Mochi Drag and Drop?
Does anyone have a preference to Scriptalicious or YUI? Well, I do have a preference for Scriptaculous as it's already ported to MochiKit :). For YUI I don't have an opinion as I didn't look at the code. Their examples are very polished, though. Thomas, is there anything I can help with? If think most of code is OK. I've ported examples from Scriptaculous so we have things to test. What we need is maybe a full clean example, with css/images. It would be good promotion. Also documentation (both in code and in rst files) is needed. And of course tests on different browsers. You could work on my branch until it's merged (soon I hope). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit Documentation - Off topic?
It would be nice if the boxes were links to each module class or method, I don't understand... You mean adding links between classes of the same module ? Or methods resulting in other objects should point to that classes ? at least in the PDF version (assuming that a PNG version is also planned). It's a scribus project, so it can be PDF, PNG or SVG without problems. BTW, Was it generated from the RST documentation sources? No, it would be great to do with the sources, but it's really a hard word (docutils is not so clear about XML output). It involves creating a docutils writer, and make a smart positioning of objects (I thought about a SVG output). It's a project by itself :). -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Color.fromRGB bug
Good catch, a hard-to-find bug! I saw the problem in your values because there were always a '010' in it (it's just a problem in toHexString). See http://trac.mochikit.com/ticket/68 for correction. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Small function works cross browser, is there a better way?
Not tested:
var isChildNode = function (child, parent) {
var curParent = child.parentNode;
while (curParent) {
if (curParent == parent) {
return true;
}
curParent = curParent.parentNode;
}
return false;
};
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: mochikit macro template thingo
OK I think I understand your problem. You try to extract HTML from your request responseXML. But the content of the request is XML, not HTML (no presentation logic present in there). For example the DOM object for your divs is the generic object Element, not the corresponding HTML object HTMLDivElement. You can see in DOM Inspector that it has no style attribute, which explains why we can't see styles. One solution would be to use innerHTML, it should work. Another is to construct real HTML DOM objects from the ones you receveived as XML. Or maybe there's one clever solution but I can't see it :) -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Target() of asd seems wrong?
target returns the element where event takes place, not the element porting the event listener, so it's correct. If I understand your problem, the best you can do is passing the myObject as argument to the gotFlash method (hint: look at Base.partial). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~--~~~~--~~--~--~---
[mochikit] Re: Target() of asd seems wrong?
Hmm. I think I understand, but why then do I include MyObject in the
connect call?
You include it because it's the way events work in Javascript :). You
don't have other choices.
What is it's purpose if not to be available as the
target()? I'd like to attach any number of member data points to it
(since I know them at runtime) and have a generic gotFlash() that
references target().foo to get any arbitrary foo I may have assigned
to that particular object.
It's not the purpose of target, that's all (and the purpose of the
underlying values target/srcElement). If you want to do this, you have
to connect your function on a node without child (it's a possiblity,
even if it may not be the good choice).
Using partial doesn't help me (that I can see) since my goFlash is
shared, and I don't want to bind it to only one node.
I'd do it like this (not tested):
connect(myObject, 'onclick', partial(gotFlash, myObject));
connect(myObject2, 'onclick', partial(gotFlash, myObject2));
gotFlash = function (node, event) {
// blabla
};
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---
[mochikit] Re: Scriptaculous status
I didn't find much time lately to work on it, but I think most of Effects and DragDrop work. Docs and examples are basic but are here. The last thing for me is the status of New.js, which contains updates to Base/DOM and a Position module (which is not very clean...). Controls (Autocomplete, Ajaxy things, ...) aren't ready yet and not in the roadmap. The other thing I can't state is whether or not it should be build by default into the packed MochiKit, because it's pretty huge (Visual alone is 52k, plus 22k for Signal and 20k for DD). Maybe having multiple packed versions is the right way to do it. Oh, and Signal tests aren't finalize yet, I think it's a TODO for 1.3. -- Thomas
[mochikit] Re: Patch for Sortables/DragDrop in scriptaculous branch
Thanks a lot that's applied. Note that the scriptaculous branch is not really sync with trunk, so you may encounter some problems with switching. -- Thomas
[mochikit] Re: Signal bug
Great work, I'll test DragDrop against it ASAP. -- Thomas
[mochikit] Re: MochiKit 1.2 bugs?
There's definitely a problem, I've fixed it here : http://trac.mochikit.com/changeset/552 but I hadn't find the time to open a ticket for trunk. -- Thomas
[mochikit] Re: formContents
var res =
MochiKit.Async.doSimpleXMLHttpRequest(this.link,formContents('loginform'));
If it's your code, it's normal it doesn't work, or I don't know what's
this.link : formContents is a function of MochiKit.DOM, not a slot of
nodes.
If it's not your code, please post your real code.
--
Thomas
[mochikit] Re: Port of script.aculo.us
Excellent! Thanks :) I tested the demos in Firefox. Two issues: * In drag and drop, dragging an item to the shopping card REPLACES any items that are already there. Yes, sorry for not telling it : it's just a problem of my ajax updater, because I don't have an application behind (just clearsilver cgi), so I cannot make simple sessions. Next step is likely to be based on Turbogears. * The 'appear' demo on the cinematic effects demo page doesn't do anything. Well, it's not my fault :). It's just stupid to make it here, because nothing can appear if it's already here. You can try it on the alternative demo at the bottom, after making a fade for example (there is the same problem on scriptaculous site). -- Thomas
[mochikit] Re: JavaScript unit testing
Well, as I work on it, you may be interested in having a look in scriptaculous unittest. Nothing wonderful but it seems to work. They have begin a very interesting work on events simulation (for mouse and key actions). Otherwise twill or selenium are great for web apps, but I don't think it's what you need. -- Thomas
