In response to - http://issues.apache.org/jira/browse/GERONIMO-1900?page=comments#action_12377441
I've taken a first shot at making this a single-click install. Please apply the attached patch (from the geronimo dir) and let me know if this is something we should do. If so, then I'll proceed with making this 'production-quality'. NOTE: I am unable to attach the images to this mail b'coz gmail thinks it's a spam. You may either get it from the console or don't worry to much abt it. The prototype - 1) has the geronimoplugins.com repo hardcoded. 2) has not been tested for a repo on a running server with optional user/pass 3) could use a timer/progress indicator if the sample install were to take a long time. Cheers Prasad On 5/2/06, Dave Colasurdo (JIRA) <[email protected]> wrote:
[
http://issues.apache.org/jira/browse/GERONIMO-1900?page=comments#action_12377441
]
Dave Colasurdo commented on GERONIMO-1900:
------------------------------------------
I still have a general uneasy feeling about this overall approach for the
default examples.
Prasad has done a good job given the current
requirements/assumptions/restrictions of this JIRA. However, I question the
assumptions.
The flow is currently:
1) User hits the welcome page and selects "servlets-examples"
2) The "would you like to install examples" page is presented
3) User selects "yes" and is brought to the admin console logon page
4) After logging on, the plugins page is displayed
5) User selects the plugin server and chooses "search"
6) User is presented with list of plugins (apachds, various examples,
ldap-realm)
7) User selects "servlets-examples" for the appropriate web container
8) Servlets-examples is magically installed along with any dependencies
9) User is presented with panel to "start servlets-examples"
10) User selects "start" and is returned to the plugins menu
The major problems I have with this approach is:
a) The user that is trying to run a few simple examples is tossed into the
middle of the admin console.
b) First time users should be gently introduced to the console via the front
welcome page
c) Users will be exposed to many other plugins (the list is growing) that are
useful but not particulary pertinent to the task of installing examples
c) The user is left stranded in the plugins page of the admin console without
any path back to the original thing they wanted to do (i.e. run the samples)..
They either have to retype the original url or hit the back button several
times..
Any chance of either pre-installing the samples (like G1.0) or installing the
samples with one click (perhaps cmdline plugin under the covers) and
automatically redirecting the user to the samples with minimal user
intervention?
Are we trying to showcase the plugin technology user interface or are we trying
to provide a mechanism to quickly let the user run the samples?
Perhaps there should be a separate "plugins" link from the welcome page to
showcase the plugin technology.
Thanks
-Dave-
> Sample app links on welcome app are broken by default
> -----------------------------------------------------
>
> Key: GERONIMO-1900
> URL: http://issues.apache.org/jira/browse/GERONIMO-1900
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: usability, sample apps
> Versions: 1.1
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: welcome-2.patch, welcome-3.patch, welcome.patch
>
> It would be nice to take users to a page that would prompt them to install
the sample if they click a link to it and it's not present. However, automating
this would require us to be able to construct a link into a portlet, which does
not seem easy.
> For now, the welcome app can include pages at the locations where the sample
apps will be bound, with text to the effect of:
> This sample has not yet been installed. To install it, visit the
(URL)console(/URL) and select the Plugins page, click the Search for Plugins
button, and select the (NAME HERE) sample to install. Then visit this same URL
again to view the (NAME HERE) example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
welcome-5.patch
Description: Binary data
