patches, ...). The API is Nebula, but the code is completely
different because we don't draw but use (end extend) RAP's
In this case it is important to keep te API compatible in the future.
version is finished, it would be great if the Nebula site could add a
screenshot of the Grid running on RAP and link to the RAP version.
It is the widget's author responsibility but I am +1 with this idea.
I guess the issue with most Nebula widgets is that they draw a lot,
which partly works in the browser as well, but is often not the ideal
solution. In those cases, it could make sense to create a
RAP-optimized version of a widget in a branch or host it in the RAP
Incubator. This is something which we're happy to help with.
The problem is the double maintenance. In intensive widgets like Grid where there is an alternative available it makes sense to make a new implementation. In other widgets like CDateTime which are not used "all of the time". I would not mind paying the price of slower performance.
Other widgets like Gantt which also draw intensively there is no alternative available so making it RAP native would be nearly impossible?
What we can also do to help pointing RAP users to Nebula is
- show some Nebula widgets in our online demo (bug 382552)
- create an addons section on our project page and point to
rap-enabled Nebula widgets
Yes +1
BTW, the RAP Oscilloscope is a completely new implementation, and it's
not (yet) open source.
Ah, I assume you moved the drawing to _javascript_? It would be a good example how to convert a widget from native drawing to _javascript_ drawing.
Best Regards,
Wim
