01-14-2016, 11:13 AM
Hi,
This is good news, it is something many people ask about. Let me try to give you my point of view.
Autocomplete functionality has nothing to with the template, it should work on all templates. That means that it is a feature of the uitype not the theme. I understand that there are only a few uitypes that need this functionality (10 and a few custom capture uitypes). So I think you should be looking at enhancing the uitypes indenpendently of the template.
Now, before going about that we have a few show stoppers.
The current way that I want to take the application is using native javascript as much as possible and jquery second. I leave advanced angularjs, react and other frameworks for external satellite apps.
So to get the autocomplete working you should find a jquery autocomplete library and add that functionality to the uitype. When you do that you will run into the need of updating the jquery version, which will take you to eliminating prototype. This is why it hasn't been done yet.
We have a whole branch with this done already (kindly created by Edlira on her spare time!!). What I need to move all the code over and start working with that version is to validate it. For that I would like to create some tests and start the unit test project and validate the extensions, specially PDFMaker.
saidmsl is already working on this branch and has reported success.
As to the theme itself, keep it independent of coding, just do images and CSS
So, in short:
- autocomplete: direct uitype enhancement, better done on the jquery branch
- theme: CSS and images as much as possible
This is good news, it is something many people ask about. Let me try to give you my point of view.
Autocomplete functionality has nothing to with the template, it should work on all templates. That means that it is a feature of the uitype not the theme. I understand that there are only a few uitypes that need this functionality (10 and a few custom capture uitypes). So I think you should be looking at enhancing the uitypes indenpendently of the template.
Now, before going about that we have a few show stoppers.
The current way that I want to take the application is using native javascript as much as possible and jquery second. I leave advanced angularjs, react and other frameworks for external satellite apps.
So to get the autocomplete working you should find a jquery autocomplete library and add that functionality to the uitype. When you do that you will run into the need of updating the jquery version, which will take you to eliminating prototype. This is why it hasn't been done yet.
We have a whole branch with this done already (kindly created by Edlira on her spare time!!). What I need to move all the code over and start working with that version is to validate it. For that I would like to create some tests and start the unit test project and validate the extensions, specially PDFMaker.
saidmsl is already working on this branch and has reported success.
As to the theme itself, keep it independent of coding, just do images and CSS
So, in short:
- autocomplete: direct uitype enhancement, better done on the jquery branch
- theme: CSS and images as much as possible
Joe
TSolucio
TSolucio