| 
     
      
      
      From: Torsten D. <To...@t3...> - 2014-09-22 06:56:28
      
     
   | 
Thanks for the feedback, glad it's working now.
I use Inkscape to draw the svgs. The elements to animate are selected by 
their id attribute, so you have to set a reasonabl name for those.
To get proper scaling of the svg, you need to set the viewBox, width, 
height and preserveAspectRation of the <svg> element.
It should be also possible to draw svg on the fly e.g. from svg.js and 
animate this, too. I havn't looked into this so far.
The port number for the httpd is set from the commandline, use whatever 
suits your needs. No other ports are involved or hardcoded, everything 
runs over http protocol at that port, the websocket included. The 
individual services are distinguished by their url (/props/, /json/, 
/screenshot/, PropertyListener etc). Again, everything runs over port 
8080 (or whatever you told http to bind to).
Personally, I like to stick with fgdata as the repo. Master branch is a 
good enough playground. During the development cycle things don't 
necessarily have to be stable to get checked in there, if they are new 
and mostly unused parts and do not get sucked into the running fgfs 
instance.
I am planning to move the .js library files out of the aircraft 
directory into common fgdata once they seem to be in someway usable.
If you want to contribute to that area, I'm happy to handle merge 
requests or appyl diffs.
Best, Torsten
Am 22.09.2014 01:34, schrieb Pedro Morgan:
> @Torsten - cool stuff.. but as usual a few comments/questions..
>
> - how did u create the svgs? my target is the PFD and ND on the 787..
>
> - how to change port no (in my case I got around 5 ports already for 
> UDP, websocket, json as part of simpit tinkering) .
>  One  idea would be to GET "/config.json" which would reply with 
> {"http": 5678} or alike ?
>
> -  is it worth setting up a seperate "fgfs-www" repos and stick all 
> the development changes in there until stable ? ie a playground to get 
> things table before integrate with fgdata ?
>
> great stuff though.. this is what I been waiting for so thanks 
> ;-)))))))))))
>
> pete
>
>
> On Mon, Sep 22, 2014 at 12:13 AM, Pedro Morgan <pe...@fr... 
> <mailto:pe...@fr...>> wrote:
>
>     ok, pulled latest changes from earlier today,
>
>     recompiled/reinsall et all..
>
>     and it seems to be working... dont know what the problem was...
>
>     and investegating the code.. main goal for me is to see if I can
>     get working on RPI. ;-)
>
>     Pete
>
>     On Sun, Sep 21, 2014 at 11:31 PM, Alan Teeder
>     <ajt...@v-... <mailto:ajt...@v-...>> wrote:
>
>         Torsten
>         Here, with git from 10 minutes ago, the panel in a browser
>         button takes me to
>         http://localhost:8080/aircraft-dir/WebPanel/Panel1.html.
>         Sadly this is 404 not found.
>         Same with http://localhost:8080/aircraft-dir
>         http://localhost:8080/gui and http://localhost:8080 work as
>         before.
>         I like the idea as I have an aircraft specific web page,
>         showing the workings of the terrain following algorithm, in my
>         WIP. The aircraft-dir  facility will be a good way to use this.
>         Alan
>         **
>
>         ------------------------------------------------------------------------------
>         Slashdot TV.  Video for Nerds.  Stuff that Matters.
>         http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
>         _______________________________________________
>         Flightgear-devel mailing list
>         Fli...@li...
>         <mailto:Fli...@li...>
>         https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.  Video for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
 |