Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
CSIDE and OScript
Integrating with 3rd party application
Sjaak_van_den_Akker_(originuser2_-_(deleted))
Hi all,In my point of view towards a development environment I think the Builder could use a lot more functionality in order to support the developer with his / her daily work. In order to become more productive i.s.o. finding a way to get the requested changes realized I think several things should be changed in the Builder:- More online help during development. In most development environments as soon as you type a command and you don?t know what the correct use or syntax is you are able to press any help button which gives you the functionality of that particular function / command.- More edit facilities. The current Builder editor is even worse then Notepad, especially when looking at the search possibilities.- Ospace integrity checking and showing the cross-references would make live also easier for some developers.- Integration with a version control system should be one of the standard functionalities of a development environment.- The compiler doesn?t check all it should (like the usage of variables) and gives (in my opinion) only suggestions where you possibly might find an error.I could make this list a lot longer since I?ve worked for a long time as developer and have seen a lot of different development environments. I would therefor ask OpenText to respond to these kind of suggestions and start talking to several developers who are working with the product in order to see what is the best way forward of the development environment.I therefor also would suggest that the development environment would be integrated to any 3rd party tool that contains a lot more of all of this (like any Visual environment) which would generate the Ospace needed for LiveLink. It would even be possible to generate the Ospace, which then can be modified (if needed) by the builder as it is right now. This would give general developers the possibility to make changes easily and more experienced developers to do the ?real? work.I think OpenText is doing a great job at the user site of LiveLink but they should also consider that customizations of the product are the main items large customers want.Regards,Richard.
Find more posts tagged with
Comments
Simone_Oettinger_(SOettinger_(Delete)_177592)
Hi Richard,Thanks for your input. You have good points, and we have been aware of these issues for a while. We are working on ways to improve the Livelink developer experience. Feel free to post more suggestions and feedback here and/or email me directly.ThanksSimoneLivelink SDK Product Managersimone@opentext.com