2 ms·

I've been playing around with it for a few weeks. It's pretty nice. I especially like their web services api. My complaint with it is that the documentation

I've been playing around with it for a few weeks. It's pretty nice. I especially like their web services api. My complaint with it is that the documentation is sparse at this point. Whether because of that, or because of something else, the language feels claustrophobic to me, like I'm limited to the standard library. For example, I'm not sure it's possible (or I never figured out how) to do things synchronously. Let's say you want to apply some jquery plugin to an object, but it must be done after the object exists; I'm not sure that's possible with mobl.

zefhemel 16y ago
Documentation is definitely an issue at this point. Although it's expanding. Not sure what you mean with your synchronous question and the "object that exists".
- MatthewPhillips 16y ago
  Mobl is control-based. From what I can tell, I can't do arbitrary (javascript) logic on the DOM unless it is wrapped in a control.
  - zefhemel 16y ago
    right, well you can also do that from any piece of logic using the JQuery API, if you have to: http://docs.mobl-lang.org/mobl/JQuery http://docs.mobl-lang.org/mobl/JQuery
    - MatthewPhillips 16y ago
      That example has the logic being performed from an event callback. How can I perform logic when a control is created? For example, I want to insert some html div into the DOM, then instantiate some jquery plugin on the inserted div. I have tried this and the compiler complained. I'm sure I'm doing it wrong but the documentation doesn't help. For example screen root() { header("Title") $("#div").someplugin(); } Can't do that. I tried to get around this by creating a control, but from what I can tell controls return html, not objects.
      - Zef 16y ago
        Not sure this is the place for it (maybe ask on the google group?) But there's two ways: screen root() { mydiv@<div/> script { mydiv.someplugin(); } } mydiv will be bound to a JQuery object representing the div. You can also just do this: screen root() { script { $("#div").someplugin(); } } So generally your answer is: put it in a script { ... } block.

zefhemel 16y ago

Documentation is definitely an issue at this point. Although it's expanding. Not sure what you mean with your synchronous question and the "object that exists".

MatthewPhillips 16y ago
Mobl is control-based. From what I can tell, I can't do arbitrary (javascript) logic on the DOM unless it is wrapped in a control.
- zefhemel 16y ago
  right, well you can also do that from any piece of logic using the JQuery API, if you have to: http://docs.mobl-lang.org/mobl/JQuery http://docs.mobl-lang.org/mobl/JQuery
  - MatthewPhillips 16y ago
    That example has the logic being performed from an event callback. How can I perform logic when a control is created? For example, I want to insert some html div into the DOM, then instantiate some jquery plugin on the inserted div. I have tried this and the compiler complained. I'm sure I'm doing it wrong but the documentation doesn't help. For example screen root() { header("Title") $("#div").someplugin(); } Can't do that. I tried to get around this by creating a control, but from what I can tell controls return html, not objects.
    - Zef 16y ago
      Not sure this is the place for it (maybe ask on the google group?) But there's two ways: screen root() { mydiv@<div/> script { mydiv.someplugin(); } } mydiv will be bound to a JQuery object representing the div. You can also just do this: screen root() { script { $("#div").someplugin(); } } So generally your answer is: put it in a script { ... } block.