Helma Logo
main list history

Version 26 by philmaker on 22. November 2007, 22:46

1Philip Weaver created this document on November 19, 2007. This is a private rough draft. It is intended to cover Helma 1.6. I intend to describe getting up and running with Helma very concisely and quickly and I will intend to present many simple statements of FACTfact. I intend to initially focus on using the internal XML database, explain how HopObjects work in relation to page requests and in relation to data persistence in the internal database, explain the workings of the properties files, explain conventions, etc. And more. If there are areas where the documentation is already obvious or sufficient or it is a non-core feature, I may link: such as skins, macros, etc.

Version 25 by philmaker on 22. November 2007, 06:56

20"Every directory that you create inside your application's code repository becomes automatically a prototype by that name and will inherit the methods, actions, macros and skins that the HopObject prototype provides." What are the methods, actions, macros and skins that the HopObject prototype provides?
21Worthy addition here maybe: point out that the HopObject tree is always assembled in code and that the directory structure of the prototypes has no bearing on URL resolution.
22What is meant by "the methods, actions, macros and skins that the HopObject prototype provides?"

Version 24 by philmaker on 21. November 2007, 22:36

5If a create a custom object which needs to extend HopObject new prototype directory - how does that all get wired? wired to root? Is it automatic? (yes?) Is it via type-properties? Only via type properties?

Version 23 by philmaker on 21. November 2007, 22:34

6In the included Note: The HopObject demo, would it be better to have the HopObject directory have some other name - to avoid confusion? Or is it necessary that it be named 'HopObject' for that demo? Is extends the HopObject dir making additions to the HopObject prototype?prototype.
7is mainMain.hac is always the default entry action for / ? Can this be altered via property files?action
8When do you have JS code in What happens if an actual JS file instead of in an hac action file? And why?and a child HopObject have the same name? Does the former action get priority/override the main action of the child HopObject?
9If each directory automatically becomes a HopObject, what are the drawbacks When do you have JS code in an actual JS file instead of creating a HopObject directly in code or - as an hac action file? And why? A: For shared code. Only put in the HopObject generation demo exampleactions what is local to that action.
10What is the purpose of the Global directory? What goes in there?

Version 22 by philmaker on 21. November 2007, 22:30

4Can each session have it's own Root object? Need more info on how session-based HopObjects workAnswer: each session has their own User object which is connected to root.
5Is session.data a HopObject? Can it be a HopObject? Why or why not?

Version 21 by philmaker on 21. November 2007, 05:07

19Key: Every token of a URL separated with a slash has a backing object: a HopObject

Version 20 by philmaker on 19. November 2007, 08:54

11What is the purpose of the Global directory? What goes in there?

Version 19 by philmaker on 19. November 2007, 08:19

25Does it jive with Helma 1.6 or just 2.0?0? Ah it does appear to be tagged with Helma 2.

Version 18 by philmaker on 19. November 2007, 08:18

25Does it jive with Helma 1.6 or just 2.0?

Version 17 by philmaker on 19. November 2007, 08:16

24This looks important: http://dev.helma.org/wiki/Config+in+Code/
25

Version 16 by philmaker on 19. November 2007, 08:08

5Is session.data a HopObject? Can it be a HopObject? Why or why not?

Version 15 by philmaker on 19. November 2007, 08:06

1Philip Weaver created this document on November 19, 2007. This is a private rough draft. It is intended to cover Helma 1.6. I intend to describe getting up and running with Helma very concisely and quickly and I will present many simple FACTSstatements of FACT. I intend to initially focus on using the internal XML database, explain how HopObjects work in relation to page requests and in relation to data persistence in the internal database, explain the workings of the properties files, explain conventions, etc. And more. If there are areas where the documentation is already obvious or sufficient or it is a non-core feature, I may link: such as skins, macros, etc.

Version 14 by philmaker on 19. November 2007, 08:06

9If each directory automatically becomes a HopObject, what are the drawbacks of creating a HopObject directly in code or - as in the HopObject generation demo example.

Version 13 by philmaker on 19. November 2007, 07:45

18"Every directory that you create inside your application's code repository becomes automatically a prototype by that name and will inherit the methods, actions, macros and skins that the HopObject prototype provides." What are the methods, actions, macros and skins that the HopObject prototype provides?
19Phil's note: so does this indeed mean that a HopObject directorty directory extends the basis basic HopObject prototype?

Version 12 by philmaker on 19. November 2007, 07:43

6In the included HopObject demo, would it be better to have the HopObject directory have some other name - to avoid confusion? Or is it necessary that it be named 'HopObject' for that demo? Is the HopObject dir extending making additions to the HopObject prototype?

Version 11 by philmaker on 19. November 2007, 07:42

20What if instead I wanted to extend HopObject in code? And why would I ever want to do that?

Version 10 by philmaker on 19. November 2007, 07:41

8When do you have JS code in an actual JS file instead of in an hac action file? And why?

Version 9 by philmaker on 19. November 2007, 06:18

6In the included HopObject demo, would it be better to have the HopObject directory have some other name - to avoid confusion? Or is it necessary that it be named 'HopObject' for that demo?demo? Is the HopObject dir extending the HopObject prototype?

Version 8 by philmaker on 19. November 2007, 06:17

7is main.hac always the default entry action for / ? Can this be altered via property files?

Version 7 by philmaker on 19. November 2007, 06:12

17Phil's note: so does this indeed mean that a HopObject directorty extends the basis HopObject prototype?

Version 6 by philmaker on 19. November 2007, 06:11

15Fact from http://helma.org/docs/guide/introductions/prototypes/
16"Every directory that you create inside your application's code repository becomes automatically a prototype by that name and will inherit the methods, actions, macros and skins that the HopObject prototype provides."
17

Version 5 by philmaker on 19. November 2007, 06:09

1Philip Weaver created this document on November 19, 2007. This is a private rough draft. It is intended to cover Helma 1.6. I intend to describe getting up and running with Helma very concisely and quicklyquickly and I will present many simple FACTS. I intend to initially focus on using the internal XML database, explain how HopObjects work in relation to page requests and in relation to data persistence in the internal database, explain the workings of the properties files, explain conventions, etc. And more. If there are areas where the documentation is already obvious or sufficient or it is a non-core feature, I may link: such as skins, macros, etc.

Version 4 by philmaker on 19. November 2007, 06:08

12I read this document: http://helma.org/docs/guide/introductions/hopobjects/
13and I'm sorry but it really tells me nothing. :-) We need more concrete verbiage about what in the heck are HopObjects.

Version 3 by philmaker on 19. November 2007, 05:47

1Philip Weaver created this document on November 19, 2007. This is a private rough draft. It is intended to cover Helma 1.6. I intend to describe getting up and running with Helma very concisely and quickly. I intend to initially focus on using the internal XML database, explain how HopObjects work in relation to page requests and in relation to data persistence in the internal database, explain the workings of the properties files, explain conventions, etc. And more. If there are areas where the documentation is already obvious or sufficient or it is a non-core feature, I may link: such as skins, macros, etc.

Version 2 by philmaker on 19. November 2007, 05:41

1Philip Weaver created this document on November 19, 2007. It is intended to cover Helma 1.6. I intend to describe getting up and running with Helma very concisely and quickly. I intend to initially focus on using the internal XML database, explain how HopObjects work in relation to page requests and in relation to data persistence in the internal database, explain the workings of the properties files, explain conventions, etc. And more. If there are areas where the documentation is already obvious or sufficient or it is a non-core feature, I may link: such as skins, macros, etc.
3Questions (I'm new to Helma so some of these may be misguided):
4Can each session have it's own Root object? Need more info on how session-based HopObjects work.
5If a create a custom object which needs to extend HopObject - how does that all get wired? Is it automatic? (yes?) Is it via type-properties? Only via type properties?
6In the included HopObject demo, would it be better to have the HopObject directory have some other name - to avoid confusion? Or is it necessary that it be named 'HopObject' for that demo?
7
8Point out:
9intro.applications maps to intro/applications and why? Will intro/applications also map to intro/applications?
10
11Notes: if you add a new HopObject to an already persisted HopObject, that new HopObject will persist automatically. However, it you update the values of a HopObject, you must call persist().
12
13Code snippets: in the code snippets area, we need more basic examples.
14
15Outline
161
172
183
19
20[Basic Scaffolding]

Version 1 by philmaker on 19. November 2007, 05:40