marten wrote:I think, that there should be a product oriented documentation telling the user how to package a Seaside application and how the framework is in general setup in a correct way during runtime (in a packaged image or ic based image).
Is there anything available ????????
marten wrote:When packaging Seaside apps all the #defined methods are mentioned - they belong to applications, which are not defined in the prerequisites. How should they be handled when packaging (using client packaging or server packaging) !?
koschate wrote:If there are applications needed by Seaside that aren't properly pre-reqed by Seaside-related apps, I'd make those applications be prerequisites of whatever application is holding onto your launch code. You could also just force them to be included using packaging rules, but I don't care for that myself - should applications be removed down the road, you won't know until you actually try to package.
marten wrote:I think, that there should be a product oriented documentation telling the user how to package a Seaside application
wembley wrote:The reason that the defined class instance variable is referenced directly is exactly so as not to need the prereq.
wembley wrote:Marten - In the big picture, it makes no difference.
Users browsing this forum: No registered users and 1 guest