jbelis's dashboard

jbelis replied on June 17, 2009 01:52 to the problem "Not able to edit my widget. Needs quick resolution - since the widget is deployed to the world" in zembly:

The fix for this problem will be included in the next production push, either this week or early next week.

jbelis replied on June 16, 2009 23:49 to the idea "Suggestion: Easier way to do an application-wide CSS" in zembly:

This makes a lot of sense, both in terms of ease and development and performance. We should definitely add it.

In the meantime, one workaround it to use CSS imports. you can upload you app-wide css file as a resource of one of your application widgets, publish the widget, add a reference to it in the CSS code using @import. You can then find out what the URL is, and use it to add imports into all other widgets.

jbelis started following the idea "Suggestion: Easier way to do an application-wide CSS" in zembly.

jbelis replied on June 11, 2009 17:36 to the problem "Not able to edit my widget. Needs quick resolution - since the widget is deployed to the world" in zembly:

Hi,

A couple more questions to help us debug this quicker.

Do you see this issue when you load the info page (take out #edit from the URL and reload if it is there) or when you open up the edit zone?

If you have firebug, would you be able to give us the error stack trace?

jbelis replied on June 09, 2009 13:45 to the idea "Javascript text editor auto formatting is annoying" in zembly:

Thanks. This is very helpful.

We'll be looking more closely at load time (I assume a long load time is the cause of #1) and typing responsiveness (#2?). Hopefully some changes already underway will help at least #1.

As for #3, just wondering if you are seeing no syntax coloring at all or if you are seeing parts of the code not being colored as they should. Also does the same piece of code sometimes get colored properly and sometimes not, or is some of your code never properly highlighted?

jbelis replied on June 08, 2009 17:00 to the idea "Javascript text editor auto formatting is annoying" in zembly:

malachid,

Thanks for the feedback. We are actually seriously considering replacing the default editor with bespin, mostly to take advantage of the rapidly growing bespin feature set, but also in part because fixing this and other issues in the default editor is not easy.

I would be very interested to hear more details about what functionality you are missing in Bespin. And which aspects of the look and feel you would miss.

jbelis replied on June 03, 2009 05:08 to the idea "Javascript text editor auto formatting is annoying" in zembly:

malachid: thanks for the feedback. Could you elaborate a bit? What does the code look like after and before you format?

Also, which one is the "other editor"?

thanks.

jbelis replied on April 30, 2009 16:02 to the problem "i cant able to see my source code" in zembly:

Hi Siva,

This happens from time to time.

If you are a firefox user you should see the "Try Bespin" button above the source editor on the right. Bespin is a new editor technology from Mozilla which will eventually replace the current editor. Can you try switching to bespin and see if this addresses your issue?

Thanks

jbelis replied on March 30, 2009 17:56 to the question "Bird template error" in zembly:

Hi John,
Can you try saving your customizations and see if this solves the problem? If not, send me a link to your app on zembly and make the app public so I can see it.

jbelis replied on March 24, 2009 15:37 to the question "Is zembly being actively developed and if so where?" in zembly:

Scott,

zembly is absolutely being actively developed. Check out http://blog.zembly.com to see what has gone on recently.

It is not an opensource project, and there is not publicly available issue tracker at this time. The forum (http://forum.zembly.com) and the wiki provide ways to get help shoudl you need it.

jbelis replied on March 23, 2009 17:14 to the question "je veux developper ma propre application mes zmbly ne me donne pas la main pour modifier le code est ce que vous pouvez m'aider merci" in zembly:

Bonjour!

Je pense que vous avez cree une application a partir d'un des modeles (templates). Dans ce cas le code des differents services et widgets de l'appli n'est pas modifiable sans passer en mode "developer" (edit mode).

Ceci se fait en cliquant sur le lien ("edit the code") dans l'editeur de code, du widget ou service a modifer. Apres confirmation vous pourrez modifier le code.

jbelis replied on January 16, 2009 06:48 to the problem "Issues with Zembly Code Editor." in zembly:

Hi Paul,

Would you be able to enable the java console to see if the editor helper applet is throwing any exception?

jbelis replied on January 08, 2009 23:02 to the problem "After publish in full-screen edit mode-no scroll bars on widget view page." in zembly:

Yep. Seeing this as well.
Bug filed.
Thanks for the report.

jbelis replied on January 07, 2009 22:58 to the question "Help needed with debugging" in zembly:

In a widget the preview logs are output in the firebug console. Don't look in the UI.

In a service, the logs are sent to the "Logs" panel inside the "test drive" tab on the right of the editor.

In the widget case, I often end up previewing in a separate tab, and using firebug from it.

jbelis replied on January 07, 2009 20:49 to the question "Problems with cache?" in zembly:

no problem. Glad it works for you know.

jbelis replied on January 07, 2009 00:34 to the question "Problems with cache?" in zembly:

Not seeing the same thing, sorry... also cloned the same widget and for me changes are active as soon I preview.

Do you have the same issue if you check "preview in a new window"?

Is it saved? If you reload the page do you see the changes? Does the preview work then?

jbelis replied on January 06, 2009 22:42 to the question "Problems with cache?" in zembly:

despite the closeness in the UI, the 2 are unrelated in terms of how they are implemented.

I am seeing the preview work regardless of the enable logging flag.

What do you mean by "doesn't work"? Is it that the changes you are making to the code are not taken into account when you preview or is it that the widget preview behaves differently (for the same draft) depending on whether logging is used or not?

Could there be something in your widget that clashes with our logging runtime?

Can you paste the link to your widget?

Also, which browser are you using?

jbelis replied on December 16, 2008 00:58 to the question "Breaking out the share this widget for wordpress to individual bookmarking sites" in zembly:

Hi traffichoney,

The widget in the share this widget section of zembly comes from clearspring. It is not a zembly widget unfortunately. I believe clearspring sharing capability can also be displayed as individual buttons, as opposed to the share menu used in zembly. But you would have to refer to the clearspring documentation for this.

At the moment zembly does not do anything specific to facilitate the creation of widgets that embed clearspring components.

Let me know if I am missing the point here.

jbelis replied on November 17, 2008 19:08 to the question "Problems with cache?" in zembly:

Harlley,
The fixed has been rolled out. Thanks again for pointing this out.

jbelis replied on November 07, 2008 23:31 to the question "Problems with cache?" in zembly:

Harlley,

Thanks for finding this out. Just reproduced the bug as well. Yes this is a bug.

I will get back to you shortly. I hope you can continue to make progress on the functionality until this gets resolved. compression optimizes performance for widgets that have a lot of code. It will not affect functionality.

Jacques