![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 11 to 14 of 14 total |
![]() |
Mon, Jul 15 2013 1:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Sergei,
<< yes, I understand. Anyway, I got a solution using TServerRequest, a loop through TListBox selected items sending each one as a parameter. The back-end did the rest. >> Good solution, given the situation. ![]() I wasn't aware of this "special-naming" requirement of PHP, and don't like it one bit. I'll keep looking to see if there's a better way, but the back-end forcing naming conventions on the front-end HTML elements is not a good design. Thanks, Tim Young Elevate Software www.elevatesoft.com |
Fri, Jul 19 2013 3:28 PM | Permanent Link |
Sergei Safar | Hi Tim,
this is just for information: I opened the js code generated by EWB and I changed the name of my TListBox from $t.tform1_listbox1.tcomponent_setname("ListBox1"); to $t.tform1_listbox1.tcomponent_setname("ListBox1[]"); and PHP could parse all the TListBox selected items! Well, as you said and I agree, "the back-end forcing naming conventions on the front-end HTML elements is not a good design".I don´t know the EWB community opinion but I guess that PHP is a very common back-end and who knows, in the near future, EWB could solve this. Thank you! Best regards Sergei Safar |
Sun, Jul 21 2013 1:57 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Sergei,
<< I opened the js code generated by EWB and I changed the name of my TListBox from $t.tform1_listbox1.tcomponent_setname("ListBox1"); to $t.tform1_listbox1.tcomponent_setname("ListBox1[]"); and PHP could parse all the TListBox selected items! Well, as you said and I agree, "the back-end forcing naming conventions on the front-end HTML elements is not a good design".I don´t know the EWB community opinion but I guess that PHP is a very common back-end and who knows, in the near future, EWB could solve this. >> I'll look into it, but I don't think I can solve it by allowing brackets in the component names - that's not a valid Object Pascal identifier and will probably cause issues at design-time. Tim Young Elevate Software www.elevatesoft.com |
Mon, Jul 22 2013 12:27 PM | Permanent Link |
Sergei Safar | Tim,
<<... but I don't think I can solve it by allowing brackets in the component names - that's not a valid Object Pascal identifier and will probably cause issues at design-time.>> Ok, I fully agree. I don´t know if this is possible but, IMHO, it could be a TListBox property, let say, "PHP compatibility" (true/false), published or not. Best regards, Sergei Safar |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Monday, October 2, 2023 at 03:09 PM | Privacy Policy![]() © 2023 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |