Collaborative Effort - Ruby Template, RDoc, and Localization

RickW

I applaud your efforts towards bringing some order to the Ruby script writing chaos. I also see you have taken it upon yourself to direct a task which I think should be directed by SU Google staff.

But it appears they are again missing in action. Unless perhaps via private email you have their blessing in this endeavor.

Actually, Scott Lininger did provide input on the template file. I do know from private correspondence that they are very busy on some things and may not be responding as much as they would like, and hope Scott will have some time for input on this as well.

But yes, it is a rather self-appointed task

I've thought about the xml vs. plain text issue. I suppose a standalone menu-generating script could be required and then called to create the menus by parsing the xml (which would need a <code> section added to Todd's example, I think). The drawback to me is that it becomes one more thing to write, distribute, support, and incorporate in the script, in addition to the extra menu file/s (which bothers me as well, but what do you do?). The benefit is that it clearly delimits each field's function.

Jim

FYI, I merged the thread about menu localization into this thread.

thomthom

I was thinking, if the plugins where made using the RDoc format, with HTML formatting. Then it should be possible to generate a documentation resource for then if they're collected into a joint repository. From what I understand, the Ruby docs http://www.ruby-doc.org/, are generated directly from the source.

With a joint repository, using this header, we can get a plugin manager working, as well as a central help system. I think that at the moment that I'm in favour of HTML formatting.

August

Hi Todd,

@unknownuser said:

Get your requests in now, during the early design stages.

I've done lots and lots of API doc, sometimes writing SED scripts to extract info from header files etc., but I'm not really at the SOTA when it comes to RDoc, JavaDoc, Doxygen, etc.

I'd like to help in this project, if I can, but it looks from the discussion like I'm way down on the curve compared to other folks.

Could you put together an outline of what it might take to catch up?

One thing I'm going to throw out here that might make a difference if it's still early stages.

I've been seeing over and over in other doc projects that the idea of going from the code comments to a Wiki seems to be catching on. From a Wiki, you have immediate collaboration on updating the doc and there are lots of ways of going from Wiki to PDF and/or print.

And if it's just about any Wiki besides SharePoint, you have some kind of standard markup format for the Wiki text that can be a very simple rework of the code comments format. Then the Wiki manages the cross-references and the formatting and display and you don't have to reinvent all of that in your HTML output from the code comments.

The piece I've been looking for and have not been seeing anywhere is going backwards from the collaborative Wiki edits to merge those changes back into the source so that the "master" does live in the code and can be updated when the code is changed.

Any interest in pursuing that idea? Building systems that do the code>Wiki>PDF and Wiki>Code round trip is something I've been brainstorming about doing professionally, so getting into that with this project might just add to my portfolio.

Let me know what you think,
August

RickW

Andrew,

It's an interesting idea, but I for one would be reluctant to let third parties edit my scripts (via a Wiki), which is essentially what you're proposing. A moderately clever person could introduce new code through the Wiki unless there was a parser that would filter out any ruby code, and then you would likely impede legitimate use of code snippets in commented sections.

It's not an impossible situation, but it would need some very serious attention to security.

As for SketchUp-oriented scripts, I'm not sure the collaborative comment editing is as important, but I'm certainly open to hearing from others about it.

todd burch

Just as a community-wide FYI - ref. me on this project. I got interrupted with another project which I hope to finish this week, then I'll be back on this.

It's never too late.

Todd

Jim

What about creating an abstract base class named Plugin which provides inspectors for the information? Not only could inspectors be created for name, author, copyright, license, etc; but also inspectors for menus, Commands and toolbar images?

This way, external applications (menu organizers, etc) can simply ask the plugin about itself.

Chris Fullmer

Ooh, I like the sounds of that.

RickW

Ditto!

thomthom

@jim said:

What about creating an abstract base class named Plugin which provides inspectors for the information? Not only could inspectors be created for name, author, copyright, license, etc; but also inspectors for menus, Commands and toolbar images?

This way, external applications (menu organizers, etc) can simply ask the plugin about itself.

Did anything happen to this?

Dan Rathbun

@jim said:

What about creating an abstract base class named Plugin which provides inspectors for the information? Not only could inspectors be created for name, author, copyright, license, etc; but also inspectors for menus, Commands and toolbar images?

This way, external applications (menu organizers, etc) can simply ask the plugin about itself.

I've actually done some playing around & testing this past week along these lines, before I saw this post.

I had seen, in many standard (extra Sketchup) ruby scripts, that coders were just declaring a string constant "VERSION" at the top of their outer code blocks. This could be easily accessed ie:, Module::VERSION.

But then the spark for me was seeing somewhere (perhaps within the RubyGems files,) someone took it a baby step forward by making the constant VERSION a Hash with 4 elements, the first 3 Integer components of the version number, and the 4th a string concatonation of the first 3. ie:

 VERSION=[MAJOR => 0, MINOR => 0, TEENY => 0, STRING => (MAJOR,MINOR,TEENY).join(".") ]

This was a bit better, as you could get any one of the version components for comparison, without having to convert to numeric, by calling as an example:

 if Module;;VERSION[MAJOR] < 7 {..do a block..}

Or if you wanted the whole version string, you'd call, like so:

messagebox( "The plugin version is; #{Module;;VERSION[STRING]}" )

But the spark had not yet ignited into flame until I stumbled across the standard ruby class OpenStruct. When I read the filenotes in 'ostruct.rb', I immediately thought this is perfect for versioning !!

OpenStruct is similar to the built-in class Struct, but really makes it act like a true data object should act in an object oriented language like Ruby. Struct on the other hand is so much like a hash, there doesn't seem to be much benefit in it; as you still set and access values as you would in a hash object.

OpenStruct is SO MUCH better! You simply state a new object name = followed by OpenStruct.new(keylist), where the keylist is just that; a list of data keys to create. The class creates all the keys as attributes, and automatically sets up getter and setter accessors for each one!

(Pssst! [whispering off topic this would also be great for ruby-side JSON as OpenStructs will look and act just like Javascript Objects..)]

So my thoughts are to set up a custom subclass of OpenStruct called VersionStruct, or just a custom class called VersionStruct that uses an OpenStruct. Still playing and testing which way is better. Any way the goal is to have something that is all setup correctly that can be either 'included' or mixed-in into a top code block, so the module or class inherits the data structure; OR instanstiated into a code block if it's set up as a class. (I cannot see making coders cut and paste a codeblock into everyscript, errors may creep in.) Anyway.. after instantiating a VersionStruct, a coder would set the fields, then freeze the VERSION object (so the data cannot be changed after the script is loaded.)

Example: ['RubyTools' is a fictional Namespace.]


module DandyCode

  VERSION = RubyTools;;VersionStruct.new(2,1,4)
  # first 3 parameters are integers; major, minor, teeny
    # note VERSION.string is created automatically
  VERSION.author="Ruby A. Coder"
  VERSION.copyright="(c) 2010 by author"
  VERSION.disclaimer="No Waranty...no particular purpose...author to be held harmless ...etc"  # can be preset
  VERSION.termsOfUse="Free for Public Use...etc." # can be preset
  VERSION.title="Title of this plugin code"
  VERSION.description="A short explanation of it's features."
  VERSION.minSUverMajor=7
  VERSION.minSUverMinor=1
  VERSION.dependancies=self.DependancyList
  VERSION.exclusions=self.ExclusionList
  VERSION.freeze

  DependancyList = Array.new
  DependancyList[0] = DependancyItemStruct.new(module='JRF;;Inputbox', minverMajor=2)

  ExclusionList = Array.new
  ExclusionList[0] = ExclusionItemStruct.new(module='SluggishKeyTrapper', allVers=true)

  VERSION.freeze

 .. more code ...
end # module

Anyway.. ideas to chew on...

Currently.. I'm only playing with a VERSION structure that has Major, Minor, Teeny and String attributes.

The other attributes in the above example, or discussed in the prior posts, could be in a separate struct as Jim suggested called 'Plugin' or whatever. (We've seen a similar thing done with the Sketchup Extension Class, except that it's put in a separate file.)

For those interested, who don't have a full ruby install, I attach the ostruct.rb file that ships with Ruby 1.9.1 (put it in a folder that's in the search path, perhaps the Tools folder. I personally have it in a folder named 'Library' which I put in my search path.)

ostruct.rb