You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AribaWeb (aribaweb.org)
Hi all
i just compteted the tutorials and played quit a bit with the
framework,but i have some questions;
first: Deployment;-
how can i deploy the resulting application, what files to include?
what configuration to tweek? how to disable the MetaUi live edit on
deployed instance(i donot want my users to alter the app) ?
second : basic customization:-
where to put the css for customizing the look and feel of the app?
how it is structred? is the DOM structure of the element widgets
standerdised or i have to re-edit the css on every release(major or
minor?)?, where is the master page which all pages inherit, obviously
i need to include my app logo instead of aribaweb logo, so how i can
do that?
can i generate the awl files(that is dynamically generated at runtime)
for the pages to see it and edit it
third : code, i wanna customize the data manipulation code and wanna
know how the control flow, i wanna see the generated code that drive
my app,
fourth: documentation:-
at least i need an overview document which describe in more
details each subsystem and state is classes , and how to interact with
them, and how to customize the basic behaviuor
another point, while the MetaUI edit is great and super
productive, i really cannot imagine that i am going to build a real
app on something i donot fully understand its guts, and cannot
reproduce everything using only VI editor, so please can u state how
can i edit the oss file, where is its reference
so customization..... customization..... customization..... how to
customize every aspect of the framework is indeed a requirement
i really like the framework and i can see its value, i think it is one
of the best things ever happened to java development , i really think
of implementing apps on it , but really i need ENOUGH documentation
(in the sense of a profesional architect)
thanks a lot for ur patience
and thanx for the great gift u gave to the community
Joe
Kingsley
unread,
Feb 27, 2009, 2:24:30 AM2/27/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AribaWeb (aribaweb.org)
Hi Joe,
We'll get you more detail answers in a more official documentation.
Here are some short answers for now:
1) Basically everything under these directories needs to be included
MyApp/build/tomcat-bases/MyApp/conf
MyApp/build/tomcat-bases/MyApp/webapps
Turning off Live Edit and other debug features is discussed here:
2) "application.css" and "cmdbar_prod.gif" for the logo will be
picked up and included on every html page rendered.
Firebug on Firefox can be used to inspect the styles that needs to
overriden.
There is no generated AWL. You can hand edit or use Live Edit to
modify "rules.oss" to tweak layout or reference your component. See
this post by more detail:
Our upcoming docs should better answer your questions.
Thanks,
Kingsley
Craig Federighi
unread,
Feb 27, 2009, 9:33:06 AM2/27/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to arib...@googlegroups.com
Just to clarify on point 1:
how can i deploy the resulting application, what files to include?
what configuration to tweek? how to disable the MetaUi live edit on
deployed instance(i donot want my users to alter the app) ?
You can run the ant target "ant war". It will produce a properly packaged .war file that you can deploy in your app server of choice -- just deploy it according the their instructions.
When you deploy a war directly this way (i.e. as opposed to launching tomcat through our build system) it will deploy with development tools off automatically (i.e. the MetaUI Live Edit and AW Options popups will not be present, etc).
So: 1) `ant war`, 2) deploy war normally, 3) there is no number 3 -- you're ready! ;-)