Activity
From 2008-11-06 to 2008-12-05
2008-12-05
-
22:35 Revision b86732ba: FLOW3:
- * the memcached cache backend can now use unix sockets
-
21:30 Feature #1882 (Resolved): Objects can be deleted
- Applied in changeset r1565.
-
21:28 Revision d06734dc: FLOW3, TYPO3CR:
- * Persistence: rewrote the way object trees are stored in the CR, fixes #1883, fixes #1882
TYPO3CR:
* Persistence: a...
2008-12-03
-
22:49 Task #2266 (Resolved): Update MVCFramework.xml [has patch]
- FLOW3:
* Adapted the MVC-documentation to the viewObjectNamePattern and added an example of the standard resolving o...
2008-12-02
-
10:52 Revision 199949ce: FLOW3:
- * some cleanup and changes to memcached cache backend, mostly by Dmitry Dulepov.
2008-11-29
-
09:28 Bug #2244 (Closed): Exception is not catchable. Exception is still shown after throwStatus
- If I excecute the following code in FLOW3 a F3::PHPCR::NodeType::NoSuchNodeTypeException is thrown:
@$taskManageme...
2008-11-27
-
20:23 Feature #2237 (Resolved): URLs can only be lowercase
- Hello,
I cannot use upper-cased URLs in case I want to.
I just had a route configuration like:
Mapping_CRUD_...
2008-11-24
-
10:59 Revision 372e8fb4: FLOW3:
- * object removal now works basically but leaves orphaned objects around, refs #1882
2008-11-21
-
18:44 Revision 9dc00052: FLOW3:
- * processRequest() in RESTController now matches the signature from ActionController, eliminating a PHP notice
* fixe... -
18:42 Feature #1882: Objects can be deleted
- I spent quite a few hours on this the last days. In the end I threw away about half of the code again, as it just did...
2008-11-12
-
14:50 Bug #2158 (Resolved): flushByTag() does not check tags for validity
- Applied in changeset r1501.
-
14:30 Bug #2158 (Resolved): flushByTag() does not check tags for validity
- Neither the File cache backend nor the Memcached backend check if the tag passed to flushByTag() is valid.
-
14:45 Revision 9e9ee081: * FLOW3: (Cache) Fixed a bug in the cache backends which accepted invalid tags in the flushByTag() method. Resolves #2158
-
14:03 Feature #1634 (Resolved): Allow omitting the @reference annotation for object properties
- Applied in changeset r1500.
-
12:56 Feature #1634 (Accepted): Allow omitting the @reference annotation for object properties
-
12:55 Feature #1634: Allow omitting the @reference annotation for object properties
- From the CR point of view: If the array is empty it's empty. No need to know the types of the stuff that might be in ...
-
13:53 Revision 8cebfc23: FLOW3, TYPO3CR:
- * the persistence framework no longer needs the @reference annotation, fixes #1620
TYPO3:
* removed @reference annot... -
12:55 Task #2156 (Resolved): Optimize autowiring in the Object Builder
- The whole autowiring process (constructor arguments and setter injection) currently happens while actually creating t...
-
12:08 Revision 9fc04893: * FLOW3: Refactored the bootstrap a bit
- * FLOW3: (Object) Fixed the Object Builder tests
-
10:28 Revision aef750e4: * FLOW3: (Object) Refactored the Object Manager and mostly rewrote all related unit tests. They now don't depend on the TestPackage anymore, are true unit tests and reach a code coverage close to 100%. Addresses #2123
- * FLOW3: (Object) Rename the "Object Cache" to "Object Registry"
2008-11-11
-
15:41 Task #2126 (Resolved): Implement sub routes support (routes should be configured globally in one place)
- Routes should be configured globally at one place to avoid complexity and make it possible to disable/change existing...
-
14:04 Task #2123 (Resolved): Refactor (Object) Framework unit tests
- Currently most of the Object Framework's tests are rather functional tests than unit tests. Even worse, most of them ...
-
13:06 Revision e5910a40: * FLOW3: (Error) Renamed the FLOW3 setting names for exceptionHandler + errorHandler: they no reside in a common section "error" which reflects both being in the "error" component / sub package
-
12:22 Task #1891 (Accepted): Adjust license to LGPL
-
12:22 Feature #1882 (Accepted): Objects can be deleted
-
12:20 Task #2119 (Resolved): Rename "component" to "object"
- Applied in changeset r1481.
-
10:46 Task #2119 (Resolved): Rename "component" to "object"
- Although the whole concept of componentry still applies to FLOW3, the name "component manager" etc. is rather confusi...
-
12:17 Task #474 (Rejected): Refactor the MVC controller class names
- The class names should
* speak for themselves if possible
* with namespaces classnames like @Default@ would stem fr... -
12:16 Revision 1409a9f7: * FLOW3: (Component) Renamed "component" to "object" - everywhere. That means we now have an Object Manager instead of a Component Manager, an Object Factory etc. Resolves #2119
- Globally adjusted all code for the above change.
-
12:07 Bug #513 (Resolved): Resource manager does not handle links in public files correct
- This no longer occurs.
-
12:00 Bug #2115 (Resolved): Base href is not correct when calling index_dev.php
- Applied in changeset r1480.
-
11:58 Bug #2115: Base href is not correct when calling index_dev.php
- Better solution: never ever prefix URIs starting with a hash.
-
11:27 Bug #2115 (Accepted): Base href is not correct when calling index_dev.php
- This is caused by interaction between relative link prefixing in the resource manager and marker replacement later on...
-
07:34 Bug #2115 (Resolved): Base href is not correct when calling index_dev.php
- The base href looks like:
Resources/Web/FLOW3/Public/MVC/http://192.168.149.129/
But it should be:
http://19... -
11:57 Revision b199be67: FLOW3:
- * changed the resource processing to not prefix URIs starting with a hash, fixes #2115
-
09:53 Task #2118 (Resolved): Decouple MVC and Security
- Remove dependencies between MVC and Security Framework (in Dispatcher)
-
09:52 Task #2117 (Resolved): Clean up bootstrap
- The subpackages of FLOW3 are initialized in the bootstrap. Currently this whole process is hardcoded in the FLOW3 cla...
2008-11-10
-
23:15 Revision 312420f0: FLOW3:
- * put the component factory back in
-
23:03 Revision 95de5458: FLOW3:
- * view helpers were created with ComponentFactory->create(), but are singletons; using getComponent() now
-
22:29 Revision dc613a76: TYPO3CR:
- * refactored the way internal instances are handed around, avoiding injection in a few places (fixes the recent "inva...
-
19:00 Revision a3c4d466: * FLOW3: (MVC) Added F3::FLOW3::Utility::GenericCollection - a "type-safe" collection which implements the SPL interfaces ::Countable, ::Iterator and ::ArrayAccess. You can create an instance of a type-safe by passing the complete class name of allowed objects to the constructor or by inheriting from this class and calling parent::__construct.
- * FLOW3: (MVC) Big refactoring in routing classes: $uriPatternSegments and $uriPatternQueryParameters are no arrays a...
-
19:00 Revision 683f7156: * FLOW3: (AOP) Renamed the setting "aop: proxyCache" to "aop: cache"
-
17:58 Feature #2110 (Resolved): Add support for custom factories
- The Object Framework should support custom factories which are used whenever a object of a certain type needs to be i...
-
17:48 Feature #2109 (Resolved): Support constructor / factory arguments in Objects injection configuration
- Currently it is not possible to pass (constructor) arguments or properties (for setter injection) to the object which...
-
17:44 Task #672 (Accepted): Finish documentation about configuration in FLOW3
- Partly solved in r1463.
-
17:41 Feature #1847 (Resolved): ComponentFactory->create() throws an exception on trying to create a component of singleton scope
- Resolved in r1422.
-
17:39 Feature #1848 (Closed): ComponentManager->getComponent() throws an exception on trying to retrieve a component of prototype scope
- After experimenting with it, I realized that the Component Manager must still be able to return also prototypes, beca...
-
17:18 Revision 63a49d75: FLOW3:
- * configuration now handles every "real" error as exceptional, changed some empty arrays from [] to {}
* defaults in ... -
13:21 Revision 83c34999: * FLOW3: (Documentation) Updated the manual to reflect the new configuration format (YAML)
-
12:28 Revision bbd29442: * Fixed FLOW3's yaml configuration: exceptional errors were defined as plain strings instead of constants resulting in even (catchable) fatal errors being ignored
- * Fixed several tests which still used the object configuration instead of arrays
2008-11-08
-
10:24 Feature #1991 (Resolved): AbstractView should have access to request in initialaizeView()
- Hello,
I think it would make sense if the AbstractView had access to the $this->request in the $this->initializeVi...
2008-11-07
-
17:06 Revision 05ecfc36: * FLOW3: Fixed a few tests which only failed when run from the CLI
-
16:25 Revision d8c9f74b: * FLOW3: (Security) Fixed the configuration usage in the Security Context class
-
16:05 Feature #1852 (Resolved): Add YAML configuration source
- Applied in changeset r1448.
-
16:02 Revision 3637985f: COMMIT PART 1
- * FLOW3: Implemented a YAML configuration source, resolves #1852
* Globally refactored code and converted configurati...
2008-11-06
-
21:15 Revision 62f9e0a0: FLOW3:
- * refactored cache frontend and backend API: save() is now set(), load() is now get(), findByTag() is now loadByTag()...
Also available in: Atom