|
Check-in Number:
|
2226 | |
| Date: |
2002-Jul-04 17:42:38 (local)
2002-Jul-04 15:42:38 (UTC) |
| User: | ps |
| Branch: | |
| Comment: |
Comments to API |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/tabea/tabea-brainstorming 1.8 -> 1.9
--- tabea-brainstorming 2002/07/04 14:46:32 1.8
+++ tabea-brainstorming 2002/07/04 15:42:38 1.9
@@ -378,7 +378,11 @@
Issues:
- [rse] $type should be not on constructor, but on render() IMHO
+ - [ps] Agree. I think it is better to have the data in an internal
+ format and reformat the data at the time when the output is
+ produced.
- [rse] $prefix should be not on constructor, but on render() IMHO
+ - [ps] Perhaps I need $prefix for internal data saving.
[thl] agree on both. That came into my mind first but i thought a
switch between two types while the program is running will happen
@@ -391,6 +395,10 @@
the reverse of render() for loading in the POST results.
I recommend: $rc = $handle->parse($type, $post_data);
$rc = $handle->render($type, $html_data);
+
+ - [ps] We must get the value POST data for updating the internal data
+ The idea of having the functions parse and render sounds good.
+
This way we get - load/save for internal/backend I/O
- parse/render for input-device-specific I/O
- import/export for output-device-specific I/O
|
|
