On Nov 1, 2006, at 2:21 PM, Dave Woodwater wrote:
> Hi,
>
> I'm trying out Mochikit to see if it's the right tool for the job. I
> can pretty much get everything I need a'working, but for some reason I
> keep getting errors when trying to call the visuals.
>
> I get "toggle/puff/etc... not define
On Nov 1, 2006, at 8:02 AM, abargnesi wrote:
> Zac,
>
> Thanks for the tip. I used innerHTML on the TD after I created it and
> it works perfectly (at least in firefox).
>
> The reason why I used Mochikit is because I would like to not use
> innerHTML (not standard) and also avoid performance pe
On Oct 31, 2006, at 3:03 PM, abargnesi wrote:
> Hello,
>
> I am using the DOM Manipulation js library that is part of Mochikit
> and
> I like it a lot. And it seems quite fast. However I would like it to
> handle one case that it doesn't.
>
> At some point in the creation of a TABLE I create
On Sep 18, 2006, at 5:38 AM, m_waschkowski wrote:
> 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.
>
> I did see some javascript type sol
On Sep 12, 2006, at 8:50 AM, Marc Boeren wrote:
> Hi,
>
> Is it useful to have a simple toDOM(html) function in MochKit.DOM? I
> like it because I can make simple templates as html snippets, which I
> find more readable than the corresponding createDOM constructions.
>
> Usage:
>
> var html = 'My
On Sep 1, 2006, at 11:09 AM, michelts wrote:
> I want to know if there is some advantage except to the less code
> script, is there any performace gain? I want to know if there is a way
> to do a lambda function inside a map (as I can do in python), I think
> in something like:
>
> function o
On Aug 29, 2006, at 5:35 PM, Beau Hartshorne wrote:
> On 29-Aug-06, at 2:07 PM, Zachery Bir wrote:
>
>>> I just figured it out. One must use the camel case notation for the
>>> CSS
>>> attribute lists. It would perhaps help to mention that in the
>>>
On Aug 29, 2006, at 5:02 PM, mirage wrote:
> Gaaahh!!!
>
> I just figured it out. One must use the camel case notation for the
> CSS
> attribute lists. It would perhaps help to mention that in the doco. :p
Gaaahh!!!
You're in Javascript, not CSS. Put it in a .css file, or use
Javascript not
On Aug 3, 2006, at 10:12 AM, elio wrote:
> Hi group,
>
> a simple question:
>
> this doen't work:
>
> $("node").getElementsByTagAndClassName("UL");
>
> what do you use to look for tags inside an element?
It's not a method, it's a function:
getElementsByTagAndClassName("UL", null, "node")
Yo
On Jul 18, 2006, at 11:11 PM, Chris Nokleberg wrote:
> I have some mousedown events that are mostly "handled" by a floating
> component but for reasons specific to my UI the parents still need to
> see the event--that is, I cannot use stopPropagation. However, the
> parent needs to know that some
On Jul 15, 2006, at 1:28 PM, Andrew wrote:
> Hi Bob,
> you are correct. What I was after was:
>
> xml = dojo.dom.createDocumentFromText(data);
> divList = xml.getElementsByTagName("div");
> dojo.byId('output').innerHTML =
> dojo.dom.innerXML(divList.item(2));
>
> Just wondered w
On Jul 15, 2006, at 12:58 PM, Andrew wrote:
> Hi Zac,
> what I'm attempting to do is getting the returned page from a submit
> and then taking out element output which is the id of a div tag in the
> returned document. So it's basicall the other way round of what you
> have mentioned:
Doesn't ma
On Jul 15, 2006, at 12:31 PM, Andrew wrote:
> Hi,
> I have just downloaded the latest, svn, version of MochiKit and am
> using it (packed) in conjunction with dojo 0.3.1. I attempt to
> create a
> new DOM like so:
>
> MochiKit.DOM.createDOM(data) - data being an xhtml document
>
> and I get the
Drop the alerts, and liberally log() your way through the app, then
use MochiKit's logging bookmarklet.
"MochiKit.Logging - we're all tired of alert()"
Zac
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Moc
On Jul 14, 2006, at 3:19 AM, Thomas Hervé wrote:
> That's great, I'm glad you find it good :). I just want to warn you,
> try to test your solution on older machines before making an Internet
> app (opposed on Intranet) using more than 100 elements in Sortable.
This is an intranet app, which is
On Jul 13, 2006, at 11:38 AM, Thomas Hervé wrote:
> 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.
It's
On Jul 12, 2006, at 7:45 AM, Peter Mularien wrote:
> Thomas Hervé wrote:
>> Yes, there is $('id'), though not advised, getElement('id') is a
>> preferred form.
>
> Just curious, why is the $ form not advised? I don't recall seeing
> that
> mentioned before.
Sorry, I read that as "advertised".
On Jul 12, 2006, at 7:45 AM, Peter Mularien wrote:
> Thomas Hervé wrote:
>> Yes, there is $('id'), though not advised, getElement('id') is a
>> preferred form.
>
> Just curious, why is the $ form not advised? I don't recall seeing
> that
> mentioned before.
It's right at the top of DOM's API r
On Jul 11, 2006, at 1:05 PM, MAria wrote:
> Hello, I'm trying to do something with dojo, but there is no way!
> The first question is:
> I have dojo-0.3.1-ajax version, is it the last one??
> This is just a folder, I haven't installed anything else. And to use
> it, I just include this line at th
On Jun 14, 2006, at 1:30 PM, Zachery Bir wrote:
> On Jun 14, 2006, at 1:25 PM, Jay Parlar wrote:
>
>> Is there no way in Mochikit to do an async POST to a server? I've got
>> some async requests that will be changing state on the server, and
>> while I can technical
On Jun 14, 2006, at 1:25 PM, Jay Parlar wrote:
> Is there no way in Mochikit to do an async POST to a server? I've got
> some async requests that will be changing state on the server, and
> while I can technically do it with a GET, it seems like the sort of
> thing I'd want to use POST for.
Sure
On May 25, 2006, at 8:00 AM, coredump wrote:
> Yes, it worked like a charm for my tags, but if I allow hrefs... and the thing start to get ugly.
> Mainly because is a simple tag, but the other ones have opening
> and ending parts...
>
> Any other ideas? On how to spit DOM vrom HTML quickly? :
Shouldn't elementDimensions and elementPosition move from DOM to
Style, as well? Seems very "presentation-y" to me.
Zac
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, sen
On May 17, 2006, at 5:34 PM, Bob Ippolito wrote:
> On May 17, 2006, at 11:03 PM, Kevin Dangoor wrote:
>
>> On 5/17/06, Jose R <[EMAIL PROTECTED]> wrote:
>>> But try prototype first (another great javascript library at
>>> http://prototype.conio.net) wich i think is a well tested and has
>>> even
On May 17, 2006, at 4:28 PM, Jose R wrote:
> information is basic and if the information is wrong... better dont
> have the info
> 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
On Jan 6, 2006, at 10:28 AM, Zachery Bir wrote:
The Zope 3 formlib chokes when all the attributes specified by a
Schema interface aren't present (that haven't explicitly been
omitted from the view). But MochiKit eliminates empty form elements
from the result of a formContents.
The Zope 3 formlib chokes when all the attributes specified by a
Schema interface aren't present (that haven't explicitly been omitted
from the view). But MochiKit eliminates empty form elements from the
result of a formContents. Any chance we can optionally get it to
include those as emp
On Nov 30, 2005, at 1:26 PM, John wrote:
I have "html_a=A( {'href':'#', 'onClick':'doX'}, null, 'doX')
why doesn't it work?
What doesn't work? You'll have to provide a little more info.
Zac
28 matches
Mail list logo
