Ok i see i should have said that i´m using tinymc editor and it seem that
mootools and tinymce aren´t compatible enough.
Did anyone use tinymce and mootools together?
2010/1/22 Davor Ilic
> ok have an other problem. The form is stoped and the content updates but
> i´m missing the value from the
ok have an other problem. The form is stoped and the content updates but
i´m missing the value from the textarea.
If i have the submit event i get it other i have an empty post array how i
get the data?
2010/1/22 Davor Ilic
> ok thank you very much this was helpful. now i understand cou
ok thank you very much this was helpful. now i understand couple of
things i do many wrong in the options field
2010/1/22 Aaron Newton
> So, a couple things. First, you don't need to add a submit event to your
> form; Form.Request does that for you. Just, on domready, new
> Form.Request(
So, a couple things. First, you don't need to add a submit event to your
form; Form.Request does that for you. Just, on domready, new
Form.Request(form, update); and you're done. As for spinner, you just have
to have it in your environment (and then you need to set up the css for
spinner; see its d
this is how i use it where i have to push the submit twice
window.addEvent('domready', function() {
$('myForm').addEvent('submit', function(e) {
e.stop();
var content = $('content');
new Form.Request( $('myForm'), content);
});
});
another question, i see that i have the optio
You can pass either; an id or a reference.
You should not have to push the submit button twice.
note that it can integrate with Spinner and Form.Validator.
On Thu, Jan 21, 2010 at 4:41 PM, hairbo wrote:
> I think it just should be:
>
> Form.Request('myForm','content')
>
> I don't think you nee
danke!
On Thu, Jan 21, 2010 at 4:40 PM, hairbo wrote:
>
> https://mootools.lighthouseapp.com/projects/2706-mootools/tickets/835-requesthtml-documentation-is-missing-instructions-on-the-append-option
>
> On Jan 21, 5:26 pm, Aaron Newton wrote:
> > That is a supported feature; the documentation e
I think it just should be:
Form.Request('myForm','content')
I don't think you need to pass in the element object itself--just the
ID to the desired elements.
On Jan 21, 5:58 pm, Davor Ilic wrote:
> ok i have it new Form.Request($('myForm'), $('content'));
>
> thats very cool but why didn´t work
https://mootools.lighthouseapp.com/projects/2706-mootools/tickets/835-requesthtml-documentation-is-missing-instructions-on-the-append-option
On Jan 21, 5:26 pm, Aaron Newton wrote:
> That is a supported feature; the documentation exclusion is an oversight. If
> you wanted to be charitable, you co
I did, and didn't see the extra , but i wasn't sure if Firebug
would show that behavior anyway. I can check again.
On Jan 21, 6:25 pm, Barry van Oudtshoorn
wrote:
> Try inspecting the DOM with Firebug. Do you see the same behaviour
> exhibited then?
>
> On 22/01/10 05:06, hairbo wrote:
>
>
>
>
>
Try inspecting the DOM with Firebug. Do you see the same behaviour
exhibited then?
On 22/01/10 05:06, hairbo wrote:
It's possible it's a bug with Firefox's HTML source rendering.
According to the web developer guy, his code just wraps around
existing FF code:
http://chrispederick.com/forums/vi
thats cool now i can use it, but i have a bug. I have to press the
submitbuttom twice to get an request.
Is that a bug?
2010/1/22 Davor Ilic
> ok i have it new Form.Request($('myForm'), $('content'));
>
> thats very cool but why didn´t work my first it´s the same as mootools i
> just copy and pa
ok i have it new Form.Request($('myForm'), $('content'));
thats very cool but why didn´t work my first it´s the same as mootools i
just copy and paste it ???
2010/1/22 Davor Ilic
> Could you write me an example i looked up this and it don´t work and i do
> not know why...
>
> 2010/1/21 hai
Could you write me an example i looked up this and it don´t work and i do
not know why...
2010/1/21 hairbo
> It kind of looks like your PHP page isn't returning HTML. I'd also
> suggest you try this code (I just learned about it, and it's pretty
> nice)
>
> var MyFormSubmit = new Form.Request(
That is a supported feature; the documentation exclusion is an oversight. If
you wanted to be charitable, you could file a lighthouse ticket to that
effect...
On Thu, Jan 21, 2010 at 2:40 PM, hairbo wrote:
> According to the docs of Request.HTML, you can only "update" an
> element with the HTML
It's on our (long, long, long) list of things to do to put together an edge
builder. If you do set up depender, updating it is pretty simple. To use
depender, just do this:
git clone git://github.com/anutron/mootools-depender.git
git submodule init
git submodule update
Then follow the instruction
The latest version is always available on github. There may be other
bug fixes in the various developer's personal repositories (there is a
list on the developers page) but they will be 'untested' as such.
Getting and building the latest version is simple, just clone the
repository and run the buil
> During testing, I've discoverd one thing. IE requires that the xml has
> a name space.
We talked about this a while back in another thread. I think IE is
doing the right thing. After all, (X)HTML does not have an
anything-goes DTD. If you want to inject els into the DOM, validat
> That of course means every time my show function gets called, it is
> given the very first event.
You would also find that your test actually worked in IE due to its
different event passing model.
I fire up IE more than most people while debugging, I'd guess, because
a simple discrepancy c
@Trevor Orr: Yes, I will get round to it soon enough, promise.
@Pete Duncanson: I have already written Intellisense for Visual Studio
for use with MooTools: http://code.google.com/p/mootoolsintellisense/.
On Jan 21, 7:24 pm, Pete Duncanson
wrote:
> This is way old now but still shows whats possi
> Why not use *JSON*? its cross platform cross programming language and its
> simply awesome!
[1] Because it is not always available: this example is an RSD feed,
among hundreds of popular XML-based formats. When you don't control
the service nor an intermediate gateway, you don't control the
According to the docs of Request.HTML, you can only "update" an
element with the HTML returned by this AJAX call. I needed to append
the HTML to an element rather than update, so I spent some time
casting around for another solution. In desperation, I looked at the
Mootools source, and found this
It kind of looks like your PHP page isn't returning HTML. I'd also
suggest you try this code (I just learned about it, and it's pretty
nice)
var MyFormSubmit = new Form.Request(
[idOfFormToSubmit],
[idOfHtmlElementWhereFormResponseGo
I'm just looking for bug-fix builds. The current release on
mootools.net/core mootools.net/download seem to be a "tagged"
release, which has bugs. I need a build from the same stream,
1.2.4.x, but with the latest patches. There has to be a better way
than for each developer to wrestle with git
What i´m doing wrong?
http://mootools.net/shell/UUdVL/2/
I've posted this need before. Mootools does not come out with builds
often enough (bug-fix releases). The process for building core and
more from git source is unknown to me. Its not clear from github
which tag or branch is appropriate (although I can rule out many). I
posted about this a while
It's possible it's a bug with Firefox's HTML source rendering.
According to the web developer guy, his code just wraps around
existing FF code:
http://chrispederick.com/forums/viewtopic.php?id=2518
On Jan 21, 3:01 pm, Roman Land wrote:
> I am positive the issue is not with Mootools, this is a
I am positive the issue is not with Mootools, this is a very basic use and I
am positive any bugs would be already fixed..
On Thu, Jan 21, 2010 at 10:17 PM, hairbo wrote:
> Hi all,
>
> This appears to be either a problem with Mootools or with the "View
> Generated Source" feature of Web Develope
Hi all,
This appears to be either a problem with Mootools or with the "View
Generated Source" feature of Web Developer 1.1.8, (running on Firefox
3.5.7 on Snow Leopard).
If I run the code contained in the shell:
var d = new Element('div', {id: 'el1'});
d.set('html','injected stuf
So I ended up figuring out the problem. What happens was because in my
curry function, I was doing:
args.extend(arguments);
My bad for not looking at the documentation but extend mutates args,
hence each later call would just push the new event to the list will
keeping the old one there. That of
I was goofing with this earlier and couldn't get it work either (or
Swiff.Remote). No time to continue fiddling but I will be as soon as
some of my current projects finish up.
On Jan 21, 2010, at 10:28 AM, Fábio M. Costa wrote:
http://mootools.net/blog/2008/02/12/whats-new-in-12-swiff/
If
Hi there,
The documentation says you can add an onload event to Asset.css, but looking
at the code, it really does not add the event. Also, doing some testing,
seems like the browser (Firefox 3.6) does not fire a load event attached to
a link element.
Any experience with this? Is the documentation
http://mootools.net/blog/2008/02/12/whats-new-in-12-swiff/
If you still cant solve your problem or have read it before just tell us.
--
Fábio Miranda Costa
Solucione Sistemas
Engenheiro de interfaces
On Thu, Jan 21, 2010 at 3:07 PM, reddrumhead wrote:
> I'm experiencing a strange problem wit
I'm experiencing a strange problem with the Swiff class.
I was loading an Actionscript 3 swf into a div using mootools with
the following code:
var swf = new Swiff('webcam.swf', {
id: 'webcam',
width: 720,
height: 370,
container: $('swf-content'),
events:
So then sometime in the near future Aptana will have auto completion and
object property introspection for mootools?
On Thu, Jan 21, 2010 at 4:53 AM, fakedarren wrote:
> With regards to Aptana support - we were approached by their team and
> asked to provide the necessary files to get autocompl
You and your "best practices" and "good coding habits".
On Jan 20, 11:59 pm, Aaron Newton wrote:
> var x = 'x';
>
> var foo = function(){
> var x = 'foo';};
>
> foo();
> //x is still 'x'
> var bar = function(){
> x = 'bar';};
>
> bar();
> //x is now 'bar'
>
> window.addEvent('domready', bar);
Thanks, thats what I figured. Alright cool!
On Jan 21, 9:36 am, Ryan Florence wrote:
> If you have to reuse it then assign it to a variable.
>
> var a = $('a');
> a.doSometing.
> // later
> a.doOtherStuff
>
> Is better than
>
> $('a').doSometing.
> // later
> $('a').doOtherStuff
>
> On Jan 21, 20
If you have to reuse it then assign it to a variable.
var a = $('a');
a.doSometing.
// later
a.doOtherStuff
Is better than
$('a').doSometing.
// later
$('a').doOtherStuff
On Jan 21, 2010, at 7:26 AM, KevinA wrote:
Just wondering whats the best practice performance-wise.
var a = $('myel');
Just wondering whats the best practice performance-wise.
var a = $('myel');
-or-
Do I just use $('myel') whenever I need it in my code as opposed to
using my 'a' variable.
Any thoughts?
Its a basic question but wondering how much a difference either method
has from the other.
I would really like to write the column name and sort direction to a
cookie so that I can make my sort order persist when I reload the
page . Once I get it into the cookie ai can do the rest. Could
someone give me some pointers?#
Thanks in advance
With regards to Aptana support - we were approached by their team and
asked to provide the necessary files to get autocompletion etc for
MooTools. Long story short, it's a very long and arduous task, and I
am waiting until MooTools 1.3 is out (which is not that far away) and
once that is done or cl
Why not use *JSON*? its cross platform cross programming language and its
simply awesome!
On Thu, Jan 21, 2010 at 2:04 PM, woomla wrote:
> Thanks for pointing me in that direction. I've got it kind of running.
> I need to test to see if textContent exists at one point because IE
> doesn't have t
Thanks for pointing me in that direction. I've got it kind of running.
I need to test to see if textContent exists at one point because IE
doesn't have that property. I can use innerText, but FF doesn't have
that one. I hope for a Moo solution one day.
During testing, I've discoverd one thing. IE
what i'm contemplating right now is to change the repo name to see if this
is really a caching issue or something like that...
the thing is the repo name is quite literal, so changing it will be quite
annoying...
---
אריה גלזר
052-5348-561
5561
2010/1/20 Fábio M. Costa
> Yes, it wasnt.
/**
* @class shape
*/
var shape = new Class({
getName : function() {
}
});
/**
* @class polygon
* @extends shape
*/
var polygon = new Class({
Extends : shape,
getWidth : function() {
},
getHeight : function() {
}
});
/**
* @type polygon
*/
var myPol = new polygon();
45 matches
Mail list logo
