Any news?

Just curious if there is any news about the future of JotSpot with the Google acquisition.  I understand that there is probably a lot of work going on in the background... but if there's any information to share with Jot users about the future of this product, we'd love to hear about it!

Thanks.

E4X and jot:ext table parsing example code

Hi everybody,

I've attached a zip with source for a couple of pages that might be of interest if you're working with E4X or jot.lib.ext().

One of the files, ImportAPIsLib, rips apart an HTML table, and uses E4X to do it.
The other one, ImportAPIs, provides an example of how to use the Lib page.

The code is mostly commented; it's not all perfectly elegant, but it does work. If people find this useful and have documentation questions, post 'em in the forums and I'm happy to answer.

Improve the performance of your Wiki in one easy step

We've found an optimization that - in the case of our large-sized Wiki - has shaved two seconds per page off of our page loads. And it's one line of code!
Please note the following disclaimer:

THIS HAS NOT YET BEEN BLESSED BY JOT. THEY INFORMED US THAT THE CODE IS THE WAY IT IS BECAUSE OF AN OLD BUG IN THE SERVER.
THEY HAVE NOT YET FULLY REGRESSION TESTED OUR OPTIMIZATION, BUT THEY PLAN ON MOVING IT INTO THE DEFAULT THEME IF THE TESTING
GOES WELL. UNTIL THAT TIME, USE AT YOUR OWN RISK.

That said, we have not had any problems. All is well and pages just load faster. The offending line of code is in
/System/Themes/_your_custom_theme/attachments. Or, if you are using the default Jot theme, the code is in
/System/Themes/Jot/attachments. If you do an xml=esc on that page, the fifth line of code is this:

<jot:search forFormName="attach" filter="it/attach/URI and it/parent/path = page/path or (it/parent/mail and it/parent/parent/path = page/path)" set="attachments" showHidden="true" />

The logic of this search is what was taking so much time in our wiki. What it does is find all attachments in the wiki, and
then makes sure the attachments are children of the page you're viewing, etc. This proves to be quite slow in our wiki
because we have so many attachments to pages. In fact, even on a page that had no attachments, the search was still
taking 2.2 seconds in our wiki.

Here is the line of code that replaces the above line of code:

<jot:search forChildren="\${page/path}" filter="it/attach/URI" set="attachments" showHidden="true" />

Note: do not include the backslash character before the dollar sign in the above line of code

This search simply finds children of the page you're viewing and then makes sure those children are attachments. Voila!

Again, use at your own risk. I recommend that you comment out the existing line of code using html comment tags, then place the new line of code underneath it.
That way, if you have to revert it will be easy.

Hope this helps some folks out there who, like us, have large wikis with lots of attachments.

Edit locally, push pages using cURL (over https)

We at Chordiant have multiple developers working on our Jot webspaces, and while the latest version of the Ant tasks published by JotSpot are a great improvement, we still couldn't quite bring ourselves to use them for a couple of reasons. First and foremost, they do not work over https (at least not out of the box). Secondly, we do not use Eclipse here and therefore getting the Ant tasks to run at all was a bit of a headache.

Enter cURL. Since cURL (http://curl.haxx.se/) can speak https from native Mac OSX, almost all Linux distributions and from within Cygwin (the installation of Cygwin is straight-forward, but beyond the scope of this blog post ... briefly, just download the Cygwin installer and make sure you check the cURL and SSH check boxes on install), it seemed like a good solution to our problem. cURL can also emulate an HTTP POST operation, which was the final piece to the puzzle.

We use Subversion as a repository for all of our Jot source code, so the script described here allows for the .svn directories that are interspersed in our Jot source directories. But even for single-developer projects, editing locally is often very convenient. It allows for global search and replace across all pages in your wiki, for example.

Attached to this page is a file called jot-bin.zip. Download the file and unzip it in the directory that you plan to use to house your local JotSpot source files. For example, I have my source files in c:/jot/svn. When you are finished unzipping the jot-bin.zip archive, the files should be in a directory like this: c:/jot/svn/jot-bin/. Now download a zip file of the webspace you wish to edit locally. Let's use my thom27.jot.com webspace as an example. Personally, I don't like to have all the revision history locally, so I use this command to grab a webspace: http://thom27.jot.com/_/cmd/admin.exportZip?includeRevisions=0

This downloads a file for me named thom27-060928-1044.zip (date and time will change, obviously). Take your zip file and unzip it to the same directory that you unzipped jot-bin. Then rename it to be just the hostname of your webspace. When I'm done I have this: c:/jot/svn/thom27/.

Now go to the jot-bin/tmp directory and create a folder with the same name, for example c:/jot/svn/jot-bin/tmp/thom27.

Next, make a duplicate (using copypaste in the Windows explorer, for example) of the jot-bin/pushTemplate.sh file, name it pushthom27.sh, for example. Open that file in your favorite editor (for example, BBEdit on your dual-core, Intel based Macintosh - oops, sorry, couldn't resist). There are several tags that need to be searched and replaced with your values before you can use this shell script. They are described below:

@@SOURCE_PATH@@ - this is the absolute path to your webspace's source tree. On Cygwin, this is something like '/cygdrive/c/jot/svn/thom27/'. On a Mac, this is something like '/Users/thom/jot/svn/thom27/'.

@@SCRIPT_NAME@@ - this is the name of your shell script, after you renamed it. In this example, the value should be 'pushthom27'.

@@SOURCE_DIR@@ - this should be the short name of your webspace. In this example, the value should be 'thom27'. It _must_ be the same name as the top-level source directory and the name of the directory you created inside jot-bintmp.

@@ADMIN_PASSWORD@@ - this is your admin password.

@@PROTOCOL@@ - this is either 'http' or 'https', depending on whether your site runs over http or https.

Now save the file. Open a Cygwin window or a Terminal window if you're on Mac or Linux, cd to the jot-bin directory and type, for example, ./pushthom27.sh --help ... this will give you some help as to what options the push script has. The first thing you should do is create a touch file by using './pushthom27.sh --touch'. Now, just to make sure we're ready to start editing, type './pushthom27.sh --show', which will give you a list of files that have been modified locally since the touch file was last touched. This should not show any files because we just created the touch file.

Now for the grand finale. Open, for example, the WikiHome.xml file for your webspace using your favorite code editor. Make a change and save the file. Now go back to your Cygwin or Terminal window and type './pushthom27.sh' and watch your change get pushed up to your webspace. If you're running in a native environment such as Mac or Linux, you will be amazed at how fast the files are found, zipped and pushed to your site. So quickly, in fact, that at first I was sure it wasn't working.

A couple of quick notes about editing locally:

* We erase any 'editTime' or 'modificationTime' information in the first <node line of our local copies. We also hand-enter our user names in the 'user' property. This ensures that the revision history of the pages that are edited locally and pushed via this script remains valid.

* As stated before, if your local copies are in fact subversion repositories, this script ignores any .svn directories. If you use CVS, change all occurrences of '.svn' with '.cvs' in the push script and it should work with CVS also.

* In a multi-developer environment, it's easy to clobber each other's changes unwittingly. We use the '--show' option a lot here before we push just to take a peek before pushing something we didn't realize had been modified locally (for example, because of an 'svn update' operation).

* Although page attachments come down in the form of ..attachment_file_name/_data/attach.URI.dat files, you can take the attach.URI.dat file, rename it and move it so that it is inside of an _attach directory and then edit it/push it using this script. For example, if you have an image.gif file attached to a page, it will come down in the .zip archive as ..image.gif/_data/attach.URI.dat. Simply rename attach.URI.dat to 'image.gif' and rename '_data' to '_attach' and then you can edit the .gif file using Photoshop or some other editor, save your changes and the use the push script to send your changes up to your webspace.

Hope this helps some folks out there. I'd be happy to answer any questions anyone has regarding this script. Also, if enhancements are made, please do share.

Cheers!

I am missing one thing in new version

Hi, in version 2.7 there is nice combination of diffrent apps but i missing one thing that is clock, it should be like world clock which should be able to show the timings of diffrent contries on one place. now we doesn't have a way to do this.

Help! Proxy Error on New / Updated Pages

Hi! I just finished creating/updating pages, and suddenly two of them, when I click on the link, give me this message instead:

 
Proxy Error
 
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /WikiHome/CustomerSupportPortal/TechAlerts/TA_717N.
Reason: Error reading from remote server

Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.
 
What does this mean, why does it happen, and how do I "recover" my pages without having to recreate them with new names (since the nodes don't like to let you create new pages over old ones of the same name).

Thanks!

Group permissions and adding comments

I've set permissions to quite a few of my pages using groups (as opposed to adding individuals to each and every page).  Unfortunately, users who are part of the group can't seem to add comments.  The comment button appears, and they can seemingly add a comment, however when the comment is 'saved', nothing appears on the page. When I add the same user directly to the ACL for that page, they can add a comment.

Is this a known issue, or perhaps there's something I've missed? I've searched the knowledgebase and developer community quite extensively, but I can't seem to find any info on this specific issue.

If anyone could help out, it would be greatly appreciated.

Rolf Johansson.

Project Gantt Chart ??

I've begun using JotSpot's Project manager, and so far so good.  However, I think it is very limited that there doesn't seem to be any ability to create and work with Gantt charts.  Is this available or in development?

Attachments > 10mg

My client was told that attachments larger than 10mg could be attached (at extra cost, I guess) but  I have not found instructions on how to do so. Ideas? Help? I have at least 3 to 5 of over 25mg (zip files)

More Version 2.7 issues

Product Bugs
·          Product Bug: When I am in edit wysiwyg mode and typing, the page suddenly wants to navigate somewhere else. I start typing in wyziwyg and I keep getting asked “Are you sure you want to navigate away from this page? You are currently editing this page. Press OK to continue Or Cancel to stay on the current page.” Why, how to stop  it?
·          Product Bug: Error message: unable to edit WZYWIG [object error]. I have to go back to an earlier version and that’s causing unnecessary rework. It’s happening more and more on some pages, and again after I return to an earlier version and try the edits again (and in other ways).
·          Product Bug: Error Message: unable to save changes -  sometimes this happens just after I add plain text, and other times after I format text I have added.
·          Product Bug: Sidebar Administration not available despite the fact that I saw and commented on it in a Webinar recently.
·          Product Issue: JotSpot  keeps adding returns between lines for no reason I can see. How to avoid without rewriting HTML code?

Jot 2.7 Theme issues

Scott recommended I create a blog post to collect Jot 2.7 Theme issues. Please comment away and add to this list. These are the ones I have found:

Some bugs or concerns I have noticed in 2.7 wikis. Some may not really be bugs:

• Can't use Create Page button to create a plugin.
• Not logged in, click on Recent Change link. Click on Feeds link. There is an error on the Feeds page. Maybe the real error is you can get to pages not-logged-in if you know the URL.
• Click on any non-HTML page in Internet Explorer (Windows XP SP1, IE6) and it cannot open the item.
• Index of all pages gives you strange results. Why is the Photo Pages Pictures page there but not any of the other pre-installed apps?
• The new design's CSS is treading into severe classitis. Way too many classes. And a lot of them aren't included in the main style sheet so you are left to deconstruct and search for missing things.
• The styles for the Page Type Picker classes are contained in a separate style sheet from the others and are missing from the main CSS file. Will this make them resistant to custom theming?
• The old "legacy" styles are still being used on some pages, such as the Index of all pages page. They are difficult to override.
• The main style sheet is not LAST in the series. This makes it very difficult to override styles that come later, such as the Jot tabs styles.
• There is no preview button when you edit!!! I can see saying it's not needed for wysiwyg editors, but it needs to be there for the XML and Markup editors.
• There should be a means to turn off the insta edit feature.
• There are old plugins that need to be removed or marked as examples or something because if you enable them they don't work.
• The Appearences page is really cool but it doesn't really apply the colors you give it. It applies shades of those colors. Maybe that needs to be made clear.

I don't want to rain on the parade, but

I stayed away because I was encountering a really frustrating login SNAFU and didn't want to get sour ... I think Jot/Dojo are foundational to Web2.0. Today login just worked.

So I added a comment to the one item I've posted. Then I appended an addendum to that item. I got "Unknown Error -  Additional information: javascript evaluation exceeded threshhold <script meter: 10730/10000ms, 12512/10000000000insts>"  and the addendum was no longer there. I went to add another comment and found that the first one was nowhere to be seen. I added the comment and went to re-edit the item. The addendum was there when I went into Edit mode.

Scary.

Workflows

Workflows: how things get done.

There are tools to help with real-time collaboration, such as IM, chat and whiteboards; the remainder of so-called "collaboration" that people do is really going through a workflow and our tools need to support this.

JotSpot is, in my opinion, an on-demand platform for building collaborative web applications, rather than the wiki that it owes its inspiration to. As such, native support for workflows would be a massive plus and I would love to know whether this is on the roadmap.

JotSpot is competing in a DIY-web space now, alongside products like Coghead, Central Desktop and Quickbase, many of which offer workflow support. Jot is, in my opinion, a fantastic environment for creating web apps that are useful to both consumers and businesses, but the one thing that it really lacks is this notion of the workflow - what do you think guys?

J.

CSS Tools

How to handle IE-specific CSS issues
http://www.satzansatz.de/cssd/onhavinglayout.html#list

Free CSS cheat sheet

<jot:toc /> acting quirkry - Is there a bug?

I am a new member to developer.jot.com and I love it.

I am using the <jot:toc /> on my wiki and I think it has a bug.

Sometimes the Table Of Contents renders corretly and works perfectly, other times the Table of Contents includes extraneous info.

Bad toc (see pic)

Good toc (see pic)

Here is my markup.

I have this bug on both Firefox 1.5.0.6 and also Safari 2.0.4.

An interesting thing is after you edit the page even with no changes the toc renders correctly, until you restart your browser or clear the browser cache.

Has any else experienced this? Is there a fix?

Marcus

Older | Newer

» I adapted this code to ... ...
» Oh, yeah. On the E4X ... ...
» For Mac users who see ... ...
» Yes, the problem has to ... ...
» I don't know. I ... ...
» Works for me. Thanks for ... ...
» P.S. you'll have ... ...
» I've gotten that error ... ...
» Any idea what this error ... ...
» I didn't really want ... ...