Re: [Jchat] Tutorial documentation

2014-06-08 Thread Joe Bogner
bob, this is neat. Thanks for sharing. I have been thinking along these lines as well. Your right window reminds me of a variable watch window. It would be handy to automatically refresh the watch list whenever one of the variables change. I'm not aware of anything out of the box that provides a ho

Re: [Jchat] Tutorial documentation

2014-06-06 Thread robert therriault
Hi all, I just put up a demo of what I have been hashing around adding media to labs in the JHS environment. I am not sure that I will be going much further with this in the lab environment on Eric's suggestion of looking into sp.ijs as a way to provide the functionality of multiple media types

Re: [Jchat] Tutorial documentation

2014-05-30 Thread Björn Helgason
It might be interesting if fif would allow searches in jsoftware. Possibly giving index to faq. On 29 May 2014 14:09, "Björn Helgason" wrote: > You could do faq to answer from different databases. > > Like: > > 'voc' faq 6 1 > > gives info on function 6 and just rank > > 'voc' faq 13 2 > > short

Re: [Jchat] Tutorial documentation

2014-05-29 Thread Björn Helgason
You could do faq to answer from different databases. Like: 'voc' faq 6 1 gives info on function 6 and just rank 'voc' faq 13 2 short description on function 13 'nuvoc' faq 15 3 long description on function 15 from nuvoc 'voc' faq 17 4 examples for function 17 and so on On 28 May 2014 16:4

Re: [Jchat] Tutorial documentation

2014-05-28 Thread Joe Bogner
I did something along these lines here: http://www.jsoftware.com/pipermail/chat/2013-October/005401.html Not faq, but pulling in dictionary entries for symbols. It would be useful to update it for NuVoc and let a person search by name (e.g. 'dict floor') too On Wed, May 28, 2014 at 12:20 PM, Bjö

Re: [Jchat] Tutorial documentation

2014-05-28 Thread Björn Helgason
It would be interesting to have a facility in J to send requests to jsoftware and get automatic answers. Lets say the verb would be running at the user. The user would type: faq 1 and get back an answer to the question: 1. What is J? J is bla bla bla and was created by bla bla bla next quest

Re: [Jchat] Tutorial documentation

2014-05-27 Thread Eric Iverson
I agree that we must keep and improve the existing labs. There is too much good and criitical material there. But if we have a better infrastructure for new labs then the old will gradually move to it. On Tue, May 27, 2014 at 12:43 PM, Björn Helgason wrote: > I do like the labs as is so using sp

Re: [Jchat] Tutorial documentation

2014-05-27 Thread Eric Iverson
Run JHS and check menu link|jhelp|sp (just a pointer to do sphelp). sphelp NB. noun that documents sp stuff The idea of managed script execution is an alternative to labs. But having a script as an html document with tags makes it very easy to include material in a script that is not just code

Re: [Jchat] Tutorial documentation

2014-05-27 Thread Björn Helgason
I do like the labs as is so using spx is a good idea but not change the labs that are now. Make new tutorial system using new features. Not eliminate existing demos and labs. I can see integrated video, helps, labs, demos, tutorials and have different versions for beginners and advanced but in a

Re: [Jchat] Tutorial documentation

2014-05-27 Thread robert therriault
Thanks Eric, I had not thought about spx as a replacement to the lab framework, in fact I have not ventured into that part of the framework at all (aside from seeing it as part of the ios when the ipad version came out). What would you recommend as the quickest way to come up to speed on this?

Re: [Jchat] Tutorial documentation

2014-05-27 Thread Joe Bogner
To throw out other ideas, I've really enjoyed using ipython notebook Here is an example notebook from someone else http://nbviewer.ipython.org/github/agconti/kaggle-titanic/blob/master/Titanic.ipynb And a random youtube video I found https://www.youtube.com/watch?v=H6dLGQw9yFQ Here's a similar

Re: [Jchat] Tutorial documentation

2014-05-27 Thread Eric Iverson
The labs were great in their time. Rather than recreate that wheel it might be worthwhile to step back and look at the issues in current light. I think the labs structure is too restricted. I strongly favor the JHS spx approach that lets you treat any script (or any text file) as a lab. I think th

Re: [Jchat] Tutorial documentation

2014-05-26 Thread Raul Miller
Environment specific stuff can be a hassle. Sometimes the best way to deal with that is to just document what the environment needs. That said, sometimes I wish I could have a dual server jhs/jqt (and I can see, in my mind, how that would have to be architected to function - but everyone has their

Re: [Jchat] Tutorial documentation

2014-05-26 Thread robert therriault
Well, I am looking at it and I will keep everyone posted if I make any progress, but I really won't feel bad if someone else wanted to take it on (or even better join in). I am starting with the JHS system using Safari as my browser. Even though the lab .ijt files are text files which any vers

Re: [Jchat] Tutorial documentation

2014-05-26 Thread Raul Miller
Does that mean you are volunteering to do the update? ;) Thanks, -- Raul On Mon, May 26, 2014 at 8:56 PM, robert therriault wrote: > Hey Raul, > > Developing a tool that can be used to create labs as they are imagined now > is mostly an update from the previous lab author, so most of the he

Re: [Jchat] Tutorial documentation

2014-05-26 Thread robert therriault
Hey Raul, Developing a tool that can be used to create labs as they are imagined now is mostly an update from the previous lab author, so most of the heavy lifting has been done. The next level is to come up with what labs might become; incorporating a number of communications methods that html

Re: [Jchat] Tutorial documentation

2014-05-26 Thread Raul Miller
Keep in mind that my "don't like video" is limited - I *would* like it under a variety of circumstances and I would not hesitate to recommend it for some purposes. I'm not trying to say it's bad or anything. But I guess I do avoid it in some contexts. Meanwhile, it can't be that hard to document

Re: [Jchat] Tutorial documentation

2014-05-26 Thread robert therriault
Hey Raul, 1) One of the advantages of scripted video is that there is a written artefact that could be included for search purposes. Similar to the way that SVG includes its text as searchable content as opposed to bitmaps of words on canvas. 2) This is a little trickier because it implicitly

Re: [Jchat] Tutorial documentation

2014-05-26 Thread Raul Miller
I guess I have two thoughts looking at that: (1) I personally prefer reading over video. Video is really hard to find using search, and it's slow to watch. (2) Why don't I know how to generate a UI like that, using J? Of course anything worth doing takes time, and I have to allow for that. But v

Re: [Jchat] Tutorial documentation

2014-05-26 Thread robert therriault
Thanks Raul, Another (albeit market driven) approach is the short video tutorial to describe use of a specific tooll. These short tutorials for the use of pixelmator software are good because they have actually provided very precise instruction on use of a tool in about a minute. The amount of

[Jchat] Tutorial documentation

2014-05-26 Thread Raul Miller
Writing decent tutorial documentation can be hard. So here's an example of how one guy who has written a fair amount of documentation has approached things: http://www.xess.com/static/media/appnotes/FpgasNowWhatBook.pdf Personally, I'm not all that fond of pdf - I personally prefer working more