right, it was only intended as an example to get the OP started - also, because I'd expect him to favor SVG files over our static textures - on the other hand, we do have a sizable library of reusable components in $FG_AIRCRAFT/Instruments obviously, and
there's also the long-term plan to re-implement our 2D panel manager code in Nasal space through a custom Canvas wrapper - so we could just as well provide a little more than just that stub, I didn't bother looking into supporting the various transformations/actions - but given the flexibility and power of the canvas system, it should actually be fairly straightforward - I cannot currently think of anything "missing" here -
the status looks pretty encouraging actually, I think I also remember seeing quite a bit of useful code in Tom's fgdata repo.
Coming up with a Nasal/Canvas wrapper that supports loading our 2D panels should be fairly straightforward, but would involve a fair bit of sophisticated Nasal hacking, i.e. "meta-programming" and familiarity with the canvas system and the 2D panel code obviously:
@OP:
Subject: FGPanel from CANVAS ideadiande wrote:Hooray, you are awesome
You help me a lot. Thanks for that!
I started this morning working with FG. Can you guide me how can I replace the IFR panlel with a single Canvas sprite?
Most people here will tell you that I am usually pretty supportive and responsive, as you may have noticed. However, you previously mentioned in
another thread that you were not too interested in sharing your work but would prefer to keep it private, which is frankly something that concerns me:
In other words, I'd rather spend my time supporting people who directly contribute things back in some shape or form, like for example kuijfe09, macnab or Philosopher (thanks guys!).
After all, that's the whole point of the exercise, and as long as we don't share our work, the project and community cannot benefit unfortunately ...
Thus, if you'd like to see more support in this form from my side, I'd appreciate it if we could work out some plan to either share your full work, or alternatively, come up with a generic Nasal/Canvas framework for rendering instruments that you can share with us. As you may have noticed, your effort does overlap with various planned projects - so it would make sense to coordinate things a little here.
Especially, because the shared knowledge and expertise available here, can probably save you tons of time - while we, as a community, would appreciate having someone working on stuff that is "good to have", but currently not being worked on by anybody else.
So, I'm offering personal 1:1 mentoring to help you with things (answer questions, provide code snippets etc), as long as we can work out a way to come up with a generic and reusable component here, that will be useful to the whole community, not just a single user.
As you may have noticed, we do have a few very knowledgeable people interested in related things, but most of us are already juggling tons of "side projects", which is why we usually have to switch in "mentoring mode" once we see something interesting.