Sweet Home 3d Github

0 views

Skip to first unread message

Vanya Lamunyon

unread,

Aug 3, 2024, 5:40:46 PM8/3/24

to tromrajetsra

As far as I can see, the only required changes should be to update existing Javascript libs with the ones found in Sweet Home 3D JS viewer, add batik-svgpathparser.min.js and jsXmlSaxParser.min.js libs, and cite them after geom.min.js in your sweethome3d.directive.js file. zip-url attribute may now contain a file exported with the Export to HTML5 plug-in or simply saved with Sweet Home 3D 5.3 or a more recent version.
There are also some additional parameters detailed in the script of the viewer to manage cameras and levels, but they are optional.

Note, the example template from -3dview/blob/master/3d-view.tpl.html was changed to work with the default.sh3d example bundled with Sweet Home 3D JS Viewer. You can click on the TV, the microwave, the dishwasher, the lights etc.
Additionally, the mouse cursor and name display will now change only when hovering interactive objects.

As I modelled our new family home completely in SweetHome3d prior to its construction, I had to try your compilation and it was working great!
However, I was running into two issues and hope you or someone around here can help.

Second issue:
For some items I would like to use more complex modal dialogs in terms of custom widgets I previously imported into HABPanel, e.g. the rollershutter / blinds widget (Rollershutter / blinds widget) or the hue color light controller (Custom Widget: Hue Color Light Controller) or the multi-state widget (Custom Widget: Multi-state Widget). Is there any way easilly integrate / reuse such custom widgets in the template withought having to copy their whole html template but rather have simple few-liners like for native / builtin widgets (e.g. slider):

You should call setAerialViewCenteredOnSelectionEnabled in UserPreferences class and select in your Home object an item that will be used as the pivot point. See this thread in Sweet Home 3D forum for more information.

Hi,
I am Vronique, Sweet Home 3Dcommunity manager, and I regularly publish in its blog some tips and articles about different ways to use it.
Thanks again for this test. We are still very interested by this kind of development and wonder if Yannick or someone else would agree to answer to some questions about OpenHAB and this program, for an article in the blog. I am sure it will interest some people of Sweet Home 3D community and will bring more users to OpenHAB.
For your information, Sweet Home 3D 6.0 is under development with many new interesting features that will be available in Sweet Home 3D JS Viewer too.
Looking forward to reading you.
Vronique

There is a need to add image or link to my pagedown textarea. I know we are able to hook image or link event but i want to do that without hooking. For example; i have an image url like files/home/sweet/home.jpg and i don't know how to add this with markdown style to content of the textarea directly.

I have used Jekyll for many years in many projects and one of the reasons whyit is so popular is that it is supported by GitHubPages out of the box, without doing any extrasteps. This makes it comparably simple to deploy blogs, homepages, and projectwebsites without running own web servers.

But recently I started exploring alternatives to Jekyll because it felt likenot a perfect fit for what I wanted to do. I often felt I am pressing somethingelse than a blog into a framework designed for blogs. I was looking fora framework where I can more easily customize things, where I achieve a betterseparation between content and form, and where I know the underlying languagebetter.

In the recent weeks have tested many of the above tools and really liked Hugobut my favorite static site generator at the moment isZola, and I have migrated already few projects toZola. Zola really stood out, offers super fast build and rebuild, easyinstallation, a link checker, clever image processing, shortcodes (reusablemacros), and much more. Overall the folder layout and the scaffold structuremaps better to how I think about a website.

The approach described there requires creating a personal access token andstoring it as a secret. This is not difficult and it only takes 2 minutes toset up but I was never fully happy with this solution because of thebus/lottery factor (how many persons have to be run over by a bus or win thelottery for a project to become unmaintained). I wanted to create open sourcewebsites which anybody can contribute to and which do not depend on me creatingand maintaining access tokens now or in future.

All you need to do is to add (and adapt, more about this later) the file.github/workflows/build.yml to your GitHub repository with the following content(I am grateful to Richard Darst for many improvements of the original workflowtowards its current form):

You will need to adapt SOURCE_BRANCH (this is where the Zola sources are; inthis example: main) and TARGET_BRANCH (this isthe branch which contains the generated HTML and is used by GitHub Pages; inthis example: gh-pages).

Zola is a really nice tool with great documentation - try it out!Indeed, this website is built using Zola andhereis the workflow that I am using to build this site.With the above recipe setting up a Zola build is no more difficult than settingup a Jekyll build.