[Plugin] Hatchfaces (v1.8 beta) UPDATED 15-Dec-2012

TIG

Sketchup uses PC's IE [older version] and Safari for the MAC - irrespective of your default browser...
Some strange hatch-pattern names

jolran

@unknownuser said:

Sketchup uses PC's IE [older version] and Safari for the MAC - irrespective of your default browser...

Aha, good to know. That explains some things..

@unknownuser said:

Some strange hatch-pattern names

Ha ha! Yes, since I had no JS going yet I had to fill the list with something to see that the scrolling work.

jolran

Think I'm choking here Trying to figure out "best" strategy for getting data from webdialog to ruby.

In short, the idea is to populate the webdialog's scrollist with skp.components from file. And GIF preview in webdialog as well.

Sounds easy? Don't even know where to start. Info is sparse, and so are plugins with webdialogs (to see how it's done).

So question is. Do I load the files and populate webdialog (scrollist, image preview.GIF and label) from the dialog directly with JS, or do I load files in Ruby and send them to webdialog?

And using "default values" must be passed from Ruby to JS in case user switch units(cm to inches etc)?

Any tip on this would be great. Or if direction could be given for any plugin to look at.

TIG

On OK button of the webdialog its callback runs a Ruby self.method that has a set of callbacks it uses to look at every user-editable entry in the webdialog at the moment OK was pressed, and return them for processing... once the webdialog is then closed.
The selected item in any 'scroll-list' will be returned.
You will have initially populated the list from with Ruby using some js - do you have code successfully doing that?
Here an example to make a 'units' list

units_array=["inches","feet","meters","centimeters","millimeters"]
units_array.each_with_index do |unit,i|
  js="document.getElementById(\"units\")[#{i}] = new Option('#{unit}','#{unit}'"
  js+=",true,true" if @unit==unit ### I.E. SELECTED/DEFAULT UNITS
  js+=");"
  @dlg.execute_script(js)
end#do

The html code has id='units' identifying the dropdown-list in the dialog @dlg - the js sets up the list in an initial 'populate'.
After the OK triggers a callback you get the current 'units' in a Ruby method thus
@@idset is set earlier as a list of values within the class itself,
e.g. @@idset=%w(units, thisthat, theother)

def getIDvalues()
  @values={} ### hash to hold id values - ALL read in as strings - even if boolean
  @@idset.each{|id|@values[id]=@dlg.get_element_value(id)}
end#getIDvalues

Then set values to use in the Ruby...

def setIDvalues()
  @units=@values["units"]
  ### etc etc...
end

The 'list' for the dropdown can be complied as an array as I showed or made from a filtered Dir.entries() array OR model.definitions.each{|d|defs << d.name if not d.group? and not d.image?} etc

jolran

Thanks for helping me, TIG. This will get me something to go on.

@unknownuser said:

You will have initially populated the list from with Ruby using some js - do you have code successfully doing that?

I have nothing yet. I'm still reading up on JS, so need some basic before getting my hands dirty. I was thinking that I don't have to become a JS expert, but focus on what's primary required for webdialogs + some basics off course. But maybe more is required..

I will digest your advice and try some snippets.

jolran

BTW, @@class variables? I have not created any classes in Hatchfaces. So that's required then?

Anyway, will investigate further. Think I need more basic understanding about this before I dig into your snippets.

Have been looking a little at your Octaine exporter, but it's tooooo complex to be to any help for me. Quite a lot of work on that one, TIG? Big script..

TIG

OK you have a module that uses @xxx - IF you has a class [e.g. a Tool where you were picking faces after it started then @@xxx would work!].
My example was quickly cut from another tools that has a class BUT you can see the way... just substitute @idset=%w(units, thisthat, theother) - it's just a reference used throughout the tools methods and shared as it's a @xxx like you use for previous dialog entries etc... in your case it's probably only ever used inside one method anyway

TIG

I usually write a plan out in words about how the tool will be used, and backtracking to add the parts in I forgot would be needed - like 'making a list of somethings' to use later in other steps.
When you have the 'storyline' you can start adding the flesh to the bones in code...
So for example in yours, a small part will say
"The user picks a hatch-pattern from a dropdown list in the webdialog."
Now we know we need to 'make the list' beforehand in the html code.
Before that we need get a list from somewhere???
This could be a premade list hard-coded into the html, but more flexibly we can populate the list with entries as the webdialog opens using js from the Ruby side [as my example].
If we are populating the dropdown's list need to compile list of patterns...
Let's say we are to use a folder of them with your tool's subfolder.
So we then know we need the folder-path - compile that.
Then we need to filter the files in that folder so we only have .skp ones, then we take an array of their basenames [no extname] and sort it into order etc.
Then compile the js string to populate the dropdown...
...
At this point you decide you want to show a preview image of the hatching selected in the dropdown.
This sets us off down another path...
You need a folder of .png images for each pattern, with the same name as the .skp...
As the user selects [highlights] a hatch from the dropdown part of the html code kicks in a js/callback to display the matching image file in the field on the form...
Then error trap - what happens if the image is missing etc etc...

You later reorganize these lists of steps into a logical/chronological order and that's the basis of the code for that/those part...

jolran

I have been thinking in a similar way, but since I know very little about JS and what it can do it's kinda difficult to structure things. Your advice here helps a lot. Now I know more what to look for.

@unknownuser said:

This could be a premade list hard-coded into the html, but more flexibly we can populate the list with entries as the webdialog opens using js from the Ruby side [as my example].

I was thinking about that. And I think using JS for more flexibility is the way to go. A bit overoptimistic maybe since I've got a long way to go yet But that way newly created "user" components will pop up in the list as well.

Thanks again.

Oh and. Phheuh. I'm glad I did not have to make any classes in the script and redo everything.
I totaly missread you advice there.

jolran

I've updated the dialog so it doesen't take up that much space(CSS hell )

Deccided to hard code the list of components(hatches) in the HTML code.
It's easy to change or add components. Thataway won't have to worry about sending many strings back and fourth?

Component names and pics are the same exept for the extension(.gif) for pic.src.

This step is to update the picture preview:

The main idea is to get the name from selected component in the list.
Use that names.text + "img/" and ".gif" to change the image source in javascript.

Any JS expert that can help me with the following code?
(been googling JS code for 2 days now..)

The main thing is that I DON'T want to preload the pictures, like everyone else seams to like. There could be hundreds of them and it's not a slideshow ..

html

<select id="selskp" name="components" size=15 onChange="setImage(this)" >
									
									
<optgroup label="Line Hatches">
	<option>Line solid fast</option>
	<option>Line dotted</option>
	<option>Line dashed</option>
              etc........

JS;

var imgSource = document.getElementById("imag").src="";

function setImage(imageSelect) {
 theImageIndex = imageSelect.options[imageSelect.selectedIndex];
 if (var imgSource)
     var imgSource = eval("img/" + theImageIndex.text + ".gif");
  }

jolran

Yeyy! Got the picture switching going. First success in Javascript.

Well this is the code I use if someone is in the need for it. If it can be improved, please tell.

The function change picture source by the name of selection in scrollist.
You will have to call the function in the <select> tag in the HTML, by "onchange" + "functionname".

function changePic(hatchImage)
{
    // Get the select options text
    var i=document.getElementById("selskp")
	var hatchSelect = i.options[i.selectedIndex].text; 
    
   // Create our Image src name, concat
    var hatchImage = "img/" + hatchSelect + ".gif";

    // Assign the image
   document.getElementById("imag").src = hatchImage;
}


And in the html you just call onchange="changePic()" 

<select id="selskp" name="components" size=15 onChange="changePic()" >

TIG

Y'see! it's easy
[If you spend hours learning it! ]

jolran

I woulden't say easy. I'm thick as a mid-evil castle door.

Yep, hours it is. Rewarding sensation when things get going a little. Time before that is frustrating pain .

jolran

Bonjour.

I thought giving a little update, so you don't think I have given up on the plugin.

Due to webdialog testing I'll noticed that the script had to be reorginized quite alot. Especially if LineHatching and ordinary component patterns are supposed to coexist in the same script. And there will be options for crosshatching for comp.patterns as well!

color background(or none).
So in order to keep the same requested grouping as LineHatches, there where a lot of conditions to be met to even be able to test the dialog. And the webdialog part is hard to code..
At the moment I can "stear" the plugin with @variables set to TRUE or FALSE or VALUE.
The idea is to link those to the Webdialog later on.

The way I have organized the script is methods on top. And a main script just calling methods with if statements. The methods have few arguments. Mostly (group) or (face), so things are easy to keep track of and to reuse methods.

Then the question is. Is there any performance differences in having it set up this way. Compared to having Modules loaded in(with methods) like I see a lot of coders use. It's not a very long script. 400 - 500 lines of code.

Here's a pic of crosshatching with comp-pattern. Grouping the same as LineHatching. Can't get rid of the border on comp-patterns though. Tough nut to crack...
Much easier with LineHatches.

version1.8 preview.jpg

ipsketchpi

Great plug in, I did it little different till now. These plug in is cool stuff in SU. Thank you.

jolran

Thanks for feedback .

FYI. I'm working on the next version quite hard and on an every day basis. Even if there hasent been any updates lately in this topic.

ciudadanochano

Hello:

I´m new in this forum. Could be possible to be rendered with v-ray?. If it were a normal material?

Thanks.

jolran

Hi Ciudadanochano!

I can imagine having a woodframe-construction with wood textures and in some angles show of some hatchpatterns. Is it something like that you desire?

But I think one will need a face with a material in any case, for a render. Unless "wireframe" is an option in your render-engine?
I have Vray as well. And could probably look in to that a little later on..

You can fake it though if you can match Sketchups field of view and pixelratio!

Just render 1 black and white version in Sketchup(with hatches) and and 1 version i Vray.
Then blend the pics with some type of layerblending in Photoshop.
Cheap trick though ....

kaas

Hello Jolran,

Any new developments you're willing to share?

Greetings, Max

jolran

Yes, sure if you like.

Think I'm ready with the base of the dialog. I'm porting it to Sketchup as of speak.

There where a lot of Javascriptcode to get the interface responding to certain events. For ex if one checkbox is selected another element is disabled, and such.
Using Jquery to help with DOM handling and events. And a spinnbox plugin.

I'm also sending lists from Sketchup to Dialog. Materials, components and layers.
Instead of hardcoding them in the HTML.
For patterns the user will be able to create new components as long as they put them in correct folder. And maybe create a pic as well(optional).

It's moving forward everyday actually. Slowly but steady. Will still have a lot of cleaning, testing and streamlining to do. But hopfully it will be a useful plugin.

Here is a screencap from latest dialog version. The style is to keep the interface as "Sketchup" as possible. Opinions in this style would be nice.
I could go crazy with colors but I kinda like this Sketchup style.