September 30, 2017 at 10:05 am #11688
Web developer tools often offer an easy way to find new components in a similar way (RapidWeaver).
Do you know any js components that might be worth looking at from an omnis point of view?October 2, 2017 at 3:38 pm #11711
Hi Christoph, you may be interested to look on the Blog (on this site) today, we have announced a new JSON component, which we have placed on a new Github repo. We have been working on this for a while and are excited to launch this today. Let us know what you think!
–Omnis EngineeringOctober 2, 2017 at 3:54 pm #11712
c’mon you’re kidding me – that’s exactly what I’ve been working on last week and I’m proud I’m done. I wanted to show this in a flash session on Euromnis…
I showed this project to Götz in Hamburg last week and I guess he sent it to you (the signature part on GitHub) ?
So I’ll compare it to my project and maybe we can merge them…
I’ll check it out and give you some feedback.October 2, 2017 at 4:19 pm #11713
Hi Christoph, first of all I’m sorry we did the same component as you, but this was just a coincidence. We have been working on this since August, but we needed to wait for the Studio 8.1.1 release before releasing the component on Github.
I hope you can proceed with your demo at Euromnis since I’m sure the developers would love to hear what you have got to say about the new JSON Components.October 2, 2017 at 4:36 pm #11714
At a first glance our projects are very similar. I created the $todataurl method that allows to access the binary data. You used the data name property which is a more natural approach I think, I really like it.
I also like the possibility to change the colors of background and border and the reflection of these values in design mode. Looks very good!
For me it is easy now to use such components because I fiddled around with all this a lot.
From a standard Omnis developers point of view it should be easier to copy components to Omnis.
It should be as easy as copying a directory or maybe a zip file into an Omnis json controls folder. The html template file should be changed automatically so it would be very easy to plug and play with json js components.
Now you have to copy too many files into different places and you also have to change the template file manually. Not a problem if you have only a few components but I dream of tens or hundreds of components.
I also dream of a global access point for Omnis json js components where I can browse and download them directly. Plug and play with it in a second – really cool! Think of itOctober 2, 2017 at 4:38 pm #11715
and YES… what a coincidence… EXACTLY THE SAME COMPONENT! Unbelievable…October 2, 2017 at 4:41 pm #11716
If you have plans to create such a “json component manager” and implement it in Omnis please let me know. If NOT… I will create a library that does all this.October 4, 2017 at 2:53 pm #11739
We have no plans for a “Component Manager” beyond what is implemented in Studio 8.1, so feel free to explore the possibilities.December 14, 2017 at 2:45 pm #12788
You must be logged in to reply to this topic.