This is a know issue, and there is an open issue for it:

https://github.com/yahoo/mojito/issues/1091

The workaround is also described in the issue.

Caridy, thanks, I wanted to use Mojito for a while but I wanted it on a windows machine.

Caridy, thanks, I wanted to use Mojito for a while but I wanted it on a windows machine.

I have a code like this:

Y.namespace('mojito.controllers')[NAME] = {        auth: function(ac) {            var auth = ac.passport.getPassport().authenticate('google');            auth(                ac.http.getRequest(),                ac.http.getResponse()            );        },

auth function is from apssport js and create redirect. After few seconds mojito return:

error: (outputhandler.server): { [Error: Killing potential zombie context for Mojit type: HTMLFrameMojit, controller: HTMLFrameMojit, action: __call] code: 408 }

Is there any way to kill this context or said to "Mojito" that it is completed?

PR1103 was merged yesterday, and v0.6.0 will be released in about 3 days with support for windows:https://github.com/yahoo/mojito/pull/1103

PR1103 was merged yesterday, and v0.6.0 will be released in about 3 days with support for windows:https://github.com/yahoo/mojito/pull/1103

PR1103 was merged yesterday, and v0.6.0 will be released in about 3 days with support for windows:https://github.com/yahoo/mojito/pull/1103

PR1103 was merged yesterday, and v0.6.0 will be released in about 3 days with support for windows:https://github.com/yahoo/mojito/pull/1103

It is your lucky day! PR1103 was merged yesterday, and 0.6.0 will be released in about 3 days with support for windows:

https://github.com/yahoo/mojito/pull/1103

just a simple question

Well, __call is an artifact for generic mojits to react to any action invoked, even when that action is not defined. This is an internal API, and one that we might eventually remove since it is a little confusing.

The good news is that you, as an app develop, have full control over the specs and the actions to be executed for every mojit instance in you application, which means you really don't need __call in your frame.

Thanks a lot for your answer.I missed that part.I like the idea of customizing my own FrameMojit, I will give it a try :-)

I found no mention of the "__call" method in the doc, about FrameMojit.

But it looks necessary to use it (in the FrameMojit), in order to have a default action.

Is it safe (or internal api subject to change)?

This was solved a while ago when ac.done() and ac.composite.done() become equivalents in term of api.

@Dodo, we encourage people to customize their own FrameMojit, so they can have full control of the page initialization, and structure. Here is the doc with the details on how to do that:

http://developer.yahoo.com/cocktails/mojito/docs/topics/mojito_frame_mojits.html#creating-custom-frame-mojits

Now, if you're not up for it, you can still achieve the header/footer implementation by creating a container mojit, set up a "base" instance of that which is responsible for setting the header, footer and body children, and later on, you can reuse and customize that per route to load a different content mojit within container, something like this:

[ { "settings": ["master"], "appPort": "8666", "specs": { "container": { "type": "ContainerMojit", // this one just do `ac.composite.done()` call, nothing else. "config": { "children": { "header": { "type": "HeaderMojit" }, "body": { "type": "DefaultBodyMojit" }, "footer": { "type": "FooterMojit" } } }, }, "custom-page": { "type": "HTMLFrameMojit", "config": { "child": { "type": "container", "config": { "children": { "body": { "type": "CustomBodyMojit" // this overrule the type from the "base" container instance } } } } } } } }]

3) I answer to myself. It works when I do not forget the {{{remove}}} in the customized view.This makes me think it is not the best way ! :)No?

Hi,I like mojito more and more!

I want to add some default chrome/ui common (footer, header, ...) to my whole app.

I was thinking about 2 of doing it.1) in the child of the HTMLFrameMojit (I have some routing problem with that, will talk about it later).2) in the view of a new customized HTMLFrameMojit .

I'll develop about the 2nd possibilty.I created a new mojit. In its controller i require the HTMLFrameMojit (and its dependencies) and simply do

 YUI.add('body', function(Y, NAME) { Y.namespace('mojito.controllers')[NAME] = Y.Object(Y.mojito.controllers.HTMLFrameMojit);  }, '0.0.1', {requires: ['mojito', 'mojito-util', 'mojito-assets-addon', 'mojito-deploy-addon', 'mojito-config-addon', 'mojito-composite-addon', 'HTMLFrameMojit']}); 

Then I copy the HTMLFrameMojit views and customize them as I want.

Few questions about that:

1) Is it bad?

2) Is there a better way of doing it?

3) Of course it is not (totally) working. My mojits are not deploy to the client ( "deploy":true in application.json). Any idea why?

Thanks a lot!

No, invoke is the API to execute an action from a binder, it just happens to rely on rpc call to a server if the mojit to be invoked is not in the page and can't be deployed to the client side. In other words, you should not use invoke to communicate with a middleware, which is what you normally use to upload files into an express application. The reason why you should not do it is mostly because there are limitations in the data you can send but mostly because we control that rpc mechanism, and we might change it in the near future since it is an internal api.

Hi,

I'm note sure it works that way.file is a map of key/value pair,not sure values are file.And if you look at the params actioncontext addon, you can notice the file params does not look so usable, as you will get an empty object.

http://developer.yahoo.com/cocktails/mojito/api/files/node_modules_mojito_lib_app_addons_ac_params.common.js.html#l36

I'm a bit confused about those params in the invoke functions, what do they correspond to?

Anyway it is still worth to try it, and wait for a bartender's answer!Have fun!

Hi!

I'm looking to MojitProxy Invoke method: http://developer.yahoo.com/cocktails/mojito/api/classes/MojitProxy.html#method_invoke

And I have noticed that I can send a file as params, I'm wondering if I can use this functionality to upload files through passing the file to params.file variable, and handeling that on the server side by calling MojitProxy.invoke function.

Is it possible to do that? if so, can you please give a guidance?

Thanks.

@caridy thanks for the answer.

It is not really a use-case, I just noticed that when experimenting with a mongodbCRUDMojit.I was creating a mongoose schema in an old unused module (bad) and creating again the same schema in a mojit model.I'll follow your advice and will only define things in YUI modules.Thanks again.

Thanks, I'll keep you updated!

@Dodo, thanks for taking the time to write about this. I did a quick pass, and everything makes sense. Make sure you share the final article with us so we can post it thru our channels.

@Dodo, yes, on the server, everything that is available with common or server affinity will be attached when the server boots. This is a provision to improve performance by not having to attach modules when needed in a controlled environment like the server. Usually, those YUI Modules will define things, instead of automatically carry on with an operation.

I want to learn more about your use-case, what exactly does the YUI Module is trying to do that it can't be automatically attached?

Hi bartenders,

My yui modules in the yui_folder are attached (the function fn in YUI.add(name, fn) is executed ) even if I do not use (YUI().use) or require (requires:[...]) them.

If one put toto.js in yui_modules:

   YUI.add('toto', function(Y, NAME) {    Y.log('Hello', 'WARN', NAME);   });

You will see the 'Hello' when starting mojito even if nobody uses toto.

Is there a way of avoiding that?

It is maybe related to https://github.com/yahoo/mojito/issues/53

Hi,

While I'm learning and playing with mojito, I'm trying to write some tips, examples and guides.The first one is an simple example of a mojit with many children.I hope it could help beginner.

The example description: http://lazybean.github.io/DocMojito/articles/multiMojits.htmlThe example live: http://examplemojito-multimojit.herokuapp.com/

I'll be happy to get some comments about it.

thanks you all ??

Hi Caridy,

Thanks for your clarification.I still have some confusion (point 2).

• I was thinking this @MojitName/actionName should not be used in production, thanks for confirming that. It's however quite convenient to have a fast look at a freshly created/discovered mojit.

• Thanks for pointing out that bot use-cases should be supported. In the non-javascript scenario, the route that handles the submit is defined at the application level, there is no way to define it in the mojit?If I put my mojit on npm, people that want to use it will need to be aware of what routes they need to set up for the mojit to work. No?Or can I imagine a way (as an addon) for my mojit to render a dynamicly created url (that is routed to the action) in my view? Bad idea, or not so possible?

• I was a bit confused with the difference between mojito deployment and mojits deployement.Super clear now, thanks.

Hey Dodo, few notes:

• @MojitName/actionName is an artifact for development, and you should not use it in production. The only reason it is there is to get the app running even when you don't have routes. I'm pushing to get that removed from the framework in 0.6.x

• About the specific use-case, in theory, if you have a form, you should support both use-cases, submittion by navigating to another page (non-javascript escenario) and an internal process to deal with the submit using ajax. In other words, you should have a route that handles the submit action by calling an action in a mojit, which can do something and redirect to a new url. And also, handle the action by doing mojitProxy.invoke(), which will do the same but thru a controlled tunnel request.

• invoke does not requires all mojits to be deployed to the client side, it can execute actions in the server side if the affinity of the mojit is server.

• invoke only works if mojito is deployed to the client side, which is what HTMLFrameMojit does, so, yes, you need that.

Hopefully this will help to clarify!

Hi.Thanks for you great work on mojito.I like it but I'm still a bit confused about some points (how should I do what).

Let's I have a mojit with a button/link/events (I'll refer to it as event) that should trigger an action in the mojit controller.(As exemple, think about a form mojit that handles by himself the the submit).I see two way of doing it:

1) Having an route at the application level: the event will trigger a http request to a path define in routes.json that call or mojit action.We do not need a binder to do that, it could even not need javascript.But the route is defined at the application level. So the mojit will not work out of the box(*) (i.e. going to <8666>

It works now, thanks!

I would have never imagined that you needed to alter the request object to change the composition of the response.

It works with POST as well, to the extent I could test it.