Re: [WebDNA] maybe silly suggestion? [founditems]
2015
It keeps the original formatting.
interpreted = N
texte = This is a multi-part message in MIME format. --------------030507080205090603080401 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hello, you can find Govinda Framework here : http://www.webdnacodesparker.com/ I'm still looking for some time to create the BackOffice that would make it a great CMS to create website very quickly... Lawrence > Donovan Brooke
you can find Govinda Framework here : http://www.webdnacodesparker.com/
I'm still looking for some time to create the BackOffice that would make it a great CMS to create website very quickly...
Lawrence
--------------040108060703070705080100 Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg" Content-Transfer-Encoding: base64 Content-ID:Hi Brian,
I think the idea of catering WebDNA to be more MVC compliant is a good idea. Yes, you can do this in several ways currently.. but,
is there better possible ways? probably.
As you know, WebDNA is not an object oriented language, so our methods would look a bit different than other languages.
Govinda did an MVC framework that can be found in the archives. His may / may not be the end-all / be all.. but I think more
discussion would be needed to figure out where WSC might want to go with supporting MVC better. To keep in-line with the ideals of
WebDNA, the solutions would have to be understandable, yet powerful enough to justify.
Currently, in your example, it might be pretty straight forward to make use of the WebDNA [function] tag to get your desired behavior.
I’m not sure core WebDNA engine tags would make things any easier / better.
more discussion I think.
Sincerely,
Donovan
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.usto help separate my controller logic from my display code it would be awesome to have a shortcut like:
[search db=allthethings.db&blahblahblah][savefounditems name=peoplenameddave][/search]
then later in the page, where i’m rendering the html
[displayfounditems use=peoplenameddave] html things [/displayfounditems]
I know it looks like it’s not saving that much code, but I can see switching which search I want in the controller, and still being able to use a universal founditems loop lower in the code. Also the ability to reuse search results (if needed) without doing the same search again.
ok, feel free to start telling me how you can do this with a table (you’re missing the point) or how we don’t need more tags or whatever :)
-Brian B. Burton
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
you can find Govinda Framework here : http://www.webdnacodesparker.com/
I'm still looking for some time to create the BackOffice that would make it a great CMS to create website very quickly...
Lawrence
--------------040108060703070705080100 Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg" Content-Transfer-Encoding: base64 Content-ID:Hi Brian,
I think the idea of catering WebDNA to be more MVC compliant is a good idea. Yes, you can do this in several ways currently.. but,
is there better possible ways? probably.
As you know, WebDNA is not an object oriented language, so our methods would look a bit different than other languages.
Govinda did an MVC framework that can be found in the archives. His may / may not be the end-all / be all.. but I think more
discussion would be needed to figure out where WSC might want to go with supporting MVC better. To keep in-line with the ideals of
WebDNA, the solutions would have to be understandable, yet powerful enough to justify.
Currently, in your example, it might be pretty straight forward to make use of the WebDNA [function] tag to get your desired behavior.
I’m not sure core WebDNA engine tags would make things any easier / better.
more discussion I think.
Sincerely,
Donovan
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.usto help separate my controller logic from my display code it would be awesome to have a shortcut like:
[search db=allthethings.db&blahblahblah][savefounditems name=peoplenameddave][/search]
then later in the page, where i’m rendering the html
[displayfounditems use=peoplenameddave] html things [/displayfounditems]
I know it looks like it’s not saving that much code, but I can see switching which search I want in the controller, and still being able to use a universal founditems loop lower in the code. Also the ability to reuse search results (if needed) without doing the same search again.
ok, feel free to start telling me how you can do this with a table (you’re missing the point) or how we don’t need more tags or whatever :)
-Brian B. Burton
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk ListThe WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...