How to add Chicken exporter in Blender's export menu - export

(Sorry for my inglish)
Hi! I followed the instructions that founded in the chicken's zip but I can't did it.
I extracted the files in C:\Program Files\Blender Foundation\Blender\2.63\scripts and in C:\Users\Martin\AppData\Roaming\Blender Foundation\Blender\2.63\scripts but blender don't show the option. Also I didn't found chicken in File\User Preferences\Addons, so I installed using the install addon button. But nothing happend.
What I'm doing wrong?
I'm using Blender 2.63 and chicken R91. I want to export a model to a Panda3d compatible format.
Thanks!

Chicken exporter ( chicken_exportR91.zip (179.8 kB) ) was last updated in 2010, which won't work in 2.63 without big changes.
Your best option looks like Panda3d Egg I/O. get the installation zip from: https://code.google.com/p/yabee/ something like https://yabee.googlecode.com/files/YABEE_r12_b263.zip
it seems to be in a folder structure called io_scene_egg, drop this folder and all it contains into 2.63/scripts/addons_contrib
In preferences -> addons-> enable the 'testing' selector (because the addon is still in development for 2.6+ ). The addon should appear in Import-Export as Import-Export Panda3d EGG Format.

Related

Neo4j export whole database to JSON_LINES, ARRAY_JSON, JSON or JSON_ID_AS_KEYS

I tried to use an APOC procedure from here to export the DB using the following:
CALL apoc.export.json.all("all.json",{useTypes:true})
I can successfuly export to JSONL. However, I am not able to change the JSON format to other available formats such as JSON_LINES, ARRAY_JSON, JSON or JSON_ID_AS_KEYS. According to the documentation the following should work but it does not:
CALL apoc.export.json.all("all.json",{config:{jsonFormat:'ARRAY_JSON'}})
The result of above procedure is in JSONL but not ARRAY_JSON.
I have also tried the solution here but did not succeed.
Cheers,
A
This is working now in neo4j versions 4.2.x with APOC version 4.2.0.2: https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/download/4.2.0.2/apoc-4.2.0.2-all.jar
The syntax is simpler. Notice the config is a dictionary rather than a nested dictionary. See my sample below.
OLD: CALL apoc.export.json.all("all.json",{config:{jsonFormat:'ARRAY_JSON'}})
NEW: CALL apoc.export.json.all("all.json", {jsonFormat: 'ARRAY_JSON'})
Result:
(type is array of dictionaries)
The solution for my question was changing the APOC.jar file with the latest release from here. I have had to update the syntax as well.
CALL apoc.export.json.all("all.json", {jsonFormat: 'ARRAY_JSON'})
You can open the plugin folder using the tree dots by the blue open button and chose Open Folder -> Plugins. Copy and paste the path showed into your file manager if it doesn't open.
In the plugin folder, you can see your APOC version on the apoc file name.

blogdown not showing plots from .Rmarkdown files but from .Rmd

I'm using blogdown to create my website. Now I found this problem:
ggplots embedded in .Rmarkdown files doesn't appear. When I rename the file to .Rmd the graphic is okay. But I need to use .Rmarkdown because I want to use the beauty syntax highlighting and other features only available in .Rmarkdown files.
When I print the fig.path with
knitr::opts_chunk$get('fig.path')
I see the difference:
In .Rmd
"2020-06-17-rmd_files/figure-html/"
In .Rmarkdown
"/post/2020-06-17-rmarkdown_files/figure-html/"
But I don't see why the paths are changed.
How do I solve this?
I found a solution (at https://discourse.gohugo.io/t/raw-html-getting-omitted-in-0-60-0/22032):
After adding
[markup.goldmark.renderer]
unsafe= true
in the config.toml the plots appear.

Why does a search engine summary contain text that is not in any of the static html files?

I have a hugo site, and on a search engine (Duckduckgo), my site's summary is:
Add your own "layouts/partials/hero.html" to replace this text.
I tried looking for the string hero in the files in my public folder, can't seem to find it.
I have added this file with some content. Nothing seems to happen. Do I need to edit the theme files or something?
Edit: changed title to make problem clearer. The original question asked about "hero cards", which I thought might have been a standard search engine friendly part of a website.
I think I understand what is happening now. I originally installed the base16 theme which does contain the text:
Add your own "layouts/partials/hero.html" to replace this text.
( it is in the file themes\base16\layouts\partials\hero.html.).
I should have realised, but search engines take time to re-index a site. I originally published the site using base16 with some text unedited. Duckduckgo was showing that old text, it will probably disappear in time when the site is reindexed.
The answer is in the documentation for the base16 theme:
You probably want to edit the homepage. Get started by copying the
supplied homepage to your own site.
$ mkdir -p layouts/partials
$ cp themes/base16/layouts/partials/hero.html layouts/partials/hero.html
After this, you can edit layouts/partials/hero.html and make it
awesome.
The default layouts/partials/hero.html contains the code Add your own "<code>layouts/partials/hero.html</code>" to replace this text., which is what DuckDuckGo was using to make its summary. As you noted in your answer above, if you edit this file then the DuckDuckGo summary should change when DuckDuckGo next indexes your site.

Updating Adobe Flash Pro CS6 to the latest Flash Player 23?

I read this post where someone asked
How can I change flash player version in flash cs6? and there was an answer instructing him how to add Flash Player 15, so I figured I could do something similar with Flash Player 23, but it doesn't seem to be working properly. Does Adobe not provide a FlashPlayer23_0.xml file themselves? There are lots of lines in there, and copying one of the older xml files and editing a couple of them as the guide suggests doesn't seem right. In one of the lines I'm supposed to edit, I'm not sure what to put in for the version of FlashPlayer23.0.
<player id="FlashPlayer23.0" version="XX" asversion="3">
After doing all that, in Flash Pro I now see a "Flash Player 23" in the Target dropdown of the Publish section, and I have that selected, but when I actually publish, I get an error when I try to use one of the newer Flash features.
I'm actually just trying to use the new removeAt() Array method where you can remove one element of an array by its index. It says you need at least Flash Player 19 for it to work. Here is my test code:
var a:Array = [0,1,2];
a.removeAt(1);
trace(a);
If I try that out with Flash Player 11 as the publish setting, I get the following expected error:
TypeError: Error #1006: removeAt is not a function.
If I set it to publish to Flash Player 23, I get this error:
ReferenceError: Error #1069: Property http://adobe.com/AS3/2006/builtin::removeAt not found on Array and there is no default value.
Does anyone know why this is?
(1)
In one of the lines I'm supposed to edit, I'm not sure what to put in
for the version of FlashPlayer 23.0.
Always look for something called "release notes" for your version and it will tell you the number. The FlashPlayer 23.0 release notes (see Authoring Guidelines section) say :
To use the new Flash Player, you will need to target SWF version 34 by
passing "-swf-version=34"...
Set that as : <player id="FlashPlayer23.0" version="34" asversion="3">
(2)
I get an error when I try to use one of the newer Flash features
Did you actually replace the existing older playerglobal.swc file with the newest downloaded one (for FP 23.0 features)? The compiler needs the latest Flash Player file placed in the installation folders.
Remember installing the plugin from Adobe website is just for benefit of browsers, you still need to manually setup the installed Flash CC or CS software with the latest SWC file so that the compiler understands these new commands/features.

Difficulty with filename and filemime when using Migrate module

I am using the Drupal 7 Migrate module to create a series of nodes from JPG and EPS files. I can get them to import just fine. But I notice that when I am done importing them if I look at the nodes it creates, none of the attached filefield and thumbnail files contain filename information.
Upon inspecting the file_managed table I see that both the filename and filemime fields are empty for ONLY the files that I attached via the migrate module. This also creates an issue with downloading the files.
Now I think the problem has to do with the fact that I am using "file_link" instead of "file_copy" as the file operation I specify. The problem is I am importing around 2TB (thats Terabytes) of image files. We had to put in a special request with Rackspace just to get access to that much disk space on our server. So I can't go around copying from one directory to the next because of space issues. So "file_link" seems like the obvious choice.
Now you probably want to see how I am doing this exactly, so here is the code snippet:
$jpg_arguments = MigrateFileFieldHandler::arguments(NULL,
'file_link', FILE_EXISTS_RENAME, 'en', array('source_field' => 'jpg_name'),
array('source_field' => 'jpg_filename'), array('source_field' => 'jpg_filename'));
$this->addFieldMapping('field_image', 'jpg_uri')
->arguments($jpg_arguments);
As you can see I am specifying no base path (just like the beer.inc example file does). I have set file_link, the language, and the source fields for the description, title, and alt.
It is able to generate thumbnails from the JPGs. But still missing those columns of data in the db table. I traced through the functions the best I could but I don't see what is causing this. I tried running the uri in the table through the functions that generate the filename and the filemime and they output just fine. It is like something is removing just those segments of data.
Does anyone have any idea what this could be? I am using the Drupal 7 Migrate module version 2.2. It is running on Drupal 7.8.
Thanks,
Patrick
Ok, so I have found the answer to yet another question of mine. This is actually an issue with the migrate module itself. The issue is documented here. I will be repealing this bounty (as soon as I figure out how).

Resources